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 8d7c7c469c 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 95c6507025 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 51be600a40 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 15de3c6809 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards f33a886239 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 6a96402747 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 0c50b22ae4 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 7153447b6e 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards e8a8c7502d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c54a9c5f7b 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 94b8ea0f4a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards f26b4cdbca 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 6db0e6c0a1 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c6e2c33d0a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 29a70d0b54 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 9d6b7b0e80 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 625d116bbe 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 082fa047d3 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards b9709ef95b 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards cf0652603b 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 10d81acc24 128: onsuccess: #2163: 1: Success after linux: 23 commits discards d5db18d0f7 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards b6c0643121 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards e4bfdd4abb 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 3325d02be9 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 6cc05e5624 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards ffe4431def 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards f7ad2f6316 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 94c04a5f57 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 2b90114150 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 372c387758 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f56796bac7 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 5653796366 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards f20bb816e3 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards f07c6d9d58 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards b964d9f3e0 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 6b6b095b92 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 47427e431c 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards f1a9466180 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 982a17acd7 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards d1f15b047b 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 44f42f35c6 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 5696baa323 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e4cde253d1 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 4e2ffc9cd2 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 3f903735e5 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards decfeec8e3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 6758cb5594 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 35c1ecbbf0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards d0bed38f44 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 359fe894c6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 41442abfa2 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 6b5bc0cea5 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 6ed94ceed4 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 7af715a089 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 6a9c7f4ffc 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards fa99c540ae 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5939ffc277 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 30975777f7 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 42f3de4f4e 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 7048f29b05 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 58b2cc8a13 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 8ce25d9885 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 0bc5842ac4 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards a08724c72e 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 29fee573aa 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 9771065088 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d3293e855f 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 95aac3f2f9 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b40e997cc7 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e3891899f0 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards e6bd2f265f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 20ae0d0866 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 159fb0ed1a 75: onsuccess: 1: Successful build after linux: 44 commits discards 42e3875761 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 693f3ee443 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2a709bde5a 72: onsuccess: 1: Successful build after linux: 12 commits discards f33f755936 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 00ec16b4ec 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5fdb48379d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1489e35af4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c053ad5a45 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards c77dfc0562 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 2e9657342d 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 650eb66a56 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 535f2172be 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 179b58ed36 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards c0991fcfba 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 11a568fcdc 60: onsuccess: 1: Successful build after glibc: 2 commits discards 9eec14cb3a 59: onsuccess: 1: Successful build after binutils: 2 commits discards 19f947f453 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards d344c1bbd0 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards bed1f15b02 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 93f68926ec 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards d7c77f090b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b3bbfa9880 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards c461f8c798 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards cd0ae7b02b 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 389dc05e40 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 49725838f8 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits discards de70a92094 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 73782144e0 48: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5ba68a9a2c 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new fcec6f040d 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 38b471d422 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7a9af80545 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new f1d776dae8 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fe552c13fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b5cba90cf6 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 6c7975bdd1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6cb86e6167 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new aa89bcc27e 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 52ce0615d4 59: onsuccess: 1: Successful build after binutils: 2 commits new 9d7d425595 60: onsuccess: 1: Successful build after glibc: 2 commits new 42ad138b43 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new cb00a936e3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 3b2d3d67d0 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 8efc7d8983 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5f29b3ba2e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7db092a812 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new bc4af4adb1 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 11855e3215 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 08cef7c0ef 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new d7ebc80d6b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 688d19f492 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new fc2e250e01 72: onsuccess: 1: Successful build after linux: 12 commits new de79be4b4e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 153975890e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9868bae5de 75: onsuccess: 1: Successful build after linux: 44 commits new 8f93137f46 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 596f51bf5f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 0b7ee2e242 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 088082f6cf 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3630bccb34 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d16182f3a8 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 4252114308 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f0072d988e 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 4be6b45285 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d5eb8ee89b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 82d4a13218 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new e7fc646075 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 852f1e375d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new d05520b230 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new a013803e09 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 45964ae13e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 40e11a73b9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 7f219aa211 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8ba757f68d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 9dec19115d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 8d4d7117d4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 4953c55cbd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 92926633a6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 1fd337ac29 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 819069775c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new e8ed7d53f6 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 72d7e0a86e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 7185f03e83 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 8f2bc2d27a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new a9dee08102 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 82d2ffd300 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 8842e5eb0c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new bd511456de 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 121f21be3e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 0ae1aad08a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 45f514c7f0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 79e66bf016 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 4120842d02 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f131bfe70b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 37e09446ca 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new abf19fe719 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new c3eefb6e1d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 944cdeb5f1 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 7296c59047 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new d7a13cce22 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new ace728951b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new bb9c4a82ef 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 1e7005c8b2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 30e7569d3b 124: onsuccess: #2159: 1: Success after linux: 23 commits new 2460b23319 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 2819cae131 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 94fb3166c9 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 6c464ec6a2 128: onsuccess: #2163: 1: Success after linux: 23 commits new 7221331945 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 44f7516f80 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 65e4c44109 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 1e4867d1ac 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 1668cdf17a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 0605fdfd5e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 9b2a17e50b 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 524294315c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new c77928f0df 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 751f3a74e6 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 99758448bc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 49e9d65eab 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new b1a9105ac5 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 5d2328e294 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 86f89b4ec1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 94a9d6a9b1 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new b43fe059a4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 1c2a30e258 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 9aa4792449 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 390c059681 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new fb658c74c7 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...]
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 (8d7c7c469c) \ 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30500 -> 30188 bytes 04-build_abe-stage1/console.log.xz | Bin 72280 -> 72476 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8652 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 240452 -> 241060 bytes 08-build_abe-stage2/console.log.xz | Bin 202832 -> 203040 bytes 09-build_abe-gdb/console.log.xz | Bin 37736 -> 37380 bytes 10-build_abe-qemu/console.log.xz | Bin 31808 -> 31740 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3928 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2640 -> 2524 bytes 13-check_regression/console.log.xz | Bin 6852 -> 5988 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 204 +- 14-update_baseline/console.log | 40 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 3413528 -> 3438500 bytes sumfiles/g++.sum | 213 +- sumfiles/gcc.log.xz | Bin 3029764 -> 3011448 bytes sumfiles/gcc.sum | 4621 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 1035540 -> 1033388 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202108 -> 202616 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 420408 -> 428988 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2522 insertions(+), 2700 deletions(-)