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 5606742690 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 1d0db5d782 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards c2a67111d2 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards e77c00a23b 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 7fdc0b3050 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards ce2863acf3 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 1dd37e71a8 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards e9c59fc262 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 3469b863e3 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards ccdce5b604 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 97700724af 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 5436d596d8 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards c48597dd2d 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 5c97707174 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards f1cb6e95c6 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards c109565232 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards df16dfe3cd 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards e75fadff5b 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 188eee554a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards eeaf749e7a 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 94249b1886 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 6048185c13 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards c3d05f9993 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 4188278a02 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 6342fe2b97 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 922c98ece5 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards cbd2bd8824 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards faabd3ae6a 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards ae2ada42af 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 8c1704f7e3 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards df743dd232 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards e47cd33ad3 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards c51d7e28f0 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 727f208817 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 8ffa91d587 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards ce0d248d8e 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards ce6d3c11db 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards d8f3026462 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 348001789c 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 098bcb9779 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 4482436bb5 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards f733575570 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards d05e8a8224 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards e4ee43cd7f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards def80afca2 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards c92de0b930 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 2838dfbbbd 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 6d3420b29f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 52e8cd9a81 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 16eb657fc7 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 05cfd5e444 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards f63ea40157 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards bd73fde2d3 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 5804509491 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 665c173c91 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards b0b6ce2046 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 5831752139 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 3d954f0392 88: onsuccess: 1: Success after gcc: 20 commits discards cb9057c648 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 82334e2d36 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 0fd94856bd 85: onsuccess: 2: Success after binutils: 4 commits discards aced4fe28d 84: onsuccess: 2: Success after gcc: 9 commits discards 650978e086 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 75d3e5c689 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 9dc4346a48 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 3bf37d1513 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 6bb0442cdc 79: onsuccess: 1: Successful build after gcc: 3 commits discards 6014bb7b52 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 27bf4e3807 77: force: 2: Successful build after gcc: 32 commits discards f66058c573 76: onsuccess: 2: Successful build after binutils: 10 commits discards d8a28c84d5 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 7064970dfc 74: onsuccess: 2: Successful build after gcc: 13 commits discards 4a4b2328b2 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards c2b2333226 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 6c1a1d049b 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 25bc48f474 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards b945a13795 69: onsuccess: 2: Successful build after baseline build: no [...] discards 99c88e39fd 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 4838897891 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0fa6e22222 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 2a0e370bfc 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards fef1eec60e 64: onsuccess: 2: Successful build after gcc: 7 commits discards 4071193f10 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 20193d9eb3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 761a5c2e21 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 9f7dcf475e 60: onsuccess: 1: Successful build after gcc: 15 commits discards e40c8722d1 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 3491d11504 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 88974f8cdd 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 3fe6ee3fed 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 0c90719d17 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards c5b79d3e1f 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7fcb06767f 53: onsuccess: 2: Successful build after gcc: 5 commits discards dfecd8923c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards e2decf2a47 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 9d0c9f628d 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 84561344fa 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards e12e3a725b 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ff0912c2a1 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 260ec7a92b 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 2b2206d960 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f05bc9b05b 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 200695b7de 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 928f4c0612 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3996c47ba4 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new b7040f4416 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 65a2ba6ac5 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new bd418883c1 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 69ae58f17c 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new bdfdcb392b 53: onsuccess: 2: Successful build after gcc: 5 commits new f7bf181169 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ac4d0fc392 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 19297155e1 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e27347e80a 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 8368c95bf1 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 6dd580862d 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new ca2053e5d3 60: onsuccess: 1: Successful build after gcc: 15 commits new e88b399609 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 684e260c0c 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new dda830e84d 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new fb9adab089 64: onsuccess: 2: Successful build after gcc: 7 commits new 056b023326 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 2b9a7e6ff0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 957a63fead 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 322546c2f4 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new e2cc1e705f 69: onsuccess: 2: Successful build after baseline build: no [...] new 6200d97521 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new f30c8118f6 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3a60390d49 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 3258ee9ad1 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 68e1a93e35 74: onsuccess: 2: Successful build after gcc: 13 commits new b8086972a6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new d77afcbc05 76: onsuccess: 2: Successful build after binutils: 10 commits new e33ee51bd3 77: force: 2: Successful build after gcc: 32 commits new 63a7b99149 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 84a347bb3f 79: onsuccess: 1: Successful build after gcc: 3 commits new 07e6ea1a54 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new a8b47a9609 81: onsuccess: 2: Success after binutils/gcc: 16 commits new d0026dbb7a 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 915b81d57b 83: onsuccess: 2: Success after binutils/gcc: 7 commits new a0435d1758 84: onsuccess: 2: Success after gcc: 9 commits new 692591cf1d 85: onsuccess: 2: Success after binutils: 4 commits new a4925cc257 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 525a75668f 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new c62d86e279 88: onsuccess: 1: Success after gcc: 20 commits new d8e7c69960 89: onsuccess: 2: Success after binutils/gcc: 39 commits new ae86174b7a 90: onsuccess: #1472: 2: Success after gcc: 2 commits new b06014d746 91: onsuccess: #1473: 2: Success after gcc: 2 commits new ebc479971a 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 8fe8ef48c6 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 5969df9dd7 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new f4dda02e5b 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new bd66a22f7a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 2ba46d3c13 97: onsuccess: #1481: 2: Success after gcc: 8 commits new b832dcb48b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 7510eb2bc5 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 61af3f4829 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new e8ca31ca50 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new ba3dff51aa 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 7c892b8d4d 103: onsuccess: #1524: 2: Success after gcc: 2 commits new ec3cc9f8a1 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new c8918ea898 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 25083ff042 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 1018d13a66 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new ab097bc776 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 058c14a351 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 635e6d08e1 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 08a9f41f79 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 970d3325ca 112: onsuccess: #1533: 2: Success after gcc: 5 commits new e6dcf750e8 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new a89ac65868 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new eec68df014 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 08cd50fcb5 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 67b86e0ecb 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new eb1d949653 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new e4ad16e779 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 78c4e5ab68 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 49f391a9a2 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 7da44d9fca 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 1da710b093 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 327f9f7a22 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 28f65a2797 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new c613f46baf 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 1264e12e6f 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new c74a78ac29 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 6b22f7c352 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 6c7b0e010d 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 713bb8d3fe 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 191f97d0a7 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 42af240b28 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 9167f13875 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 3ac9e1d15d 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 24891a09da 136: onsuccess: #1561: 2: Success after binutils: 3 commits new f07ee24d7c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new c7a233ac15 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new d6fee00efe 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 252c853075 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new f58fbe71d6 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new a22c263632 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 8f28e2eb5c 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new d5bac15cb3 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new 65082e52d2 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new a1d013977e 146: onsuccess: #1573: 2: Success after binutils: 7 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 (5606742690) \ 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 1616 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 38060 -> 38576 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272228 -> 270884 bytes 06-check_regression/console.log.xz | Bin 3036 -> 2780 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +++++++------- 12 files changed, 33 insertions(+), 33 deletions(-)