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 caa85f8d44 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards b9a53bec7f 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 5d33988490 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 9a426f3e9b 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards f9c40221be 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards c26af2b5b0 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards cbf78b5d67 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 09e57fbdb0 135: force: #1540: 2: Success after gcc: 23 commits discards 90e530c903 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards ecbab5eff0 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 1ccc794182 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards a904d7988a 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 6e9c538383 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 81de547ab4 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards f1c3ec414d 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 3b478e1eba 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards e590c1f6d5 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 454fd07dfe 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 5aa98ea155 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 2517b2ef83 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards e76e494afc 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 1c4dbdba8f 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 77e187a411 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 5ad1616f76 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 4a26767bf2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards a9b933bb31 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards c8bc4c7a46 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards e4c113faf3 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 596dfa70f3 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 4405d234cf 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 27baa74d4f 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 48e5415dd2 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 20df2263a4 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 4164408f30 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards bb92d130b1 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 5d30c4c336 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards c6eab3c0f5 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 1986b2f83a 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 66d4809ae2 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 80b4780774 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 75a91b1c67 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 20ce9853ce 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards c2fafc59d7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 2b52994ab8 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards cf79dfa567 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 6f343de00e 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards ff251f9142 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 4228ce2e40 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 6a7746bddb 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards e1ff5feae1 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards ad673c7f96 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards d1c523d7a0 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards c276d1bf77 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 4530a3c043 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 9d939551c9 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 76cdb585cd 87: onsuccess: 2: Success after gcc: 4 commits discards 4e56409de8 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 50e894aec2 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards e9ff150338 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 28914e5e39 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards c0ae6112bd 82: onsuccess: 1: Successful build after gcc: 3 commits discards 910708ec58 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards c713fbb9c4 80: force: 2: Successful build after gcc: 14 commits discards 88cbe4094f 79: onsuccess: 2: Successful build after binutils: 5 commits discards 2463d2819d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 376d5ec074 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 791ac139df 76: onsuccess: 2: Successful build after gcc: 12 commits discards f8e2e1ab6f 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards f63b1545b3 74: onsuccess: 2: Successful build after baseline build: no [...] discards 9810da6a68 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 97fc36f932 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f893f7c65e 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 7f4c623004 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5de4eca650 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b42f3b1bc1 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 1bbb96d192 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards bb79d0c742 66: onsuccess: 2: Successful build after gcc: 9 commits discards 469096f44a 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 7e68b2cf05 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3dc07b6ffd 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards f3f44d8b4a 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards c6e10a07df 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards e65695a983 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 58c2b9a1e6 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 9b232bed0a 58: force: 2: Successful build after gcc: 6 commits discards 2913747bca 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards c40b1e7cfb 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 351a86fe65 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 78afd6072d 54: onsuccess: 2: Successful build after gcc: 5 commits discards 2adcde16fe 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards b3cb479b7c 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e03daf6b0a 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 17634d9e1f 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ee77df96e7 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e7ad1c7c70 48: onsuccess: 2: Successful build after gcc: 4 commits discards 82ab555d5e 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 8b093920e1 46: onsuccess: 2: Successful build after baseline build: no [...] discards c9d79395d5 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards b8ea14bff0 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 36c3f2c6ef 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 51d3d5ba71 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 302e28a5b8 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new cadb70cf6e 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new f00ff4ee7f 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 55ed6134a7 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new fb37d43dff 46: onsuccess: 2: Successful build after baseline build: no [...] new 577ddee362 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 7e593de193 48: onsuccess: 2: Successful build after gcc: 4 commits new fe258e3a89 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 39ed0f5f2e 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 1eb059151a 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e69f343542 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8744cf2bf2 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 2d099a13d5 54: onsuccess: 2: Successful build after gcc: 5 commits new 5519ddb9d3 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a67f540f64 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4aab83d857 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 3e6d6a7e5a 58: force: 2: Successful build after gcc: 6 commits new 3981306b32 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new ebfa0a38fe 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 24f606794e 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 7419bef8f0 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 540d48fc2c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 249e1ec5c5 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d9ef433e21 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new afa3ce72a2 66: onsuccess: 2: Successful build after gcc: 9 commits new dcccbafded 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ce5942a1a9 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 002c63ba23 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cb0814d755 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new e273578f99 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 9b00a6787d 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 563d460136 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 22ecc8a809 74: onsuccess: 2: Successful build after baseline build: no [...] new 21137a3601 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new c063b7829b 76: onsuccess: 2: Successful build after gcc: 12 commits new ba007ea134 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1fae03c2e6 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 478050e90e 79: onsuccess: 2: Successful build after binutils: 5 commits new 6b947c3db9 80: force: 2: Successful build after gcc: 14 commits new 79a3acd00c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 77604bb0d7 82: onsuccess: 1: Successful build after gcc: 3 commits new ff816e1ee5 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 43e7e15a35 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 6dca411232 85: onsuccess: 2: Success after binutils/gcc: 25 commits new dc39a500b4 86: onsuccess: 2: Success after binutils/gcc: 10 commits new cfb0d6870b 87: onsuccess: 2: Success after gcc: 4 commits new e29f8f687e 88: onsuccess: 2: Success after binutils/gcc: 25 commits new bac41fecee 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 36f4cb6870 90: onsuccess: 2: Success after binutils/gcc: 16 commits new b711a506bc 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 6ed3ced888 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 36ec130dea 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 489bb05f69 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 6d7e5889e9 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 2caf1e20ab 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 9015d512e4 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 74a2c23ac7 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 89e95a347f 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 2cf4829bf7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 4d74ea7f09 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new babcd5680c 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 613f0fb932 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 5c47828b9c 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new ac5d964de1 105: onsuccess: #1506: 2: Success after gcc: 2 commits new bb5ca631eb 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 8eebcccbdf 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 0c9e1b9402 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 249a4c8412 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 555aac3a57 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 2aacfb4393 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new eef838cbef 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 4f9577d37f 113: onsuccess: #1514: 2: Success after gcc: 5 commits new b4c8a66011 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new d0dfab3a8c 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new a21ed59484 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new aea09ab6a1 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 84840fdf13 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new b961e47184 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 15eb84dc7c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new e8ada16555 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 8e7512683c 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 40767e1083 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 6ffd4f8f03 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 0e97f7b4ac 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 5ec1e8506b 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 93a530337c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new b752851b7d 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 2f44eb863e 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new b560337a70 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new a86c16777f 131: onsuccess: #1534: 2: Success after gcc: 9 commits new e4a719f540 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 92f5d3396d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new eadbd3758c 134: onsuccess: #1538: 2: Success after binutils: 2 commits new f80fe83d09 135: force: #1540: 2: Success after gcc: 23 commits new c567d0fe03 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 8825e6998e 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 3409ee6069 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new ea9734f4e8 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new d7d21bb819 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 7c01513734 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 18fede7dde 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 0cb7121136 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 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 (caa85f8d44) \ 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 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51476 -> 50792 bytes 05-build_abe-bootstrap/console.log.xz | Bin 112236 -> 110396 bytes 06-check_regression/console.log.xz | Bin 2968 -> 2620 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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, 34 insertions(+), 34 deletions(-)