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 ac4b585383 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] discards abafad1d63 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] discards 3ee4e9c169 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] discards 23c73fe47d 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards eacb44af22 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards fca5e90383 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] discards e7a6515952 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] discards 1eef9370f9 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] discards 848b8eb4ba 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] discards 1bc86276ec 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] discards 03f94bd424 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] discards eba5773860 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 1ff40d8d51 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits discards 67289af8da 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] discards f5e5c26486 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards e4416ef864 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] discards d4ecf5e6f3 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards 765357880d 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards c618163db8 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards ee4d018647 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 7273546e78 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 945a9ad034 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards b922dc1a20 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards ca7702cb12 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 4f84ab730e 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards d545157c6a 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards ffd17911d0 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards c54e997681 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 67939d7c4d 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 7933641e8d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 837e8171c0 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 3adec6a604 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards 6abfd39626 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 68f747eaa7 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards e95cb6d7f6 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 2ac2e4fbf6 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 72924c8784 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 43a59370c5 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards d05b6864d2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 147bff82fb 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 7b73dd2199 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 6d2e97c045 128: onsuccess: #2163: 1: Success after linux: 23 commits discards ddcf2409ec 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards a6468dc900 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards e9bfa109f9 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards 8d9c029fea 124: onsuccess: #2159: 1: Success after linux: 23 commits discards ee149f6f97 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards 107abfe735 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 2877cc1461 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 389500abe4 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards 0dd62a1d2b 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards a70251f01e 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards f7fb1df333 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards 89120d82ba 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards 30517d7931 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 7b76344c79 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 88a7e320c1 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 7ef997f5c3 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards f2a9872c0e 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 398c4bf10d 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards 5e8ec89d49 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards d1fbe57af4 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 7ff5ac3616 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 53ccd48622 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards fee4097cca 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards f3a389fef4 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards e1d84ec7d5 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards 1c23142ba6 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 313f240578 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 855f01adf2 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 472ab4581b 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c31ac63f72 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 7dc6eece9a 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards b31e8341fd 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 145b527a2e 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 4602abe110 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards 0b7a09e171 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 5350572a74 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 942fe15a7d 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 6bba865f7d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 12939b4017 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards ca43f887b5 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards 3dc5ada593 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 2add9a7170 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards 650d755ccc 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 31e531637a 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 12d8245521 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards f60f857584 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 6de47d02e4 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 0b36046607 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 1e2535173e 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 78c7fa04c7 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 110e4e4988 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards 162ac62811 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 76b8ecdf6b 75: onsuccess: 1: Successful build after linux: 44 commits discards d85ab6e05a 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 82a9b615ac 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 92c7a35100 72: onsuccess: 1: Successful build after linux: 12 commits discards e47725fe06 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 78e3b09cd7 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bf6428eff5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 257ff7d639 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new b1b0957b27 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 9911c3be18 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new 516a96a491 72: onsuccess: 1: Successful build after linux: 12 commits new 596dc1e4c5 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c8dae6a62 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 5ad4e371c7 75: onsuccess: 1: Successful build after linux: 44 commits new 00bff74630 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2782b74b74 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 2cf4006b6f 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new acf3bf9e23 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 274de1f6cb 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e3e3cabf96 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new ad58a42a48 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 83dc123e07 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new de8c566ac0 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new f597b15025 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 5c9f3b5221 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new 35ccf06fbe 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 4bb9c47cd0 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new d21c55d731 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new c40cc1850d 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 4ae18547a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 132a0d11db 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 80de97cf78 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 23c9d28d48 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new 18e303f8b1 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new 1459ea44d1 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 1c1f8cbf86 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new d4fbaa667a 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 88d4a4d1f8 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 5b6809d7cf 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5e83c280e8 101: onsuccess: #2130: 1: Success after binutils: 81 commits new bb0000e4cf 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new bf48ee3235 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new 09780ccfd5 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 2874a33cec 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new cda2787f74 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new 711ab3d832 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new f58f2c75e6 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 3464ddb026 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 9061ae6acc 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 5f95ec78fb 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new f88a00b2c4 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new 30f363efef 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new 581a6cf96c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new d207680feb 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 5b74fa32ea 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new f49095129b 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 52de90d588 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 000c1e7f8c 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 3e277b0413 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new bc81afb17c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 1851c30f60 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 0d7af62a22 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new afbcd49a44 124: onsuccess: #2159: 1: Success after linux: 23 commits new 824de7865d 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new f43cb6ff69 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new 68847552db 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 7bca415181 128: onsuccess: #2163: 1: Success after linux: 23 commits new ff02477f4e 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new cfd06e24b0 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new 23f8204fbd 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 9ded356e65 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new 39f4a1b798 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new fe22393d59 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 726025ac66 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new c073f9d3db 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 2a9a71a420 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 45719a330a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 3f2c606640 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 21264f1b13 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 04b72780af 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 80ad6e13b9 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 7a22e65646 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new feb058d58f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new 0f4df8aec8 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new c42f0a1812 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 3256fe5eee 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new 4dd9aa1f6a 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new 1725cac99d 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new bd1270d101 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 04af39b9f0 151: onsuccess: #2186: 1: Success after gcc: 2 commits new 0d7c785a71 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new ce98df23a9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 37d6dcb946 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...] new 16cd349383 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 78831c1cfd 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/g [...] new 6e43586169 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 commits new 2a26378aa2 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new 1f492c06a1 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 197 [...] new 015a5b072f 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/g [...] new 69666dc9a9 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/g [...] new 0f8bd032cb 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/g [...] new bb9a26491f 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/g [...] new 62a1a770e5 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/g [...] new 9c342d0c84 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new 74f6a0bd04 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new 6aba51a1fc 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qemu [...] new 0d7e2f6455 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/g [...] new 450f30d492 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/g [...] new 22218a2e5a 170: onsuccess: #2205: 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 (ac4b585383) \ 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 1752 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30612 -> 30872 bytes 04-build_abe-stage1/console.log.xz | Bin 72668 -> 73836 bytes 06-build_abe-linux/console.log.xz | Bin 9456 -> 9484 bytes 07-build_abe-glibc/console.log.xz | Bin 240312 -> 239708 bytes 08-build_abe-stage2/console.log.xz | Bin 203316 -> 204500 bytes 09-build_abe-gdb/console.log.xz | Bin 37676 -> 38052 bytes 10-build_abe-qemu/console.log.xz | Bin 31376 -> 31656 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3924 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2656 -> 4144 bytes 13-check_regression/console.log.xz | Bin 12400 -> 26556 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 386 ++- 13-check_regression/mail-body.txt | 174 +- 13-check_regression/results.compare | 362 +- 13-check_regression/results.compare2 | 4374 +++++++++++++++++++++--- 13-check_regression/results.regressions | 172 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 176 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 172 +- sumfiles/g++.log.xz | Bin 3438112 -> 3400624 bytes sumfiles/g++.sum | 3843 ++++++++------------- sumfiles/gcc.log.xz | Bin 3007960 -> 3007952 bytes sumfiles/gcc.sum | 5644 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1028612 -> 1035680 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202472 -> 202704 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2692 bytes sumfiles/libitm.sum | 7 +- sumfiles/libstdc++.log.xz | Bin 424388 -> 423672 bytes sumfiles/libstdc++.sum | 170 +- 44 files changed, 9497 insertions(+), 6115 deletions(-)