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-arm in repository toolchain/ci/base-artifacts.

discards de1ba66901 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 8d7e54c880 111: force: #520: 6: Success after gcc: 9 commits discards c0c1066d82 110: onsuccess: #518: 6: Success after binutils: 5 commits discards da547db7be 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards b4fddcfa14 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 8a6948ca5c 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards a96cdb20ab 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards b006d680f9 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards 0c35f39e34 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards bc42419deb 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards 4dd1ab8080 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 85cbd43d25 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards 39818ef3ac 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards f71086a123 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards e2f3edbfcb 98: force: #504: 6: Success after gcc: 18 commits discards e7a483667c 97: onsuccess: #503: 6: Success after linux: 11 commits discards 883a4b18be 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 472b693315 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 102d580c0a 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards ca7f9a6fba 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 78836c95cb 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards d8d3f74bf9 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 8821d0e2d2 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards e3bfd4a989 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 04905b6810 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards a90bf095d1 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 110f642294 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards a39ebaa0d1 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards aed2dd8e00 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards 0385a8fe08 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards 05cb18fd65 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards 0f006df887 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 65e14ffa16 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 8786b2d6ee 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards e70b71316b 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards 2e1a635d22 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards f1f2c37a6f 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 31cf0e6255 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 985d0b4628 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 6fb3eb9489 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 2fcd6259a8 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 630a6a3517 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards 05ce20edc4 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards fbbb67023a 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 18d1cdece8 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards d66dbe05e0 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 9793560d31 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 7fba191d27 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 1bf1e25fde 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 10b8726d44 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards dfd1611910 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 3969d5c563 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 5e96c39c45 60: onsuccess: #463: 1: Success after gcc: 10 commits discards 7ee84a687d 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 105c6b5e60 58: force: #461: 6: Success after gcc: 29 commits discards 4110b6392c 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 05a1a01195 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards 61753f2f5c 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards 30cb6d40c1 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards 2e59c291ff 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] discards 91fe33b158 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] discards 8b2a97a03b 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] discards f4c269377b 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] discards d198781934 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 5b1766a152 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] discards 2065f659fc 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] discards b0cd777107 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards 8822c6265e 45: onsuccess: #446: 4: Success after gcc: 13 commits discards d061ada9ba 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] discards 490d7a578d 43: force: #444: 6: Success after gcc: 5 commits discards 38f63ee5f2 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] discards 8854a43e50 41: onsuccess: #442: 6: Success after glibc: 3 commits discards 4ebd52a080 40: onsuccess: #440: 6: Success after binutils: 11 commits discards e7ea76d878 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] discards 349dabc098 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards 22e1b8ebe5 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] discards 146bf3862b 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] discards 357d3794b4 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] discards b348b73256 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] discards 06a33e1432 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] discards 0f62c6a90e 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] discards 10f400361d 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] discards 49e0ff7f4f 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] discards c4798bf46c 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits discards beaac4234d 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 5344c1ce0e 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards cbc6f81332 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 3532c30662 25: onsuccess: 6: Successful build after linux: 72 commits discards 039bbe4f52 24: onsuccess: 6: Successful build after binutils: Automatic [...] discards 4c1c3c9526 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 47b297e040 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards abf850e229 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 8ad174bf88 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 7548de4bbc 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 9d2744ba55 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 55cc1a077f 17: force: 6: Successful build after gcc: 17 commits discards 7ebcf915cd 16: onsuccess: 6: Successful build after binutils: 4 commits discards ba3a2fc2c6 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards a4e54d409a 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards e7f47344a2 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 85ff8e3d08 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 4b95e099d8 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 774b6357e0 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new c4e94548e6 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 2eabf008a9 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 515ac0eb7a 16: onsuccess: 6: Successful build after binutils: 4 commits new aa14e2060c 17: force: 6: Successful build after gcc: 17 commits new 0cd3d6a6c2 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 921674f06c 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 7d6d10ce02 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new b725e6f190 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 2c28566753 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 980de14568 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new b4fb1aef30 24: onsuccess: 6: Successful build after binutils: Automatic [...] new cfbeefb831 25: onsuccess: 6: Successful build after linux: 72 commits new 0a5c16d578 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new fd83cc3b22 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 65f1bd7447 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new 2e526ca18e 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits new b2f1dc82e8 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] new fb12d4d367 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] new e18765b4ad 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] new 6deb182aed 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] new 592931d329 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] new 017fc3b71c 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] new 5dc61332b2 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] new abae710733 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] new 17abe693a9 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new 0e5a463521 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] new 2609ba6e1d 40: onsuccess: #440: 6: Success after binutils: 11 commits new a460763439 41: onsuccess: #442: 6: Success after glibc: 3 commits new f495bafbfd 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] new 59b64db436 43: force: #444: 6: Success after gcc: 5 commits new 7b74b330d0 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] new abd60e2a55 45: onsuccess: #446: 4: Success after gcc: 13 commits new 6ec06ea138 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 6112b0ec71 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] new 26cfee426d 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] new e218a407a9 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new 7761766a22 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 36bba15127 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] new 0001021101 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] new 3a3beffd8e 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] new fd58b27455 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 9cea937500 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new af2c80eacc 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new a908db59bc 57: onsuccess: #459: 6: Success after binutils: 8 commits new 44008c7623 58: force: #461: 6: Success after gcc: 29 commits new 5a4253f468 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new 830dbf56a6 60: onsuccess: #463: 1: Success after gcc: 10 commits new 0b1a9e7f19 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new be061a81cd 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 3b95b2488f 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 048af2a0c1 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 6a79b38e88 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 0e8290c2e8 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 62a2557f8a 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 001b2abc71 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new de5366742f 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 24c4ff5491 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 4ddcbada14 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new f48aee258b 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 9e563b40d4 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 33268e4d89 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 788db2aa66 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new 99c9a8326c 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new 44bb01c7e8 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new 3cf6670dd4 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 1fee07494f 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new d26c00801c 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 15befa130b 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 71ac556563 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 48041f07cb 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new e20418c4b0 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new 20727e7ce9 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new ff4e2a2647 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new 1be033677a 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 1c1dd2072b 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 0b957a6b0f 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 256340d09a 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new 2c80fd2c8a 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new deaee26b7e 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new dce4239380 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 15ca7eee12 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 61d385dc58 95: onsuccess: #500: 6: Success after binutils: 8 commits new edac4e1e1a 96: onsuccess: #502: 6: Success after glibc: 10 commits new 322a9fbfd4 97: onsuccess: #503: 6: Success after linux: 11 commits new 8f98482a11 98: force: #504: 6: Success after gcc: 18 commits new 02e85ad007 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new cb1bc97903 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 93a0273356 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 5c925bbd1c 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new 91f86388f2 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new c3b6abbedb 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new 15ada7b8c2 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new fd66439216 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 97eb1afe49 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new 72017cbeb4 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new 439d92140f 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 4315c4b471 110: onsuccess: #518: 6: Success after binutils: 5 commits new 76c857a454 111: force: #520: 6: Success after gcc: 9 commits new e4a4ef5813 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...] new fba4efc334 113: onsuccess: #522: 1: 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 (de1ba66901) \ 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 1596 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51328 -> 51112 bytes 05-build_abe-gcc/console.log.xz | Bin 231128 -> 233224 bytes 10-check_regression/console.log.xz | Bin 3656 -> 2688 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 | 9 - 10-check_regression/trigger-bisect | 2 - 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 34 ++-- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 302 -------------------------------- 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 | 14 +- results | 9 - 24 files changed, 50 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