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 45a2f658e0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f7f0026c51 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 0763283062 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 9d5ebd361a 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 5f18552f79 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 0b879e4e4f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 465f75ecb2 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 7f02e30565 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards e3dc6e6622 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 4d360dc8ce 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 025dc0db6e 295: onsuccess: #2545: 1: Success after linux: 10 commits discards a778e5cc8b 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards a8defd7550 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 2e74783117 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards cfb164a2b5 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 02fcbeec40 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 2b0e19fe04 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards a8ec297bec 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards f4b2a74660 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ece413d5f5 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards a1dfb25876 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 449a6caf3e 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 864df4a583 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 0470953ef8 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 12eba69cdc 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 2545b82e00 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards c9f0423870 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 5605a6d302 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards f5bb539c07 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 50bfbb580f 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 5b9e042519 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards b9efa55123 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards d4728c6aa5 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards cc2ea17137 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 1bac4fe54f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 44cc8969bf 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 8a3832217d 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 40b372195a 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 9f7fcecc33 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 2256721824 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 40f0834bd1 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 5d28e8eb9f 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards c4039506b1 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 06be983fe0 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 456a96bc74 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 764ec4d063 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards a65f9c26a1 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 78230a75df 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 308470083b 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 5853a47e85 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards d088b29ef7 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 21859932a3 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 7218dd99c0 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 0e008f3a9f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards dbae915f39 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards bc05081937 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 6b7544a840 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 7b5ac3187d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 4a6401bc1f 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards f865641919 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards eec6ea8abf 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 4292205593 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 354efb1f0a 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards f070ea55d5 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 015266533b 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 11d9517bbf 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 28687e9edf 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 0ec7419761 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 39d99b21f6 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 269ae6c11c 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards 4dffdfc7e0 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 56507eca8b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards faad3d0a02 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 4a0d03620d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 8674f2b6cd 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards d0e9a09487 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 4119576ea3 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards c490d7a420 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards c6341e2895 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 8200fec718 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 09f2865622 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards d93091f31c 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 7306dbf415 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards b70888f9af 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards bbda47ee8e 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards 2aef525485 220: onsuccess: #2465: 1: Success after linux: 572 commits discards 3559566997 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 8996c34c23 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 9af95acc5a 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 37c0140c8a 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 90b9c8e177 215: onsuccess: #2455: 1: Success after binutils: 3 commits discards a5a682e193 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] discards e74df4e7c8 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] discards 1b57507dde 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] discards 3fd722acde 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits discards 8cc379813a 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits discards 5d625e5ba7 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] discards 62a49e0eb8 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] discards 1dd85ef68e 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] discards 5e341485ba 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] discards 997d963145 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 8ce944a985 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/g [...] new 8f32aa8da1 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/g [...] new bfb26507e6 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/g [...] new c27759e96f 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 14 [...] new 91b04cd5af 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/g [...] new 6423cf2af5 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 commits new d98c5928bd 211: onsuccess: #2450: 1: Success after gcc/linux: 7 commits new bd8404f187 212: onsuccess: #2451: 1: Success after binutils/gcc/linux/g [...] new dcd7039cbb 213: onsuccess: #2452: 1: Success after binutils/gcc/gdb: 22 [...] new 715dbae1c2 214: onsuccess: #2453: 1: Success after binutils/gcc/glibc/g [...] new b9033d7d48 215: onsuccess: #2455: 1: Success after binutils: 3 commits new d7dd214c24 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 178e285bf6 217: onsuccess: #2459: 1: Success after binutils: 3 commits new dfbbce1942 218: onsuccess: #2461: 1: Success after linux: 916 commits new 6abf7af131 219: onsuccess: #2463: 1: Success after binutils: 3 commits new db372576c0 220: onsuccess: #2465: 1: Success after linux: 572 commits new 8c144b85b5 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 6aa1405a1e 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 0b00eeacb4 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 102cfca1ce 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new ea3b42a1d7 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 8272af4c54 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 6d0a46c94f 227: onsuccess: #2474: 1: Success after gcc: 2 commits new d38e4da9b4 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 1641d1793d 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new caed2f9558 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 1dc6e4707f 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 7716a3000c 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 19f06af5c8 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 7c13c362a3 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new b96fc260d4 235: onsuccess: #2483: 1: Success after linux: 108 commits new 0c4e70cc93 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 3c16291bb1 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new e0c39b5ca6 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new f5bf98cd0d 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new bce1fd8cc8 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 620eb8221b 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 22e9f88761 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new 9c5185cafe 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 09aa832533 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 6b4659b599 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 183cbbba0e 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new fe9e41c363 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new e83602673f 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 7c43abd774 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new b483f036a0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 2378c882e2 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 944aace86f 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new d3527de6eb 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 1dc8cd8469 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 25b84a6004 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 966bb4158a 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 4b7df5bd66 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 8f23f266ee 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 1482c4176a 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 6abe1b4924 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new f622c7dc66 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new e3b7295ba3 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new ac3cca6a13 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 185a4c2a05 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new c593eda9b0 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new c0ea5e4403 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new d8598ce984 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 67a3400c87 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new d64092becb 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new f562283f2f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new f32c800f62 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new fdff71ae84 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 4a23531298 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 8a20b44554 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 42d98e8f2c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new a932a5747b 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new a568e4bbf0 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 0c7279481c 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 48f2a9035d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new eee4f5c4af 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 5a0df04f03 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new edda4341fb 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 48bb47fa2a 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new c93fa530dd 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 8ee2386310 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 127e95bb21 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new e885e743db 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new f335d26c89 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 91c01babf2 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 667087aa0b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new e2fcf2ef21 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new f5c16351df 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 6d6c39cce3 293: onsuccess: #2542: 1: Success after gcc: 5 commits new addcdb1ebd 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 6683e3741a 295: onsuccess: #2545: 1: Success after linux: 10 commits new be679fd47b 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new e04cbe7cf7 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new bc02905d6d 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new f07ee1d1e0 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new b6d702a8e0 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 02312e14af 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new d117be503f 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 124644d390 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 04ef12d5dd 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 3aef8d76b0 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 897a4901bd 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits

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 (45a2f658e0) \ 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 1776 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32032 -> 32160 bytes 04-build_abe-stage1/console.log.xz | Bin 73216 -> 73648 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8540 bytes 07-build_abe-glibc/console.log.xz | Bin 245332 -> 245308 bytes 08-build_abe-stage2/console.log.xz | Bin 204948 -> 204996 bytes 09-build_abe-gdb/console.log.xz | Bin 39568 -> 39700 bytes 10-build_abe-qemu/console.log.xz | Bin 31624 -> 31100 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2652 -> 2916 bytes 13-check_regression/console.log.xz | Bin 5832 -> 5928 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 9 + 13-check_regression/mail-body.txt | 83 +- 13-check_regression/results.compare | 57 +- 13-check_regression/results.compare2 | 57 +- 13-check_regression/results.regressions | 29 + 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 | 85 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 29 + sumfiles/g++.log.xz | Bin 3405532 -> 3422392 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 3037924 -> 3038332 bytes sumfiles/gcc.sum | 4178 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1042760 -> 1045636 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214720 -> 214964 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 430748 -> 433052 bytes sumfiles/libstdc++.sum | 8 +- 42 files changed, 2324 insertions(+), 2376 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions