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 09a2186a60 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards ba9a706731 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards c15c9e9059 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 1d4a2af931 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards dedca665a3 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 0b55072078 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 4d727691a7 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 8baf7ea42b 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards fb9bd77a77 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards a6a502277e 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 38f6426571 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 527479ef32 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 2ca4c4e458 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 3e816aab16 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 1635da04f0 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 11381470fd 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards c5d32dc10b 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards cd6199c7a4 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 89a75d52e1 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards e4ef62faaf 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards d66764bb9a 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 31a9c9ca9d 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards e84a68dc7a 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards d0f9ebd668 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 8cb4766b75 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 8dfd8f08ca 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 65b0e0857e 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 02078956bf 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 62001c262b 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 3ab731600e 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 24de503acd 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards fad4342e93 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 03014beb6a 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards eee9a4d8b7 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards c8530d3f30 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 0c9290b01e 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 769895d936 87: onsuccess: 2: Success after gcc: 4 commits discards 99a4a699bd 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 938d874b8c 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 0278022940 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 59ec75f974 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards d9284241ca 82: onsuccess: 1: Successful build after gcc: 3 commits discards f1bc04db48 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards c08dcfe093 80: force: 2: Successful build after gcc: 14 commits discards 22670154d5 79: onsuccess: 2: Successful build after binutils: 5 commits discards abe39c62b0 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 69aedb6c5b 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards dbf652446c 76: onsuccess: 2: Successful build after gcc: 12 commits discards 90b9589bcb 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e978f46cb4 74: onsuccess: 2: Successful build after baseline build: no [...] discards 7fa06251bb 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 546c87a311 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1588d2d59b 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards e478d64a99 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards ccab9bb6e6 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1a547f2979 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 9f80817c6f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8312473b00 66: onsuccess: 2: Successful build after gcc: 9 commits discards c50b75c58a 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e018438440 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ccd89f1c90 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 52ca71afe1 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 4b580337c3 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 811639c2e7 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 52c0776a06 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards c15976e7a9 58: force: 2: Successful build after gcc: 6 commits discards e6b7d325eb 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards bf0e0a8744 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards db5873312c 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 68746ed7b8 54: onsuccess: 2: Successful build after gcc: 5 commits discards 340add4d1f 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards b30ec9768f 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f55f1e4020 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards a72b6c7e97 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 1277283a0d 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards af910a7db5 48: onsuccess: 2: Successful build after gcc: 4 commits discards 6f0134f25c 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 71cd2eac7d 46: onsuccess: 2: Successful build after baseline build: no [...] discards a929f0ff33 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 46426b58b0 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards aa3883ee4d 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards fb3026abf2 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards ca36ce64ac 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 0f4ec7cdb2 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards a153064d41 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 174412c93a 38: onsuccess: 2: Successful build after gcc: 2 commits discards 60698d9104 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 8490f1fb91 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 5364c9877a 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 512f57cc80 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 57329e400c 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f1ed75777b 32: onsuccess: 2: Successful build after gcc: 6 commits discards 411d1401da 31: onsuccess: 2: Successful build after gcc: 6 commits discards fb7f8978aa 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards e53d280505 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f867e4aa25 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 4ae6894276 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards 0a7bbb96a2 26: onsuccess: binutils-gcc: 2 discards 64002f8300 25: onsuccess: binutils-gcc: 2 discards 7fd0b17d68 24: onsuccess: binutils-gcc: 2 discards 8500b8e62b 23: onsuccess: binutils-gcc: 2 new 06b3003ff6 23: onsuccess: binutils-gcc: 2 new dc26b6da90 24: onsuccess: binutils-gcc: 2 new df5113d857 25: onsuccess: binutils-gcc: 2 new d72139f94d 26: onsuccess: binutils-gcc: 2 new 6901582d8a 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new 45658ecb63 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new a15cfe1745 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d8808b25a7 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 9f0075e731 31: onsuccess: 2: Successful build after gcc: 6 commits new f6dd57e023 32: onsuccess: 2: Successful build after gcc: 6 commits new e31d30dd5b 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6cdcebe6ec 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f52e49c92b 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new f7edf42050 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new ea30dcd66f 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4a1b10335b 38: onsuccess: 2: Successful build after gcc: 2 commits new a0cb1e416f 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c4544bb0b0 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2bffea3e70 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new f17f06444c 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 5d4e2ce875 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new cb184bb088 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5b4ba9fc8a 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 8ed05e8004 46: onsuccess: 2: Successful build after baseline build: no [...] new 1bacc04131 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9de61a2704 48: onsuccess: 2: Successful build after gcc: 4 commits new 6ee35f7758 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b6ea7c093c 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 46cf161ce3 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 9da88c70c5 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 5f32f878ad 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 0121da0416 54: onsuccess: 2: Successful build after gcc: 5 commits new a23570a4fa 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9c110ddca5 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 25af4d6074 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 08b0f94b4e 58: force: 2: Successful build after gcc: 6 commits new 01cd5b90df 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new bf3774f3a4 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new a8fd4ccf66 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 31b5c25826 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new c65cc3479b 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 01d883e42b 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new dcd293c382 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1c696dfd23 66: onsuccess: 2: Successful build after gcc: 9 commits new 7c79e33d68 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 5a1e8d992b 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new d8c292edb6 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5e73a1cd78 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 090790188d 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 2d4b0b347e 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 68be4eacba 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 560e1d73a7 74: onsuccess: 2: Successful build after baseline build: no [...] new 50969ff51f 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0b2698a7b7 76: onsuccess: 2: Successful build after gcc: 12 commits new 1a90f3bd04 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 4858362019 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new c6bebc9190 79: onsuccess: 2: Successful build after binutils: 5 commits new 13a5cee1e1 80: force: 2: Successful build after gcc: 14 commits new 7cf1d91d4b 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new f6452dc2ab 82: onsuccess: 1: Successful build after gcc: 3 commits new 1c7b6d30bc 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new ceba3d3ab0 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 088070e65a 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 6e48211037 86: onsuccess: 2: Success after binutils/gcc: 10 commits new f26df0cb11 87: onsuccess: 2: Success after gcc: 4 commits new a1d093644f 88: onsuccess: 2: Success after binutils/gcc: 25 commits new e7930001e0 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 780510f9f7 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 815b4bbba8 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 02d2ba141b 92: onsuccess: 2: Success after binutils/gcc: 9 commits new e6a075c433 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 95891a6a74 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new b4997d97ae 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 871ea0efb6 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 146908e5d2 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 1945ee6213 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 952c8d824f 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new dbd165d9b3 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new f6ab21619f 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new ad7c71f0cc 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 88ed3105c3 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 025cd2c625 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new d28d1dc132 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 327b323f20 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 18f0977502 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 8163f59249 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new deb5b0021f 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new c5b28ae5ee 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 532beae932 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new d2cdf5f188 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 356c4162c8 113: onsuccess: #1514: 2: Success after gcc: 5 commits new f9566efcd3 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 0a5d3ad685 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 60064d8114 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 66a1bbcd21 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 6b7f2ef712 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 49290b86b5 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 476a5485f7 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new d1f36e68de 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 5787cc554b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 14571c5e8c 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 32034cf392 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 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 (09a2186a60) \ 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 1716 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 52080 -> 53052 bytes 05-build_abe-bootstrap/console.log.xz | Bin 461812 -> 463112 bytes 06-check_regression/console.log.xz | Bin 2204 -> 3084 bytes 07-update_baseline/console.log | 32 ++++++++++++++++---------------- 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 | 19 ++++++++++--------- 13 files changed, 32 insertions(+), 31 deletions(-)