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 fb658c74c7 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 390c059681 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 9aa4792449 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 1c2a30e258 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards b43fe059a4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 94a9d6a9b1 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 86f89b4ec1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 5d2328e294 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards b1a9105ac5 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 49e9d65eab 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 99758448bc 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 751f3a74e6 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c77928f0df 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 524294315c 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards 9b2a17e50b 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 0605fdfd5e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1668cdf17a 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 1e4867d1ac 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 65e4c44109 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 44f7516f80 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 7221331945 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 6c464ec6a2 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 94fb3166c9 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 2819cae131 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 2460b23319 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 30e7569d3b 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 1e7005c8b2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards bb9c4a82ef 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards ace728951b 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards d7a13cce22 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 7296c59047 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 944cdeb5f1 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards c3eefb6e1d 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards abf19fe719 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 37e09446ca 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards f131bfe70b 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 4120842d02 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 79e66bf016 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 45f514c7f0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 0ae1aad08a 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 121f21be3e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards bd511456de 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 8842e5eb0c 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 82d2ffd300 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards a9dee08102 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 8f2bc2d27a 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 7185f03e83 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 72d7e0a86e 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards e8ed7d53f6 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 819069775c 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 1fd337ac29 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 92926633a6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 4953c55cbd 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 8d4d7117d4 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 9dec19115d 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 8ba757f68d 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 7f219aa211 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 40e11a73b9 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 45964ae13e 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards a013803e09 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d05520b230 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 852f1e375d 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards e7fc646075 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 82d4a13218 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards d5eb8ee89b 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 4be6b45285 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards f0072d988e 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 4252114308 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards d16182f3a8 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 3630bccb34 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 088082f6cf 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0b7ee2e242 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 596f51bf5f 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 8f93137f46 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9868bae5de 75: onsuccess: 1: Successful build after linux: 44 commits discards 153975890e 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards de79be4b4e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fc2e250e01 72: onsuccess: 1: Successful build after linux: 12 commits discards 688d19f492 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards d7ebc80d6b 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 08cef7c0ef 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 11855e3215 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc4af4adb1 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 7db092a812 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 5f29b3ba2e 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8efc7d8983 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3b2d3d67d0 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards cb00a936e3 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 42ad138b43 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9d7d425595 60: onsuccess: 1: Successful build after glibc: 2 commits discards 52ce0615d4 59: onsuccess: 1: Successful build after binutils: 2 commits discards aa89bcc27e 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 6cb86e6167 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 6c7975bdd1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5cba90cf6 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards fe552c13fa 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards f1d776dae8 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7a9af80545 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 38b471d422 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fcec6f040d 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5ba68a9a2c 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 340c427316 49: onsuccess: 1: Successful build after gcc/glibc: 5 commits new 48f2206bbe 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e502a4213b 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5673f96610 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 884ef541cd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fea7f4cc50 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2ec0641d1a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new cd764bfc0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea4ba54f2f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 08ed925a2b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new cf66ffc8b0 59: onsuccess: 1: Successful build after binutils: 2 commits new e349a63a86 60: onsuccess: 1: Successful build after glibc: 2 commits new 79815bb43f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new d763481550 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 164d95d30b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new b408306f95 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 87ab95e678 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a51a66269 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 8cf5b5f510 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d012719d99 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7d3089ac2e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 944a208bcf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cbb626bd1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 9ed50c670e 72: onsuccess: 1: Successful build after linux: 12 commits new 833b96fa17 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c43b276759 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b9b524b84c 75: onsuccess: 1: Successful build after linux: 44 commits new d6aca2f47d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d0f83ac534 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 0dfdb94337 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 504de0a5ef 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 284c5e82ce 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1a4abe82a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 7753741514 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new dbd5806d13 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 3bae85608b 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a7f4188a9f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new ae6a318a53 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 176499303d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 1874b03c00 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 6f284d9e77 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 8071ac88cf 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 7568a0ef46 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new e1dd9bcd5c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a6a106682d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 5315b08ee1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 430fe56d7b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 007eb97a94 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new a5fb4df8ea 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b53a59fc91 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 2d0c22adca 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new e4ac5a1057 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new eb695b2f24 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 3ca01c611f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 96b6900835 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new bac7e0a175 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 3ad84f798a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 49ead43d56 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new dd71f1dd68 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 6c768c41a6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 89a2c0cfa3 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new d288051c76 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 429c75f84a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new d8b11c088a 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 7eeeb50521 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e79d998d25 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 4826b13519 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 360e13b317 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 8fa47ff213 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a6190937e9 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6aa4b0c4a7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new e16a53816e 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new acda6ae050 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new d1b9630fd5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 630493ff38 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new bef18d16d2 124: onsuccess: #2159: 1: Success after linux: 23 commits new f6df9c3ca4 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 66062a554e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 75185f98fe 127: onsuccess: #2162: 1: Success after gcc: 9 commits new bdcb0c95fb 128: onsuccess: #2163: 1: Success after linux: 23 commits new 48179d035d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 2ede3446c9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 6c2d745882 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new e0da216d0a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 1ffa4d04b3 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new b80a5d451f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new daf83f037a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 004503ef06 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new cd0672b5e3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 5c67743b47 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a53fcf24bd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new d7f59292e3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ff73a233e8 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 82ca4ef3f1 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 5c729a4148 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new bc88c36c91 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 92922a2be4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6ed5438594 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new ce48f072de 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 6e487becd9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 697ed8a9f4 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new eb7339a4a8 150: onsuccess: #2185: 1: Success after gcc: 3 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 (fb658c74c7) \ 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 1700 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30188 -> 30124 bytes 04-build_abe-stage1/console.log.xz | Bin 72476 -> 72704 bytes 06-build_abe-linux/console.log.xz | Bin 8604 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 241060 -> 240396 bytes 08-build_abe-stage2/console.log.xz | Bin 203040 -> 203216 bytes 09-build_abe-gdb/console.log.xz | Bin 37380 -> 37508 bytes 10-build_abe-qemu/console.log.xz | Bin 31740 -> 32036 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2524 -> 2856 bytes 13-check_regression/console.log.xz | Bin 5988 -> 9344 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 130 + 13-check_regression/mail-body.txt | 101 + 13-check_regression/results.compare | 149 +- 13-check_regression/results.compare2 | 763 ++++- 13-check_regression/results.regressions | 101 + 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 103 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 101 + sumfiles/g++.log.xz | Bin 3438500 -> 3426616 bytes sumfiles/g++.sum | 90 +- sumfiles/gcc.log.xz | Bin 3011448 -> 3032264 bytes sumfiles/gcc.sum | 5536 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1033388 -> 1038696 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2300 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202616 -> 202728 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 428988 -> 427560 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 4409 insertions(+), 2776 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