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 8d3ce50bb6 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 2d7f49b62d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards 97e24dd4bd 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards 85f9ef4d12 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards e53ef5c895 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 6fd16afad0 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards ade2f0c447 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 5a81cdead8 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 0611b2b6df 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 2df96e5982 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 28657532c0 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 4a60fef982 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 55a005c03a 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards d488cadaff 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards ab3e7552c9 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 099d426846 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 8bf71148ba 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 1aa09c9e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 4220f91247 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 655630692b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 2c66720dc2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 6736bd40b0 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 67c1011b89 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 8c76e28b32 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 6466e5b73b 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d07fb31402 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 520f617b8c 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards e006d20a7e 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards d0c4b4420b 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 0fdf9314de 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards a36acc7e59 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 31da94eca3 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards f4101169d3 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 585dca773b 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards ea35bbde20 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards a250a2c011 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards e21b53fd9a 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 7de3c09bd6 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards e12789585e 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 44b17f7e59 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards a3a92098d5 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards a529f2b8be 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 52ca284001 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 16371344e0 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 55c83b6936 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 8500ee16fa 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards b11ee28046 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 62dcb6be60 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 48712973d6 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards c9a019a51a 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 3819152073 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 283a417612 88: onsuccess: 1: Success after gcc: 20 commits discards 0771183c77 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 2506632d75 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards bdce2ac01a 85: onsuccess: 2: Success after binutils: 4 commits discards 9ade228813 84: onsuccess: 2: Success after gcc: 9 commits discards 47c3a850bc 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards a557f4dbe0 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 372b2ac658 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 1e5110bf00 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 9809502afe 79: onsuccess: 1: Successful build after gcc: 3 commits discards 7c43b843ab 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 9c3ed7c27f 77: force: 2: Successful build after gcc: 32 commits discards c51b03f19d 76: onsuccess: 2: Successful build after binutils: 10 commits discards 6d20251af2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 2ca9e6b3c1 74: onsuccess: 2: Successful build after gcc: 13 commits discards e9fdbbdbb2 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards e7af0b45f2 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 63524d1fa4 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1e77c6bca6 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 3ab930845f 69: onsuccess: 2: Successful build after baseline build: no [...] discards 4777b33d30 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards d063059b07 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bff996804f 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards c8f8552414 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 8649af42c6 64: onsuccess: 2: Successful build after gcc: 7 commits discards ea643cbd23 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 341a54ecc5 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1f9eeee305 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 07f02e7124 60: onsuccess: 1: Successful build after gcc: 15 commits discards 293b7ea278 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards c8636c2042 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards ee74832be8 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 6453a596f2 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards dc7c0110ee 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0b00dffb7e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards eedd21a439 53: onsuccess: 2: Successful build after gcc: 5 commits discards 5428c6e577 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards f91be039ee 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 121679d000 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards c7bae43b54 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 41072eecf5 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards fe5695379d 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6dced22d8c 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards ba5c9817de 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 30cb9ce6b9 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 398b451d1c 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards c3ed263c57 42: onsuccess: 2: Successful build after gcc: 2 commits discards 64bb8724ae 41: onsuccess: 2: Successful build after baseline build: no [...] discards 0e1e68c1c7 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 457a838674 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 88ea6e373d 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9a82deaf09 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2645c6f7ec 41: onsuccess: 2: Successful build after baseline build: no [...] new 5a755ce570 42: onsuccess: 2: Successful build after gcc: 2 commits new 157c628e18 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 7000d9480c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6d09b9354c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 41dfc5430e 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 2d9e00ca61 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new cff74e1b22 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 9e8c011283 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 5d2d247355 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 435f42b3fa 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 59bcb84a77 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 1f34fdf8e6 53: onsuccess: 2: Successful build after gcc: 5 commits new 178a4865d0 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7f09a53e5b 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4c9bffe094 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 8d496666e4 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 385281cff7 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new af4c7cb2b4 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 6d4538fa99 60: onsuccess: 1: Successful build after gcc: 15 commits new 23b22cbecd 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new a79f286b64 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8b385ff1b8 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new a24a10c930 64: onsuccess: 2: Successful build after gcc: 7 commits new 1f67d9b284 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 75981bf6d0 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 45e67ffbb0 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 7a9153f206 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2ca5ee087d 69: onsuccess: 2: Successful build after baseline build: no [...] new 87c21bb655 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 7edfba27ce 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e5aeb7928a 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 1a4f4f9229 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 74165f3c8f 74: onsuccess: 2: Successful build after gcc: 13 commits new 0b63f680d1 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 29f84e0a5c 76: onsuccess: 2: Successful build after binutils: 10 commits new 116adef768 77: force: 2: Successful build after gcc: 32 commits new b32084d20e 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 6b113239fb 79: onsuccess: 1: Successful build after gcc: 3 commits new 57277fbfde 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 0717c72393 81: onsuccess: 2: Success after binutils/gcc: 16 commits new e7ef387a6d 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 7e4cd4c665 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 4f76d2c8d3 84: onsuccess: 2: Success after gcc: 9 commits new f49f3fbcc1 85: onsuccess: 2: Success after binutils: 4 commits new f6a6f6e8ae 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 502efe2eb3 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 0617c8302d 88: onsuccess: 1: Success after gcc: 20 commits new 8d0aa589b7 89: onsuccess: 2: Success after binutils/gcc: 39 commits new e5e4074570 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 237a8278cf 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 60d3432bf1 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 3b8bdbfc85 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new 3b53d22a56 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new e59cc35961 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new eb2d00236c 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new f1891e42a4 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 904a1af05f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 6905a77008 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new c642153784 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new b2cf20ae98 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 9ed795ab61 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new bf98fbea7a 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 07db120b6c 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 90c42ee657 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 323a223e3e 106: onsuccess: #1527: 2: Success after gcc: 2 commits new a3c63e85b6 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 0b795bebc9 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 3bbb609891 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 4c5664b55e 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 11b09fd6fd 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new fd45360139 112: onsuccess: #1533: 2: Success after gcc: 5 commits new d1e0a4d1f7 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 8c8547ce9a 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 8152a2fbe4 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 66743fe5ce 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 8a89d87672 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new f6ea1fee85 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 45422693ae 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new db73ab08db 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 67c1dad625 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new af67af3263 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 7e1a112706 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new fc169844ad 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 3f7a3451aa 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 3c9ff417e9 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 48b8570fa6 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new d0643c32cb 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new f2102539cc 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 07a1e448ea 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 1f86a7de80 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 0ad5d579f3 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new b18efac88e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 1f351730bb 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 758f6ac094 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 36033ee4e8 136: onsuccess: #1561: 2: Success after binutils: 3 commits new f8450a4e96 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 5bd3750114 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new fc971084a2 139: onsuccess: #1566: 1: Success after gcc: 5 commits new dffe7e64a4 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 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 (8d3ce50bb6) \ 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 1728 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 39048 -> 38064 bytes 05-build_abe-bootstrap/console.log.xz | Bin 81024 -> 78636 bytes 06-check_regression/console.log.xz | Bin 2856 -> 3120 bytes 06-check_regression/mail-body.txt | 11 ------ 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 | 13 +------ mail/mail-subject.txt | 2 +- manifest.sh | 19 +++++----- 14 files changed, 48 insertions(+), 69 deletions(-)