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 eb7339a4a8 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 697ed8a9f4 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 6e487becd9 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards ce48f072de 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 6ed5438594 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 92922a2be4 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards bc88c36c91 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5c729a4148 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 82ca4ef3f1 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards ff73a233e8 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards d7f59292e3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards a53fcf24bd 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 5c67743b47 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards cd0672b5e3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 004503ef06 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards daf83f037a 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards b80a5d451f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 1ffa4d04b3 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards e0da216d0a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 6c2d745882 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2ede3446c9 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 48179d035d 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards bdcb0c95fb 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 75185f98fe 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 66062a554e 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards f6df9c3ca4 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards bef18d16d2 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 630493ff38 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards d1b9630fd5 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards acda6ae050 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards e16a53816e 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 6aa4b0c4a7 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a6190937e9 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 8fa47ff213 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 360e13b317 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 4826b13519 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards e79d998d25 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7eeeb50521 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards d8b11c088a 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 429c75f84a 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards d288051c76 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 89a2c0cfa3 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 6c768c41a6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards dd71f1dd68 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 49ead43d56 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 3ad84f798a 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards bac7e0a175 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 96b6900835 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 3ca01c611f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards eb695b2f24 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards e4ac5a1057 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 2d0c22adca 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards b53a59fc91 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards a5fb4df8ea 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 007eb97a94 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 430fe56d7b 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 5315b08ee1 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a6a106682d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards e1dd9bcd5c 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7568a0ef46 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 8071ac88cf 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 6f284d9e77 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 1874b03c00 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 176499303d 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards ae6a318a53 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards a7f4188a9f 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 3bae85608b 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards dbd5806d13 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7753741514 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1a4abe82a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 284c5e82ce 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 504de0a5ef 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0dfdb94337 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards d0f83ac534 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards d6aca2f47d 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9b524b84c 75: onsuccess: 1: Successful build after linux: 44 commits discards c43b276759 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 833b96fa17 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9ed50c670e 72: onsuccess: 1: Successful build after linux: 12 commits discards cbb626bd1d 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 944a208bcf 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 7d3089ac2e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards d012719d99 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8cf5b5f510 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 8a51a66269 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 87ab95e678 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b408306f95 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 164d95d30b 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards d763481550 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 79815bb43f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards e349a63a86 60: onsuccess: 1: Successful build after glibc: 2 commits discards cf66ffc8b0 59: onsuccess: 1: Successful build after binutils: 2 commits discards 08ed925a2b 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards ea4ba54f2f 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards cd764bfc0b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2ec0641d1a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards fea7f4cc50 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 884ef541cd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 5673f96610 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards e502a4213b 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 48f2206bbe 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e0f9fc0c8c 50: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0bf7feca28 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3a2507915 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new 08743b3fdd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 43b9d4a9b6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c275f03fb4 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 88915b49f7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 59655c07ec 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 60443b2561 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 577e843f00 59: onsuccess: 1: Successful build after binutils: 2 commits new 3ff75e1fdf 60: onsuccess: 1: Successful build after glibc: 2 commits new dcf44eff59 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new fc00e91859 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new fe184a6add 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3e57bc0e0b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e05ef882e9 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b410f816a6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 1b02fbe001 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 14585422cc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a8d51ec456 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new d69c299ed5 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c9e14f5f52 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 7bf7b52fb3 72: onsuccess: 1: Successful build after linux: 12 commits new 9c3e447af1 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f50420b867 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 92fdb6add9 75: onsuccess: 1: Successful build after linux: 44 commits new b5a6625b93 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 26e49df14a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new f3761975d2 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new ce537a1ca0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8513f6306f 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 4b5d78e4a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 7f7c600717 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a328704a65 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new fb22afbf7d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fda7541c8c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new cd8c03396b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new b731a62853 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new f2e9c352d7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new d3653ccfc4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new ee20939a8a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 60e1688217 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 5e282f3b8a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 93c83a4f89 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new fe21c4113c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d31ce8d33e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 764e790fd7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 9d8875decb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new b20db61f5d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 16bd20a9f3 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 82543d9b4b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 1bd70fdbe8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 1fa98d81a3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new a94519ca0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1a00e6566f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 23bbb22461 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new c4b843f500 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new fca395bc31 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 0b921c00ce 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 14aead96a8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new b8552d8f41 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 4f09e584e0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 8e118c9b3d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 52108643d0 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 2e67d1c7f2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 8c0b6e2f75 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new e653209cb1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 16770253ac 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new c45308d954 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 6cca899bee 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 87740866b4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new dc5a37d7a8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new f281393b0c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new ecac712530 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 9336ab6f63 124: onsuccess: #2159: 1: Success after linux: 23 commits new 116c2d91c3 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 23f66441df 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 899185f3db 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 9e88a336eb 128: onsuccess: #2163: 1: Success after linux: 23 commits new 5ad8f3420c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 5618709d8f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 5e61f8e71e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 1acc64abd2 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new ef9712fcc0 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 7dfd0ce638 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new c3172eb8b0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 9da815801b 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 32f5482ab3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 99c6da183c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 36622b15c3 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new a33ded6894 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new bfaee73947 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 0746420734 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new f3bf294a8c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 4a1f24a92e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new e1e13951b5 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 6e26704665 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 81952a59ca 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 2eb2e09f04 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 3781117740 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new c186696221 150: onsuccess: #2185: 1: Success after gcc: 3 commits new e6438df687 151: onsuccess: #2186: 1: Success after gcc: 2 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 (eb7339a4a8) \ 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30124 -> 30292 bytes 04-build_abe-stage1/console.log.xz | Bin 72704 -> 72612 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 240396 -> 239464 bytes 08-build_abe-stage2/console.log.xz | Bin 203216 -> 203232 bytes 09-build_abe-gdb/console.log.xz | Bin 37508 -> 37504 bytes 10-build_abe-qemu/console.log.xz | Bin 32036 -> 31836 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2856 -> 2848 bytes 13-check_regression/console.log.xz | Bin 9344 -> 9660 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 152 +- 13-check_regression/mail-body.txt | 143 +- 13-check_regression/results.compare | 72 +- 13-check_regression/results.compare2 | 622 ++-- 13-check_regression/results.regressions | 124 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 145 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 124 +- sumfiles/g++.log.xz | Bin 3426616 -> 3405440 bytes sumfiles/g++.sum | 184 +- sumfiles/gcc.log.xz | Bin 3032264 -> 3026724 bytes sumfiles/gcc.sum | 6026 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1038696 -> 1030676 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 202728 -> 202360 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2660 -> 2652 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427560 -> 421788 bytes sumfiles/libstdc++.sum | 14 +- 41 files changed, 3857 insertions(+), 3896 deletions(-)