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-arm-bootstrap in repository toolchain/ci/base-artifacts.
discards 32034cf392 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 14571c5e8c 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 5787cc554b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards d1f36e68de 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 476a5485f7 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 49290b86b5 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 6b7f2ef712 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 66a1bbcd21 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 60064d8114 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 0a5d3ad685 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards f9566efcd3 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 356c4162c8 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards d2cdf5f188 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 532beae932 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards c5b28ae5ee 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards deb5b0021f 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 8163f59249 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 18f0977502 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 327b323f20 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards d28d1dc132 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 025cd2c625 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 88ed3105c3 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards ad7c71f0cc 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards f6ab21619f 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards dbd165d9b3 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 952c8d824f 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 1945ee6213 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 146908e5d2 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 871ea0efb6 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards b4997d97ae 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 95891a6a74 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards e6a075c433 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 02d2ba141b 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 815b4bbba8 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 780510f9f7 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards e7930001e0 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards a1d093644f 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards f26df0cb11 87: onsuccess: 2: Success after gcc: 4 commits discards 6e48211037 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 088070e65a 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards ceba3d3ab0 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 1c7b6d30bc 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards f6452dc2ab 82: onsuccess: 1: Successful build after gcc: 3 commits discards 7cf1d91d4b 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 13a5cee1e1 80: force: 2: Successful build after gcc: 14 commits discards c6bebc9190 79: onsuccess: 2: Successful build after binutils: 5 commits discards 4858362019 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 1a90f3bd04 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0b2698a7b7 76: onsuccess: 2: Successful build after gcc: 12 commits discards 50969ff51f 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 560e1d73a7 74: onsuccess: 2: Successful build after baseline build: no [...] discards 68be4eacba 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 2d4b0b347e 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 090790188d 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 5e73a1cd78 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d8c292edb6 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5a1e8d992b 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 7c79e33d68 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 1c696dfd23 66: onsuccess: 2: Successful build after gcc: 9 commits discards dcd293c382 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 01d883e42b 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c65cc3479b 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 31b5c25826 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards a8fd4ccf66 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards bf3774f3a4 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 01cd5b90df 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 08b0f94b4e 58: force: 2: Successful build after gcc: 6 commits discards 25af4d6074 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 9c110ddca5 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards a23570a4fa 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0121da0416 54: onsuccess: 2: Successful build after gcc: 5 commits discards 5f32f878ad 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 9da88c70c5 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 46cf161ce3 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards b6ea7c093c 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6ee35f7758 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 9de61a2704 48: onsuccess: 2: Successful build after gcc: 4 commits discards 1bacc04131 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 8ed05e8004 46: onsuccess: 2: Successful build after baseline build: no [...] discards 5b4ba9fc8a 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards cb184bb088 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5d4e2ce875 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards f17f06444c 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 2bffea3e70 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards c4544bb0b0 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards a0cb1e416f 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 4a1b10335b 38: onsuccess: 2: Successful build after gcc: 2 commits discards ea30dcd66f 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f7edf42050 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards f52e49c92b 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 6cdcebe6ec 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e31d30dd5b 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f6dd57e023 32: onsuccess: 2: Successful build after gcc: 6 commits discards 9f0075e731 31: onsuccess: 2: Successful build after gcc: 6 commits discards d8808b25a7 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards a15cfe1745 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 45658ecb63 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6901582d8a 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards d72139f94d 26: onsuccess: binutils-gcc: 2 discards df5113d857 25: onsuccess: binutils-gcc: 2 discards dc26b6da90 24: onsuccess: binutils-gcc: 2 new 26ef8976dc 24: onsuccess: binutils-gcc: 2 new 4b0fabafb1 25: onsuccess: binutils-gcc: 2 new 94e43e7c8b 26: onsuccess: binutils-gcc: 2 new ddc6f79281 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new b8ff02de24 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 37e7036d00 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8cffb919f6 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 636b22f2e5 31: onsuccess: 2: Successful build after gcc: 6 commits new 12216baf14 32: onsuccess: 2: Successful build after gcc: 6 commits new 3f001d90fc 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c687cc391d 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6bd5508bda 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new c5e67159ce 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 24b017a236 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 1d05bc535f 38: onsuccess: 2: Successful build after gcc: 2 commits new 41fa8a8ce5 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b0388e4000 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a76da99812 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new 0b76f2dcd4 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 43e95c6e03 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 4e7b2d2410 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a3e39f682a 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 53ee873688 46: onsuccess: 2: Successful build after baseline build: no [...] new e22289ec61 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 81802c402c 48: onsuccess: 2: Successful build after gcc: 4 commits new 929ac0e301 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 813c264bb6 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new bb2a519a28 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a462a28b02 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 38bb00b7dc 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 119d8aade8 54: onsuccess: 2: Successful build after gcc: 5 commits new 06f57a3ed1 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0216876c89 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 886ac18091 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 8eaaf01557 58: force: 2: Successful build after gcc: 6 commits new 6b11625e9e 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 1252553a35 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 668617cc4f 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new e4025bc88e 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new c06f1a06eb 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b75ff35386 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ad2e709d92 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b8fb168a99 66: onsuccess: 2: Successful build after gcc: 9 commits new ba12d16421 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9678cf0fdb 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 4c57b7c810 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d6ccbbdf37 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 468fe86a42 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 8ab0346e2e 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9832672754 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 5106f4eefa 74: onsuccess: 2: Successful build after baseline build: no [...] new bda87af96d 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new bd116a2ff3 76: onsuccess: 2: Successful build after gcc: 12 commits new e242ed7164 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8d533dc6c3 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 824bbd7ca4 79: onsuccess: 2: Successful build after binutils: 5 commits new bf62aafd9a 80: force: 2: Successful build after gcc: 14 commits new 4d3553500f 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 5ae5245dce 82: onsuccess: 1: Successful build after gcc: 3 commits new ce3ee63726 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new a2099ea8b0 84: onsuccess: 2: Success after binutils/gcc: 15 commits new f29f91d547 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 00a28b46ee 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 44f59832a9 87: onsuccess: 2: Success after gcc: 4 commits new bc47ffed40 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 64f0b977fe 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 1eea4347ab 90: onsuccess: 2: Success after binutils/gcc: 16 commits new d14f4db073 91: onsuccess: 2: Success after binutils/gcc: 7 commits new d119e33c8b 92: onsuccess: 2: Success after binutils/gcc: 9 commits new b47436e2d5 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 1a71bcd4ca 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 1be8466a58 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 8b72339a30 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 7cb6589c3c 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new f8592d2882 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 4cf5da09c3 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 631de0866e 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 54dd074225 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 12c619f500 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 34cdd492dd 103: onsuccess: #1504: 2: Success after gcc: 2 commits new a6e416927b 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 58bd979ba1 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 0d08f2c4ef 106: onsuccess: #1507: 2: Success after gcc: 2 commits new e05710cdfd 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 2d5e24b540 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 93c538e312 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 558c818dee 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 6e6be04294 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 8bc0f77ca9 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new a36fb7247c 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 22564cd76e 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 63c81872e5 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new be675f544a 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 477779686c 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 214defede2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 775013e05b 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 83b92903a4 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new e7bd137b07 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 0c02eaf6c5 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 809d852a1e 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 9872b22804 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 5dcb3910b2 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 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 (32034cf392) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...]
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 1676 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 53052 -> 50372 bytes 05-build_abe-bootstrap/console.log.xz | Bin 463112 -> 462572 bytes 06-check_regression/console.log.xz | Bin 3084 -> 2788 bytes 07-update_baseline/console.log | 56 +++++++++++++++++----------------- 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, 43 insertions(+), 43 deletions(-)