This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap in repository toolchain/ci/base-artifacts.
discards 22b11c8e6 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits discards 17230b9af 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits discards fc723ebd2 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits discards 0da65ecc7 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards d003c4eff 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards cd2fdc90c 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards 6fd4e5d93 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards 79dd2176e 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards df5a81719 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards b3a0e0eb3 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards f12cfb182 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 8e9f81990 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards e51914175 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards c3450b73c 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-292 [...] discards 247bf5fe6 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 345c85ed3 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards d587544d2 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 2d69bdee5 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 09ffe0249 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g8 [...] discards 454d36de6 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 35471273e 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards e65c93ac5 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards c1a562f90 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 46cc46e40 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 7b72e4cce 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 6853aeaab 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 4a39755e8 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-283 [...] discards 97b198803 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards f6ff83425 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-283 [...] discards 3d574ce45 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-20 [...] discards 29da3a6b1 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 9f67dbd66 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 0e45d967b 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards fe94950d1 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards dca7b4634 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 07451cdca 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards eeaa7d5e4 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards d9f59c382 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 4628b6c3f 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 947589be9 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards e60104e45 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards aad77732c 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 7f8a966a5 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards e75f8687f 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 19f39a905 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 309a26be3 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards f3c8f1507 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 1d806b567 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards c1454feab 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 34e8e375d 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 8ac56721e 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards a71881fa3 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards dfd67ecca 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 01cf4f7ba 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 8841ba178 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 02147de5a 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 626c72826 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards e7c3ea92f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards be280762a 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 5d11342ca 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards af9f972d9 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 9cc667a70 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 6b4fe9eaf 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 672a654ad 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards a92c25328 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 67a468cc3 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 5ab19a073 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards bb1468045 88: onsuccess: 1: Success after gcc: 20 commits discards b1ecd35df 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 0d4352ec6 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards d77400479 85: onsuccess: 2: Success after binutils: 4 commits discards fa38cca73 84: onsuccess: 2: Success after gcc: 9 commits discards 0c9773cd8 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards c421cff2b 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 73aa3c4f3 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards a69b9c9f9 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 075d40893 79: onsuccess: 1: Successful build after gcc: 3 commits discards 25161b783 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards aa4fe7e4f 77: force: 2: Successful build after gcc: 32 commits discards b24e3077a 76: onsuccess: 2: Successful build after binutils: 10 commits discards 5de7dfe93 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f26458c51 74: onsuccess: 2: Successful build after gcc: 13 commits discards 2129f3ef0 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards c2d204422 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 430279652 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4dceb06e2 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b3656ac48 69: onsuccess: 2: Successful build after baseline build: no n [...] discards b899ab7e9 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 556df20d5 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f9cd98eec 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards ca9bc11b5 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 004b37670 64: onsuccess: 2: Successful build after gcc: 7 commits discards 615fe50c9 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 91fd0175e 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b34723e8e 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 7b0878f99 60: onsuccess: 1: Successful build after gcc: 15 commits discards 693d4b816 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards ab5cf88ef 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards 9aa137682 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards f41574a4d 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 40d358c4e 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1df887d85 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f103ec288 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 34b836b43 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 0f1337ced 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new 6ffe8a732 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 7e54dda58 60: onsuccess: 1: Successful build after gcc: 15 commits new 69e36aa13 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 203725763 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 07aa17c63 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1aa884d67 64: onsuccess: 2: Successful build after gcc: 7 commits new ad2fa447d 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a376725ae 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new e117f8109 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2ebbe6e84 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a4a8e14a2 69: onsuccess: 2: Successful build after baseline build: no n [...] new 4c4ca49e3 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new f4cef4f41 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3ba1cca41 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 9fa27d3b8 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new bebdcc175 74: onsuccess: 2: Successful build after gcc: 13 commits new bc7e1483c 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 3c8c524e4 76: onsuccess: 2: Successful build after binutils: 10 commits new 793478953 77: force: 2: Successful build after gcc: 32 commits new 7a264149d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 801e7b0ea 79: onsuccess: 1: Successful build after gcc: 3 commits new 980ecf0a1 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 3e1a3416c 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 3996d2baa 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 3d0f269bf 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 37af5167e 84: onsuccess: 2: Success after gcc: 9 commits new 095fd49f0 85: onsuccess: 2: Success after binutils: 4 commits new d545ffaf2 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 91bdd27cc 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 1693f6b62 88: onsuccess: 1: Success after gcc: 20 commits new d8b82c983 89: onsuccess: 2: Success after binutils/gcc: 39 commits new a18773fd6 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 242c8e60b 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 244c8c319 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 0a228d838 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new fc70fdda5 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 3933dd4eb 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 540cad5fd 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 40c8ed80b 97: onsuccess: #1481: 2: Success after gcc: 8 commits new a5e3b9d9e 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 818f8cdd2 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 82b5c863d 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new c6f7cc5bf 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new f876a1b75 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new ccf99a189 103: onsuccess: #1524: 2: Success after gcc: 2 commits new c125bb168 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 17c8f564c 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 4c3f4da38 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 1c4f9c47b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 75c2243cd 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 2c2a5c3f5 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new b8d0715ad 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d31a436b9 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 5427c205f 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 2e3177cd5 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new d11979c18 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new b23835394 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 0ab9b414d 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 023dd5995 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f9553d9f9 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 8ba22f6d9 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new eed16b55c 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new e95f6b8e2 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 2c88ff6db 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 925ed3b7c 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 32b32b5e7 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 27c25668b 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 5028d6c4d 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-20 [...] new 00c66ba9a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-283 [...] new 53830d380 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new e84a64246 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-283 [...] new 998573932 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 5a4d008e7 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 959f55c93 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new db71d0e46 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 3188d3254 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 3c48bacbc 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 530ee89d1 136: onsuccess: #1561: 2: Success after binutils: 3 commits new b956fd509 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g8 [...] new 474c950d1 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-gb [...] new f14ce9014 139: onsuccess: #1566: 1: Success after gcc: 5 commits new e08a76399 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 5d3081649 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 40a66d6a0 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-292 [...] new a6a5c601d 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new 9a44fa2c5 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new ba3a324c3 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 133762c37 146: onsuccess: #1573: 2: Success after binutils: 7 commits new f9c6823e5 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new a60ef20c1 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 19874b6a1 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 3632171a1 150: onsuccess: #1577: 2: Success after gcc: 3 commits new ed86f5255 151: onsuccess: #1578: 2: Success after gcc: 2 commits new 4612c44ef 152: onsuccess: #1579: 2: Success after gcc: 2 commits new 4ff574147 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 commits new 41b2efd5d 154: onsuccess: #1581: 2: Success after binutils/gcc: 11 commits new 34bf312fa 155: onsuccess: #1582: 2: Success after binutils/gcc: 15 commits new a5064c949 156: onsuccess: #1583: 2: Success after binutils/gcc: 2 commits
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 (22b11c8e6) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]
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 1704 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 37672 -> 38040 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269692 -> 273804 bytes 06-check_regression/console.log.xz | Bin 2880 -> 2544 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++-------- 13 files changed, 35 insertions(+), 35 deletions(-)