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 7a40f8dc8fa 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g [...] discards b5af1592b53 142: force: #565: 6: Success after gcc: 8 commits discards 07517a82600 141: onsuccess: #564: 6: Success after linux: 3224 commits discards cf8f84daa16 140: onsuccess: #563: 6: Success after glibc: 2 commits discards e89b4a9f8b1 139: onsuccess: #561: 6: Success after binutils: 23 commits discards da1d5ef1aa6 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards ce3b1d130c8 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 719ce68851b 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards 166c41509e6 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 8f73bdf5b02 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards 55d9c4e8c57 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 351951aedd7 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] discards 1f4de2a27a3 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] discards 3d603a3146e 130: force: #551: 6: Success after gcc: 10 commits discards 21b59ed6335 129: onsuccess: #548: 6: Success after binutils: 8 commits discards fd2db5076f1 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards a521cc5ef3f 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards ad2067fefa0 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards 958ed3c8974 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 2437b1d1222 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 26a60fdc41c 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 99bb754d61f 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 7c6ce7054c0 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 4b5a3637cbc 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 11472b1792b 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards b133814ec69 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 4c47005e701 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards e4204655af4 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards 70fb08e866e 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 8a5b7830f8d 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards 603125501f0 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards be67d85a0aa 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 61a16e0a7e5 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards b3e35563c40 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 5e52d8aac52 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 6ae17aeceec 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards e3b2c590b64 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards f6b83fb1498 106: onsuccess: #524: 1: Success after gcc: 11 commits discards f1a5d84d3ce 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards e33e1df37a0 104: force: #522: 6: Success after gcc: 24 commits discards 6648e07f7a2 103: onsuccess: #520: 6: Success after binutils: 10 commits discards f36cd1a63a1 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards af1c5848502 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards 65e3469f0fb 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards 0ce5cc87561 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 020a822379e 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards eab6fff9952 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards ed235fa9d3b 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards b5533ac00d0 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards c74909ca0a6 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 2c6b8b6aca9 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 727f3a85106 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards e42eec3900d 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards 17473e95fe3 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards ce1171ec436 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards 9d2f7f58489 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards b19d9c803dc 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards 69a6df4253f 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards d6d22cc2b1a 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 1e99b06b351 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 2d830fae5be 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards f51c79504fe 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards 6b9156dd779 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards f480135fcb1 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards 01b3de8079c 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 8349696df4c 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards a495156938f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards aa5c2ce6324 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 4ba95a7a5f9 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 7e52c2d51d3 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards 035b31255fc 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 1c8d2a0bae6 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards e240223d15b 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards 8c7d6997f42 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 4695f0a206f 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards 88b65574a4c 68: force: #484: 6: Success after gdb: 6 commits discards ffa411f2f11 67: onsuccess: #483: 6: Success after linux: 384 commits discards 198bae50534 66: onsuccess: #482: 6: Success after glibc: 2 commits discards a520a4018ad 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 8c3971515fa 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 33a2ec80955 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards ab7f6ca1c2b 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards a670f5bc216 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 7ba10ac7384 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards 7da71fa75c5 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards bc744cdf378 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards 40de539abc3 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 391962dcd91 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards 755c6722f2f 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards a8ba5bba6c6 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards 6b56f13bd88 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards da965502904 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 885a0107f2b 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 06be5289910 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 5eb6614913f 49: force: #463: 6: Success after gcc: 18 commits discards 63441230beb 48: onsuccess: #461: 6: Success after binutils: 10 commits discards 3e9c46ad086 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards b4352d9f81b 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards 4651491e823 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards 21ca62f666d 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards 013e191f1e8 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new d06d779f4ff 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new b09387d8a7d 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new b5891eca76b 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new d3597f6070c 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 8a0b4f37ef5 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 2c5832e9edc 48: onsuccess: #461: 6: Success after binutils: 10 commits new 11efafa0c36 49: force: #463: 6: Success after gcc: 18 commits new 79b2c3b41fa 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new 5c4840c391e 51: onsuccess: #465: 1: Success after gcc: 10 commits new d349df7ac7e 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new cacd3da1b2a 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 1ef9f3ba813 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 71f18c00bf1 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 68dcf0c5f49 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new 57edb4e3707 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new 28f9e3c0916 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new e6cc68dd209 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 9ad284028f4 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new 2f7f9c0bfc4 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new 018b5d2e52c 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new e6c43c64df0 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new db92830f69e 64: onsuccess: #479: 6: Success after binutils: 14 commits new e1e092d3570 65: onsuccess: #480: 6: Success after gcc: 12 commits new df65e182766 66: onsuccess: #482: 6: Success after glibc: 2 commits new 4d8fca9eecb 67: onsuccess: #483: 6: Success after linux: 384 commits new 21db5c2dec4 68: force: #484: 6: Success after gdb: 6 commits new dae191f6fc3 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new 6578c164c86 70: onsuccess: #486: 5: Success after gdb: 7 commits new f510159ee4b 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new a75fe7f52ef 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new a8718892ef8 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new d8d0a36e3da 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new f0685c6b52c 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new 828383509e0 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new 3dd01a16741 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 4034f237bf1 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new 7473ae0be2b 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new 68c8fb660be 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new 9be147bbd1d 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new baf1de44676 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new dd59a01ce4f 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new d2553e21070 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new a0b4c7eef09 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new 8307b21ca39 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 60de68353b6 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new 09bddd4dec1 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new 0c83cb9c55a 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 38cf62a6056 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new a3cdcab8b9e 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new cc4b93f120a 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 239c041ce26 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 4ff9d54b20c 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 6aee2bd9420 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 8ecab06d304 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 74385d16549 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new e46ce733481 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 2efbff4d4a2 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 76d763cad88 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new f4d7c14317b 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 5bb205ac898 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new 5886206b590 103: onsuccess: #520: 6: Success after binutils: 10 commits new c252f937d3d 104: force: #522: 6: Success after gcc: 24 commits new 985665f89b2 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new a0114793418 106: onsuccess: #524: 1: Success after gcc: 11 commits new d872b1b7674 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new c5925d4a278 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new bbba19917fe 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new 4ea846a5d30 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new 04d461ff42d 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new c0d3ea350fc 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new d47a1ecdfcb 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new a0597cf7720 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new 6d4e07863b6 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new ca17aec65a4 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new af5cd950219 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new df83a903d7a 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 7e24d238ae5 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new ff20f26da52 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new be6c5798ae5 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new 73a9697431a 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 4d07b89b2f9 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 2d395d23b4b 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new f7fbc036d42 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new bd983ec39d4 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new f0391a7369c 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new e65eb364126 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new dedb1325a1d 129: onsuccess: #548: 6: Success after binutils: 8 commits new 8a2e39d82af 130: force: #551: 6: Success after gcc: 10 commits new a29443391cd 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] new fdedbfe7dff 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...] new 31b5781591a 133: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new 91bc86b341b 134: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new b4d7dbee4e3 135: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 18d6637c27c 136: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 1fbff21119b 137: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new aee74ec0ebb 138: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 0cea7fef036 139: onsuccess: #561: 6: Success after binutils: 23 commits new 25a1d96950e 140: onsuccess: #563: 6: Success after glibc: 2 commits new af66b27ca3c 141: onsuccess: #564: 6: Success after linux: 3224 commits new 97f0b690562 142: force: #565: 6: Success after gcc: 8 commits new 18c44b90945 143: force: #566: 4: Failure after basepoints/gcc-13-4618-g [...] new 53183097c12 144: onsuccess: #567: 4: Success after gcc: 12 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 (7a40f8dc8fa) \ 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 1700 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 40396 -> 39936 bytes 05-build_abe-gcc/console.log.xz | Bin 217712 -> 215828 bytes 07-build_abe-linux/console.log.xz | Bin 9524 -> 9656 bytes 08-build_abe-glibc/console.log.xz | Bin 171108 -> 167668 bytes 10-check_regression/console.log.xz | Bin 3640 -> 2860 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 20 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 7 - 10-check_regression/trigger-bisect | 2 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 60 +++--- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 312 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 7 - 26 files changed, 62 insertions(+), 403 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