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 aeed0adf8 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 17f7d0a7d 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 26f4f1da5 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-283 [...] discards 6d2291519 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...] discards cef12838c 124: onsuccess: #2159: 1: Success after linux: 23 commits discards c1ea316b1 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] discards cbf15f68d 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards e893dde3b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] discards 0bb4c277e 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] discards 03b6b3e90 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] discards c82969701 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] discards 654a8c29e 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] discards 9abc4c8c1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 1b488ef9e 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] discards d7281c91a 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] discards f8254b7ee 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] discards 21b304b76 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] discards 4ad0b2e43 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] discards d7b935de5 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] discards cf478e855 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 9c22334ac 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 67e6426a2 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 6082e9d6d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] discards f0cb96259 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] discards e0bcd0ed4 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 1b4a90ff8 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] discards 06ed925d0 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] discards 0f9cb51a1 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 87ead92b2 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] discards e6b680138 99: onsuccess: #2074: 1: Success after baseline build: no new [...] discards dc97bc8cf 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 0db390e75 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards b179ab29a 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 7e2d97c33 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] discards c7eb2493a 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] discards 509ae5a18 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 7a98832a9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6c798a75d 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 10f02ecf0 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 03180b48f 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 55966d26e 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards bfc845b3f 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 40df6b8a1 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 15975a456 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards ea65c0f7d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 49bf34729 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards cd16b8d44 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards dc70f82c1 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits discards d0b4f04ba 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9a2bb3e57 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5afde2eb6 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 89f8e43b9 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits discards d2af31dff 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 31a055fdd 75: onsuccess: 1: Successful build after linux: 44 commits discards 2ce98140c 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards e12adaf94 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 48d44ede8 72: onsuccess: 1: Successful build after linux: 12 commits discards c75e9aa75 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards b50e2d9c0 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards c27164fa1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 2453c9f8d 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f5c0d31eb 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] discards 51f5c02ce 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards ceec0d866 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d91fab40a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 461222a1d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 612a85b48 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] discards 18204364f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 99a49d712 60: onsuccess: 1: Successful build after glibc: 2 commits discards 81092427a 59: onsuccess: 1: Successful build after binutils: 2 commits discards 434400305 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] discards bb540aeb8 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ce9f4d75e 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 65256a036 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] discards 20568a5ce 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 3235d1efe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards ba04cbe71 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits discards f94e3e8b2 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 79f4f951d 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 49604e431 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards 45de1213a 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f4bbc46d3 47: onsuccess: 1: Successful build after linux: 10 commits discards 8b805f385 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f2d675693 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b33406c84 44: onsuccess: 1: Successful build after gcc/linux: 35 commits discards 6f547eb97 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] discards 3628c83f1 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] discards e0bccf732 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1fe8dc0ef 40: onsuccess: 1: Successful build after linux/qemu: 147 commits discards 6ce99322b 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 2195fada7 38: onsuccess: 1: Successful build after gcc/linux: 95 commits discards 223c12031 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 629fe8e67 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a678fbc3d 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5519524b3 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 509ccc4d7 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0d0c0b9d1 32: onsuccess: 1: Successful build after gcc: 7 commits discards 6c17f1abd 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards aa4258633 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 0297e4c63 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards caea53670 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 93cadb5b8 28: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 68cc5a46f 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aabc31e57 30: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 7fb7ec1b0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d0edb8f86 32: onsuccess: 1: Successful build after gcc: 7 commits new af68fcf74 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 726c55a03 34: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4e912f505 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 08ef82439 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c4204fd2b 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5225daa46 38: onsuccess: 1: Successful build after gcc/linux: 95 commits new 329b2571b 39: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 4ecad2fce 40: onsuccess: 1: Successful build after linux/qemu: 147 commits new bac03f810 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ef67d63aa 42: onsuccess: 1: Successful build after gcc: libcpp: Impleme [...] new c7ca264bb 43: onsuccess: 1: Successful build after gcc: LoongArch: Add [...] new 924a3974c 44: onsuccess: 1: Successful build after gcc/linux: 35 commits new c65a3b9fd 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1d6bc55e8 46: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 48532a820 47: onsuccess: 1: Successful build after linux: 10 commits new 70d764c4e 48: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new de3e00a54 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 8c1d7bd36 50: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3a7339bfe 51: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d012575e0 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 commits new 3f87c1b1e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 116ad9148 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 203cc585b 55: onsuccess: 1: Successful build after gcc/linux/glibc/qemu [...] new 4df6af025 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fdf5525ae 57: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fb943af2f 58: onsuccess: 1: Successful build after binutils: gdb: new ' [...] new 3d1ffdfc4 59: onsuccess: 1: Successful build after binutils: 2 commits new b25c757db 60: onsuccess: 1: Successful build after glibc: 2 commits new 7122f926d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 51c146b94 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 22 [...] new a8fb7cbb5 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 9a31f25b2 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0eb244d8d 65: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new af26dfdac 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 41a77c666 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 10 [...] new 2d598076d 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a65b46af3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new f2302f389 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new a519450d5 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new e0ff04508 72: onsuccess: 1: Successful build after linux: 12 commits new fb3441f03 73: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5b35a6b2e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5332fb995 75: onsuccess: 1: Successful build after linux: 44 commits new 5d2ba8f28 76: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 145e87564 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 commits new 8dcf6fa31 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new c3e52a629 79: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 79e47ffc4 80: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f1b5d648e 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 commits new 2af0a0ef6 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 75037182e 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new ef6054c60 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 71f21d0dd 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 1b223f75d 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new edc7f9dde 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 509df9a2a 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new a196fea2b 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new bb29915c4 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new ef675a99b 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 84a980b15 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e1dd9ff48 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 014446a5c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP 5 [...] new e12dc33f1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-2389 [...] new 1e99357a7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new e0a26c64a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 20838ce18 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new e4b776259 99: onsuccess: #2074: 1: Success after baseline build: no new [...] new 493ff0494 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/gd [...] new 24659dbcd 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 85265bdb6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-19 [...] new 96c2f8c73 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/q [...] new d4bd4cfed 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new e20f9431b 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-271 [...] new 766d8b213 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/gd [...] new 0107e3c9d 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 735f0f8f7 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new f652280c1 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 51fc658f1 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/gd [...] new 22e062b97 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/gl [...] new e208a193c 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/gd [...] new 6fce869d7 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/gd [...] new 39d97639e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/gd [...] new 4f3004a95 115: onsuccess: #2147: 1: Success after binutils/linux/glibc/ [...] new 84b815789 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 0151ecbd9 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/gd [...] new c85b7195a 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/gl [...] new c4c62aabb 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/gl [...] new 388750ab0 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/gl [...] new 6e2221887 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/gd [...] new aebd9dd99 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 6b403760b 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-283 [...] new d92e8f18a 124: onsuccess: #2159: 1: Success after linux: 23 commits new d93b7bc53 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/gd [...] new 8999b2c82 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-283 [...] new 31aedf976 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 4c1883752 128: onsuccess: #2163: 1: Success after linux: 23 commits new b3895bfbf 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/gd [...]
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 (aeed0adf8) \ 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 1732 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30380 -> 30236 bytes 04-build_abe-stage1/console.log.xz | Bin 72952 -> 72272 bytes 06-build_abe-linux/console.log.xz | Bin 8824 -> 8312 bytes 07-build_abe-glibc/console.log.xz | Bin 240500 -> 240760 bytes 08-build_abe-stage2/console.log.xz | Bin 204580 -> 205820 bytes 09-build_abe-gdb/console.log.xz | Bin 37608 -> 38268 bytes 10-build_abe-qemu/console.log.xz | Bin 31648 -> 31644 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2912 -> 2464 bytes 13-check_regression/console.log.xz | Bin 6680 -> 13360 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 75 +- 13-check_regression/mail-body.txt | 187 +- 13-check_regression/results.compare | 126 +- 13-check_regression/results.compare2 | 1868 +++++++++++- 13-check_regression/results.regressions | 115 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 189 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 115 +- sumfiles/g++.log.xz | Bin 3405272 -> 3422004 bytes sumfiles/g++.sum | 1883 ++++++------ sumfiles/gcc.log.xz | Bin 3028632 -> 3028000 bytes sumfiles/gcc.sum | 5057 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1031472 -> 1029312 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201980 -> 202060 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420192 -> 427872 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 5977 insertions(+), 3772 deletions(-)