This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts.

discards ab6b891a10 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...] discards be619e86f3 169: force: #594: 6: Success after gdb: 2 commits discards 296a37a081 168: onsuccess: #593: 6: Success after linux: 10 commits discards 8bbc5c4682 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] discards 7d6bc54e43 166: onsuccess: #590: 6: Success after gcc: 23 commits discards a63413d778 165: onsuccess: #589: 6: Success after binutils: 24 commits discards dc29f216cb 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] discards 66b7234e58 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] discards fc7e11aec8 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] discards abd1ac83ed 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] discards 5357cbcc12 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 commits discards de7d8fb757 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 commits discards 3f3457b8cb 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 commits discards 1ca69f4f65 157: onsuccess: #580: 6: Success after binutils/gcc/linux/gd [...] discards fb90277aaf 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 commits discards 03ee5b3ae3 155: onsuccess: #578: 6: Success after binutils/gcc/linux/gd [...] discards 4cdf826cb7 154: onsuccess: #577: 6: Success after binutils/gcc/linux/gl [...] discards 22658f302b 153: onsuccess: #576: 6: Success after binutils/gcc/linux/gl [...] discards 8868e0ae67 152: onsuccess: #575: 6: Success after binutils/gcc/linux/gl [...] discards 4ba437f28c 151: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards 54174eeebf 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/gd [...] discards f121f4e9b2 149: onsuccess: #572: 6: Success after binutils/gcc/linux/gd [...] discards bed8e6fabe 148: onsuccess: #571: 6: Success after binutils/gcc/linux/gd [...] discards d961ebacbc 147: onsuccess: #570: 6: Success after binutils/gcc/linux/gl [...] discards 1ddfe534bd 146: onsuccess: #569: 6: Success after binutils/gcc/linux/gd [...] discards 43d9cc7d7f 145: onsuccess: #568: 6: Success after binutils/gcc/linux/gl [...] discards f4f151e470 144: onsuccess: #567: 4: Success after gcc: 12 commits discards b52658b352 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g1 [...] discards 712bf0e206 142: force: #565: 6: Success after gcc: 8 commits discards 712de47abf 141: onsuccess: #564: 6: Success after linux: 3224 commits discards a3866c2d97 140: onsuccess: #563: 6: Success after glibc: 2 commits discards 42b9390754 139: onsuccess: #561: 6: Success after binutils: 23 commits discards 488035ae66 138: onsuccess: #559: 6: Success after binutils/gcc/linux/gd [...] discards 5e20908995 137: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 2dd7361643 136: onsuccess: #557: 6: Success after binutils/gcc/linux/gl [...] discards 23f0cca250 135: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 962b1dd1c6 134: onsuccess: #555: 6: Success after binutils/gcc/linux/gl [...] discards 62a3c293a5 133: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards 2845500303 132: onsuccess: #553: 4: Success after basepoints/gcc-13-449 [...] discards a863fc3a10 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g4 [...] discards 8ac01a646e 130: force: #551: 6: Success after gcc: 10 commits discards 94944adaaa 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 1a006d9784 128: onsuccess: #546: 6: Success after binutils/gcc/linux/gd [...] discards e5ab9ed33e 127: onsuccess: #545: 6: Success after binutils/gcc/linux/gl [...] discards 59c79e3839 126: onsuccess: #544: 6: Success after binutils/gcc/linux/gd [...] discards 65c978ba6c 125: onsuccess: #543: 6: Success after binutils/gcc/linux/gd [...] discards 857a5e27aa 124: onsuccess: #542: 6: Success after binutils/gcc/linux/gl [...] discards 09335e48d7 123: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards 57da77d76e 122: onsuccess: #540: 6: Success after binutils/gcc/linux/gl [...] discards faa94a03f8 121: onsuccess: #539: 6: Success after binutils/gcc/linux/gd [...] discards 82623d5c02 120: onsuccess: #538: 6: Success after binutils/gcc/linux/gd [...] discards 1d6e85f29d 119: onsuccess: #537: 6: Success after binutils/gcc/linux/gd [...] discards 90005fe428 118: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards fcf1196ad1 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 commits discards 219c604d50 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/gd [...] discards 6f1a1e2958 115: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 7923555308 114: onsuccess: #532: 6: Success after binutils/gcc/linux/gd [...] discards 3a00e971da 113: onsuccess: #531: 6: Success after binutils/gcc/linux/gd [...] discards fc10dc4dc8 112: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 691de6da42 111: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards 6f9cea2220 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 commits discards f1c9e698fa 109: onsuccess: #527: 6: Success after binutils/gcc/linux/gd [...] discards d5e3096916 108: onsuccess: #526: 6: Success after binutils/gcc/linux/gl [...] discards ada9314df0 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 7c6d1d1b05 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 718dd58474 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 40af779b0b 104: force: #522: 6: Success after gcc: 24 commits discards ef36aec590 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 279061c00e 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] discards e89e7c0bcb 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] discards c58f8c93f7 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 4a2585a61b 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] discards bca4e23796 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] discards 2f3e3e14c7 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] discards 97bc9c3250 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] discards 1d313cff63 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] discards 73ead3f053 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] discards 2ede59f14f 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] discards 2a4fef852b 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] discards 60dc4b9aed 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] discards c9a4e63ef2 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] discards 57a5185f0b 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] discards fae703663c 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] discards 992c1464fc 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] discards 0bf1cde2a6 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] discards 052a34c4b0 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] discards 435973622a 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] discards 77c3f6b7af 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] discards 20f4c4f314 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] discards 77ed944f9e 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] discards 641aa3ab87 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] discards f7e03b1308 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 8487b6ecaf 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] discards 6ed8db0741 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] discards 5e5bc04e50 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] discards 48192906a1 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 8690560b15 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] discards 5c8bedd0ae 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] discards b0f3224161 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] discards b3d789be50 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] discards 2777177be7 70: onsuccess: #486: 5: Success after gdb: 7 commits new 89607dd45b 70: onsuccess: #486: 5: Success after gdb: 7 commits new 90aa39d69a 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] new addb1fe35b 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] new 5199a949bc 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] new 8c16ac806f 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] new 66120a3330 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 210fdb5a1a 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] new c50f4fdff6 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] new d37749350a 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] new 7c2a38060d 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 2ef7642d44 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new 8fad271ab7 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] new 57c3dbbc4a 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] new 9fb9ed6bfc 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] new 8b77a1e654 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] new eb62a2a5ae 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] new 78ebd2b4fd 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] new 85fd161713 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] new b5b6828d03 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] new 2a51f4f43b 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] new c30163e342 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] new 6a13a51a7f 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] new 8e655e29fb 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] new 48496dffe9 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] new f22485ed5b 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] new cc3dce60e3 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] new de065daa1b 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] new 40465fd873 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] new ae84d1df71 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] new 7603f74561 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] new 78f5857f67 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new ce1f5740a2 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] new 9b7b860833 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] new e01da887ca 103: onsuccess: #520: 6: Success after binutils: 10 commits new ac9ac9d2a3 104: force: #522: 6: Success after gcc: 24 commits new 4856a9d5ba 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] new dbc2419082 106: onsuccess: #524: 1: Success after gcc: 11 commits new 1ab9554b35 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 996ae43634 108: onsuccess: #526: 6: Success after binutils/gcc/linux/gl [...] new 4766326797 109: onsuccess: #527: 6: Success after binutils/gcc/linux/gd [...] new 5d46c7041b 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 commits new 38353e178a 111: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new d2e51c6261 112: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 41121d81a0 113: onsuccess: #531: 6: Success after binutils/gcc/linux/gd [...] new 6d833808be 114: onsuccess: #532: 6: Success after binutils/gcc/linux/gd [...] new 0ae51aa1ec 115: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 4a0e6e0532 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/gd [...] new a30453359e 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 commits new 656533297f 118: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 5a7094bbbd 119: onsuccess: #537: 6: Success after binutils/gcc/linux/gd [...] new bc4646ae7f 120: onsuccess: #538: 6: Success after binutils/gcc/linux/gd [...] new d4560ddb11 121: onsuccess: #539: 6: Success after binutils/gcc/linux/gd [...] new e01dc0bb36 122: onsuccess: #540: 6: Success after binutils/gcc/linux/gl [...] new 867ff4e151 123: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 877d88dceb 124: onsuccess: #542: 6: Success after binutils/gcc/linux/gl [...] new 9430c70bf6 125: onsuccess: #543: 6: Success after binutils/gcc/linux/gd [...] new 6bbde3e56b 126: onsuccess: #544: 6: Success after binutils/gcc/linux/gd [...] new 483893be3c 127: onsuccess: #545: 6: Success after binutils/gcc/linux/gl [...] new a11ee60126 128: onsuccess: #546: 6: Success after binutils/gcc/linux/gd [...] new 659ca76ab8 129: onsuccess: #548: 6: Success after binutils: 8 commits new 12438e923f 130: force: #551: 6: Success after gcc: 10 commits new adae5251c4 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g4 [...] new adad124829 132: onsuccess: #553: 4: Success after basepoints/gcc-13-449 [...] new 1607cf3a40 133: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 9ab80ba5dc 134: onsuccess: #555: 6: Success after binutils/gcc/linux/gl [...] new ecc1099a04 135: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 251b24678a 136: onsuccess: #557: 6: Success after binutils/gcc/linux/gl [...] new 1299c4f58f 137: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 80c95c07e5 138: onsuccess: #559: 6: Success after binutils/gcc/linux/gd [...] new 0c4b92efbd 139: onsuccess: #561: 6: Success after binutils: 23 commits new 2f60cb637e 140: onsuccess: #563: 6: Success after glibc: 2 commits new c4a4bea753 141: onsuccess: #564: 6: Success after linux: 3224 commits new f738135d9e 142: force: #565: 6: Success after gcc: 8 commits new 93d9a601e5 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g1 [...] new 73ba04a8ed 144: onsuccess: #567: 4: Success after gcc: 12 commits new fb21f6eda7 145: onsuccess: #568: 6: Success after binutils/gcc/linux/gl [...] new f42020c183 146: onsuccess: #569: 6: Success after binutils/gcc/linux/gd [...] new 3412626f7a 147: onsuccess: #570: 6: Success after binutils/gcc/linux/gl [...] new fa07efc600 148: onsuccess: #571: 6: Success after binutils/gcc/linux/gd [...] new 9a231743be 149: onsuccess: #572: 6: Success after binutils/gcc/linux/gd [...] new 592653f1e8 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/gd [...] new 9ed41dd3d9 151: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new 93aff75ff8 152: onsuccess: #575: 6: Success after binutils/gcc/linux/gl [...] new f8c9a92c6e 153: onsuccess: #576: 6: Success after binutils/gcc/linux/gl [...] new 5588c5e625 154: onsuccess: #577: 6: Success after binutils/gcc/linux/gl [...] new b103999458 155: onsuccess: #578: 6: Success after binutils/gcc/linux/gd [...] new 5ff6105e32 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 commits new 9b6e221f85 157: onsuccess: #580: 6: Success after binutils/gcc/linux/gd [...] new fa76323652 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 commits new f8db3471e4 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 commits new ea516c9436 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 commits new c50f224204 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] new 88e95269a9 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] new ffe5e8022c 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] new a9d14da3b6 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] new 4e542de2c0 165: onsuccess: #589: 6: Success after binutils: 24 commits new 8c11aefdc9 166: onsuccess: #590: 6: Success after gcc: 23 commits new 698b7456a7 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] new 220cb4b43f 168: onsuccess: #593: 6: Success after linux: 10 commits new 1da36fdef8 169: force: #594: 6: Success after gdb: 2 commits new b79157036f 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...] new 327068aaa9 171: onsuccess: #596: 5: Success after gdb: 21 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 (ab6b891a10) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]

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 1704 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 39776 -> 40124 bytes 05-build_abe-gcc/console.log.xz | Bin 215176 -> 216508 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8908 -> 8880 bytes 08-build_abe-glibc/console.log.xz | Bin 244656 -> 244644 bytes 09-build_abe-gdb/console.log.xz | Bin 37260 -> 37160 bytes 10-check_regression/console.log.xz | Bin 3688 -> 3032 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 12 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 4 - 10-check_regression/trigger-bisect | 2 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1066 ------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 4 - 28 files changed, 46 insertions(+), 1131 deletions(-) delete mode 100644 10-check_regression/results.regressions delete mode 100644 10-check_regression/trigger-bisect delete mode 100644 10-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh