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 7a5ff5dc1c4 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] discards 6a4854e0b87 130: force: #551: 6: Success after gcc: 10 commits discards 114af001f48 129: onsuccess: #548: 6: Success after binutils: 8 commits discards 78b8d343ce7 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] discards da6a597ab4f 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] discards b8829ed9adc 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] discards acc51b84877 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] discards 43df11f8f75 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards 1a294a36835 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards e51da1d06a5 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 182330f32c4 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 12332345559 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards 30f22ca50d1 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 2b9656abb9a 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards d4f771f8ea0 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] discards 7bb2a610d81 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] discards f510dd048e2 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards bab839c7a76 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] discards 2155ae9febf 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] discards a2b1bcf9568 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] discards b83035748be 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] discards 5672fcebb84 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] discards 138c3c3ef7f 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] discards 15cec543219 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] discards f64de83d14a 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits discards e21c1478af0 106: onsuccess: #524: 1: Success after gcc: 11 commits discards 241f1c10d20 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] discards 2164582d297 104: force: #522: 6: Success after gcc: 24 commits discards c0962631ab0 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 6e4007f9de2 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] discards 90e7d90f96f 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] discards 35d6d384d03 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] discards 840958ff998 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] discards 2956ed727de 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] discards 508e91405b3 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] discards 053e0c40bcd 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards d4f2a110d55 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] discards e6127c91777 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards 6046f89352f 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 08d91577350 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 734b35e95a2 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] discards 1a999024722 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] discards 3ea569c8ee4 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] discards f6ea1a29234 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] discards 2122f9a5791 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] discards adc4dbfef83 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] discards 4775028c1cc 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] discards 071fcfe9414 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] discards 987c0e571a4 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] discards c6e6c707e40 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] discards cac777969f1 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] discards f4cb5d4593f 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] discards acdc0efb59e 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] discards 3b890f7d6c6 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] discards 9683d73290f 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] discards f962b0419a1 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] discards 9945aa6f84a 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] discards 0ffa208e1d9 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] discards 34f936c201e 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] discards 10142aebe53 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] discards 261bc7c9fef 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] discards b4602de78b1 70: onsuccess: #486: 5: Success after gdb: 7 commits discards ff481568a00 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] discards 62e51652d14 68: force: #484: 6: Success after gdb: 6 commits discards 2bd0416891a 67: onsuccess: #483: 6: Success after linux: 384 commits discards 7cbf1c76fea 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 61ccb78218b 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 40d066d6475 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 291d3d30805 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] discards 00f4502d624 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] discards 86ea9530fb6 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] discards 7f464befbde 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] discards db889892718 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] discards 59e40f74a7d 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] discards b9d9795343f 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] discards 85cd66712d4 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] discards f62489b6927 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] discards 5865b4f293c 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] discards 23ac25865a5 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] discards 731e17cb8ac 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards ecafa049665 51: onsuccess: #465: 1: Success after gcc: 10 commits discards abc7df0afb8 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] discards 84973bed37e 49: force: #463: 6: Success after gcc: 18 commits discards 9421347e391 48: onsuccess: #461: 6: Success after binutils: 10 commits discards 182bf1626be 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] discards 32ec89a39f6 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] discards 09eef24e78e 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] discards 303a858b19b 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] discards c8130bac4d7 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] discards 18f43c9da5f 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] discards 625953c2bdd 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] discards b4c5c1ed823 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] discards 3770aeab827 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] discards 6cba24d2264 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] discards 0085d5fc0d1 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] discards 0c3ad60bf88 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] discards 65d9a47fb50 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] discards 13fc103fc15 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] discards ffa3a910d65 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] discards 7c6714ffef5 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] discards d0a915184f9 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new d3581b55640 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gl [...] new 2c90da2a4de 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gl [...] new 072dffadb39 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gd [...] new 058f61f4fd5 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gl [...] new 5645ee2e651 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gl [...] new 3b791abf032 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gd [...] new 2b388c3574c 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gd [...] new 4a0efa90226 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gl [...] new 2fbfaf5f7e7 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gd [...] new 61dd2936db2 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gl [...] new b499af9bfbb 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gd [...] new d05259e16fd 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gl [...] new d26a97ba29d 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gl [...] new a90b4d0900a 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gl [...] new 5290a9a59c2 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gl [...] new 440073d351e 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gd [...] new 88b83eaac21 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gd [...] new 50e7fd0e486 48: onsuccess: #461: 6: Success after binutils: 10 commits new 44c33f2c389 49: force: #463: 6: Success after gcc: 18 commits new b293b197af6 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb [...] new e6e533517bf 51: onsuccess: #465: 1: Success after gcc: 10 commits new fbdc071d4d7 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 1983960d876 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gl [...] new 65f649e5baf 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gl [...] new 26559041ad7 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gl [...] new c3dde71dcdc 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gl [...] new fa5954aacec 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gd [...] new ce7a1dda202 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gl [...] new 9f27075dc3d 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gl [...] new 1a9472f0814 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gl [...] new c7e6707ca75 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gl [...] new abf39af6d34 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gl [...] new 9597e5c1860 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gl [...] new cd3e251db2e 64: onsuccess: #479: 6: Success after binutils: 14 commits new a7600d1ccab 65: onsuccess: #480: 6: Success after gcc: 12 commits new e4db7b09bad 66: onsuccess: #482: 6: Success after glibc: 2 commits new 3021fda5c07 67: onsuccess: #483: 6: Success after linux: 384 commits new 777314d1c42 68: force: #484: 6: Success after gdb: 6 commits new ed42b8ccfb7 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-g [...] new d2d1c212ed4 70: onsuccess: #486: 5: Success after gdb: 7 commits new 568ba842fcb 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gl [...] new 88ebdef3b92 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gd [...] new 1ac4fbce60b 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gl [...] new e5308b6cab3 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gl [...] new 6254e0e3f2b 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gl [...] new a2b15a4ccd2 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gd [...] new 6cfda650f6e 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gl [...] new 92971a1b375 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gd [...] new 6568b409500 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gl [...] new 91b83192568 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gd [...] new 1e000b3ed26 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gl [...] new 05bc7323752 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gd [...] new 771bf57942d 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gd [...] new 413826d50d7 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gd [...] new fb5190470e2 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gl [...] new a6665ed270d 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gl [...] new 49d6babb8b0 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gl [...] new aaba28acd4c 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gl [...] new f1d6b1a44d4 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gl [...] new 721b0fb359f 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gd [...] new d59776c1f70 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gl [...] new 03251bbb4bc 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 6157c724de9 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 51e062c7531 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new dd5da2fb33e 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gl [...] new 9fe55f064b6 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 2178ee7d941 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gd [...] new fece1713805 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gd [...] new 5b2852455fb 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gl [...] new 38c74219bf6 100: onsuccess: #516: 6: Success after binutils/gcc/linux/g [...] new fae1050ed56 101: onsuccess: #517: 6: Success after binutils/gcc/linux/g [...] new 00cbe87ee3c 102: onsuccess: #518: 6: Success after binutils/gcc/linux/g [...] new f490eec7821 103: onsuccess: #520: 6: Success after binutils: 10 commits new daadf81ae69 104: force: #522: 6: Success after gcc: 24 commits new e69cb7a616d 105: force: #523: 1: Failure after basepoints/gcc-13-3918-g [...] new 0fcf4ff578e 106: onsuccess: #524: 1: Success after gcc: 11 commits new 8bb2646c87a 107: onsuccess: #525: 1: Success after binutils/gcc: 11 commits new 311dd6d6904 108: onsuccess: #526: 6: Success after binutils/gcc/linux/g [...] new ee1066e066e 109: onsuccess: #527: 6: Success after binutils/gcc/linux/g [...] new 5a82bd39f7b 110: onsuccess: #528: 6: Success after binutils/gcc/gdb: 13 [...] new a4b56a3e3f9 111: onsuccess: #529: 6: Success after binutils/gcc/linux/g [...] new 8a5eb3fbbe8 112: onsuccess: #530: 6: Success after binutils/gcc/linux/g [...] new 4e45c265fb6 113: onsuccess: #531: 6: Success after binutils/gcc/linux/g [...] new 7306caa42c4 114: onsuccess: #532: 6: Success after binutils/gcc/linux/g [...] new 9178269485d 115: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new 2d06523f77e 116: onsuccess: #534: 6: Success after binutils/gcc/glibc/g [...] new 55c809b34f3 117: onsuccess: #535: 6: Success after binutils/gcc/gdb: 72 [...] new 14e7f510142 118: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 194297e36f5 119: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 82d39c3c006 120: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new eb2d20a8616 121: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new ed91ad08586 122: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new d14265fed6c 123: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new 608b75bddec 124: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 193ebbf716b 125: onsuccess: #543: 6: Success after binutils/gcc/linux/g [...] new de55aaab1da 126: onsuccess: #544: 6: Success after binutils/gcc/linux/g [...] new ef1af5e02e7 127: onsuccess: #545: 6: Success after binutils/gcc/linux/g [...] new b8bad1aac75 128: onsuccess: #546: 6: Success after binutils/gcc/linux/g [...] new adaf2ee94df 129: onsuccess: #548: 6: Success after binutils: 8 commits new 399404a7d11 130: force: #551: 6: Success after gcc: 10 commits new c757632ad4f 131: force: #552: 4: Failure after basepoints/gcc-13-4492-g [...] new ea74a5f72a1 132: onsuccess: #553: 4: Success after basepoints/gcc-13-44 [...]
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 (7a5ff5dc1c4) \ 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 1720 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 40144 -> 40456 bytes 05-build_abe-gcc/console.log.xz | Bin 216680 -> 217252 bytes 07-build_abe-linux/console.log.xz | Bin 8812 -> 8852 bytes 08-build_abe-glibc/console.log.xz | Bin 175588 -> 175588 bytes 10-check_regression/console.log.xz | Bin 3672 -> 2780 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 28 ++-- 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 | 66 ++++---- dashboard/dashboard-generate.sh | 2 +- 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 | 28 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 -- 26 files changed, 72 insertions(+), 393 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