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 2b91244e05 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 648e4028d9 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 0bc73929b9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 393ed254c7 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 5426f12bdd 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 612c4ec723 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 4aa9f49cdd 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 76ef6aac5b 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 64afae6b98 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 788f1dea76 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 4e747155ec 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards ec3b6066c2 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 02d927a194 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 1d2a4c621b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards f666ccd97c 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 5c46d9485d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 4e408870d1 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards cd5fd3ced9 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards dd8bc8962c 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards ae80fcbd6c 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 7cb3b260e9 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards d5453e82ea 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e5d1f8eb76 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1725c00de9 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 1fb4a04d24 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 40cebb770a 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 78985b8781 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 50a43eb4f7 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 3aea75f813 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 85f0f35ecd 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 59945b3fa1 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 942f13746b 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 3d8fb56421 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards d98550b35a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 37bdf91a4b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 2f39bcd0b4 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards cf7a655f03 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards a470b747b0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 77651ba5f8 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 24c0d84f21 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 7d605e9ca0 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 75769551d2 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 5b43ed60dc 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 42023fc28c 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 6bf8d1bd76 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 8cf09ff864 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 20aced68bc 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards ee87f56831 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f51c93f233 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a48c13be98 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fd5997f2ac 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 1fa2f105bb 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 155fbdb2b2 75: onsuccess: 1: Successful build after linux: 44 commits discards b6b25c8b62 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2d46ee1faf 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f742c2f18b 72: onsuccess: 1: Successful build after linux: 12 commits discards 81a51cf9d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 3b1783027a 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4aacfd28d6 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 24ee5de0f9 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bf03d09766 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 469c329fb0 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards b13d331792 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6169662f7e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 35f9d016bc 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fe19b0fc25 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards d447fd8bd5 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d5da5257d4 60: onsuccess: 1: Successful build after glibc: 2 commits discards f898a2a8ad 59: onsuccess: 1: Successful build after binutils: 2 commits discards 791f28f6bc 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 7f2bf93b94 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 01252187a6 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d234819837 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards ff0c600bb5 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c6f779c249 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 51048f5cd7 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 90bfefc24f 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cdc41acf0b 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9b85c461a9 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 7ac59cf51f 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 743a6b44f9 47: onsuccess: 1: Successful build after linux: 10 commits discards 6cbfac6eb8 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 3d0a81cbe3 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4adf019850 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 05c99aeda7 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 348495b81e 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] discards 51bb2ad42d 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7e4a13dfcc 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards c71beef93a 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 17bc107a18 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards de1dd49adb 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0332da96cb 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 04fafe275e 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 65809ee9f9 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a0c343b33d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ebf3600571 32: onsuccess: 1: Successful build after gcc: 7 commits discards 7929e2b22b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 75c585ab2b 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 6df1057457 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 722f534308 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c3a6c1184c 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e50ca4861e 27: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new caea53670f 28: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0297e4c63a 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aa42586334 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6c17f1abd0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0d0c0b9d14 32: onsuccess: 1: Successful build after gcc: 7 commits new 509ccc4d75 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5519524b35 34: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a678fbc3dd 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 629fe8e67e 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 223c120313 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2195fada73 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 6ce99322be 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1fe8dc0efb 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new e0bccf7322 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3628c83f15 42: onsuccess: 1: Successful build after gcc: libcpp: Implem [...] new 6f547eb977 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new b33406c846 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new f2d6756932 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8b805f385e 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new f4bbc46d3a 47: onsuccess: 1: Successful build after linux: 10 commits new 45de1213ab 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 49604e431c 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 79f4f951d2 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f94e3e8b2d 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ba04cbe711 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 3235d1efea 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 20568a5ce6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 65256a0362 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new ce9f4d75e5 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bb540aeb8c 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 434400305f 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 81092427af 59: onsuccess: 1: Successful build after binutils: 2 commits new 99a49d7127 60: onsuccess: 1: Successful build after glibc: 2 commits new 18204364fc 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 612a85b48c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 461222a1d4 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new d91fab40a1 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ceec0d8666 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 51f5c02ce7 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new f5c0d31eb6 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 2453c9f8dd 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c27164fa1d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b50e2d9c09 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c75e9aa750 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 48d44ede83 72: onsuccess: 1: Successful build after linux: 12 commits new e12adaf944 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ce98140c0 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 31a055fddb 75: onsuccess: 1: Successful build after linux: 44 commits new d2af31dff0 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 89f8e43b91 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 5afde2eb61 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 9a2bb3e57c 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d0b4f04bac 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new dc70f82c1c 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new cd16b8d44b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 49bf347293 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new ea65c0f7d1 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 15975a4563 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 40df6b8a1d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new bfc845b3fb 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 55966d26eb 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 03180b48fb 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 10f02ecf02 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 6c798a75dd 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 7a98832a95 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 509ae5a187 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new c7eb2493a2 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 7e2d97c33d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new b179ab29ab 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 0db390e75a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new dc97bc8cf6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new e6b680138c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 87ead92b23 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 0f9cb51a10 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 06ed925d0b 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 1b4a90ff88 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new e0bcd0ed41 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new f0cb96259f 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 6082e9d6df 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 67e6426a23 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 9c22334ac2 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new cf478e855f 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new d7b935de5b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 4ad0b2e43c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 21b304b762 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new f8254b7ee7 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new d7281c91ab 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 1b488ef9ed 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 9abc4c8c15 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 654a8c29e4 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new c82969701d 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 03b6b3e905 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 0bb4c277ec 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new e893dde3bb 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cbf15f68d5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new c1ea316b14 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new cef12838c7 124: onsuccess: #2159: 1: Success after linux: 23 commits new 6d22915194 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 26f4f1da54 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 17f7d0a7df 127: onsuccess: #2162: 1: Success after gcc: 9 commits new aeed0adf8b 128: onsuccess: #2163: 1: Success after linux: 23 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 (2b91244e05) \ 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 1788 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 30132 -> 30380 bytes 04-build_abe-stage1/console.log.xz | Bin 72428 -> 72952 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8824 bytes 07-build_abe-glibc/console.log.xz | Bin 239660 -> 240500 bytes 08-build_abe-stage2/console.log.xz | Bin 203664 -> 204580 bytes 09-build_abe-gdb/console.log.xz | Bin 37180 -> 37608 bytes 10-build_abe-qemu/console.log.xz | Bin 31232 -> 31648 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2888 -> 2912 bytes 13-check_regression/console.log.xz | Bin 7384 -> 6680 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 41 +- 13-check_regression/mail-body.txt | 129 +- 13-check_regression/results.compare | 72 +- 13-check_regression/results.compare2 | 315 +- 13-check_regression/results.regressions | 72 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 131 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 72 +- sumfiles/g++.log.xz | Bin 3438748 -> 3405272 bytes sumfiles/g++.sum | 308 +- sumfiles/gcc.log.xz | Bin 3009796 -> 3028632 bytes sumfiles/gcc.sum | 4989 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1026840 -> 1031472 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202204 -> 201980 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 418544 -> 420192 bytes sumfiles/libstdc++.sum | 18 +- 41 files changed, 2992 insertions(+), 3317 deletions(-)