This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 813ccd715 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards 1d40b4681 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards e8122087d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 9db196689 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards f9f476c4c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 8f7aecc90 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards 25fcce8e4 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 572bcbb76 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards d1c682d48 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 8afc2f835 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 0965dcbc8 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 3c39ae1e0 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards cd878059b 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 9ceacf174 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards e85b6eb7d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards f86b8f161 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 3ba692278 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9d4e660ab 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7d823ab1d 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 2c3d68bbd 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards 38355c4c2 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f6306d240 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9be766b40 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 3b8b52ce4 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards 7baa0dd1d 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 37d1419c8 75: onsuccess: 1: Successful build after linux: 44 commits discards c25606aa7 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 03da212b1 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b2608ed6a 72: onsuccess: 1: Successful build after linux: 12 commits discards eb01e518b 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards d66479c7d 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards d85b6fbbe 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 5e952650d 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0b88a83a7 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 0cc8daad8 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 416455db3 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e5f434baa 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cbb5a487b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 6183521cd 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards a7b86b88f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards f511b391e 60: onsuccess: 1: Successful build after glibc: 2 commits discards 2aab5e312 59: onsuccess: 1: Successful build after binutils: 2 commits discards 7f1b1b942 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards 0fe9f7084 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 444d2215e 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0d96245fa 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 34d538fa1 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 53ef7e173 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 242e50b8d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards 34be6c034 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b4bec2784 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ff1ea0777 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 87411193c 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9028eacf5 47: onsuccess: 1: Successful build after linux: 10 commits discards 36abf9d1a 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards db611158d 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d803c3394 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards c662acf2d 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 05b9bfcfd 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards 843233a33 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7a5a293da 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards fcc732ee1 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards f17e21101 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 6d05bea1a 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f003b2645 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3291f3845 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c82800786 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 122f53d0d 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards eafcac52e 32: onsuccess: 1: Successful build after gcc: 7 commits discards 62efcbdbf 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 43a114532 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 75cefdbdb 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7fe11dd84 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ecba1e494 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] discards daf8ef2cd 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 07c637b3e 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 96b48e3fa 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 924f95d6f 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8188ed04f 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 86ddd93eb 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8df9ee080 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e49c31cd6 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f6588c90f 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 28843140d 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fe98376e6 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2f1b8cb6b 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b4fe5efb8 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fa6becac9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c6975e076 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards aecfd0d88 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b72ce7e45 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cc535fa44 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 566db6dd9 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8e6c973c1 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 00add54b9 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d4c09d791 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f2ca49731 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 03fdcc258 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bc5dec2d2 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ab93acceb 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 68113c9e0 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1 new b10d9db89 0: update: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6bd93579f 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6791892ab 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 314bedafc 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 044c7b5f2 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9cac9ddd9 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2185071dc 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6487f6de0 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b4755a4a7 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 34011e530 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d4971e6ea 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 42863783f 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5c4b411e2 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 83f06f7cf 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f939024ab 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cf840cc52 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cf9b4e0f0 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f5c83d44e 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e690823e7 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new abfacde7f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 99d45d4b7 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 55b309020 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9d464892e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9fd7e1852 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 805cf595a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bfb259e8b 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d8e04a7f5 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 610b2c92e 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 25 [...] new e5514cec9 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 02b6a2933 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9b3d63303 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new c7094eafe 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 43f94fc14 32: onsuccess: 1: Successful build after gcc: 7 commits new 79fde465f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2cb8a1d9c 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e80f5df43 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new eddd34bea 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2e395adf6 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 447d5ea79 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new d7a885e33 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 38a0801a5 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new a710ad32c 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e0f592c2b 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new da1e632db 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 79e40d499 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 06b96c4c2 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d378e646a 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new c14108649 47: onsuccess: 1: Successful build after linux: 10 commits new b91392046 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c19b9dbb2 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 07a3843a4 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5d5e53cb3 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1b2e0d514 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 8d6160011 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 76de4e3b8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new a16ece0e7 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 84771f642 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e107f28ac 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 93a6c7825 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new afa64b187 59: onsuccess: 1: Successful build after binutils: 2 commits new feb80378a 60: onsuccess: 1: Successful build after glibc: 2 commits new d3b2e2182 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d92f208d2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new 53718168d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new f5905f18d 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c6f111e54 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8c4622578 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 581af9895 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 98462f272 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8143ba5a4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new add8c492a 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 89901294d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new f697e8bf3 72: onsuccess: 1: Successful build after linux: 12 commits new 4bb8fb91a 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a0003fe86 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1137a04c4 75: onsuccess: 1: Successful build after linux: 44 commits new 33df202e8 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8c1c3be9f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 494e04510 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 7374fe6a3 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ec3c3f012 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8b7f85fa3 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 10a357f58 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new eabf755c8 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 843f3fdfe 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5c3eb66e9 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new c3df05af8 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 2b75f8db8 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new cf14659d7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 847059e9d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 1d5aad55b 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 8c17959ad 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 2b944190d 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 2b882c0e0 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 1da510b6c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new c78823320 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new aa3f225c5 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 526911cf0 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new ff87fa492 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new b26a23609 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new f4bf6ad7a 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new e9a7b56e7 101: onsuccess: #2130: 1: Success after binutils: 81 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 (813ccd715) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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 1692 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30660 -> 30404 bytes 04-build_abe-stage1/console.log.xz | Bin 73772 -> 73592 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8456 bytes 07-build_abe-glibc/console.log.xz | Bin 240088 -> 240100 bytes 08-build_abe-stage2/console.log.xz | Bin 204740 -> 206936 bytes 09-build_abe-gdb/console.log.xz | Bin 37860 -> 38308 bytes 10-build_abe-qemu/console.log.xz | Bin 31916 -> 32132 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3452 -> 3448 bytes 13-check_regression/console.log.xz | Bin 8856 -> 4196 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 127 +- 13-check_regression/results.compare | 157 +- 13-check_regression/results.compare2 | 651 +-- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 39 +- dashboard/dashboard-generate.sh | 6 +- dashboard/dashboard-push.sh | 8 +- dashboard/squad/dashboard-push-squad.sh | 14 - dashboard/squad/score/results-functional.json | 1 + dashboard/squad/summary-annotation.txt | 0 dashboard/squad/test/results-functional.json | 4 - dashboard/squad/test/results-metadata.json | 12 - dashboard/squad/test/results-metrics.json | 3 - git/binutils_rev | 2 +- jenkins/dashboard-push.sh | 7 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 129 +- mail/mail-subject.txt | 2 +- manifest.sh | 31 +- results | 26 + sumfiles/g++.log.xz | Bin 3415276 -> 3393248 bytes sumfiles/g++.sum | 178 +- sumfiles/gcc.log.xz | Bin 2988576 -> 3011160 bytes sumfiles/gcc.sum | 5409 +++++++++++++------------ sumfiles/gfortran.log.xz | Bin 1026200 -> 1025640 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 200464 -> 200376 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424300 -> 426528 bytes sumfiles/libstdc++.sum | 16 +- 49 files changed, 3039 insertions(+), 3884 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions delete mode 100755 dashboard/squad/dashboard-push-squad.sh create mode 100644 dashboard/squad/score/results-functional.json delete mode 100644 dashboard/squad/summary-annotation.txt delete mode 100644 dashboard/squad/test/results-functional.json delete mode 100644 dashboard/squad/test/results-metadata.json delete mode 100644 dashboard/squad/test/results-metrics.json create mode 100755 jenkins/dashboard-push.sh