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 67ab8fd787 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 41fb894d13 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 2162f752e9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards dd8974de0b 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 893b81c7ff 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 43e7f01c23 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards c04b8363a5 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 3a3afcab6e 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d6b5d66ae2 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 59f04a673f 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 6d7c57dfa6 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards e801290bd9 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 2b5bba3c75 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 6098220ead 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 190d99ca22 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards d0d9a13ca5 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 081bd79ee9 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 7baecdf346 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 034b51508d 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 527b8bfa9e 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 4bf4a5db38 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards a7c98ccea9 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards a1315d1bc4 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 0d3de5cc4f 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 5f576fb802 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 6450cc8187 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards f2bc968ba6 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards b815f7f951 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards ac5a7073ae 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 9f10f6a60a 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 3b6e02ff23 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 9b72c932c1 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 2db56f1d74 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 93cbe76211 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards a25fe33f9b 88: onsuccess: 1: Success after gcc: 20 commits discards 39d27dfb3d 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 8285bd1bb3 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 9c51a46a0f 85: onsuccess: 2: Success after binutils: 4 commits discards ac36f5b5a5 84: onsuccess: 2: Success after gcc: 9 commits discards a5a03b4dcc 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 7108effabd 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards f746842b43 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards c1c0322e48 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 5f888bef32 79: onsuccess: 1: Successful build after gcc: 3 commits discards e5acbd0e2d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards e2410ccacc 77: force: 2: Successful build after gcc: 32 commits discards bd421466d8 76: onsuccess: 2: Successful build after binutils: 10 commits discards 8e0525a229 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ecbffb2550 74: onsuccess: 2: Successful build after gcc: 13 commits discards 9c56908791 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 43df6b9207 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 0f04607f1e 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7ad023d37d 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 9ea677a3f4 69: onsuccess: 2: Successful build after baseline build: no [...] discards 2438817e44 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e3be527595 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 20360c356e 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards b6a3ab8d37 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 93381ebab6 64: onsuccess: 2: Successful build after gcc: 7 commits discards 58d988d91f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9bf36a5f29 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 60e778f187 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards e172930347 60: onsuccess: 1: Successful build after gcc: 15 commits discards 6167c727d6 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards d495ab056c 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 77fe35047d 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 04b26f0f7b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 23066c9da4 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7f91eb55eb 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2c4bc77d88 53: onsuccess: 2: Successful build after gcc: 5 commits discards 50f4e186cc 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards dba43c3243 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards bd0e3bf484 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards f7fd24435d 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards d189e63711 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a71cfb7e6e 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5d01cec363 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards dba31544ee 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards f74cb85d26 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 53c21f849e 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 878a350986 42: onsuccess: 2: Successful build after gcc: 2 commits discards 86657901b0 41: onsuccess: 2: Successful build after baseline build: no [...] discards c8dd0ec39c 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 49ce0ba78c 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c1d9e354d3 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 532a8e4839 37: onsuccess: 2: Successful build after gcc: 2 commits discards 4421f31394 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards b7df55c6bc 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 92d1b83ca1 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards eed8b760e2 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4550eefe7b 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 60c455035b 31: onsuccess: 2: Successful build after gcc: 8 commits discards b9bd189333 30: onsuccess: 2: Successful build after gcc: 7 commits discards 8769bf5d86 29: onsuccess: 2: Successful build after binutils: 5 commits discards ca130caa8f 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7b51d63959 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 2317a5daa1 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 1119aa32d6 25: onsuccess: binutils-gcc: 2 discards bc6fa476c4 24: onsuccess: binutils-gcc: 2 discards a228228256 23: onsuccess: binutils-gcc: 2 discards d0b018910a 22: onsuccess: binutils-gcc: 2 new 814a6a6302 22: onsuccess: binutils-gcc: 2 new 2c5948d602 23: onsuccess: binutils-gcc: 2 new ffbd3c7c22 24: onsuccess: binutils-gcc: 2 new 6a958f4e0d 25: onsuccess: binutils-gcc: 2 new 23c23c9de6 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 971d13a256 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new a967c97941 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 48555f2ba7 29: onsuccess: 2: Successful build after binutils: 5 commits new 2eab43c469 30: onsuccess: 2: Successful build after gcc: 7 commits new 3ff5e53fb6 31: onsuccess: 2: Successful build after gcc: 8 commits new 7276031ff3 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 2decbdd3d2 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4f66bffcdd 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new ddc7ba6a56 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new e9f54bdd16 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 81bb236186 37: onsuccess: 2: Successful build after gcc: 2 commits new 8059ec2c72 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8dfc2a38a2 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f80b169fd2 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 8497b4876a 41: onsuccess: 2: Successful build after baseline build: no [...] new 3add4198b8 42: onsuccess: 2: Successful build after gcc: 2 commits new a05fbc628d 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 8031a73248 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2bc14fc52e 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 980cc8bb60 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 172e394787 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 71e0049924 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 3ec1a47bed 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 63e65f76da 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new ba6a6d0c03 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new c6786402f1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 42556d8302 53: onsuccess: 2: Successful build after gcc: 5 commits new 98f181c34b 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 711a2c42b5 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6b959d5d06 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new fb750fe8a2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 454b2dbf1a 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 5a239165ba 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 69b716b77a 60: onsuccess: 1: Successful build after gcc: 15 commits new 17ac042400 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 5690ba66c3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ecf17bbaf8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8fa3830244 64: onsuccess: 2: Successful build after gcc: 7 commits new 63787b7d81 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 933c9fbbdc 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 2669af3dea 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 12b6613f0f 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7690df4f57 69: onsuccess: 2: Successful build after baseline build: no [...] new 9a57eecad2 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 8753e714dc 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 92e4fbf692 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new a20557fb58 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new d01d0ac5e2 74: onsuccess: 2: Successful build after gcc: 13 commits new 132aa0754a 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new ac09a829d4 76: onsuccess: 2: Successful build after binutils: 10 commits new b46db30d50 77: force: 2: Successful build after gcc: 32 commits new f95fe45a0e 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new a49cb1e9c9 79: onsuccess: 1: Successful build after gcc: 3 commits new 24b026d4bb 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 865925a175 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 847145ba80 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 75d5f86c0e 83: onsuccess: 2: Success after binutils/gcc: 7 commits new d3df4f6768 84: onsuccess: 2: Success after gcc: 9 commits new e4d227e1ad 85: onsuccess: 2: Success after binutils: 4 commits new 846b598e95 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new b1dfe21ea9 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new eeb5e24d52 88: onsuccess: 1: Success after gcc: 20 commits new 3d969bdc4b 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 78ec8abd56 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 30c35dd1b2 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 98e141d0f2 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 5f4daa00a8 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 0c7eb743f3 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new a5f19ab632 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 21ce602eca 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 0103b7bbc4 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 522a07e84b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new b3f8b5b6c3 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new d81cfeae7b 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 641023737f 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new d7bb2e8f6f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 8e6d35689f 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 102d141a60 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 5be84da731 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 3b77e4eadc 106: onsuccess: #1527: 2: Success after gcc: 2 commits new f103e021f4 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 370ac09a0b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 0f374bb893 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 54ba9f1eda 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 5dd7471f69 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 86f8845a9d 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 4d1bbf88c9 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 94f1636da0 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 27fc04366d 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new a74c212311 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 8ff9d54137 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 780a497e45 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 7058814eab 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new ae92426f61 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new f8334be1bf 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 12807888d6 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 750ce81709 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 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 (67ab8fd787) \ 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 1832 -> 1832 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 37596 -> 37476 bytes 05-build_abe-bootstrap/console.log.xz | Bin 269020 -> 269180 bytes 06-check_regression/console.log.xz | Bin 3072 -> 2872 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- 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, 47 insertions(+), 47 deletions(-)