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 7569c6ed68 111: force: #520: 6: Success after gcc: 9 commits discards 9766f56703 110: onsuccess: #518: 6: Success after binutils: 5 commits discards 045f3564ec 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 7087da0862 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] discards 8055d1f61e 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] discards e290b0f461 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] discards 72cf94d250 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] discards b015e4a8d9 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] discards e1b5d543c0 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] discards d985b812dc 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] discards 60ef596284 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] discards 225d310ca4 100: onsuccess: #506: 4: Success after baseline build: no ne [...] discards b9a72c6b53 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] discards 585277d648 98: force: #504: 6: Success after gcc: 18 commits discards 6a8ac364bb 97: onsuccess: #503: 6: Success after linux: 11 commits discards dc5a8e4361 96: onsuccess: #502: 6: Success after glibc: 10 commits discards 266c74dceb 95: onsuccess: #500: 6: Success after binutils: 8 commits discards 7ef4dea034 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] discards 1a9196135f 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] discards 16ef440d2a 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] discards b8f02d1dd9 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards 64d05c693c 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] discards 21b3078693 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] discards 89c9f6a37d 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards af1df563f2 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] discards 6a22dcd856 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] discards def8092b61 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] discards d5b5878599 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] discards b998a84cac 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] discards d51c9975b6 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] discards cc7cd0014b 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] discards 2f401e24ac 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] discards 2a9ecc703f 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] discards 5962e22adf 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] discards ba544a84fe 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] discards 255977543e 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] discards 7721395a86 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] discards 58bd384d7c 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards 0b6af3b4a9 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards bbf9f5d95b 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards c447ebe5e7 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] discards adb80c87d0 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards e609977797 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 0a996b2b7a 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] discards ab209c98a6 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards 1d9cea2eff 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 72bdade413 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 19c5bf128c 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards 5736d8839b 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] discards 58fd1436fb 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits discards 3b87a595bd 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits discards 67b03b8938 60: onsuccess: #463: 1: Success after gcc: 10 commits discards d6e1d3502a 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] discards 13928bff25 58: force: #461: 6: Success after gcc: 29 commits discards 535e107bbe 57: onsuccess: #459: 6: Success after binutils: 8 commits discards 946b6079b7 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] discards 56808bd228 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] discards 7f8b10a972 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards 7852adeae6 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] discards b7ee1f6a67 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] discards 9cd13a3747 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] discards b35e15db2b 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] discards 11514018d3 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 4c7b8e07bd 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] discards b3129da48f 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] discards 17fd36725a 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits discards 6a5ebafc09 45: onsuccess: #446: 4: Success after gcc: 13 commits discards 90b0760df0 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] discards 6f7bf13b21 43: force: #444: 6: Success after gcc: 5 commits discards eafcc93222 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] discards 0705bacfe9 41: onsuccess: #442: 6: Success after glibc: 3 commits discards ab67bae23b 40: onsuccess: #440: 6: Success after binutils: 11 commits discards 0882db225b 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] discards cfb81e97e3 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards 8e146f7886 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] discards 2ed806cdf6 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] discards ad0d1750be 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] discards 2f2e7cc62c 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] discards 8a48fa7c7e 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] discards 9819217d80 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] discards 40f0773402 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] discards 5ac6af5af0 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] discards cce261d3c4 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits discards ae0b34dc39 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards 7520fc7a90 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards a6020a63d3 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 1890c37a80 25: onsuccess: 6: Successful build after linux: 72 commits discards 8953b66be8 24: onsuccess: 6: Successful build after binutils: Automatic [...] discards f582b4bc60 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 116fc7f49c 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards feacb18f41 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards ec26e57991 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 6519b331b5 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 07f6ea749f 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards cb55576980 17: force: 6: Successful build after gcc: 17 commits discards 3dc66ef715 16: onsuccess: 6: Successful build after binutils: 4 commits discards fe568437bf 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 6bb398e18c 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 3c2670be94 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 21f09172e9 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 16b7ff1562 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 64b30b954b 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 85ff8e3d08 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new e7f47344a2 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new a4e54d409a 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new ba3a2fc2c6 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 7ebcf915cd 16: onsuccess: 6: Successful build after binutils: 4 commits new 55cc1a077f 17: force: 6: Successful build after gcc: 17 commits new 9d2744ba55 18: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 7548de4bbc 19: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 8ad174bf88 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new abf850e229 21: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 47b297e040 22: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 4c1c3c9526 23: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 039bbe4f52 24: onsuccess: 6: Successful build after binutils: Automatic [...] new 3532c30662 25: onsuccess: 6: Successful build after linux: 72 commits new cbc6f81332 26: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 5344c1ce0e 27: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new beaac4234d 28: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new c4798bf46c 29: onsuccess: 6: Success after binutils/gcc/linux/gdb: 117 commits new 49e0ff7f4f 30: onsuccess: #428: 6: Success after binutils/gcc/linux/gdb [...] new 10f400361d 31: onsuccess: #430: 6: Success after binutils/gcc/linux/gli [...] new 0f62c6a90e 32: onsuccess: #431: 6: Success after binutils/gcc/linux/gli [...] new 06a33e1432 33: onsuccess: #432: 6: Success after binutils/gcc/linux/gdb [...] new b348b73256 34: onsuccess: #433: 6: Success after binutils/gcc/linux/gli [...] new 357d3794b4 35: onsuccess: #434: 6: Success after binutils/gcc/linux/gli [...] new 146bf3862b 36: onsuccess: #435: 6: Success after binutils/gcc/linux/gdb [...] new 22e1b8ebe5 37: onsuccess: #436: 6: Success after binutils/gcc/linux/gli [...] new 349dabc098 38: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new e7ea76d878 39: onsuccess: #438: 6: Success after binutils/gcc/linux/gli [...] new 4ebd52a080 40: onsuccess: #440: 6: Success after binutils: 11 commits new 8854a43e50 41: onsuccess: #442: 6: Success after glibc: 3 commits new 38f63ee5f2 42: onsuccess: #443: 6: Success after v6.0-rc5-25-g3245cb65f [...] new 490d7a578d 43: force: #444: 6: Success after gcc: 5 commits new d061ada9ba 44: force: #445: 4: Failure after basepoints/gcc-13-2658-g64 [...] new 8822c6265e 45: onsuccess: #446: 4: Success after gcc: 13 commits new b0cd777107 46: onsuccess: #447: 4: Success after binutils/gcc: 19 commits new 2065f659fc 47: onsuccess: #448: 4: Success after binutils/gcc/linux/gli [...] new 5b1766a152 48: onsuccess: #449: 6: Success after binutils/gcc/linux/gli [...] new d198781934 49: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new f4c269377b 50: onsuccess: #451: 6: Success after binutils/gcc/linux/gli [...] new 8b2a97a03b 51: onsuccess: #452: 6: Success after binutils/gcc/glibc/gdb [...] new 91fe33b158 52: onsuccess: #453: 6: Success after binutils/gcc/linux/gli [...] new 2e59c291ff 53: onsuccess: #454: 6: Success after binutils/gcc/glibc/gdb [...] new 30cb6d40c1 54: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 61753f2f5c 55: onsuccess: #456: 6: Success after binutils/gcc/linux/gdb [...] new 05a1a01195 56: onsuccess: #457: 6: Success after binutils/gcc/linux/gdb [...] new 4110b6392c 57: onsuccess: #459: 6: Success after binutils: 8 commits new 105c6b5e60 58: force: #461: 6: Success after gcc: 29 commits new 7ee84a687d 59: force: #462: 1: Failure after basepoints/gcc-13-2871-g1b [...] new 5e96c39c45 60: onsuccess: #463: 1: Success after gcc: 10 commits new 3969d5c563 61: onsuccess: #464: 1: Success after binutils/gcc: 30 commits new dfd1611910 62: onsuccess: #465: 1: Success after binutils/gcc: 27 commits new 10b8726d44 63: onsuccess: #466: 6: Success after binutils/gcc/linux/gli [...] new 1bf1e25fde 64: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new 7fba191d27 65: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 9793560d31 66: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new d66dbe05e0 67: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new 18d1cdece8 68: onsuccess: #471: 6: Success after binutils/gcc/linux/gli [...] new fbbb67023a 69: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 05ce20edc4 70: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new 630a6a3517 71: onsuccess: #474: 6: Success after binutils/gcc/linux/gdb [...] new 2fcd6259a8 72: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new 6fb3eb9489 73: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new 985d0b4628 74: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 31cf0e6255 75: onsuccess: #478: 6: Success after binutils/gcc/linux/gli [...] new f1f2c37a6f 76: onsuccess: #479: 6: Success after binutils/gcc/linux/gli [...] new 2e1a635d22 77: onsuccess: #480: 6: Success after binutils/gcc/linux/gli [...] new e70b71316b 78: onsuccess: #481: 6: Success after binutils/gcc/linux/gli [...] new 8786b2d6ee 79: onsuccess: #482: 6: Success after binutils/gcc/linux/gli [...] new 65e14ffa16 80: onsuccess: #483: 6: Success after binutils/gcc/linux/gdb [...] new 0f006df887 81: onsuccess: #484: 6: Success after binutils/gcc/linux/gli [...] new 05cb18fd65 82: onsuccess: #485: 6: Success after binutils/gcc/linux/gli [...] new 0385a8fe08 83: onsuccess: #486: 6: Success after binutils/gcc/linux/gli [...] new aed2dd8e00 84: onsuccess: #487: 6: Success after binutils/gcc/glibc/gdb [...] new a39ebaa0d1 85: onsuccess: #488: 6: Success after binutils/gcc/linux/gli [...] new 110f642294 86: onsuccess: #489: 6: Success after binutils/gcc/linux/gdb [...] new a90bf095d1 87: onsuccess: #490: 6: Success after binutils/gcc/linux/gdb [...] new 04905b6810 88: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new e3bfd4a989 89: onsuccess: #492: 6: Success after binutils/gcc/linux/gli [...] new 8821d0e2d2 90: onsuccess: #494: 6: Success after binutils/gcc/linux/gli [...] new d8d3f74bf9 91: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 78836c95cb 92: onsuccess: #496: 6: Success after binutils/gcc/linux/gli [...] new ca7f9a6fba 93: onsuccess: #497: 6: Success after binutils/gcc/linux/gdb [...] new 102d580c0a 94: onsuccess: #498: 6: Success after binutils/gcc/linux/gli [...] new 472b693315 95: onsuccess: #500: 6: Success after binutils: 8 commits new 883a4b18be 96: onsuccess: #502: 6: Success after glibc: 10 commits new e7a483667c 97: onsuccess: #503: 6: Success after linux: 11 commits new e2f3edbfcb 98: force: #504: 6: Success after gcc: 18 commits new f71086a123 99: force: #505: 4: Failure after basepoints/gcc-13-3596-ge7 [...] new 39818ef3ac 100: onsuccess: #506: 4: Success after baseline build: no ne [...] new 85cbd43d25 101: onsuccess: #507: 4: Success after binutils/gcc/linux/gl [...] new 4dd1ab8080 102: onsuccess: #508: 6: Success after binutils/gcc/linux/gl [...] new bc42419deb 103: onsuccess: #509: 6: Success after binutils/gcc/linux/gl [...] new 0c35f39e34 104: onsuccess: #510: 6: Success after binutils/gcc/linux/gl [...] new b006d680f9 105: onsuccess: #511: 6: Success after binutils/gcc/linux/gd [...] new a96cdb20ab 106: onsuccess: #512: 6: Success after binutils/gcc/linux/gl [...] new 8a6948ca5c 107: onsuccess: #513: 6: Success after binutils/gcc/linux/gl [...] new b4fddcfa14 108: onsuccess: #514: 6: Success after binutils/gcc/linux/gl [...] new da547db7be 109: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new c0c1066d82 110: onsuccess: #518: 6: Success after binutils: 5 commits new 8d7e54c880 111: force: #520: 6: Success after gcc: 9 commits new de1ba66901 112: force: #521: 1: Failure after basepoints/gcc-13-3918-gb [...]
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 (7569c6ed68) \ 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 -> 1596 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 52288 -> 51328 bytes 05-build_abe-gcc/console.log.xz | Bin 232984 -> 231128 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 0 bytes 07-build_abe-linux/console.log.xz | Bin 9752 -> 0 bytes 08-build_abe-glibc/console.log.xz | Bin 236372 -> 0 bytes 09-build_abe-gdb/console.log.xz | Bin 50164 -> 0 bytes 10-check_regression/console.log.xz | Bin 2972 -> 3656 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 19 +- 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 | 36 +-- 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 | 302 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 19 +- mail/mail-subject.txt | 2 +- manifest.sh | 23 +- results | 17 +- 29 files changed, 385 insertions(+), 64 deletions(-) delete mode 100644 06-clean_sysroot/console.log.xz delete mode 100644 07-build_abe-linux/console.log.xz delete mode 100644 08-build_abe-glibc/console.log.xz 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