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 d61ddcbb13 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards 1557265622 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards dcc8751c7d 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards 7a7a922740 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards af0dbee057 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards eba784f4c0 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards fb041ba4c0 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards 52046ff7cd 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 01d8bb6c1d 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 8067ae23d9 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 0d65924b1d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 8d6eae0e0b 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards a6876737f3 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards e79be4da83 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 1a5fffa944 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards e4f6a77ff3 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards c059c6c5ad 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 5d2dff8ca1 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards f91cb76422 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 307573428c 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 24f0d3370a 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 6ec32935de 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 18a59dc3f4 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 8273d194d8 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 0ac402a1f4 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 65248d2428 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards b258f715d9 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 0681bbd016 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 81eb149ae2 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 483e6b5694 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 8f1eb3b2f3 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 0b507b3288 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 673723d14a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 542f8c4d6e 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards c522c61181 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 400e8e6c56 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 2d0e5ace5d 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards e03d06225f 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards ed704332f0 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards a4c5e08857 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 939b417c7a 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 56a4fc0388 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards fbc33d5928 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 3dd3ee9576 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 70295c8fd8 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards e07fda5110 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards d07507c268 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards e6a8df4eee 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards aaa095dd46 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 8ae88b5e5d 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards b3cde0353c 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 910e8bff15 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 10d20ae65c 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 1b37ac2fdc 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards 48302773a3 88: onsuccess: 1: Success after gcc: 20 commits discards 15cdd1eb2c 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards e006cab64c 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 05baa890cf 85: onsuccess: 2: Success after binutils: 4 commits discards 40072a2a39 84: onsuccess: 2: Success after gcc: 9 commits discards 181e222a81 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards c7ac9bbd36 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 2c54e1ea16 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards 0be4202811 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 25914de365 79: onsuccess: 1: Successful build after gcc: 3 commits discards 9698ccefce 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 17b90a2539 77: force: 2: Successful build after gcc: 32 commits discards 5d9d7c6fa0 76: onsuccess: 2: Successful build after binutils: 10 commits discards d4dda51522 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 3de611b9dc 74: onsuccess: 2: Successful build after gcc: 13 commits discards b14b850b71 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards d694358cc6 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards cef193f809 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 17b233b1e1 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 079337575e 69: onsuccess: 2: Successful build after baseline build: no [...] discards 82df31960d 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards eff327312c 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3fcb3b306c 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 0586d8b9b6 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4333b2800d 64: onsuccess: 2: Successful build after gcc: 7 commits discards 850a74c629 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 4758f8de94 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a46f45d2e2 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards 0e2b130125 60: onsuccess: 1: Successful build after gcc: 15 commits discards 21b291f444 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards ef6e76c601 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 746a589261 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 5b53a91141 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards ce72b8dc9f 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 71c3ebfc9a 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 4c1657efc0 53: onsuccess: 2: Successful build after gcc: 5 commits discards 9cbb37b7d4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d0c83457c7 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 098f8f7aec 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 744599b3da 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 470ee5df1d 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards aa392cb1ad 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 79a0125829 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 06e4b189c9 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards ddc7f5613c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d45bfae2b7 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 49311f5c3a 42: onsuccess: 2: Successful build after gcc: 2 commits new d82e367d8f 42: onsuccess: 2: Successful build after gcc: 2 commits new 8ebc7de16b 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new d6015fd7b5 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f11ef52def 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new a88c518f96 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new ce85bff53a 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a4e7c553aa 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0b80d778e8 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 2681a96aca 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c3ff845b96 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new a92791edc4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 8859bd7423 53: onsuccess: 2: Successful build after gcc: 5 commits new 302df28d35 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 16b9478125 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d723014e30 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 8bab4aea72 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 59c4c0c747 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 3e6dfd59b9 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 799a54e448 60: onsuccess: 1: Successful build after gcc: 15 commits new a1ef177779 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new a105c79cb9 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 645d55db21 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 9ef0685b0e 64: onsuccess: 2: Successful build after gcc: 7 commits new 5c64e704ae 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new d119904856 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 68fda19d4f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 776859926b 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f77e97724c 69: onsuccess: 2: Successful build after baseline build: no [...] new c7140e48b3 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 7abd7065f8 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 2da2369004 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 25d6b2d336 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 8549b36f9d 74: onsuccess: 2: Successful build after gcc: 13 commits new 934c73b244 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new f3e5e06dbf 76: onsuccess: 2: Successful build after binutils: 10 commits new 3f9b94e076 77: force: 2: Successful build after gcc: 32 commits new b018776a85 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 0ec2b1aecc 79: onsuccess: 1: Successful build after gcc: 3 commits new f241733788 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 40a8fcf668 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 1c788a79cc 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 28b471ff0a 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 9f9d7a0c33 84: onsuccess: 2: Success after gcc: 9 commits new b3533c1cfe 85: onsuccess: 2: Success after binutils: 4 commits new 597d5bae0f 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 22db97d9fd 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new ac87c3d470 88: onsuccess: 1: Success after gcc: 20 commits new 91d79f3538 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 15c77bbf8e 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 9efdb80e6f 91: onsuccess: #1473: 2: Success after gcc: 2 commits new 6c0fba64f9 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 996d3c4887 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new b04940768e 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new 8020a54b39 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 4e1b8d523a 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new 9e5fc61408 97: onsuccess: #1481: 2: Success after gcc: 8 commits new f736f1f98c 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new d8948cda8d 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 41e03433e7 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new a7486bdffd 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 654d968bfd 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 6db0bdbb1f 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 57e28253ed 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 4333429aff 105: onsuccess: #1526: 2: Success after gcc: 2 commits new a685304c92 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 9137420bea 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 669f8c689e 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 6fc9a2be25 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 0b71ac8643 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new d8164a8a45 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new caf4f9af2f 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 96e3f4a1cc 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 37fabfd79b 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new bfac9a1fec 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 41e65df0da 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 935571ad1d 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 83cf4376dd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new efad3665d5 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new f3869da67b 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 4023415c52 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new be50ea5e24 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new a70152c538 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new c5e487bc0b 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 334a74405e 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 6959193559 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 2f45cad5ac 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new e9c3847eda 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 61d2e43fb9 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new f81385134f 130: onsuccess: #1554: 2: Success after gcc: 9 commits new a1072df597 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 95ecfe5d38 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 4a3d6a598f 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new e3dc3263a6 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 816b54f8ce 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 46fc25c5fe 136: onsuccess: #1561: 2: Success after binutils: 3 commits new eeeae63b7f 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new 787df8d6d6 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 8f31cf030e 139: onsuccess: #1566: 1: Success after gcc: 5 commits new 3bf2cdcb54 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 60d42435ef 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 6686a2cca7 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new b721a53d64 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 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 (d61ddcbb13) \ 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 1676 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 37768 -> 37652 bytes 05-build_abe-bootstrap/console.log.xz | Bin 79884 -> 272200 bytes 06-check_regression/console.log.xz | Bin 2536 -> 2844 bytes 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++-------- results | 2 +- 15 files changed, 37 insertions(+), 37 deletions(-)