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 89aa4fb753 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 4e30a2844c 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 50c5a9a9e8 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 5ddad75b2e 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 131de71846 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 2de1219e1e 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards b511c17c69 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 531f055904 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 074eebb725 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 9f5142cfe5 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards dc15bf4a7c 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards a5508b9b33 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards ead5b38269 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 4b886865fc 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 64c7864816 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards aa4d7f5b90 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 566f8e9b52 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards a1bffe875f 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 3d7ef16ed6 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 62230800e9 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 72fc11fba6 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards b02d685d98 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards bbb7591436 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards ca4af70eeb 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards a53680d019 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 685b5b510a 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards fbce35b9b5 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards d5546c1fd0 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 5938854312 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards fcdd496c3b 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards d866dcca45 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 7eae362f45 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 6de6a60015 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 9c4b0dbfc5 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards f5458c2368 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 0ee4d1ae16 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards dfcadfdf6a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 7d2fdca1cb 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 9cb77a988e 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 0d501ec55f 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 4ce0aa533a 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards b277aa6907 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards ddbeda76aa 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards a2729428d3 87: onsuccess: 2: Success after gcc: 4 commits discards 5187a940a5 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards a22615dc6c 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 4fe59848c3 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 9136b0740a 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 6e4a17f52b 82: onsuccess: 1: Successful build after gcc: 3 commits discards 5a50e124e3 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards fa5044d11d 80: force: 2: Successful build after gcc: 14 commits discards 3b0d690cca 79: onsuccess: 2: Successful build after binutils: 5 commits discards 3639297e16 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 95043fc248 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6431d74f16 76: onsuccess: 2: Successful build after gcc: 12 commits discards 4c011ab50b 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards d234071527 74: onsuccess: 2: Successful build after baseline build: no [...] discards 4c7c37eb4a 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 92949c60e8 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ecc28acc84 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards e629d4dfd1 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5612f77053 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e75cb8435d 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 83a66bf397 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 1b63af9832 66: onsuccess: 2: Successful build after gcc: 9 commits discards 8fc7aebeca 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 3eb3fcd3f1 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 74ca5b7e2b 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 47e716c4b1 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 25f03952cf 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards c56d955054 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards dd02f68389 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 7e5e2efb02 58: force: 2: Successful build after gcc: 6 commits discards 90e6ecbe15 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 7d43bd0a3d 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards b4ccc4de55 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 2759027a2c 54: onsuccess: 2: Successful build after gcc: 5 commits discards b7e9db1eea 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 13c6d8b929 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0b790bd9b1 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 82c2bc827f 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards b1072913fa 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards de6b8791ea 48: onsuccess: 2: Successful build after gcc: 4 commits discards e7636976a7 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 678a244ad5 46: onsuccess: 2: Successful build after baseline build: no [...] discards 6dde4af80e 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards bb54404dd1 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ce73d1ced2 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards bc678eac2f 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 267e9fbe10 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 56b257d0aa 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards d5bec4d91c 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9439b6892b 38: onsuccess: 2: Successful build after gcc: 2 commits discards 68f6c16e61 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2c04fa11dc 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 48afc62e45 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 1f27fcf703 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 02cfcba510 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6ff1b79dd6 32: onsuccess: 2: Successful build after gcc: 6 commits discards aa7e366a15 31: onsuccess: 2: Successful build after gcc: 6 commits discards 21253866f6 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 504e426654 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 76284904e6 31: onsuccess: 2: Successful build after gcc: 6 commits new fa13ab85af 32: onsuccess: 2: Successful build after gcc: 6 commits new a7ea08b862 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 2c8dd9d379 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9c872c8f8b 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 4ab22c59b6 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new bfd46e7c7c 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new e90cbb8dcc 38: onsuccess: 2: Successful build after gcc: 2 commits new aedcbeba08 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e5b8990b35 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2459c47036 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new d3dba4f78b 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 3ae607619a 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 71cd4b3be9 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e1930234ec 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 5916e66c16 46: onsuccess: 2: Successful build after baseline build: no [...] new 3eaaef17fd 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8517d5eb1f 48: onsuccess: 2: Successful build after gcc: 4 commits new 2eaff476a8 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new de06054374 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 4444748337 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new ad5d1e1eec 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b4b1e4823c 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 67cbce7297 54: onsuccess: 2: Successful build after gcc: 5 commits new 725e289696 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b6fedff163 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 6e108578ab 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 16e6d278e7 58: force: 2: Successful build after gcc: 6 commits new 60c82700ac 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 8ded2a6080 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 87c1d32ceb 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new e436c00bda 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 7287434cfd 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 259e22d472 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e463494159 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 12f5575f6c 66: onsuccess: 2: Successful build after gcc: 9 commits new ec46237539 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3ba7b91fa4 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new f404dbd02c 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 0c1792f75d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a36c042a0b 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new a5c8fc5bfe 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cac1c28ddc 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new dd4d902810 74: onsuccess: 2: Successful build after baseline build: no [...] new 99a5977b56 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 83b4b69664 76: onsuccess: 2: Successful build after gcc: 12 commits new 1f2446ea7f 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b1ed28b47b 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 00e9007691 79: onsuccess: 2: Successful build after binutils: 5 commits new 5008173a09 80: force: 2: Successful build after gcc: 14 commits new bd8c34785d 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 5d0411eca7 82: onsuccess: 1: Successful build after gcc: 3 commits new 16994b4e90 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 933ba2cac8 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 243ea5459d 85: onsuccess: 2: Success after binutils/gcc: 25 commits new fc9339c26f 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 26e7e71b6e 87: onsuccess: 2: Success after gcc: 4 commits new 84d0f8275c 88: onsuccess: 2: Success after binutils/gcc: 25 commits new ce5b8ba56b 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 652f37004a 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 1795ca59db 91: onsuccess: 2: Success after binutils/gcc: 7 commits new f50c75a066 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 4e57a9c776 93: onsuccess: 2: Success after binutils/gcc: 3 commits new bc77150a23 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 8a60b35064 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 3f93865050 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 3fc958371a 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new e5d5e88314 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new a6912c6aa5 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new b556eb133b 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 4b23262654 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new d9a322eb9a 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new fe06d91df1 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 92e4a01dcf 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new d160a0ab58 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 4029d896be 106: onsuccess: #1507: 2: Success after gcc: 2 commits new fb583b5a25 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 2bec0b9d0c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 5a9c4019ff 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 29e4bb3bed 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new c63620df16 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 5e7f67ed8b 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 654eab5e9d 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 0cd7022e35 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new e150e824db 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 47518117be 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new c1a7108c58 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 264504bef5 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new c1c3331e78 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 4a768a2427 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new f57397e111 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 45e06dadf0 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new c3e21c3c48 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 31b38b1b34 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new 954108fce9 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 124c818fb5 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new b43b7c1ba1 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 52e88f89ce 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new ef3668a9ae 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new ff6d818358 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new a4b5eeff09 131: onsuccess: #1534: 2: Success after gcc: 9 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 (89aa4fb753) \ 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 1668 -> 1716 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 50272 -> 50976 bytes 05-build_abe-bootstrap/console.log.xz | Bin 465140 -> 462768 bytes 06-check_regression/console.log.xz | Bin 2548 -> 2648 bytes 07-update_baseline/console.log | 56 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 ++++----- 12 files changed, 40 insertions(+), 40 deletions(-)