This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 225a878581 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 80da1edbf8 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards f721d4589c 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 619266d837 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards f57f6e4ba3 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 2694b60104 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 33db9b8662 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 89d0b07652 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards a787ecc3b6 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards c53af1cff9 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 9d86e74533 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 8f91d32148 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 154f79a91b 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 7f22da529e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards a23300e194 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 8b80b585d3 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 723bbfa91c 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards e2ca10a67c 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards d4a6355848 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards e6c76975b6 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 96290f83a4 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards b5367e6a15 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 1c326f2c4a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 6a80ba9151 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 07d6503ae5 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards df54482cea 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards e2d4963647 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards e9460e4a38 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards d771789414 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards c7b46f8f80 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 5c63a13f0f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 74ae5a7b03 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards ce51c31dda 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 7a17ac0536 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 50a9f5c0fb 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 41c0301827 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 283f323f6e 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 25c0cc0ffd 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards daeb17442a 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards e3c9b76afb 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards fb8d1773cc 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 36dc374d65 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards f5d97171dc 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 904d9b419d 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 1598495f23 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 17b2eba8a8 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 7e380ef60f 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 7d3eaa41f2 102: force: #1551: 1: Failure after gcc: 306 commits discards 687894bf0c 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 7592b08b02 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 00383f5333 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 37b2f60dd2 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 04ccff08d6 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 6fc3facb8f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 40a05b5073 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6f4c68e528 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards f85b9c8514 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a2ea1236d6 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards b5c6a51de3 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 9ec145d09a 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 9773caa7c4 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 315c272596 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 743d4acabc 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 2f40010745 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 0549c42662 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards fb3525eb9c 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 6d71b70cb1 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cbf062ed08 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 85529a4cb9 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 333a7abb9e 80: onsuccess: 7: Successful build after linux: 44 commits discards f98d714770 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c630148cfd 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards d3c4c75fd6 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 446b072115 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 0d6b57e3c6 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 66e4a4fc93 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ce5607d6f2 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7df2a78c9c 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 130566037a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2c949ccb50 70: onsuccess: 7: Successful build after gcc: 4 commits discards 3e0de6c593 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 94c868f14e 68: onsuccess: 7: Successful build after linux: 6 commits discards 7d7a2593e8 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 957c3233d0 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 504dd2b02f 65: onsuccess: 7: Successful build after binutils: 3 commits discards b9d4e7b7bb 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1e65a73396 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards ef360ae470 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 4ba9d5fa44 61: onsuccess: 4: Successful build after gcc: 5 commits discards 534d944432 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards f1a8c82151 59: force: 7: Successful build after gcc: 3 commits discards e9066dd907 58: onsuccess: 7: Successful build after glibc: 2 commits discards b4de426809 57: onsuccess: 7: Successful build after gcc: 7 commits discards cf1be0130e 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9fec548da7 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0a12db3fb2 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards a6f9a331a3 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards c1de2774f7 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 53efb95d2b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 10d6f26a90 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1d7d382c48 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 87bf64b6e7 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 39bba0e279 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 123b90c766 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a79b17200a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new b21ae178c0 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 824ce943c3 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new e3bc225115 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 2278b88f0f 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 17c279db1e 57: onsuccess: 7: Successful build after gcc: 7 commits new 7aa5a5cf2d 58: onsuccess: 7: Successful build after glibc: 2 commits new d3b0621f15 59: force: 7: Successful build after gcc: 3 commits new 5a32f5167e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 6492a3a9b9 61: onsuccess: 4: Successful build after gcc: 5 commits new 37abe245d4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 1fc5772a04 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f3cef8d6ab 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 2138e19228 65: onsuccess: 7: Successful build after binutils: 3 commits new a35f01138e 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 56310234dc 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 891348c50a 68: onsuccess: 7: Successful build after linux: 6 commits new a85864339f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 52273cdc86 70: onsuccess: 7: Successful build after gcc: 4 commits new b0fe21063d 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new cca67bfb27 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 597d6e267f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5cf0f6be3 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 69d1fbeaeb 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 8be3a73027 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new ebb7d1d870 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6f4cd10498 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 8f28027165 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 759e63b4f4 80: onsuccess: 7: Successful build after linux: 44 commits new 4db26b6cac 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new da58c21c6a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 86abc121ca 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5288c73379 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 72050842db 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 316bde4182 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new f0463e5422 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 25c9b14dd5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 1188a5032f 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 10faab4f4e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new e1527ec993 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 55c7430a45 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 66a66dd7b1 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 175392d033 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 47215ee23c 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9b9c8c488f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 58f75eaf48 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 9d53b1f4c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new cfa4ed2f1e 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 2ed851d00b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new a7b484a5e3 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 6eb14d96f2 102: force: #1551: 1: Failure after gcc: 306 commits new e10ad07e67 103: onsuccess: #1552: 1: Success after gcc: 5 commits new fe1872db29 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 6626fd9ab5 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 087c145baf 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new c220db1c74 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 4338f78beb 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new abd2fe3b78 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 4a29ea1fe5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 34abed9c36 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 4f25974fc3 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 7a1434469a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 4eaa9f63c4 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 4d0a802fe0 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 66ee97dee1 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 90e8cebb1b 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new b935c1eb89 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new f1f3493ee2 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 6f275adfd2 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new aa8c73a2ab 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 42b6482aa3 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new eb77b36443 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 750c588471 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 6cf0b5a4aa 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 31eda81b71 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 9eb5dd02b9 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 93623b2000 128: onsuccess: #1579: 7: Success after linux: 12 commits new f4175f2140 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 875a917acb 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new fb5865ce69 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 2a15581337 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 78f8fcaa9a 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 6ec201adbb 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 729a91c88b 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new c4ecc7d5a3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new e04a6fe2a0 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 4115fadad1 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 46f0eba61d 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 504d71d5df 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new dbfd26ee42 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new c0491206dc 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 6b914a2ac4 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 9ff41cbf60 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 9c3f5c6c46 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new aad7879eb3 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 5c28a506e6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 76123cfe37 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new b4a9416e62 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new e19dc3d295 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (225a878581) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1716 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30200 -> 30388 bytes 05-build_abe-stage1/console.log.xz | Bin 72740 -> 72780 bytes 07-build_abe-linux/console.log.xz | Bin 8460 -> 8656 bytes 08-build_abe-glibc/console.log.xz | Bin 239864 -> 239916 bytes 09-build_abe-stage2/console.log.xz | Bin 203060 -> 203196 bytes 10-build_abe-gdb/console.log.xz | Bin 37396 -> 37712 bytes 11-build_abe-qemu/console.log.xz | Bin 32160 -> 32012 bytes 12-check_regression/console.log.xz | Bin 3976 -> 4492 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 ++++++++++++------------ 21 files changed, 61 insertions(+), 61 deletions(-)