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 5ae928d7e8 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits discards c5125356ad 157: onsuccess: #1562: 2: Success after gcc: 2 commits discards d3eb00b99b 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards 3d5cce0f83 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards 23614f30d6 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards ced6b6d078 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards 001eef3a50 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 28e61fecf9 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards 93c4cbf520 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards 6273915269 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 14b5ce7c49 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards 3d75ae8346 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 5fcbe65dde 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 61f4dc7a10 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 35176fdd78 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 4a14ea0283 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards b732245f12 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards be9d5fc2db 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 688e7f4252 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards aa9e29205b 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 7350d2d852 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 6c5513dfd8 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards a9ea4635b3 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards 2bffb098ee 135: force: #1540: 2: Success after gcc: 23 commits discards df0c1eae86 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 86dc881186 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 1ad89ec8a7 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 2bba7f94d2 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 00b9af7f0d 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 1d55b707b4 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 93025be92c 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 1c3a91f8ed 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards bde9f77821 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards be1f63921b 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 5961cda855 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards a356baed0e 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards ad016f49a5 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 67eaf9ed94 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards ceed5cdfcf 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 4344c8b88e 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 03b3419170 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 92a9cea3f4 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards e3b8f558f6 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 74a22d4696 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 5e7d9578bc 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 554b5543ee 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 04aea6ea48 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards e43e0a8f29 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards c9657f5cf4 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards b9281207e7 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 01e95c9bd1 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards a85a68bda4 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards c996569db5 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards f67beaeb73 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards e19923d0a3 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 219da72dd9 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 1ac28dd3f7 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 3ddfbe0c18 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 6a5f189d0a 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 260d2405dd 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards f782bf07fe 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 703db77977 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards a8b6700cb0 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards ba72be9a20 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 46f14d0e26 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 970f0a6959 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 619bcdf09e 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 434348c56f 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 440630ba00 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 39eb991de3 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 5947af51af 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards f6a951ea2d 87: onsuccess: 2: Success after gcc: 4 commits discards 89c5b807d5 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards e319e871c7 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 02d96cf8fa 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 6a60f85a66 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 3bc3cc9d92 82: onsuccess: 1: Successful build after gcc: 3 commits discards ca80738103 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 77948c77d0 80: force: 2: Successful build after gcc: 14 commits discards a30d1e5290 79: onsuccess: 2: Successful build after binutils: 5 commits discards f1a10f8fc4 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards b561ec64d2 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 27b86d3c11 76: onsuccess: 2: Successful build after gcc: 12 commits discards 38009496c0 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6c9c291e56 74: onsuccess: 2: Successful build after baseline build: no [...] discards 50d5b546b9 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards c400a96cdb 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ce35d37fca 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards fe9384d82b 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6ffb176786 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 5e34f3644b 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d6a3e0310f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e2a6962afb 66: onsuccess: 2: Successful build after gcc: 9 commits discards a1a58657a0 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 2f2b6153f1 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 084e7a55d7 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9a21e676f4 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 88df68db70 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 55edbf950b 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 8b083989f3 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards ed03baa057 58: force: 2: Successful build after gcc: 6 commits new 9d568750fa 58: force: 2: Successful build after gcc: 6 commits new d61bd4220f 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new c95b280acf 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new b8a9ed3c1b 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new e0ff3813aa 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 7a3aa34c5c 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new eca03b4b20 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 90cf1c0251 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ad5c84a0cb 66: onsuccess: 2: Successful build after gcc: 9 commits new 250b4007e7 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 1f0a806bd3 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 57ef459b3e 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c70c9d8faf 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 6268f9d9aa 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 014c2de609 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c64f3bf4fd 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 8fc6353754 74: onsuccess: 2: Successful build after baseline build: no [...] new 4fce825e98 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 07dc3dfdc6 76: onsuccess: 2: Successful build after gcc: 12 commits new db434aedc8 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 56ef02956d 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new a770eb4320 79: onsuccess: 2: Successful build after binutils: 5 commits new e4484f7af0 80: force: 2: Successful build after gcc: 14 commits new fabd283813 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 85cd99697e 82: onsuccess: 1: Successful build after gcc: 3 commits new 7f56265841 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new ce6719b230 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 4359658086 85: onsuccess: 2: Success after binutils/gcc: 25 commits new d64dc01248 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 34c30da9a6 87: onsuccess: 2: Success after gcc: 4 commits new affb04e5be 88: onsuccess: 2: Success after binutils/gcc: 25 commits new e0b26fae6f 89: onsuccess: 2: Success after binutils/gcc: 4 commits new ac926b1523 90: onsuccess: 2: Success after binutils/gcc: 16 commits new e7812a3b1d 91: onsuccess: 2: Success after binutils/gcc: 7 commits new a3ee6e9c31 92: onsuccess: 2: Success after binutils/gcc: 9 commits new f52b1f289a 93: onsuccess: 2: Success after binutils/gcc: 3 commits new b8fa6b2db3 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 84d7d39ca1 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 5c313dd43e 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 241071d2ad 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 4a79a502fe 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 95a18b5a38 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 28b3a16048 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 4658ca736b 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 86a54b9721 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new ef3c00bc37 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 38d9226b13 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 533a0f2a8e 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 24f73ca604 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 38dc8900aa 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 1c4cdf24c4 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 5baed27ed0 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new b0835f4f33 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 6970f1af20 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 431f70fb9e 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new dab034465a 113: onsuccess: #1514: 2: Success after gcc: 5 commits new ff4e51e482 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 1b59aa5868 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 73b00ca18f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 83283c4a56 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 8f0de45a96 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 393c3a5684 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 5115e264ad 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new aaddc43704 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 3e3f6cad23 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new abf5393a55 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 8b0a34e649 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new ba22158b3f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new af5d184481 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 821530f6b4 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 8263fa2229 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 8c3234a815 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 3874e62338 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new ac1524020a 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 0e5ea3caa9 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 7aa2387fe6 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new c5de971989 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 8d4ffbb79f 135: force: #1540: 2: Success after gcc: 23 commits new c490ac0034 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 20b4ba9386 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 59ddeab559 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new 097ce66972 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 5015dc1536 140: onsuccess: #1545: 1: Success after gcc: 7 commits new e7f6120ada 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 5e2c689a1a 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 37bd41a22c 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new aecc1ecb77 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 148c090f65 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new cd8699f0ce 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 73459c7691 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 5fbb797adc 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new e31b85fd0a 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new 8388951d85 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 4ea5471864 151: onsuccess: #1556: 2: Success after binutils: 12 commits new c8a1dcc399 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new acb4df430f 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 0339688032 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new 4c5c522c09 155: onsuccess: #1560: 2: Success after gcc: 3 commits new f603304fd6 156: onsuccess: #1561: 2: Success after gcc: 2 commits new 83948e1737 157: onsuccess: #1562: 2: Success after gcc: 2 commits new 60294a6683 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 commits new 341aee75dd 159: onsuccess: #1564: 2: Success after binutils/gcc: 11 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 (5ae928d7e8) \ 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 1672 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 51324 -> 51524 bytes 05-build_abe-bootstrap/console.log.xz | Bin 465744 -> 464884 bytes 06-check_regression/console.log.xz | Bin 2540 -> 3052 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- 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, 47 insertions(+), 47 deletions(-)