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 886c9ebd03 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards cb58d21e93 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 2346a15f6e 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards a8395a7404 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 6c83ac8086 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards cc08fe0b80 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards e6efc1a07e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 815068f083 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 80cb407153 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 0fd9d69cc9 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 20dd824ca6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards f4bbe9fbe9 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards cc47eae7ad 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 029e7e4ab6 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards f631a890ca 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards d6deb98e7f 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 6bfd4f8e19 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 935d676fb6 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards befd70f331 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards e9efa5a517 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 15611a6d67 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 05c813ae2f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 09677a4ee2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards a46b40400b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 91d834319f 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards b4f66bf14c 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards b7b1d9e5e2 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards f1bd832c10 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 39c064baf1 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 925d331e87 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1a45628dd7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards f65109eba0 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 00663f3204 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 653e958381 75: onsuccess: 1: Successful build after linux: 44 commits discards 1d872369f1 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards c4ec19092b 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 11609a5766 72: onsuccess: 1: Successful build after linux: 12 commits discards 68a001adfd 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards ae5f39b7d0 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 480259dfb0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 84af50aea0 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 527af5c0b1 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 3b30df9e9f 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards d975e26d67 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 20dca5d28e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4275658a69 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 3bcc2f6160 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 9d43c18773 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d330a43b0d 60: onsuccess: 1: Successful build after glibc: 2 commits discards 022326fe93 59: onsuccess: 1: Successful build after binutils: 2 commits discards 07379d41a8 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 3a8bc60ddd 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards aa19872913 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4749be0717 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards cd723d1ca9 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 438a0dafad 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 98fb4ed1da 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards d0e64122ed 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4dc5d7a4fe 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7a7713b899 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 79d9b05f62 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f45ded6a26 47: onsuccess: 1: Successful build after linux: 10 commits discards 977ef268ee 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8f08a258d6 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 34855c146f 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards ecbb9f14b5 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 79b2214e33 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 2766b0a051 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7f59ea9e06 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 1436a6727d 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c3e0b43801 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 027aa1004b 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2364f85fcf 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4123e2f1f3 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 64a3a8149e 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f72898035b 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards add7d8bc59 32: onsuccess: 1: Successful build after gcc: 7 commits discards 9a1050e987 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5ef6252eae 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3a720d98a5 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c8fdfbfeaa 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4fbda78dca 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 15ba86c91e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bb3643fe19 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards da142e0bd5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1c677d453e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f6128d2c86 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d963e055eb 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c055f11d0d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b9cf0c2400 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bf477cf43c 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 97e142c526 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bc14256a39 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8ad523641b 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 57b5e006a9 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fbac8c5efd 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 91d4999f47 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 89498ddbb0 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 07ede4c312 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f2a687b581 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b8056f6482 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 870ceb37bb 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e03565e9d1 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dda3af23e2 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5e29734930 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ee714cd5c5 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 17fba60fb2 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f469c52248 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d6e25b1ebe 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a3873884bb 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b25e798311 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9dfff13c44 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f2908fba4a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f8e9b862d2 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0f300bfe9f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 647370a88a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4dbcfe994e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3a4c2dffd0 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5016aabda3 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c7b1a539e3 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 637843f84f 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 59925859eb 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c9e0b56948 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4d56c3cd48 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 979869e24e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new bb546348fc 32: onsuccess: 1: Successful build after gcc: 7 commits new 72ddf63d9c 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 85959550d8 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new de1fa9a745 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b68be05fa2 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2160017c60 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7afa6edc8c 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 19ed19e8ea 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e9dfe1b5b5 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new f9404ff9fb 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e6e7baa1f5 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 8ec7103c27 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new ede787e82b 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new 8442cbb912 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ec1bd74933 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1a80542ece 47: onsuccess: 1: Successful build after linux: 10 commits new 547c45fa74 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b26d8a66a6 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 9841ba8d55 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d889c8471 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6489160a9c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new ec3bb000c7 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2d624befad 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6791e8c85a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new b152428c29 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 670df0a2a5 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fe14d54208 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new f626cead90 59: onsuccess: 1: Successful build after binutils: 2 commits new 64b31c6ab2 60: onsuccess: 1: Successful build after glibc: 2 commits new ca0f253b47 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 04e30b36d0 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 1008b6ba41 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d1b0253707 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 20839aae5c 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4fcd6fd675 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 98771a61ab 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 816249dff4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6114ce37f4 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 8617e9627e 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new a086d0281f 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 29a410774f 72: onsuccess: 1: Successful build after linux: 12 commits new 661d8f896f 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6306121aa9 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 048c37b1c0 75: onsuccess: 1: Successful build after linux: 44 commits new 6e453ed778 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 56a27c0ee6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new f41c81fd5d 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 98970cc7ca 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3e0ce88b25 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new b591ff7c33 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 2c6f448400 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 1dcc094e0a 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new a18f694bd3 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 6f3bbc95ce 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 355b8bce96 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new c6c6a9b00e 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 83e4e8ca30 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new cba3899af0 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 8ccabf58aa 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new a7d84478cb 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new c7627ad3d4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b6d53599ba 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new c9341312e2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 46cfcdf4b5 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new db20621345 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 152d285f31 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new ac6a932857 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 660b2f01e1 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 9ecb273082 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new c17185157c 101: onsuccess: #2130: 1: Success after binutils: 81 commits new fef88f93a5 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 7d770591f6 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 326878f270 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 7974292b44 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new a8ef81e6de 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new cec535ac10 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d9a68f12ca 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 0b7f234e66 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 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 (886c9ebd03) \ 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 1740 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30144 -> 30104 bytes 04-build_abe-stage1/console.log.xz | Bin 72308 -> 72164 bytes 06-build_abe-linux/console.log.xz | Bin 8260 -> 8280 bytes 07-build_abe-glibc/console.log.xz | Bin 240280 -> 239652 bytes 08-build_abe-stage2/console.log.xz | Bin 202856 -> 201920 bytes 09-build_abe-gdb/console.log.xz | Bin 37328 -> 37360 bytes 10-build_abe-qemu/console.log.xz | Bin 31844 -> 31592 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2532 bytes 13-check_regression/console.log.xz | Bin 18312 -> 5188 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 34 + 13-check_regression/mail-body.txt | 169 +- 13-check_regression/results.compare | 599 +--- 13-check_regression/results.compare2 | 3321 +-------------------- 13-check_regression/results.regressions | 68 + 14-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 171 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 68 + sumfiles/g++.log.xz | Bin 3396064 -> 3396200 bytes sumfiles/g++.sum | 37 +- sumfiles/gcc.log.xz | Bin 3019024 -> 3022332 bytes sumfiles/gcc.sum | 4783 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1024948 -> 1023508 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202216 -> 201860 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2660 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422776 -> 427092 bytes sumfiles/libstdc++.sum | 10 +- 41 files changed, 2885 insertions(+), 6481 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