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 e18d6daa24 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 853e7c7717 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 7ac3f867b8 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 69a39416ea 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 5006cb03e1 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards 777eaffdd2 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 1e993eed7b 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards c2765a2fb5 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards b6153acd4f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 99bef2312a 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards 83c7b85621 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 4b6ea9ac2a 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards db3c83745b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards 4d9f7af32d 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards b7f7f4a43d 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards ac91615e37 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 1edf1366c0 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards 3f332cd4c5 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards d9070cfc69 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 77b8765cee 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 6bd3f33ae2 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards e6448de526 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards ea4f9d04d6 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 163fffdc8e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 5f8b71c40a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 5088c378cb 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards 3605df8610 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards b7ed1a9a2f 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 851981a1fc 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 2a7f3babad 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 5e45b6d5f9 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards c95358486e 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 3419c2bbf7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards a9c378a4aa 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards e79832f07f 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 5680f760e8 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 8514d48403 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 875c9ef0d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 2ea701dd33 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 809b3241c6 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 7fb40cc54c 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 0dd86766a7 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards fc2699cfa2 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards 6877f7a418 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 6769d555f0 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 0435bca341 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards df2b71fac2 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 50925b503f 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 728be28c77 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 329cb6c5f3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards b3ffa4d7df 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 34a0f2a046 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 3e5bf61a7b 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards c0fa9f1f50 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 3d15d1822f 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 5c85382a78 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 3925fed944 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 21a3ba8ceb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 2a1e600fa3 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 7478b50a97 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards dbb042f0fe 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 0ae0b09ded 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards f0873b63c0 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards 51f3228056 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards b2497a9718 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards fad593599b 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 5430c691f6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 790dffe978 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 20dd0aeaea 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards ecba86c5c8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards 3379109346 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 17930ed0b7 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards a455d7d603 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards d91b4de0cc 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 7a296ca038 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0dd27c0cf8 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 88e6a82edd 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 798df13a5a 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 4198919a83 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 06b0404741 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 8cc7353f56 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 60e760c285 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 4fc3690a9b 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards e1385db204 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 1027e8d691 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards dc7e0d8a98 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards 848c3a470c 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards ed3f60a930 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards ac0152c59d 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 484ba5ae18 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 503febccbd 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 01873480a6 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 91ea91fd94 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 39a7e3bee3 75: onsuccess: 1: Successful build after linux: 44 commits discards 458b65aa96 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 830496133e 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8d4ebcfcbf 72: onsuccess: 1: Successful build after linux: 12 commits discards 242af325d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards c69d6497e3 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5c11a675b2 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 8fefcf48b0 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4ad3077db3 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bf6428eff5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 78e3b09cd7 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e47725fe06 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 92c7a35100 72: onsuccess: 1: Successful build after linux: 12 commits new 82a9b615ac 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d85ab6e05a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 76b8ecdf6b 75: onsuccess: 1: Successful build after linux: 44 commits new 162ac62811 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 110e4e4988 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 78c7fa04c7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 1e2535173e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0b36046607 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6de47d02e4 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new f60f857584 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 12d8245521 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 31e531637a 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 650d755ccc 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 2add9a7170 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 3dc5ada593 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new ca43f887b5 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 12939b4017 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 6bba865f7d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 942fe15a7d 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 5350572a74 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0b7a09e171 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 4602abe110 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 145b527a2e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new b31e8341fd 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 7dc6eece9a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new c31ac63f72 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 472ab4581b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 855f01adf2 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 313f240578 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 1c23142ba6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new e1d84ec7d5 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new f3a389fef4 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new fee4097cca 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new 53ccd48622 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 7ff5ac3616 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new d1fbe57af4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 5e8ec89d49 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 398c4bf10d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new f2a9872c0e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 7ef997f5c3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 88a7e320c1 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 7b76344c79 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 30517d7931 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 89120d82ba 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new f7fb1df333 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new a70251f01e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0dd62a1d2b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 389500abe4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 2877cc1461 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 107abfe735 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new ee149f6f97 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 8d9c029fea 124: onsuccess: #2159: 1: Success after linux: 23 commits new e9bfa109f9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new a6468dc900 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new ddcf2409ec 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 6d2e97c045 128: onsuccess: #2163: 1: Success after linux: 23 commits new 7b73dd2199 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new 147bff82fb 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new d05b6864d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 43a59370c5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 72924c8784 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new 2ac2e4fbf6 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new e95cb6d7f6 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new 68f747eaa7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 6abfd39626 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 3adec6a604 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 837e8171c0 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 7933641e8d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 67939d7c4d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new c54e997681 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new ffd17911d0 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new d545157c6a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 4f84ab730e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new ca7702cb12 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new b922dc1a20 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 945a9ad034 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 7273546e78 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new ee4d018647 150: onsuccess: #2185: 1: Success after gcc: 3 commits new c618163db8 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 765357880d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new d4ecf5e6f3 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new e4416ef864 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new f5e5c26486 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 67289af8da 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 1ff40d8d51 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new eba5773860 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 03f94bd424 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 1bc86276ec 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 848b8eb4ba 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 1eef9370f9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new e7a6515952 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new fca5e90383 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new eacb44af22 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 23c73fe47d 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 3ee4e9c169 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new abafad1d63 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new ac4b585383 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/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 (e18d6daa24) \ 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 1708 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30136 -> 30612 bytes 04-build_abe-stage1/console.log.xz | Bin 72176 -> 72668 bytes 06-build_abe-linux/console.log.xz | Bin 9468 -> 9456 bytes 07-build_abe-glibc/console.log.xz | Bin 240004 -> 240312 bytes 08-build_abe-stage2/console.log.xz | Bin 202628 -> 203316 bytes 09-build_abe-gdb/console.log.xz | Bin 37372 -> 37676 bytes 10-build_abe-qemu/console.log.xz | Bin 31792 -> 31376 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3904 -> 3924 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2656 bytes 13-check_regression/console.log.xz | Bin 6384 -> 12400 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 98 +- 13-check_regression/mail-body.txt | 129 +- 13-check_regression/results.compare | 123 +- 13-check_regression/results.compare2 | 1132 ++++++- 13-check_regression/results.regressions | 98 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 131 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 98 +- sumfiles/g++.log.xz | Bin 3443748 -> 3438112 bytes sumfiles/g++.sum | 363 ++- sumfiles/gcc.log.xz | Bin 3017360 -> 3007960 bytes sumfiles/gcc.sum | 5021 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1032696 -> 1028612 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202740 -> 202472 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 424924 -> 424388 bytes sumfiles/libstdc++.sum | 6 +- 43 files changed, 4514 insertions(+), 2815 deletions(-)