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 8f1830b193 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards db4b5e1b6e 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards c89278ad42 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 23af48f50d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards b5073e015c 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards e144415d79 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards dbdfe38659 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 08ad8c5e00 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards 65dece7e6e 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards 30d8067b3c 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards 4cbb2323c5 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 1a95d390b7 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 99144ceb20 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards 2427a6e541 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards 2361bf8cd2 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 235e5da1cb 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards 0be9fe3b40 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 2e159c424d 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards ecd8fdf2c6 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards afa68c22c6 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 7369843715 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards b803da1498 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 197630f33a 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards e03fea1c78 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards f751ebe0e6 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 4340076d74 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 2f4145fa58 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards 7ca45609e4 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards e6131d811e 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards e2e7c8e051 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards bfbe2874ff 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 5a27be31a1 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 848939d72b 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards a6858a2332 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 68e955358a 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 64e7ebd51f 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 6de85b5071 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards d82fef84d1 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 769a566fab 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 62ee7971c2 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards ce6af7080c 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 8c92762909 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 3da63a48b6 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 18643dea4f 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 9ce40e9ca5 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards caa413966b 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards 4151e7bd6d 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 3d7296adbc 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 3446d7c940 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 9ca58a450b 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 77f160a8b4 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards c101ab7dfa 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards f8163cf810 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards defef53ca7 88: onsuccess: 1: Success after gcc: 20 commits discards 7cfcba9a33 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards 70ea99e876 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards b35318e71e 85: onsuccess: 2: Success after binutils: 4 commits discards 2f36657552 84: onsuccess: 2: Success after gcc: 9 commits discards 0d6756a9a4 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 353e9657ee 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 706a0f2f4d 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards c9f104817b 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 9ba08bbaf5 79: onsuccess: 1: Successful build after gcc: 3 commits discards 72d4d2e384 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards c829258f47 77: force: 2: Successful build after gcc: 32 commits discards 4d97984824 76: onsuccess: 2: Successful build after binutils: 10 commits discards 9e6e00c077 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 6cf842652b 74: onsuccess: 2: Successful build after gcc: 13 commits discards 5c54365a28 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 23b5db938e 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 1c7d38c1ac 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a20c0469fc 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 00976aca70 69: onsuccess: 2: Successful build after baseline build: no [...] discards c35b1bde18 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 5314aaa81f 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3267ddd7ac 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards e397509ff9 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 09c5984d61 64: onsuccess: 2: Successful build after gcc: 7 commits discards 76f3d48474 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9b40d67311 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 443f71d456 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards a2bf100a15 60: onsuccess: 1: Successful build after gcc: 15 commits discards 2749a7ac8b 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 6a5e223314 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards c98c0fcbb5 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards a4496ef2c2 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 51fbd39765 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f26fd6c241 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e31bfcf08a 53: onsuccess: 2: Successful build after gcc: 5 commits discards c94291233a 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a926ec0b45 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 096025cc3e 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 27ef903bac 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 60c0ddcc49 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 459a7ad7a4 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ad2df3fafe 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 022d0ba10c 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards f6de4a8d54 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards b71aedf8c0 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 77e3d060a8 42: onsuccess: 2: Successful build after gcc: 2 commits discards 0dcedb1613 41: onsuccess: 2: Successful build after baseline build: no [...] new 4cf10b8506 41: onsuccess: 2: Successful build after baseline build: no [...] new 49311f5c3a 42: onsuccess: 2: Successful build after gcc: 2 commits new d45bfae2b7 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new ddc7f5613c 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 06e4b189c9 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 79a0125829 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new aa392cb1ad 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 470ee5df1d 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 744599b3da 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 098f8f7aec 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new d0c83457c7 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 9cbb37b7d4 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 4c1657efc0 53: onsuccess: 2: Successful build after gcc: 5 commits new 71c3ebfc9a 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ce72b8dc9f 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5b53a91141 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 746a589261 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new ef6e76c601 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 21b291f444 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 0e2b130125 60: onsuccess: 1: Successful build after gcc: 15 commits new a46f45d2e2 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 4758f8de94 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 850a74c629 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 4333b2800d 64: onsuccess: 2: Successful build after gcc: 7 commits new 0586d8b9b6 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 3fcb3b306c 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new eff327312c 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 82df31960d 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 079337575e 69: onsuccess: 2: Successful build after baseline build: no [...] new 17b233b1e1 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new cef193f809 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d694358cc6 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new b14b850b71 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 3de611b9dc 74: onsuccess: 2: Successful build after gcc: 13 commits new d4dda51522 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 5d9d7c6fa0 76: onsuccess: 2: Successful build after binutils: 10 commits new 17b90a2539 77: force: 2: Successful build after gcc: 32 commits new 9698ccefce 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 25914de365 79: onsuccess: 1: Successful build after gcc: 3 commits new 0be4202811 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 2c54e1ea16 81: onsuccess: 2: Success after binutils/gcc: 16 commits new c7ac9bbd36 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 181e222a81 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 40072a2a39 84: onsuccess: 2: Success after gcc: 9 commits new 05baa890cf 85: onsuccess: 2: Success after binutils: 4 commits new e006cab64c 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 15cdd1eb2c 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 48302773a3 88: onsuccess: 1: Success after gcc: 20 commits new 1b37ac2fdc 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 10d20ae65c 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 910e8bff15 91: onsuccess: #1473: 2: Success after gcc: 2 commits new b3cde0353c 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 8ae88b5e5d 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new aaa095dd46 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new e6a8df4eee 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new d07507c268 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new e07fda5110 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 70295c8fd8 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 3dd3ee9576 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new fbc33d5928 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 56a4fc0388 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new 939b417c7a 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new a4c5e08857 103: onsuccess: #1524: 2: Success after gcc: 2 commits new ed704332f0 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new e03d06225f 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 2d0e5ace5d 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 400e8e6c56 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new c522c61181 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 542f8c4d6e 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 673723d14a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 0b507b3288 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 8f1eb3b2f3 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 483e6b5694 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 81eb149ae2 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 0681bbd016 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new b258f715d9 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 65248d2428 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 0ac402a1f4 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 8273d194d8 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 18a59dc3f4 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 6ec32935de 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 24f0d3370a 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 307573428c 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new f91cb76422 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 5d2dff8ca1 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new c059c6c5ad 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new e4f6a77ff3 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 1a5fffa944 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new e79be4da83 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new a6876737f3 130: onsuccess: #1554: 2: Success after gcc: 9 commits new 8d6eae0e0b 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new 0d65924b1d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new 8067ae23d9 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new 01d8bb6c1d 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new 52046ff7cd 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new fb041ba4c0 136: onsuccess: #1561: 2: Success after binutils: 3 commits new eba784f4c0 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new af0dbee057 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 7a7a922740 139: onsuccess: #1566: 1: Success after gcc: 5 commits new dcc8751c7d 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 1557265622 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new d61ddcbb13 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...]

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 (8f1830b193) \ 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 1696 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 37640 -> 37768 bytes 05-build_abe-bootstrap/console.log.xz | Bin 79072 -> 79884 bytes 06-check_regression/console.log.xz | Bin 2792 -> 2536 bytes 07-update_baseline/console.log | 58 +++++++++++++++++----------------- 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 | 14 ++++---- 12 files changed, 41 insertions(+), 41 deletions(-)