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 e0275b1839 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 8550835ac1 104: force: #522: 6: Success after gcc: 24 commits discards 76497e70ff 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 72fa83d6e4 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] discards 3a0b7c5971 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] discards 176549ce7d 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 074291cc62 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] discards cd32162e2c 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] discards b71d13eb5c 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] discards e39be3293f 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] discards 9708bf91af 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] discards b9484abf6d 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] discards e1aafeea20 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] discards 1cd5756461 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] discards 71fb1b82ec 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] discards 142f8fbed8 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] discards 5bf2f47e7d 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] discards 39b956b0c4 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] discards 770f6556ae 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] discards 921046c67b 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] discards 48c79b97a3 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] discards 8b9392a10d 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] discards 9b59923e6a 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] discards 97dd127848 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] discards 44fb2d5eac 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] discards 8c1568e773 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] discards c8c226f27d 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 478ebea776 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] discards 31800a7176 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] discards 902baeefbc 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] discards b467d7a896 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 8cd82c160d 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] discards 758d532955 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] discards 8586e4f68b 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] discards b5afa700dd 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] discards bf0892bb32 70: onsuccess: #486: 5: Success after gdb: 7 commits discards d0c779aac1 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] discards 4d9f8062b3 68: force: #484: 6: Success after gdb: 6 commits discards dee09f2418 67: onsuccess: #483: 6: Success after linux: 384 commits discards 23506aa4bf 66: onsuccess: #482: 6: Success after glibc: 2 commits discards c456e15a4a 65: onsuccess: #480: 6: Success after gcc: 12 commits discards 8b7f13a808 64: onsuccess: #479: 6: Success after binutils: 14 commits discards d1c1b08d5c 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards ecf44ff485 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 2f705f510c 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards d9efc99b6f 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gli [...] discards 3070c84d40 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards af072368b4 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards b569722211 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] discards 4fed8d01de 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 29b1086d8e 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards d4df2d7ec2 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards cd8e7c689f 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 3702dac9b7 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards c8f833d10e 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 10a34cf794 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb0 [...] discards 691f9a6973 49: force: #463: 6: Success after gcc: 18 commits discards 51e773031c 48: onsuccess: #461: 6: Success after binutils: 10 commits discards cf1e183416 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gdb [...] discards e35d14fdc5 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gdb [...] discards 6ea5d401f2 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gli [...] discards 002c1208d3 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gli [...] discards 3ecc9e9df6 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards b683f7163d 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] discards 1abe33ebc0 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gdb [...] discards 2288000fa9 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gli [...] discards fdd211c86b 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gdb [...] discards 84f58ba332 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 596f8a774e 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gdb [...] discards e0c98223a2 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gdb [...] discards 82c990bbaa 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gli [...] discards fadf90d11b 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gli [...] discards 3e16bc8aa2 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gdb [...] discards 80b926af50 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gli [...] discards 88299b41a5 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gli [...] discards 061d887d5e 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gli [...] discards 26b840a0ea 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gdb [...] discards 9f262e0786 28: onsuccess: #440: 6: Success after binutils/gcc/linux/gli [...] discards 81e25bafe7 27: onsuccess: #439: 6: Success after binutils/gcc/linux/gli [...] discards d47cf42fe9 26: onsuccess: #438: 6: Success after binutils/gcc/linux/gdb [...] discards 95df15ef3e 25: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards b433565a4f 24: onsuccess: #436: 6: Success after binutils/gcc/linux/gdb [...] discards cdbca0999d 23: onsuccess: 6: Success after binutils/gcc/linux/gdb: 125 commits discards d7bd7bb4c9 22: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 37d00092d6 21: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 470a6a805e 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 540d13bc85 19: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ac2c00b4de 18: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 4bc7a03a1a 17: onsuccess: 6: Successful build after binutils/gcc/glibc/ [...] discards bed3761b89 16: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards b4fa7684e5 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 0a027030c5 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 76a17059cd 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ca9a7ae4cb 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 869947d138 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 1970f42d8e 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ce44479c3c 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] discards b47a965bbb 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] discards 747d5af537 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards f929a53fc0 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 24a7cc9981 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new a6c7931c45 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 4715c8fbcf 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 943c67036a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 0275697149 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] new ea847f17f0 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] new 3cb7779561 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 48d89689ea 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 60367566e6 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new d3135831ca 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 28d93ab8f8 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 175b2b5237 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 036f85d564 16: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 04222701e4 17: onsuccess: 6: Successful build after binutils/gcc/glibc/ [...] new ddc30659cd 18: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new a6d58a6997 19: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 45acfa09b8 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 9ad10a938a 21: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new e514d03d36 22: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new c04d43030e 23: onsuccess: 6: Success after binutils/gcc/linux/gdb: 125 commits new 49089441d8 24: onsuccess: #436: 6: Success after binutils/gcc/linux/gdb [...] new 21bb461f5a 25: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new 187e8aa25e 26: onsuccess: #438: 6: Success after binutils/gcc/linux/gdb [...] new 246c4c4fe8 27: onsuccess: #439: 6: Success after binutils/gcc/linux/gli [...] new badcb48b7c 28: onsuccess: #440: 6: Success after binutils/gcc/linux/gli [...] new e0fe6134f4 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gdb [...] new 00c78c8957 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gli [...] new bc8d9eb8c7 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gli [...] new 04ba657bc1 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gli [...] new dac6ce86f7 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gdb [...] new 5e6ef021dc 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gli [...] new f5e89dc558 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gli [...] new c2eddbd892 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gdb [...] new 7214e9af1e 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gdb [...] new 97095fd02d 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new 0cd53d6ac8 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gdb [...] new e88bee9bf2 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gli [...] new d991d8074f 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gdb [...] new 28050671a0 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] new 585e9ec9ef 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new c87d721905 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gli [...] new 5c91895ae0 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gli [...] new f82d9ab144 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gdb [...] new ddb87bd1ec 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gdb [...] new 571b497f05 48: onsuccess: #461: 6: Success after binutils: 10 commits new 8fafdfd3e8 49: force: #463: 6: Success after gcc: 18 commits new b4498104ae 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 6b1db2688e 51: onsuccess: #465: 1: Success after gcc: 10 commits new c4b4afa131 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new 63d5bdad3d 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 137b365018 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 98f9059db9 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 9d8bb3f312 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 5f215e861f 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] new 03a01639ee 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 1eabd997c8 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 71881fe45f 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gli [...] new 53ab9b6923 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 66d3859e96 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new c1e22400da 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new f1ec164719 64: onsuccess: #479: 6: Success after binutils: 14 commits new 033cb2f75b 65: onsuccess: #480: 6: Success after gcc: 12 commits new ae5283c35b 66: onsuccess: #482: 6: Success after glibc: 2 commits new 1112106694 67: onsuccess: #483: 6: Success after linux: 384 commits new f6bf707c57 68: force: #484: 6: Success after gdb: 6 commits new 56f62fee82 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] new 291bd568fb 70: onsuccess: #486: 5: Success after gdb: 7 commits new b95c8d687a 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] new 24918934ee 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] new ec542c4d5e 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] new 302bc08800 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] new e5530d9a26 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 66f96c2976 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] new 0426941eb8 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] new f81e3db900 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] new 76054758be 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new c0ab67fca6 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new fdb335323f 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] new f9675c0c52 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] new c122b12245 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] new 476655f65c 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] new de3a854d5c 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] new c74aafa016 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] new 25ee89fec6 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] new fef2dab030 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] new 3ddc23507a 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] new ab53a54337 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] new 1867f6ed16 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] new 37367db332 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] new 84a67dfc36 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] new fe5915ce43 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] new 71744dd24c 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] new 3b01d4e90f 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] new 629c71d9a6 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] new c6c1d9e6cb 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] new b4916367b2 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] new b08cff6205 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 50b57fbed8 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] new c962d36531 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] new 8f4a9f7cc7 103: onsuccess: #520: 6: Success after binutils: 10 commits new 1aff0f9743 104: force: #522: 6: Success after gcc: 24 commits new d2e0fcdf22 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...] new c103ae5d17 106: onsuccess: #524: 1: Success after gcc: 11 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 (e0275b1839) \ 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 1668 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2716 bytes 04-build_abe-binutils/console.log.xz | Bin 39188 -> 38744 bytes 05-build_abe-gcc/console.log.xz | Bin 209520 -> 209440 bytes 10-check_regression/console.log.xz | Bin 3688 -> 2792 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 26 ++- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 10 -- 10-check_regression/trigger-bisect | 2 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 64 +++---- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 303 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 26 ++- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- results | 10 -- 24 files changed, 66 insertions(+), 412 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