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-aarch64-bootstrap in repository toolchain/ci/base-artifacts.

discards 84293c4169 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards c617b4f2b3 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards c155b174e5 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards b311791d8e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 0ef80209a3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 79f0cfcced 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards f5c9175aee 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 3735af67fa 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards d9a60a7f42 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 0fe3ddcc8a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards aee2e3aed2 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 786d5abb19 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards a8c3d9cf73 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards d2694b1330 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 0f1d2ddbc2 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 7ebb58ff9f 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 7b73fa4044 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 4527a2100a 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 24d48aee7f 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards d8c4a759c4 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards a9d39d104c 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 07d7f8cb2f 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 3f0d87f417 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards abc2180c5e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards c1fe994f2d 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards c8bdef4094 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards c514874882 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 2a0eb1c03c 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 327512e19b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 7af8a74edd 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 6637cd9d3b 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards aea7a32945 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards 7eff3cb581 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 6849cab5ca 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards e07da669e7 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards b97a4244b1 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards d24f1b6077 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 153af2adde 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c0667641a9 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 05f0eb2dfa 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 0426b63700 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards f07e4552bb 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards e3597cd06f 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 2462ba46f4 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 88a732df7c 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 0313110a1b 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 28b90ab6d1 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards a2de5a278d 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 664a9dd562 88: onsuccess: 1: Success after gcc: 20 commits discards dca837b2c8 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards ae6926beba 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 4f3dbb90da 85: onsuccess: 2: Success after binutils: 4 commits discards 41f967234e 84: onsuccess: 2: Success after gcc: 9 commits discards 86cfb827da 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 37b4764a1d 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 6a8e33bb5c 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 2f8923081b 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 0b77a71c8c 79: onsuccess: 1: Successful build after gcc: 3 commits discards 3ea405fd6d 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards dd8ec4d453 77: force: 2: Successful build after gcc: 32 commits discards 77b3646f6b 76: onsuccess: 2: Successful build after binutils: 10 commits discards 17fd198e92 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 5d29f346d6 74: onsuccess: 2: Successful build after gcc: 13 commits discards 4df9c337b6 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1f91d63c75 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 9249e6a149 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5d547438b5 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b1ea0c7800 69: onsuccess: 2: Successful build after baseline build: no [...] discards aa60714c32 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d3be365cc2 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9750c93ad2 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 23c5e3e43f 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards d262b3997c 64: onsuccess: 2: Successful build after gcc: 7 commits discards 25b996c134 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 72fdd5d387 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 08f8641639 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 6b1db3bf52 60: onsuccess: 1: Successful build after gcc: 15 commits discards 6f68d1f3f6 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 7e1f8e581d 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards c599c3a0b2 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 5d3255499a 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 4c531f1f64 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8afdd04fcb 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 89cc525855 53: onsuccess: 2: Successful build after gcc: 5 commits discards f983165c3e 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards bd202ca332 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 163454b7dc 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards e3c1ea949b 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 3dfa727e4a 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 9ad3ac9911 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1c5deb07ca 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e1ba7f6d31 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards e1ccc1bbba 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6403dc9d49 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards e255b6c676 42: onsuccess: 2: Successful build after gcc: 2 commits discards 509ee1f28c 41: onsuccess: 2: Successful build after baseline build: no [...] discards 6f791e6c57 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards eccc89220a 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5aeb1101f7 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e049625997 37: onsuccess: 2: Successful build after gcc: 2 commits discards 977da20844 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c6b0429c74 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 43fedade5d 37: onsuccess: 2: Successful build after gcc: 2 commits new 60dcc484f9 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3cbc004a1d 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 81365b58db 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new bc1ea137a6 41: onsuccess: 2: Successful build after baseline build: no [...] new 96f419ebf5 42: onsuccess: 2: Successful build after gcc: 2 commits new e2f082ca5b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 774a02e743 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f7c3447c85 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 901cb7cda6 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 14f637e6dd 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7ba5e0cdc7 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 27345ecd99 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 4a82debf12 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 0acf2bd610 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new b41eeced20 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 96be7f36d4 53: onsuccess: 2: Successful build after gcc: 5 commits new 9202dd8a8e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ce24407efc 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 929b43ff21 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 272de95cf5 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 23cf5712c4 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new a110822ce4 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 51ca05a10b 60: onsuccess: 1: Successful build after gcc: 15 commits new 67566a79c1 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 502397bd0c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5cac00bd46 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8b9caae289 64: onsuccess: 2: Successful build after gcc: 7 commits new 5bf4b901d4 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new e4d9ba0010 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 384b9ed16c 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ae961cd9cb 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new fc93483c88 69: onsuccess: 2: Successful build after baseline build: no [...] new 91b5a445c1 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 0eea79fc8c 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new b1fec64e0a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new b42747bc28 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 0e1e07ab03 74: onsuccess: 2: Successful build after gcc: 13 commits new 1cabecd014 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 2bd3a754ea 76: onsuccess: 2: Successful build after binutils: 10 commits new 24c445f6bf 77: force: 2: Successful build after gcc: 32 commits new b7f57ef072 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 54133f7474 79: onsuccess: 1: Successful build after gcc: 3 commits new ffc08c2ba8 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 1323827699 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 0f5d374cdf 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 5b5bf392d5 83: onsuccess: 2: Success after binutils/gcc: 7 commits new afe8bfcbdc 84: onsuccess: 2: Success after gcc: 9 commits new 24e118a2f6 85: onsuccess: 2: Success after binutils: 4 commits new d91c975c90 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 8c160d131f 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 81c2d4ddb4 88: onsuccess: 1: Success after gcc: 20 commits new adbb4d6961 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 97305f59de 90: onsuccess: #1472: 2: Success after gcc: 2 commits new dad3e0eb7a 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 5f3c6791d3 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 133a347da6 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new e679ab4ecb 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new aebc689fb0 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new eecfccc6d7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 687615bcb2 97: onsuccess: #1481: 2: Success after gcc: 8 commits new a198e66a7e 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new b61e6c00df 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 38928ae750 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new ce7690a430 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new a79f912d38 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 9ab13e424e 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 3b67dc52fd 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 96fcd27eeb 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 448fd30ffb 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 932131948b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 088d3777af 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 327c5c382b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 9eb377954a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 8d0cf8b876 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 32baaf94b3 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 149585fb2e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 15ea156b8c 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 4290868587 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 0dcc4fd0d6 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 3335ffd21c 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new ce2a863b6c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new f9ef2f9329 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 99fbab5de1 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 9c2a7ad0ee 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 032b3cfde7 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new ff1b94c33a 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 1a60b73b97 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 9a6d147db8 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 3c68bd0d12 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 6107a98acc 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new b09d1bf39d 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new ba00a90d6b 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 72219ccb76 130: onsuccess: #1554: 2: Success after gcc: 9 commits new cb2b0c2159 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new ecc2220980 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 91b6c7ae1f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 9a9be68219 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 11b1d26490 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 114519ccf3 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 83e3847ac6 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...]

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 (84293c4169) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...]

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 1660 -> 1656 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38468 -> 38360 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272984 -> 269504 bytes 06-check_regression/console.log.xz | Bin 2608 -> 2504 bytes 07-update_baseline/console.log | 44 +++++++++++++++++----------------- 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 | 18 +++++++------- 12 files changed, 36 insertions(+), 36 deletions(-)