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 c974eec8c9 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits discards aaae8b9a98 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits discards eb0d2c2eb5 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 5e9ce2c692 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 67748ddce0 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 5037f3e509 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits discards 47b3157434 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] discards f6f45ca686 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards ded5e9f481 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards 2698a1617f 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] discards 66950a863c 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] discards eb30d469e4 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards 2b19bb66b6 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits discards 4d72c7ac9d 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards c294c6389d 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] discards 72a938d90a 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits discards e640b68e9a 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 2e8c41fad0 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] discards c375c087fb 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards f4ef12ff19 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] discards 2e4ea7bf31 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] discards 45793d8734 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] discards 7f766c23ac 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] discards 259714adf3 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] discards 0a89644c38 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] discards 211e72c40f 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 44a311f1af 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 388f8e822f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] discards ca431d4021 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] discards feb7775395 124: onsuccess: #2159: 1: Success after linux: 23 commits discards c28effc580 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] discards f1b2e9923b 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits discards 9abdb76c14 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 9c434c2b37 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] discards b1c2e1657a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 5fb91f1dd7 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards ce68806775 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] discards c61b3e5c94 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits discards af63e90745 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] discards 7f8b2b5ed4 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] discards 7c44c50b57 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards 8169b717df 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] discards 3280b6a0b9 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] discards 53c3ccb96b 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] discards d84776fa4d 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits discards 1b252bc42f 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits discards 1361dbb1f8 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits discards 8069f52b3b 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] discards e851ef1544 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] discards 17a724f0a0 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits discards 795d96a765 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] discards cb931c623f 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] discards 2130e3b186 101: onsuccess: #2130: 1: Success after binutils: 81 commits discards 8369a8e0a3 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards 50068afd4c 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] discards c837e522c2 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits discards 1e2d6e079d 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits discards e500a09daf 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits discards 5ee2928305 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] discards 10d78a0fab 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] discards a504260c24 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits discards 39c355949b 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 245c27491c 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits discards 355fa83df9 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits discards 889d0699cc 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits discards 65b97bca9c 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits discards c922711f71 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits discards 3e7e4e7c33 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits discards bb23acee08 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 25b45f26e7 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7da9e9f1f8 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits discards a9e2080c11 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 35387dc2e7 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] discards 81b44c860c 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3fbb8d9cf6 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d21361a0ce 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 09e92d6465 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] discards ad5e9d3917 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fb0cd6d0c5 75: onsuccess: 1: Successful build after linux: 44 commits discards 190b13b4ba 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 1c77c8c483 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea23afa0e7 72: onsuccess: 1: Successful build after linux: 12 commits discards 9924ecf8d3 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits discards 7c74861e72 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards fa3cb83ba5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards a4d4532fd4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f44f50819e 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 4745c3dcb1 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits discards 035093f380 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aefa48c3c6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 44ba1ba40d 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ceed1fdcff 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 7da0537923 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards f3aaef0df4 60: onsuccess: 1: Successful build after glibc: 2 commits discards 73715f6186 59: onsuccess: 1: Successful build after binutils: 2 commits discards 93bf971ed4 58: onsuccess: 1: Successful build after binutils: gdb: new [...] discards 7350e54aa3 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ad390a4e72 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee3f07c7df 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] discards 2d9302893b 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1f1ca48756 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new f9894b2526 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 34ca317eef 54: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 2b11c3cbe1 55: onsuccess: 1: Successful build after gcc/linux/glibc/qem [...] new 4d23312c09 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48a6a6ebaa 57: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 61447effca 58: onsuccess: 1: Successful build after binutils: gdb: new [...] new 8ad950b6f9 59: onsuccess: 1: Successful build after binutils: 2 commits new 8890bfccff 60: onsuccess: 1: Successful build after glibc: 2 commits new 556572c05d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 0791c14d58 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 00c5a29a07 63: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new fc01bf115c 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8d217635b6 65: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 48b5bd8c40 66: onsuccess: 1: Successful build after gcc/glibc: 10 commits new 7e83936eb8 67: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new e064d825eb 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c04746aba0 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new feb063d296 70: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new fb88d81a54 71: onsuccess: 1: Successful build after gcc/glibc: 3 commits new ce233d5e6b 72: onsuccess: 1: Successful build after linux: 12 commits new cbc8a6ee89 73: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8a32fc4488 74: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 74734d50ee 75: onsuccess: 1: Successful build after linux: 44 commits new 5c8ff8f4d5 76: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f5c8cd4ff 77: onsuccess: 1: Successful build after gcc/linux/glibc: 22 [...] new 5f9cb89224 78: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 3239c67024 79: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 390e1e966e 80: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8d364e5b6d 81: onsuccess: 1: Successful build after binutils/gcc/gdb: 6 [...] new 5b62c17768 82: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new eca1677e17 83: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 17 commits new 79b23630d5 84: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e5f153c843 85: onsuccess: 1: Success after binutils/gcc/glibc/gdb/qemu: [...] new 27090cdfab 86: onsuccess: 1: Success after binutils/gcc/gdb: 7 commits new dbfc541e4b 87: onsuccess: 1: Success after binutils/gcc/gdb: 14 commits new 4d82e1c116 88: onsuccess: 1: Success after gcc/linux/qemu: 149 commits new 7030de2c24 89: onsuccess: 1: Success after binutils/gcc/gdb: 5 commits new 7d8fd5fc42 90: onsuccess: 1: Success after binutils/gcc/gdb: 19 commits new 702d6b42a3 91: onsuccess: 1: Success after binutils/gcc/gdb: 8 commits new 4778ac950e 92: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 728856177d 93: onsuccess: 1: Success after binutils/gcc/linux/gdb: 88 commits new 8a365cf2a5 94: onsuccess: 1: Success after gcc: openmp: Partial OpenMP [...] new d1b2427d67 95: onsuccess: #2070: 1: Success after basepoints/gcc-13-238 [...] new a82cf3602c 96: onsuccess: #2071: 1: Success after gcc/linux: 56 commits new 3c0c6d495e 97: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 3 commits new 6ebd5dadf6 98: onsuccess: #2073: 1: Success after gcc/linux: 11 commits new 4c69320477 99: onsuccess: #2074: 1: Success after baseline build: no ne [...] new 350d4713e0 100: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 628325fa6a 101: onsuccess: #2130: 1: Success after binutils: 81 commits new 24e54cb662 102: onsuccess: #2133: 1: Success after gdb-12-branchpoint-1 [...] new 6d89c82827 103: onsuccess: #2135: 1: Success after gcc/linux/glibc/gdb/ [...] new b7dc133863 104: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 3 commits new 7e8e336a57 105: onsuccess: #2137: 1: Success after basepoints/gcc-13-27 [...] new ab6208f50d 106: onsuccess: #2138: 1: Success after binutils/gcc/glibc/g [...] new fc1155c886 107: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 3 commits new 487fe1ff7a 108: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 5 commits new 25fb2ace23 109: onsuccess: #2141: 1: Success after gcc/glibc: 6 commits new 12fae94892 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/g [...] new 0fc7da07e8 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/g [...] new 08e4d4814f 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/g [...] new fbc1b40a3d 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new fd488ab35c 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/g [...] new 213acea74c 115: onsuccess: #2147: 1: Success after binutils/linux/glibc [...] new 93e8cfecbd 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 commits new b85803a92f 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/g [...] new 5dc4416720 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new b9e067cf8a 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 87eb4bce48 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/g [...] new 87870cea6c 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 796dd6cfbc 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 commits new 4cde71f5fe 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-28 [...] new 6ce8802fd0 124: onsuccess: #2159: 1: Success after linux: 23 commits new 18e91df37e 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/g [...] new 13d18aac66 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-28 [...] new a4a18fe655 127: onsuccess: #2162: 1: Success after gcc: 9 commits new 09b1c5ba75 128: onsuccess: #2163: 1: Success after linux: 23 commits new cc9b35b3b1 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/g [...] new a2cbf0188f 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 32 [...] new abf11365a2 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 12 [...] new 9a56e7436f 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/g [...] new fefeaae2cc 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/g [...] new fa84d0d547 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 13 [...] new 539572a8d3 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new df2d235808 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qem [...] new 30e5ede381 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 2bfe33c0af 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 commits new 6b19e634cf 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 13 [...] new 3cb57b59bb 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new 516568f786 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 commits new 68f3ff84c8 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new a07bcdb306 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qem [...] new 650dcc5464 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/g [...] new a813b5b6a1 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new b3db7cc387 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 84dc5a2b68 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 18 [...] new bbbf11ee45 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 commits new a2a347de9f 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 2edc7eea38 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 864296c798 151: onsuccess: #2186: 1: Success after gcc: 2 commits new f6c92d1503 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 commits new 25cc411511 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 commits new 71f554bdb1 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 18 [...]

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 (c974eec8c9) \ 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 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30232 -> 30832 bytes 04-build_abe-stage1/console.log.xz | Bin 72116 -> 72680 bytes 06-build_abe-linux/console.log.xz | Bin 8944 -> 8928 bytes 07-build_abe-glibc/console.log.xz | Bin 239304 -> 240008 bytes 08-build_abe-stage2/console.log.xz | Bin 202832 -> 203648 bytes 09-build_abe-gdb/console.log.xz | Bin 37484 -> 38152 bytes 10-build_abe-qemu/console.log.xz | Bin 31944 -> 31844 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3956 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2448 -> 2880 bytes 13-check_regression/console.log.xz | Bin 31100 -> 18844 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 308 +- 13-check_regression/mail-body.txt | 206 +- 13-check_regression/results.compare | 313 +- 13-check_regression/results.compare2 | 8066 +++++++++---------------------- 13-check_regression/results.regressions | 46 +- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 208 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 46 +- sumfiles/g++.log.xz | Bin 3433428 -> 3415412 bytes sumfiles/g++.sum | 92 +- sumfiles/gcc.log.xz | Bin 2999004 -> 3030792 bytes sumfiles/gcc.sum | 7486 +++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 1029608 -> 1029700 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 202576 -> 202448 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423868 -> 423268 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 6766 insertions(+), 10146 deletions(-)