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 2d30c920ec 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards c4688fb95a 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 1f98b522f0 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards fcb497b285 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 70c21106a0 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards ab16ce92a8 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 6a1abf0a6e 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards e2d9a9cf3e 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards b9686060ba 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 628a8df105 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards b73090d615 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards edb11d5e80 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards c3116a0cdc 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 60e41f3389 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 0f01d3d501 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 6d6a652259 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 1eefeaacb6 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 9fefa4fae2 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards fd1e5d7da4 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 4b0b6d98bd 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 1820d6ff28 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 96b0d8a878 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 9fdf0d0387 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 3432d84ab7 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 15cbf8a30d 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards be9a29fc69 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 12054e2836 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 9701a9da1d 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 62f11067df 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards c46315490b 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards 0bcd2ecd20 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 60ce355dbe 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards d90c84343b 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 3827cbc6b7 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 533efc819f 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards d64c324acd 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards ce60784a5b 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards c17e6fbbd7 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards f8398d3d6f 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards eba3ef5c1c 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 52e439710c 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards c6eff935b0 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards c7b3469ebc 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 8454b0c757 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 066ea1ed25 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 3c58a6b983 235: onsuccess: #2483: 1: Success after linux: 108 commits discards ea0ca346a4 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards c19020e4b0 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 13282419d0 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards d9f88f073e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards d037ff2fc3 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards a859e8fd8c 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 63df0298c1 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 512a3340eb 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 05076bcd77 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards ff8010db08 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 4623f8491f 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 1e56dd447b 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 84be8811d2 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards 2abe7cb5de 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards d93d1505be 220: onsuccess: #2465: 1: Success after linux: 572 commits discards cb1d10234c 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards dd93ab9a21 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 0365fc073f 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards e2358af5ce 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards a7e5986efb 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards ff97685745 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards 84f7df78cd 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 5ea73eeb6e 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 8f5e69a697 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 6e65891599 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards de4b418c3f 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards a55c68ccd5 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 4c76808ef7 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 764cbe039b 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards de45a64d5a 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] discards 9f0cfbf855 204: onsuccess: #2435: 1: Success after linux: 3 commits discards a3e6222aa4 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 958537efd7 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 4155064a24 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards f822266d4f 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 31cdd6661d 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] discards 93dcea92ad 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] discards 1c906df0f8 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 5a0a00820d 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] discards 4f9f720107 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] discards e27cdf0cd4 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] discards 5a6182fe67 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] discards 22e35631f7 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] discards 7e86595df7 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 4e9f36a458 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] discards 63c61a8f48 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] discards b7a827f63b 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] discards 15c2335139 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] discards 4cb90cff86 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] discards af5c027832 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] discards 8cf06257a5 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] discards c678bf0acf 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] discards 4329752af6 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] discards 05712c8dde 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] discards cb0ff09aac 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new b3f4221aed 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/g [...] new 32ab0ad0a4 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/g [...] new ac5b81239e 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/g [...] new f322dd39f8 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/g [...] new 04ff8c88e7 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/g [...] new b8e1258e1e 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/g [...] new 1e94ead259 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/g [...] new 1c5bdca66f 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/g [...] new cf68837c80 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/g [...] new 05c1ef0008 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/g [...] new 0e961e77c4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/g [...] new 92e6da0219 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 97dd0cc542 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/g [...] new e143bf0961 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/g [...] new 45f75aa949 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/g [...] new 7624338d4b 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/g [...] new 11be4d5c47 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 41 [...] new cb889851b4 197: onsuccess: #2348: 1: Success after linux: 190 commits new 2539d25c6b 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/g [...] new 2a55bbaedf 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/g [...] new ff652b717a 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 9bc4b7239f 201: onsuccess: #2430: 1: Success after glibc: 26 commits new 495631de9b 202: onsuccess: #2431: 1: Success after linux: 944 commits new 55b3081afe 203: onsuccess: #2433: 1: Success after binutils: 27 commits new f722ae14be 204: onsuccess: #2435: 1: Success after linux: 3 commits new 172a8d89a9 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 6df4a49c7d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new 6bb499538e 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new db4e8c0bf2 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 8c4a877ca7 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new acebecbeb8 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new 56c8334e52 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new 4dfbd6346f 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new 25bcc28a5d 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new ae5be77fc9 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new a7fe1a2d18 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 147e9f1665 216: onsuccess: #2457: 1: Success after linux: 1736 commits new c7187092bc 217: onsuccess: #2459: 1: Success after binutils: 3 commits new f011d87950 218: onsuccess: #2461: 1: Success after linux: 916 commits new 2558c30315 219: onsuccess: #2463: 1: Success after binutils: 3 commits new f90ebcb3ea 220: onsuccess: #2465: 1: Success after linux: 572 commits new 51ec43a897 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 9906a1e21b 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 0ca525c407 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new ded2f72191 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new faa1dd7c3a 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 7a1a4da897 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 72e4247566 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 0fc12a2ed6 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 3df53941c9 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 0e6876ae59 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 34dea25521 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new bacebdd016 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 10ff0ae576 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 04aba8765e 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new b59df6e317 235: onsuccess: #2483: 1: Success after linux: 108 commits new ba0a7a2e26 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 380338a89b 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 438564319f 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 634283134d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 0fad7550be 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 692ccbc5f2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 81423da099 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 1860dc9cd0 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 97eb77ff86 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 33b10037fe 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 120d722d86 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new e304712ffe 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 497ea19e10 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new dd903b655c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 035365a5d4 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 08c18385c7 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new acb357ce00 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new fd47c5e714 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 1cd49413fc 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 9f0e0bbb12 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 36f9fc50dd 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 130ce1568b 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 654d80f4d6 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 18b7599c77 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new d0fff35600 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 0efe4c2196 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 9a896e4eca 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 26f038d4f9 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new a5ec3ab48b 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new c09413968a 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 4831930d9d 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new f1cbc62040 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 052aa9b76c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 4dd5a4ad99 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new bd32020bdb 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 2d2e34fcb5 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 446db3eb8b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 0ba05d6b39 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 7ac304eec1 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new ad6cc2f364 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 4c7f98d574 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 46350a5fc3 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new c3b8df3568 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 3709ac4aa4 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 654fa6abf6 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 4f760b11ad 281: onsuccess: #2529: 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 (2d30c920ec) \ 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 1800 -> 1804 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32696 -> 32584 bytes 04-build_abe-stage1/console.log.xz | Bin 73800 -> 73780 bytes 06-build_abe-linux/console.log.xz | Bin 9252 -> 9040 bytes 07-build_abe-glibc/console.log.xz | Bin 245152 -> 245800 bytes 08-build_abe-stage2/console.log.xz | Bin 205096 -> 205232 bytes 09-build_abe-gdb/console.log.xz | Bin 39832 -> 39984 bytes 10-build_abe-qemu/console.log.xz | Bin 31972 -> 31676 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3216 -> 3140 bytes 13-check_regression/console.log.xz | Bin 5888 -> 6544 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/mail-body.txt | 73 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 35 +- 13-check_regression/results.regressions | 38 +- 14-update_baseline/console.log | 42 +- 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 | 75 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 38 +- sumfiles/g++.log.xz | Bin 3409708 -> 3416872 bytes sumfiles/g++.sum | 24 +- sumfiles/gcc.log.xz | Bin 3031080 -> 3038816 bytes sumfiles/gcc.sum | 3985 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1040396 -> 1041864 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214732 -> 214572 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2700 -> 2700 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431160 -> 437008 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 2244 insertions(+), 2178 deletions(-)