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 09955aed76 169: force: #594: 6: Success after gdb: 2 commits discards 97096cca32 168: onsuccess: #593: 6: Success after linux: 10 commits discards 09017a85a1 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] discards 89b8d989f6 166: onsuccess: #590: 6: Success after gcc: 23 commits discards ab490e0aa8 165: onsuccess: #589: 6: Success after binutils: 24 commits discards 074dced2eb 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] discards 834f41a335 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] discards af6e343a26 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] discards 5eea4398e0 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] discards 1a8b0faadf 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 commits discards 5f3840db4c 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 commits discards 1a45934f19 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 commits discards 1c5340a236 157: onsuccess: #580: 6: Success after binutils/gcc/linux/gd [...] discards f1a732e8ad 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 commits discards 9550b49f0a 155: onsuccess: #578: 6: Success after binutils/gcc/linux/gd [...] discards 7245277613 154: onsuccess: #577: 6: Success after binutils/gcc/linux/gl [...] discards 9d891ea079 153: onsuccess: #576: 6: Success after binutils/gcc/linux/gl [...] discards 3179353a8e 152: onsuccess: #575: 6: Success after binutils/gcc/linux/gl [...] discards 136bc1d861 151: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] discards 70761ffd14 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/gd [...] discards 3287e61bb3 149: onsuccess: #572: 6: Success after binutils/gcc/linux/gd [...] discards 84f00bc9c6 148: onsuccess: #571: 6: Success after binutils/gcc/linux/gd [...] discards 0dd20d486b 147: onsuccess: #570: 6: Success after binutils/gcc/linux/gl [...] discards bd58d42f1e 146: onsuccess: #569: 6: Success after binutils/gcc/linux/gd [...] discards c6c8b5a102 145: onsuccess: #568: 6: Success after binutils/gcc/linux/gl [...] discards e90f2306a0 144: onsuccess: #567: 4: Success after gcc: 12 commits discards ebca3d720c 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g1 [...] discards 84d705277f 142: force: #565: 6: Success after gcc: 8 commits discards cc018db922 141: onsuccess: #564: 6: Success after linux: 3224 commits discards b9e4d74310 140: onsuccess: #563: 6: Success after glibc: 2 commits discards 3bca30535b 139: onsuccess: #561: 6: Success after binutils: 23 commits discards eed5db53bc 138: onsuccess: #559: 6: Success after binutils/gcc/linux/gd [...] discards 0cee58bb72 137: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] discards 056aee0abb 136: onsuccess: #557: 6: Success after binutils/gcc/linux/gl [...] discards 9bacc0afdb 135: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] discards 25cfce9d95 134: onsuccess: #555: 6: Success after binutils/gcc/linux/gl [...] discards e8754ad3f7 133: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] discards e0fdf00050 132: onsuccess: #553: 4: Success after basepoints/gcc-13-449 [...] discards dcf4e8de82 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g4 [...] discards c675f50f41 130: force: #551: 6: Success after gcc: 10 commits discards f8406f2994 129: onsuccess: #548: 6: Success after binutils: 8 commits discards be31853321 128: onsuccess: #546: 6: Success after binutils/gcc/linux/gd [...] discards 9716f816e7 127: onsuccess: #545: 6: Success after binutils/gcc/linux/gl [...] discards 3c179d3b26 126: onsuccess: #544: 6: Success after binutils/gcc/linux/gd [...] discards 6435277729 125: onsuccess: #543: 6: Success after binutils/gcc/linux/gd [...] discards 26346545bb 124: onsuccess: #542: 6: Success after binutils/gcc/linux/gl [...] discards 089c6f1cfd 123: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] discards 430347cbad 122: onsuccess: #540: 6: Success after binutils/gcc/linux/gl [...] discards c25051e697 121: onsuccess: #539: 6: Success after binutils/gcc/linux/gd [...] discards 47afec47fe 120: onsuccess: #538: 6: Success after binutils/gcc/linux/gd [...] discards d794d81736 119: onsuccess: #537: 6: Success after binutils/gcc/linux/gd [...] discards ae25188dd1 118: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] discards 0cc95137b8 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 commits discards 3053a4f7e6 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/gd [...] discards 62a1f3a3a0 115: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] discards 182ea9055e 114: onsuccess: #532: 6: Success after binutils/gcc/linux/gd [...] discards ad996ad22d 113: onsuccess: #531: 6: Success after binutils/gcc/linux/gd [...] discards 6fd0f37623 112: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] discards 0ca2744df1 111: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] discards 90e02b742f 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 commits discards c037484e0f 109: onsuccess: #527: 6: Success after binutils/gcc/linux/gd [...] discards 95ecd92dec 108: onsuccess: #526: 6: Success after binutils/gcc/linux/gl [...] discards 6f62d10be2 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards f91116a48f 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 5479494fd4 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 1a1968f1ae 104: force: #522: 6: Success after gcc: 24 commits discards 82c880cf91 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 4696bdb340 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] discards 2583e1d2e1 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] discards 7f28d6382d 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 2d600b5f05 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] discards 9409ad5f98 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] discards a6627a8aa3 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] discards 19311d98c2 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] discards 1e4309c404 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] discards 202de2c2dd 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] discards 43aaa0e1ca 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] discards 6ade28eaef 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] discards 746cc5807a 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] discards 29bf6d03ad 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] discards 2cc5492c88 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] discards ad2222015a 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] discards 11563f4466 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] discards ea7bb1062c 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] discards c2a8cd8523 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] discards ebf0823b83 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] discards 2678fe0f1a 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] discards 09e1cdc27c 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] discards c0e9694584 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] discards a5a286102b 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] discards 073ccae00b 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 224d04a344 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] discards 59ad4bb232 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] discards 783c05de56 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] discards 9e9ca7ef5e 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 4a29b6e00e 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] discards 68e2a6fc39 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] discards c014648c9b 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] discards 327dfe21e7 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] discards cf5ea62fdf 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 45a6de9232 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] new 38f2fb6811 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] new 2777177be7 70: onsuccess: #486: 5: Success after gdb: 7 commits new b3d789be50 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] new b0f3224161 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] new 5c8bedd0ae 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] new 8690560b15 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] new 48192906a1 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 5e5bc04e50 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] new 6ed8db0741 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] new 8487b6ecaf 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] new f7e03b1308 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 641aa3ab87 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new 77ed944f9e 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] new 20f4c4f314 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] new 77c3f6b7af 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] new 435973622a 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] new 052a34c4b0 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] new 0bf1cde2a6 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] new 992c1464fc 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] new fae703663c 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] new 57a5185f0b 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] new c9a4e63ef2 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] new 60dc4b9aed 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] new 2a4fef852b 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] new 2ede59f14f 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] new 73ead3f053 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] new 1d313cff63 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] new 97bc9c3250 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] new 2f3e3e14c7 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] new bca4e23796 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] new 4a2585a61b 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] new c58f8c93f7 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new e89e7c0bcb 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] new 279061c00e 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] new ef36aec590 103: onsuccess: #520: 6: Success after binutils: 10 commits new 40af779b0b 104: force: #522: 6: Success after gcc: 24 commits new 718dd58474 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] new 7c6d1d1b05 106: onsuccess: #524: 1: Success after gcc: 11 commits new ada9314df0 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new d5e3096916 108: onsuccess: #526: 6: Success after binutils/gcc/linux/gl [...] new f1c9e698fa 109: onsuccess: #527: 6: Success after binutils/gcc/linux/gd [...] new 6f9cea2220 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 commits new 691de6da42 111: onsuccess: #529: 6: Success after binutils/gcc/linux/gd [...] new fc10dc4dc8 112: onsuccess: #530: 6: Success after binutils/gcc/linux/gl [...] new 3a00e971da 113: onsuccess: #531: 6: Success after binutils/gcc/linux/gd [...] new 7923555308 114: onsuccess: #532: 6: Success after binutils/gcc/linux/gd [...] new 6f1a1e2958 115: onsuccess: #533: 6: Success after binutils/gcc/linux/gd [...] new 219c604d50 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/gd [...] new fcf1196ad1 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 commits new 90005fe428 118: onsuccess: #536: 6: Success after binutils/gcc/linux/gd [...] new 1d6e85f29d 119: onsuccess: #537: 6: Success after binutils/gcc/linux/gd [...] new 82623d5c02 120: onsuccess: #538: 6: Success after binutils/gcc/linux/gd [...] new faa94a03f8 121: onsuccess: #539: 6: Success after binutils/gcc/linux/gd [...] new 57da77d76e 122: onsuccess: #540: 6: Success after binutils/gcc/linux/gl [...] new 09335e48d7 123: onsuccess: #541: 6: Success after binutils/gcc/linux/gl [...] new 857a5e27aa 124: onsuccess: #542: 6: Success after binutils/gcc/linux/gl [...] new 65c978ba6c 125: onsuccess: #543: 6: Success after binutils/gcc/linux/gd [...] new 59c79e3839 126: onsuccess: #544: 6: Success after binutils/gcc/linux/gd [...] new e5ab9ed33e 127: onsuccess: #545: 6: Success after binutils/gcc/linux/gl [...] new 1a006d9784 128: onsuccess: #546: 6: Success after binutils/gcc/linux/gd [...] new 94944adaaa 129: onsuccess: #548: 6: Success after binutils: 8 commits new 8ac01a646e 130: force: #551: 6: Success after gcc: 10 commits new a863fc3a10 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g4 [...] new 2845500303 132: onsuccess: #553: 4: Success after basepoints/gcc-13-449 [...] new 62a3c293a5 133: onsuccess: #554: 6: Success after binutils/gcc/linux/gd [...] new 962b1dd1c6 134: onsuccess: #555: 6: Success after binutils/gcc/linux/gl [...] new 23f0cca250 135: onsuccess: #556: 6: Success after binutils/gcc/linux/gl [...] new 2dd7361643 136: onsuccess: #557: 6: Success after binutils/gcc/linux/gl [...] new 5e20908995 137: onsuccess: #558: 6: Success after binutils/gcc/linux/gl [...] new 488035ae66 138: onsuccess: #559: 6: Success after binutils/gcc/linux/gd [...] new 42b9390754 139: onsuccess: #561: 6: Success after binutils: 23 commits new a3866c2d97 140: onsuccess: #563: 6: Success after glibc: 2 commits new 712de47abf 141: onsuccess: #564: 6: Success after linux: 3224 commits new 712bf0e206 142: force: #565: 6: Success after gcc: 8 commits new b52658b352 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g1 [...] new f4f151e470 144: onsuccess: #567: 4: Success after gcc: 12 commits new 43d9cc7d7f 145: onsuccess: #568: 6: Success after binutils/gcc/linux/gl [...] new 1ddfe534bd 146: onsuccess: #569: 6: Success after binutils/gcc/linux/gd [...] new d961ebacbc 147: onsuccess: #570: 6: Success after binutils/gcc/linux/gl [...] new bed8e6fabe 148: onsuccess: #571: 6: Success after binutils/gcc/linux/gd [...] new f121f4e9b2 149: onsuccess: #572: 6: Success after binutils/gcc/linux/gd [...] new 54174eeebf 150: onsuccess: #573: 6: Success after binutils/gcc/glibc/gd [...] new 4ba437f28c 151: onsuccess: #574: 6: Success after binutils/gcc/linux/gl [...] new 8868e0ae67 152: onsuccess: #575: 6: Success after binutils/gcc/linux/gl [...] new 22658f302b 153: onsuccess: #576: 6: Success after binutils/gcc/linux/gl [...] new 4cdf826cb7 154: onsuccess: #577: 6: Success after binutils/gcc/linux/gl [...] new 03ee5b3ae3 155: onsuccess: #578: 6: Success after binutils/gcc/linux/gd [...] new fb90277aaf 156: onsuccess: #579: 6: Success after binutils/gcc/gdb: 47 commits new 1ca69f4f65 157: onsuccess: #580: 6: Success after binutils/gcc/linux/gd [...] new 3f3457b8cb 158: onsuccess: #581: 6: Success after binutils/gcc/gdb: 25 commits new de7d8fb757 159: onsuccess: #582: 6: Success after binutils/gcc/gdb: 26 commits new 5357cbcc12 160: onsuccess: #583: 6: Success after binutils/gcc/gdb: 11 commits new abd1ac83ed 161: onsuccess: #584: 6: Success after binutils/gcc/linux/gl [...] new fc7e11aec8 162: onsuccess: #585: 6: Success after binutils/gcc/linux/gd [...] new 66b7234e58 163: onsuccess: #586: 6: Success after binutils/gcc/linux/gd [...] new dc29f216cb 164: onsuccess: #587: 6: Success after binutils/gcc/linux/gl [...] new a63413d778 165: onsuccess: #589: 6: Success after binutils: 24 commits new 7d6bc54e43 166: onsuccess: #590: 6: Success after gcc: 23 commits new 8bbc5c4682 167: onsuccess: #592: 6: Success after glibc-2.36.9000-416-g [...] new 296a37a081 168: onsuccess: #593: 6: Success after linux: 10 commits new be619e86f3 169: force: #594: 6: Success after gdb: 2 commits new ab6b891a10 170: force: #595: 5: Failure after gdb-13-branchpoint-245-gd [...]

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 (09955aed76) \ 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 1660 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 39984 -> 39776 bytes 05-build_abe-gcc/console.log.xz | Bin 215060 -> 215176 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8936 -> 8908 bytes 08-build_abe-glibc/console.log.xz | Bin 246068 -> 244656 bytes 09-build_abe-gdb/console.log.xz | Bin 39496 -> 37260 bytes 10-check_regression/console.log.xz | Bin 2752 -> 3688 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 8 +- 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 | 36 +- 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 | 8 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 6 +- 28 files changed, 1130 insertions(+), 37 deletions(-) create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/trigger-bisect create mode 100644 10-check_regression/trigger-notify create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh