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-arm in repository toolchain/ci/base-artifacts.
discards d1da188a80 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] discards 48db3fff04 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 0405b777eb 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 16af9fbb8c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 5480015ec1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards e3b9fdbaa4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards 1e663a9042 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards 52ea0cb736 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 986555f5d9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 9d8f106de1 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards f44d7d71b2 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 3ab854d060 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 562574e476 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 1a8e5cf26a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards d80e1f05e5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 089b423d23 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 75c3ad7c79 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 695a2bf3a5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 65e223b683 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards a489745c37 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards ee8ee2251f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards 623153d069 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards df354603ee 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards 81c7a2203a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards 7c7102eda1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards 1c0fb77a52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 55f8f09597 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards aa95b2d17e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards ed5e36fa57 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 2bdce65cf2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 6a4bba0402 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 86fd3ccad3 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards 15e97fc96a 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards 191b5901d3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards ae0fba5b9b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 9f7bd9ff57 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards 74af86ce04 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards ae458b159a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards c396244e10 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 79bd89044e 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards dd9e8c4862 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards cf3cc03dc2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards 0d85506880 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards 30a59ccef0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards f76a860c35 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards 22e5b6d190 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 7ba5b904bf 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 968c6a6abc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 30c22fc2a6 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards 990f479d67 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards ebbcab6fb6 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards d4e1e9ea74 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards 3b132be110 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 61644a76a0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards b4fc00d608 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 83dae4a708 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 026834b9b0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards ac43432cb2 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 1fa46a8323 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards cca2670b69 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 5260c4fa2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 39eb23c4fb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards a7e773ebeb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards da40f8bf37 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 0743dc022e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 853469ec78 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 356f240792 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards da5855f53c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 11629f7a12 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 8ab1059922 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards c4e4c534f5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards 541340611d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards cf32b3739a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards 7a33b26c63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 2966cdfba9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards b805ff64b5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards f69834a310 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards aab99f3084 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 01dcdc4d2c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 611f6d69bb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 547341ec11 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 902f69c40f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards f377976a29 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9ec3c2a2a7 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 94e9aef106 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 422375620e 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards c8769e3b61 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards c4cf95d7d7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards bbc71d1571 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 55b165bb90 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards eea3093a23 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards e800728c36 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 18d92c923e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 3485756c0d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards b608db89fd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 66c152703f 301: onsuccess: #2118: 1: Success after linux: 16 commits discards de38d86801 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 0fbfa5a634 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 8c9f6baa43 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 5f6ede2ff8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards ebd53026c1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 4aa5649fc9 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new f7815925b6 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 7a2eb97e5b 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 3e6309063a 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 9920a37271 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 0fdd16c443 301: onsuccess: #2118: 1: Success after linux: 16 commits new 6bd6859e0b 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new ff8567fdc8 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 276df279d9 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 10c11bebcc 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new 019d130f81 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 099d9f19fa 307: onsuccess: #2124: 1: Success after gcc: 2 commits new 30ec737c10 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 2e969e5676 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new 51c6f84e14 310: onsuccess: #2129: 1: Success after binutils: 4 commits new fbc51565bd 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 06c7892017 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new e2a26665dd 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 33f514a94e 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 4df974a83f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 149108daf0 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 6b39a72224 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new ab4cedb9bd 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new ca1790a4e4 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new c99123ef96 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new 40fdd39ee1 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new a1ac9c7493 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new dd28aad890 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new 78973d0811 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 917ba96cb4 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new e0216145e2 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 3acfafdfc4 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 8d7c21f6a1 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new cd9c63c78b 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 92824673af 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new ace3d26754 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 3051148946 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new c045bd4062 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new dbc8526681 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 1c50c57cde 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 7d68ed7ea4 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new 23a7f59a7c 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 0a84d89044 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new d51f9a1964 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 76a77c2be1 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 1324ba9283 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new 781abce72f 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new eacd0c7e69 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 5f47bccbc7 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new 621d2b3f61 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new 3a949d918f 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 3e615efb37 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new fc3d0697f5 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 303f5a4126 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 5d35f03211 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 40599d572b 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new 84a472cbf1 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 9f8c71a9b8 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new d1f3785cf1 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new 193d696582 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new ab97d6a9dc 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 9b37a77e72 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new c42a45810a 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new 2c6899fa6b 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new de8d965520 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new a277856390 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new 9052c946ef 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 671a9096b6 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new d67c9d0e5d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 75f9f44148 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 48f4aa2f05 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 4fca1d7451 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new 0fc9bee10d 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new 557c6c5edc 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 21c09e845a 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 11027f54c6 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 2bab471ea6 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new a2413d4fdd 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new c7e7a36caa 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 333a53d8d3 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new 6b9cd94a62 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new 16ee579285 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new de4608cf8b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new f5d48a5fba 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 76cca0f78d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 4b43491f64 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new 1b6b5f4c31 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 53e7ab9670 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new bd2ca0b42c 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 5eae999a38 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new e83307dd57 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new cffc987933 387: onsuccess: #2208: 1: Success after gcc: 2 commits new dbf9890d02 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 1c9a8e3951 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new e6c7e32e7f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new 89ebe5671a 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new b90bc11e67 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new e9e8375fcd 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 1871e8d733 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 12e93408b4 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new 8de1a61ad6 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] new 531983cc33 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/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 (d1da188a80) \ 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 1816 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 31040 -> 30868 bytes 04-build_abe-stage1/console.log.xz | Bin 91984 -> 91792 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 9376 bytes 07-build_abe-glibc/console.log.xz | Bin 236352 -> 235792 bytes 08-build_abe-stage2/console.log.xz | Bin 229732 -> 228136 bytes 09-build_abe-gdb/console.log.xz | Bin 38488 -> 38460 bytes 10-build_abe-qemu/console.log.xz | Bin 30832 -> 30636 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2984 -> 3104 bytes 13-check_regression/console.log.xz | Bin 7400 -> 6780 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 60 +- 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 124 +- 13-check_regression/results.regressions | 25 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 62 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 25 +- sumfiles/g++.log.xz | Bin 2650780 -> 2651172 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 2186412 -> 2205476 bytes sumfiles/gcc.sum | 2069 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 886596 -> 893624 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217064 -> 216992 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 434616 -> 434720 bytes sumfiles/libstdc++.sum | 35 +- 42 files changed, 1268 insertions(+), 1307 deletions(-)