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 3e5d37a8c0b 130: force: #551: 6: Success after gcc: 10 commits discards 6f90d179ade 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 70459bc8675 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards 7022f3a68e1 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards 236fdf55183 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards ef37f630392 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 82a2f10b18f 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 356ef66893d 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards 38cc8a79b0c 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards f3f852116c6 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 25985b0b3ef 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 9e8f7d97a07 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 6af1db6578f 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 12c0d3ba98c 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards c5f549dcc1b 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards c3525a0ecb7 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards 02babae0cfc 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards f6c5d053a30 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards 1cc92bbdc38 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards 9d6e897404f 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards d382b147d65 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards b94f267d386 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 391f22a0614 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards 66de46ec63e 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards 0d55bbe4146 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 7ad95ce3cd0 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 3d920e8ae5d 104: force: #522: 6: Success after gcc: 24 commits discards 84f60009857 103: onsuccess: #520: 6: Success after binutils: 10 commits discards f4fb3d40d8c 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards 57227f7ba1c 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards 11105699c69 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards fb72d514d9e 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 9c99a465aa7 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards dec51c52a15 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 69bb9849684 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 315624db7c5 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards 300f9d3a75d 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards f6e9599c24e 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 1b1659d7c91 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards c3631741977 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards ac9777d7ebf 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards 89d8fa514bd 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards 43b5681d6ad 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards d0970979323 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards 9ca43d01e25 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 56765a71cf9 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 462f1d2e6e9 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards d58f6d09068 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards f3640b38b04 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards b77a170ab03 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards a88d592d28c 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards 5963a4ca736 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 9791afb8143 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards c3d38f06624 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards 7d1ef7be554 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 1657af5564b 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 01d96b1640a 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards d3b50a418c5 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 18c65a6c663 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 02596ef0387 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards baf2b4655ed 70: onsuccess: #486: 5: Success after gdb: 7 commits discards 24765a26b32 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards af9dade6e74 68: force: #484: 6: Success after gdb: 6 commits discards 6a1a2093efc 67: onsuccess: #483: 6: Success after linux: 384 commits discards ce3a9f2a46b 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 064181a4d62 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 3efc3fdc416 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 9391f37b8f4 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards f3d158a8a4d 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards b5d0db65d25 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 6c136a4ea88 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards b46fa16b959 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 893a0aebb09 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards 333335d2ac6 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 09665dc2fdb 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards 7157748b555 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 367d83b9874 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards b531a127682 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards 798bbde78b0 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 7159cf8998d 51: onsuccess: #465: 1: Success after gcc: 10 commits discards f08e1e2faf5 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 6e9f07a7c90 49: force: #463: 6: Success after gcc: 18 commits discards 594cc1b527b 48: onsuccess: #461: 6: Success after binutils: 10 commits discards f6274b46fee 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards 65ed76ae37e 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards b2e247bf316 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards 2d758a1b6f6 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards 4b87b0da4f0 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 268b39e5b3d 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards b0ec32d45e8 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] discards afc11cce5dd 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] discards 2508d96760e 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] discards 6e5e09d2764 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] discards a7f9ddc0e46 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] discards ac326123b22 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] discards d92799014a6 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] discards 4d546c23b23 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] discards b673db6031b 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] discards a57ab138a82 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] discards 5755e19658b 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] discards 6cca397b1f4 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gl [...] new 3d63cc270be 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gl [...] new d0a915184f9 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new 7c6714ffef5 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] new ffa3a910d65 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] new 13fc103fc15 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] new 65d9a47fb50 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] new 0c3ad60bf88 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] new 0085d5fc0d1 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] new 6cba24d2264 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] new 3770aeab827 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] new b4c5c1ed823 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new 625953c2bdd 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new 18f43c9da5f 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new c8130bac4d7 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new 303a858b19b 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new 09eef24e78e 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 32ec89a39f6 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 182bf1626be 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 9421347e391 48: onsuccess: #461: 6: Success after binutils: 10 commits new 84973bed37e 49: force: #463: 6: Success after gcc: 18 commits new abc7df0afb8 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new ecafa049665 51: onsuccess: #465: 1: Success after gcc: 10 commits new 731e17cb8ac 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 23ac25865a5 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 5865b4f293c 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new f62489b6927 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new 85cd66712d4 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new b9d9795343f 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new 59e40f74a7d 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new db889892718 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 7f464befbde 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new 86ea9530fb6 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new 00f4502d624 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 291d3d30805 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new 40d066d6475 64: onsuccess: #479: 6: Success after binutils: 14 commits new 61ccb78218b 65: onsuccess: #480: 6: Success after gcc: 12 commits new 7cbf1c76fea 66: onsuccess: #482: 6: Success after glibc: 2 commits new 2bd0416891a 67: onsuccess: #483: 6: Success after linux: 384 commits new 62e51652d14 68: force: #484: 6: Success after gdb: 6 commits new ff481568a00 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new b4602de78b1 70: onsuccess: #486: 5: Success after gdb: 7 commits new 261bc7c9fef 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 10142aebe53 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new 34f936c201e 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new 0ffa208e1d9 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new 9945aa6f84a 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new f962b0419a1 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new 9683d73290f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 3b890f7d6c6 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new acdc0efb59e 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new f4cb5d4593f 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new cac777969f1 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new c6e6c707e40 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 987c0e571a4 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 071fcfe9414 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new 4775028c1cc 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new adc4dbfef83 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 2122f9a5791 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new f6ea1a29234 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new 3ea569c8ee4 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 1a999024722 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new 734b35e95a2 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new 08d91577350 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 6046f89352f 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new e6127c91777 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new d4f2a110d55 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 053e0c40bcd 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 508e91405b3 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new 2956ed727de 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 840958ff998 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 35d6d384d03 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new 90e7d90f96f 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 6e4007f9de2 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new c0962631ab0 103: onsuccess: #520: 6: Success after binutils: 10 commits new 2164582d297 104: force: #522: 6: Success after gcc: 24 commits new 241f1c10d20 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new e21c1478af0 106: onsuccess: #524: 1: Success after gcc: 11 commits new f64de83d14a 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 15cec543219 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new 138c3c3ef7f 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new 5672fcebb84 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new b83035748be 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new a2b1bcf9568 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 2155ae9febf 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new bab839c7a76 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new f510dd048e2 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 7bb2a610d81 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new d4f771f8ea0 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new 2b9656abb9a 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 30f22ca50d1 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 12332345559 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new 182330f32c4 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new e51da1d06a5 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new 1a294a36835 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 43df11f8f75 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new acc51b84877 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new b8829ed9adc 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new da6a597ab4f 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new 78b8d343ce7 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new 114af001f48 129: onsuccess: #548: 6: Success after binutils: 8 commits new 6a4854e0b87 130: force: #551: 6: Success after gcc: 10 commits new 7a5ff5dc1c4 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...]
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 (3e5d37a8c0b) \ 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 1724 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 39324 -> 40144 bytes 05-build_abe-gcc/console.log.xz | Bin 213908 -> 216680 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 07-build_abe-linux/console.log.xz | Bin 8704 -> 8812 bytes 08-build_abe-glibc/console.log.xz | Bin 246876 -> 175588 bytes 09-build_abe-gdb/console.log.xz | Bin 39604 -> 0 bytes 10-check_regression/console.log.xz | Bin 2936 -> 3672 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 17 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 11 + 10-check_regression/trigger-bisect | 2 + 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 40 +-- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 284 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 17 +- mail/mail-subject.txt | 2 +- manifest.sh | 15 +- results | 15 +- 29 files changed, 376 insertions(+), 47 deletions(-) delete mode 100644 09-build_abe-gdb/console.log.xz create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/trigger-bisect create mode 100644 10-check_regression/trigger-notify delete mode 100644 dashboard/squad-vs-first/score/results-functional.json 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