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 e6438df687 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards c186696221 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 3781117740 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 2eb2e09f04 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 81952a59ca 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards 6e26704665 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards e1e13951b5 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 4a1f24a92e 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards f3bf294a8c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 0746420734 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards bfaee73947 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards a33ded6894 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 36622b15c3 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 99c6da183c 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 32f5482ab3 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 9da815801b 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c3172eb8b0 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 7dfd0ce638 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards ef9712fcc0 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 1acc64abd2 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 5e61f8e71e 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 5618709d8f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 5ad8f3420c 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 9e88a336eb 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 899185f3db 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 23f66441df 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 116c2d91c3 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 9336ab6f63 124: onsuccess: #2159: 1: Success after linux: 23 commits discards ecac712530 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards f281393b0c 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards dc5a37d7a8 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 87740866b4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 6cca899bee 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards c45308d954 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 16770253ac 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards e653209cb1 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 8c0b6e2f75 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 2e67d1c7f2 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 52108643d0 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8e118c9b3d 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 4f09e584e0 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards b8552d8f41 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 14aead96a8 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 0b921c00ce 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards fca395bc31 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards c4b843f500 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 23bbb22461 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 1a00e6566f 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards a94519ca0b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 1fa98d81a3 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 1bd70fdbe8 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 82543d9b4b 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 16bd20a9f3 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards b20db61f5d 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 9d8875decb 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards 764e790fd7 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d31ce8d33e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards fe21c4113c 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 93c83a4f89 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 5e282f3b8a 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 60e1688217 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards ee20939a8a 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards d3653ccfc4 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards f2e9c352d7 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards b731a62853 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards cd8c03396b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards fda7541c8c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards fb22afbf7d 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a328704a65 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 7f7c600717 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4b5d78e4a5 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 8513f6306f 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ce537a1ca0 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f3761975d2 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 26e49df14a 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards b5a6625b93 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92fdb6add9 75: onsuccess: 1: Successful build after linux: 44 commits discards f50420b867 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9c3e447af1 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7bf7b52fb3 72: onsuccess: 1: Successful build after linux: 12 commits discards c9e14f5f52 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards d69c299ed5 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards a8d51ec456 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 14585422cc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1b02fbe001 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards b410f816a6 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards e05ef882e9 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e57bc0e0b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fe184a6add 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards fc00e91859 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards dcf44eff59 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3ff75e1fdf 60: onsuccess: 1: Successful build after glibc: 2 commits discards 577e843f00 59: onsuccess: 1: Successful build after binutils: 2 commits discards 60443b2561 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 59655c07ec 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 88915b49f7 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c275f03fb4 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 43b9d4a9b6 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 08743b3fdd 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b3a2507915 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] discards 0bf7feca28 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4920f934f 51: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b8d26046d6 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 7 [...] new acee7af3c1 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 3ac44e44b8 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 18614bd02a 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 00c5bbc850 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e4e68beeaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0417ff5cca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 7b18926549 59: onsuccess: 1: Successful build after binutils: 2 commits new 092ade8c85 60: onsuccess: 1: Successful build after glibc: 2 commits new f9de5fa520 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 6a0d49642d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 5becb79a90 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2ee14d9715 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dc34eed820 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae503a0953 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new dfdeb3c4da 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 220e18170c 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c04f277f9 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 0761aa3ce4 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new aef1f635d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new cfcf575760 72: onsuccess: 1: Successful build after linux: 12 commits new 52d4b1de96 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad2f7f09db 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 1afdbc4eae 75: onsuccess: 1: Successful build after linux: 44 commits new 8656b64b8e 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 89e374cb9c 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new c73ada8051 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c6e1e974d4 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1363080bbd 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d523cedda7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 40f13e8a2b 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new a2834d31ec 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 98eca2b187 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 5613d12e4c 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new b0d88fb795 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 519861e50a 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 1761460875 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 3de00f745d 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new a900ed8698 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new d9211b8db1 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 6ec4826787 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ba2c8b932b 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 5872eccd35 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new c11ef400d6 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new ae02da8b4c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 177f987fc3 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 983956e668 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 0067b93e69 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new ac8f36cab4 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 934a139ae3 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 9bbf7a0cb8 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 03c591b401 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 1f8acc9750 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new b5100f8b66 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 8dfd72cfe3 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new cb838bce82 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 0b0d7447c4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5d755e1c8e 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 165fce0b7e 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 48e68689d2 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 1b8fbaccce 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new aa99a97982 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 32fb46244e 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 17514b4380 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 2a1cfdaeef 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new 7fac25b697 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 466b9fb17c 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b1b08ea7ed 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1ccdd20e86 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new be4e97d9da 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 17d9b587a1 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new cd7448bc58 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8eb77bbd6e 124: onsuccess: #2159: 1: Success after linux: 23 commits new da42910593 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 39e417160d 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 5965b9088a 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 636b0befc1 128: onsuccess: #2163: 1: Success after linux: 23 commits new fe3ae2a3e5 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new e78b22551a 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 597e496d36 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 489d03abe6 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 6778a7124c 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 4051a5662e 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new dcc22bcec8 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 3b23288adb 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 8ab35bf65e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 7e00e1b7ba 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new a7758c4970 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new cca0bca499 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 9b31385d80 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 8a94dc384a 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new c308c9f499 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new f34e05c534 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 6f49237c28 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new cf5937fd21 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 03652fcecc 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new f04888c058 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 18433d903f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new b090ef2ba0 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 17fe5be600 151: onsuccess: #2186: 1: Success after gcc: 2 commits new d8c3fe1d26 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 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 (e6438df687) \ 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 1704 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30292 -> 30156 bytes 04-build_abe-stage1/console.log.xz | Bin 72612 -> 72668 bytes 06-build_abe-linux/console.log.xz | Bin 8556 -> 8920 bytes 07-build_abe-glibc/console.log.xz | Bin 239464 -> 240060 bytes 08-build_abe-stage2/console.log.xz | Bin 203232 -> 203076 bytes 09-build_abe-gdb/console.log.xz | Bin 37504 -> 37404 bytes 10-build_abe-qemu/console.log.xz | Bin 31836 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3876 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2848 -> 2752 bytes 13-check_regression/console.log.xz | Bin 9660 -> 19812 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 272 +- 13-check_regression/mail-body.txt | 244 +- 13-check_regression/results.compare | 410 ++- 13-check_regression/results.compare2 | 4149 ++++++++++++++++++++----- 13-check_regression/results.regressions | 146 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 246 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 146 +- sumfiles/g++.log.xz | Bin 3405440 -> 3414820 bytes sumfiles/g++.sum | 2617 ++++++---------- sumfiles/gcc.log.xz | Bin 3026724 -> 3030236 bytes sumfiles/gcc.sum | 5177 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 1030676 -> 1033340 bytes sumfiles/gfortran.sum | 34 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202360 -> 202640 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2652 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421788 -> 427340 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 8159 insertions(+), 5413 deletions(-)