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 d0bf6901d 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 36d837d52 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g1 [...] discards 72ec3dd8f 135: force: #1540: 2: Success after gcc: 23 commits discards cbb62ac84 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards ab0f0a858 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards acf01d627 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 2ecb54e4b 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 5480c3a07 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-283 [...] discards af197310b 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards e06fdecec 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 201ff0334 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 27eb2ff90 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards db7b8def8 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 214b09187 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 0a22e9138 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards e8c1988b0 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 3343e9528 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 919a67d7c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards b699d1bb1 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 77ff86e9f 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards bf3ce4c3c 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 6d5cfedbd 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 735ad6f04 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 1bea332cc 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 6e1840480 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards da8553cbf 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards f4dcb7c63 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 545478907 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 7e24422c4 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards 02b76ee2a 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 2fadfd87a 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards a6168497f 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 990f98932 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 72844bd60 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards c1ae6022c 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 1d8d3211b 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards a6271de7c 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards f1a1655cc 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 91c4fcb08 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards b30f4d0b3 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards d6389572e 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 1ae9b1449 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 88c1f5111 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards 52acbf0d5 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 2d9db5e39 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards eff93bd9f 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards c46ce7275 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards ec13a0d71 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards d436f7abe 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 8151343cd 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1df4ab519 87: onsuccess: 2: Success after gcc: 4 commits discards 0bc39fc8c 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 35d091084 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards b0a967711 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 725ae7ccf 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards c3558ea2c 82: onsuccess: 1: Successful build after gcc: 3 commits discards 8b953488f 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards db4d123d8 80: force: 2: Successful build after gcc: 14 commits discards 5446ec282 79: onsuccess: 2: Successful build after binutils: 5 commits discards 3dd30dee0 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 8ec77c7a9 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0f54bec02 76: onsuccess: 2: Successful build after gcc: 12 commits discards 815307191 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 4ce3b261e 74: onsuccess: 2: Successful build after baseline build: no n [...] discards 65ae2889f 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 61197e12c 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 459e926b5 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 66fdd5d72 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 168711631 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 96613a4de 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a9be6ccb0 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6a765bb5a 66: onsuccess: 2: Successful build after gcc: 9 commits discards 7cf64da6d 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 3ee381c8f 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ad9bc8687 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 573bbf621 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 134739fae 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 02fbfb2fd 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 02ed1089e 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards 9be91909f 58: force: 2: Successful build after gcc: 6 commits discards 6488e2e2c 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards e14023d92 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 79db3131c 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9183b0fe6 54: onsuccess: 2: Successful build after gcc: 5 commits discards 9b5025b64 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 069be655a 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6797b1865 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4d5ae0db0 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 2b2d4ca61 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6cf691518 48: onsuccess: 2: Successful build after gcc: 4 commits discards 0993822d1 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5bbb246b9 46: onsuccess: 2: Successful build after baseline build: no n [...] discards 3a4268eac 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards c2b2e17f6 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9afa34669 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards d55311cfb 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 8ff394add 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards fa4a11b3b 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 42c0745ed 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8e0e4c979 38: onsuccess: 2: Successful build after gcc: 2 commits discards 5cf48836f 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 64f585328 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 7e7645cf5 38: onsuccess: 2: Successful build after gcc: 2 commits new b535e01dc 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6d766e1e5 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 0b03a9656 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new 2f1838f06 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 281a1ed4c 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new bc7ff4610 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 30f19b8fe 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new b569cf7ee 46: onsuccess: 2: Successful build after baseline build: no n [...] new 34bd4507f 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 58141d64e 48: onsuccess: 2: Successful build after gcc: 4 commits new 292168b59 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d15fbc43d 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new eed44f60a 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 6a5cc384c 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9effc4e5b 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new b73205f15 54: onsuccess: 2: Successful build after gcc: 5 commits new da0c76847 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new aec505ffd 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 9de1dd345 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new 2f48b74cc 58: force: 2: Successful build after gcc: 6 commits new 92e8cad1c 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new eb3b794c1 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new ebdce913b 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new c151d2c62 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 38220c239 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 4de634532 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ec2e2d8fa 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 52bfa8e4f 66: onsuccess: 2: Successful build after gcc: 9 commits new 9ce754f76 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new a8c7b45d2 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 54954ff14 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8db220caa 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 4feffbb15 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 4e7070e94 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0943a05a7 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new f230905e1 74: onsuccess: 2: Successful build after baseline build: no n [...] new af7ae617c 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 28ff378dd 76: onsuccess: 2: Successful build after gcc: 12 commits new 7f82c8c65 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new ac627dac3 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new a4e237e42 79: onsuccess: 2: Successful build after binutils: 5 commits new 149c7315a 80: force: 2: Successful build after gcc: 14 commits new da6ecfa48 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 1eb806e28 82: onsuccess: 1: Successful build after gcc: 3 commits new d862326ff 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 3b04d643c 84: onsuccess: 2: Success after binutils/gcc: 15 commits new f3399e538 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 0b9a46f80 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 293c1c877 87: onsuccess: 2: Success after gcc: 4 commits new e808f0392 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 9bc0298a1 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 6bf8d5aab 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 016594efb 91: onsuccess: 2: Success after binutils/gcc: 7 commits new a890e49bb 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 54e8d8940 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 323bb43b7 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new 155d15dc4 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new c4bd382b0 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 55a1d5634 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new a6c26ee32 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new 32cb245df 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new ef6cdf047 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 38edf4882 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new c682c3b6e 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 031c96c76 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 7519ed5b1 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 1f64e63bc 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 39ad22415 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 0effe67c4 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new 83df8e92f 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 3a1d75037 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new 47c4c1cad 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 78511af9d 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 893f21875 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new fdf0822b4 113: onsuccess: #1514: 2: Success after gcc: 5 commits new b27146e07 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 2a19be8df 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 4199fa3e0 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 64b43c687 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new db20b7058 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 0a9e2ccd1 119: onsuccess: #1520: 2: Success after binutils: 8 commits new d2a4199d0 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new c5a1f6ee6 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 2f103e4df 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 5d99f8a4e 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new bd0d2b64b 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new c0fdb98b3 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new b40e8ed19 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 20e35fff5 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 1f5d05ecb 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new c8cea3170 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 5cc8356d7 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-283 [...] new a9d13c204 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 27aec1d82 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 9804f8e97 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new e4baef755 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 8539340d1 135: force: #1540: 2: Success after gcc: 23 commits new cd64350d7 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g1 [...] new c802b403b 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 572ad3d66 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 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 (d0bf6901d) \ 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 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50804 -> 51080 bytes 05-build_abe-bootstrap/console.log.xz | Bin 107036 -> 107424 bytes 06-check_regression/console.log.xz | Bin 2572 -> 3080 bytes 06-check_regression/mail-body.txt | 9 -------- 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 | 11 +--------- mail/mail-subject.txt | 2 +- manifest.sh | 19 ++++++++-------- 14 files changed, 36 insertions(+), 53 deletions(-)