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 8f3536796 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards ebb5ec7eb 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 71be77ab3 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 54f1f95c1 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards c313a9c4a 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards a733eb8e9 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards c684ec5c1 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards 5932a236f 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 0be3af258 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 2003a600d 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards db66cc1ed 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 1105b1b20 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 7dc5012d2 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards bdf39b3bf 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 5ef15448b 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards d52a73682 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards 6220f677b 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] discards f4170df95 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards baaabbc1c 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards b4f5a024c 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards eb362832d 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards 142d3e0e2 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards 20c1ef5e1 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 865865331 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards 7e1c26775 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 020470b03 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards c7ae78543 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 6ed924959 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards 84720f8db 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards ecf6092d4 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 1fc5da151 94: onsuccess: #1476: 2: Success after baseline build: no new [...] discards 2265af61c 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] discards 2e6f4ffae 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 7a95a3e4c 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards ed3611c3a 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards d9e316b1b 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards e181b1e8b 88: onsuccess: 1: Success after gcc: 20 commits discards a638d60b2 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] discards 9d4ae449a 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] discards 556b94f89 85: onsuccess: 2: Success after binutils: 4 commits discards a525d4fa2 84: onsuccess: 2: Success after gcc: 9 commits discards ef019a76a 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 5548aab83 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 40dae8233 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards f1500a79e 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 1973ed94a 79: onsuccess: 1: Successful build after gcc: 3 commits discards 17d7e065c 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards b7aeb71fe 77: force: 2: Successful build after gcc: 32 commits discards 36fb60659 76: onsuccess: 2: Successful build after binutils: 10 commits discards 47080fd75 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a753cddac 74: onsuccess: 2: Successful build after gcc: 13 commits discards 94dbceedd 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6e7ef6b5e 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards 38f587b29 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ff29a7721 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards df7a82076 69: onsuccess: 2: Successful build after baseline build: no n [...] discards 148194542 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 364de079b 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1999b0917 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 4690e8cdd 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 1096d171d 64: onsuccess: 2: Successful build after gcc: 7 commits discards 62f36bfd9 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 5e6b5a1ba 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 05c8189ff 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards cdc8d7b49 60: onsuccess: 1: Successful build after gcc: 15 commits discards a51259b13 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards b4bbc220d 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] discards 8904c2c90 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards e0c36a21d 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 68f4397b0 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 92bea6257 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 13acdf7ca 53: onsuccess: 2: Successful build after gcc: 5 commits discards ad9fe76e1 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 48b65a688 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 34ad37759 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 17306260c 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 4c21d5192 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards b1d8c72a7 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bdc33bc6f 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 6ab5d64d3 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 3ae096e11 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8b798e6dd 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards a6d5eba7b 42: onsuccess: 2: Successful build after gcc: 2 commits discards e4b532612 41: onsuccess: 2: Successful build after baseline build: no n [...] discards 67a3d6e7f 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 467515cc2 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ac71046e3 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 4b918533e 37: onsuccess: 2: Successful build after gcc: 2 commits discards 4ddd94893 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 3e57ff107 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 733d65d5b 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 28b8cfb62 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 070a5b356 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards aad193669 31: onsuccess: 2: Successful build after gcc: 8 commits discards 2675769fe 30: onsuccess: 2: Successful build after gcc: 7 commits discards ed6a650d2 29: onsuccess: 2: Successful build after binutils: 5 commits discards 4910b903f 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d5c5768d1 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 5b4a86f7b 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits discards 3d56489bf 25: onsuccess: binutils-gcc: 2 discards 069807280 24: onsuccess: binutils-gcc: 2 new 9fe4c6bc6 24: onsuccess: binutils-gcc: 2 new c6cee18ea 25: onsuccess: binutils-gcc: 2 new 38dae2829 26: onsuccess: 2: Successful build after binutils/gcc: 15 commits new 0a8d27768 27: onsuccess: 2: Successful build after binutils/gcc: 9 commits new b5400579e 28: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3cb25474a 29: onsuccess: 2: Successful build after binutils: 5 commits new 2bd80f533 30: onsuccess: 2: Successful build after gcc: 7 commits new 32317af3d 31: onsuccess: 2: Successful build after gcc: 8 commits new c0f1b33b6 32: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 76c7c7b49 33: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e5d4a7867 34: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 64bfa906f 35: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 326c1ffb9 36: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4356068f9 37: onsuccess: 2: Successful build after gcc: 2 commits new c6cdc3fb6 38: onsuccess: 2: Successful build after binutils/gcc: 3 commits new a9b000fc4 39: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 6f09ee769 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 7999368fd 41: onsuccess: 2: Successful build after baseline build: no n [...] new fa5f5c8d9 42: onsuccess: 2: Successful build after gcc: 2 commits new b2e6973ce 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new 4e38aa9c8 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ddc091e7a 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 2010ac3b1 46: onsuccess: 2: Successful build after binutils/gcc: 2 commits new b51ae64d0 47: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 43068431b 48: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4cd43a522 49: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 9fb1275b6 50: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 378f309bc 51: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 37d3b8d88 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new f0e2714d0 53: onsuccess: 2: Successful build after gcc: 5 commits new d1da4434e 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 90f3d37fc 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 62688ec6b 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 87c588c0e 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new 69a344bdc 58: force: 2: Successful build after gcc: tree.cc: Fix optimi [...] new dd7d119dd 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 721909222 60: onsuccess: 1: Successful build after gcc: 15 commits new abcb4eb38 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new c7c88d0d3 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1d0680235 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ccc195929 64: onsuccess: 2: Successful build after gcc: 7 commits new b0a2016e7 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new af37595c3 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new fb390a9ac 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1fb1ed7a4 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b846e2a28 69: onsuccess: 2: Successful build after baseline build: no n [...] new 4c6a4d98a 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 12ba011ab 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5ebf5caaa 72: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 0a4929635 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 07ad20e4a 74: onsuccess: 2: Successful build after gcc: 13 commits new c06cad2ac 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new edc514aa1 76: onsuccess: 2: Successful build after binutils: 10 commits new b9024e52f 77: force: 2: Successful build after gcc: 32 commits new 0081d60a1 78: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new b87cfbdb5 79: onsuccess: 1: Successful build after gcc: 3 commits new 7a58becd5 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new a32a8ddd0 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 2ef88b122 82: onsuccess: 2: Success after binutils/gcc: 26 commits new 8967b82ab 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 85f9bf1fa 84: onsuccess: 2: Success after gcc: 9 commits new 55b219c5a 85: onsuccess: 2: Success after binutils: 4 commits new 6bb456a4e 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 w [...] new 442f95e73 87: force: 1: Failure after gcc: Fix up dump_printf_loc forma [...] new 799a4b42a 88: onsuccess: 1: Success after gcc: 20 commits new 64a6b781e 89: onsuccess: 2: Success after binutils/gcc: 39 commits new ff7b796ca 90: onsuccess: #1472: 2: Success after gcc: 2 commits new bf295f4b2 91: onsuccess: #1473: 2: Success after gcc: 2 commits new ea3fd4f2b 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new bbb38a36d 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-2393 [...] new a72e7a275 94: onsuccess: #1476: 2: Success after baseline build: no new [...] new 3ffa32a4d 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 1da91e1fc 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new f82cf5db3 97: onsuccess: #1481: 2: Success after gcc: 8 commits new 87acbddd1 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new ff4cf8f26 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new 2ca3f4197 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new c5104705f 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new c023a1700 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new d882c94f1 103: onsuccess: #1524: 2: Success after gcc: 2 commits new b6a4d13c3 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new 4bc7c7f4c 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 4a17a1fe7 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 74f65273b 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new fac94f433 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-271 [...] new 7ed15e39a 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new b3d82ff0a 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 05408733f 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new a13fb6d4e 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 23b2d0b02 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new 9938ab163 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 1cfd45ab2 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new 5cd78fe3a 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 670eb4aee 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new 500f95dbd 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 3766c68cf 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 201a306e9 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 01bf6b40a 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new 236ca15d1 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 298d40a9a 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 16f50db6f 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 76540e1b6 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 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 (8f3536796) \ 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 1708 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 38828 -> 37812 bytes 05-build_abe-bootstrap/console.log.xz | Bin 272636 -> 272892 bytes 06-check_regression/console.log.xz | Bin 2896 -> 2648 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(-)