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 e371653135 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 7bf18407ef 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 5b6a8eb26f 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards abe7af67bc 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards beddba07c5 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards a4fc841a63 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 4b59e537de 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 5e62d5463b 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 8cecf48734 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 4c32dc77a9 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 24b581bfa3 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 49604374c0 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 4abb0bb745 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 7591e3d7e5 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 7b1195a8da 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards 0ca216c3c5 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards a712180eec 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards ad390784d2 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards f2967b0842 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards 747a6c3abb 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 4666a22916 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards efd418d259 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 642106d29e 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 83d1a87438 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards b4bc2e9538 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 3cbe94d40e 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 04489a7c6f 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 48ae2f5aa7 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 4d5c1bdce4 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 357954d3bd 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 4b8c3e08df 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 9ed7c2a3b4 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 2a36b613aa 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 253c89db81 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 4c428a1300 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards ccc1fb21ae 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 19c9697b42 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 05c15ff75c 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 2d5775d0ab 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards f308a05e46 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 682a947344 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 4d048f3e25 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 4194c7b086 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 44239f39f5 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 0e69781fd4 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards e0d39d566d 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 33d6329704 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ac86f0eb45 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 630e55d297 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 11621ecac5 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 03a295618b 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards b4dcdd183a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 6d8b71b2b3 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 71108a1ed7 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 79ac66fd74 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 36a7ccd696 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 9a0ee0cec1 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards b868d8f0a6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards dbcd182bac 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards c11593e540 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 30db71ce71 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 68f2b97474 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 31737468de 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards c910cb7d27 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards c7b3911e97 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 5459556e00 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards e3861eba63 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards a0179bfa61 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 776f4c4253 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards eccd707880 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 81dae2b2be 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 41d20d4721 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards c1b1c7b61f 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards f671bed945 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards c692a04f24 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards dcc859e273 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 38bd1bbc7d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 240b9db2b9 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ba545a8857 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 34bc6c4383 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards f9b841b1a3 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards f004db64a8 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 5b7870c434 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 68fb7a191a 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards abcdd98adc 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards e2ab60b41f 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 3b210acd9f 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 57a211976f 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 3dc3430b65 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards b6fc0eee08 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards ad3121f24b 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 9c38b552b2 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 407e272de3 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards a8b4ae9ed5 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards edf1e21c78 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards d1329da204 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 0c44595c40 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 9151dac931 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 6b05e209a3 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards d527b88f12 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards a43cd2a69f 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new fa6d4d676d 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 5347492fb4 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 3f608e3ed2 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new dfc9621a36 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new cf6b8d51e2 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 3552ac1c1e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 88393f1e92 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 8c5a0d895f 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new f2ae19421f 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 70954e7180 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 37c67865f0 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 693ae2686b 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 9755a19317 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new dc464b2968 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 75585f2584 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new f294af7fef 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new edb5e65e64 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 4b7c426c5c 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 3cd7ce5e0b 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new e7c5abea3e 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new b2e4ae7109 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 9bd58f619a 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new d05738e670 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new d6fd8eb05c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 433e8488ab 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 3f419ea292 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 531526482b 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 1ae0e32ad5 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 4d2b9aa320 292: onsuccess: #2541: 1: Success after binutils: 13 commits new b0c2a6faee 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 0dd378f9b3 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new b78d9bde39 295: onsuccess: #2545: 1: Success after linux: 10 commits new aa49bd3eff 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 59d6ba6e86 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 8b64db2c41 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new d4a0ca909d 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 4e8f7a82d4 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 16286a9e1e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new b5d2933da1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new f7dbf65319 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 1192b07fbc 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 85d7ed48e9 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 59a374d9da 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 1989c4d06d 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 8beec4834e 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 77efd1605d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new e621cdeb23 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new f0ef16c4ed 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new d1de1c8065 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new ea76c56652 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 2916a8c433 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 139e243008 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 9657199ca5 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 8be9034b7d 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new f1033ef8c5 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new e8a89c8cc3 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new b6445fbc43 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 96001e1c1f 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 7305354236 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 51d9315890 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 11bccd5693 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 3ca1cecbb4 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 6b09475939 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new ed7434107b 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 9e52550086 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 83f7c64589 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new eaa5d9340c 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new aed6094193 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 9c8acec18d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new 899851ef1b 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 93c1220327 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new c86a63cd7d 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 5cc0bd821c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 6524307c46 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 37d9285bb4 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 234d41011e 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new c905e3fc5d 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 437fa50337 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new d307b6b66b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new 8dad320f7a 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new e1cdb20fb8 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 0e223e9f60 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new a870db33dc 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new eb59917b64 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 35d7362e10 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new bf2b2a6c9c 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 2eaca38290 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new b889a1f122 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new f6609634b2 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 4ca428a046 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new f4dba3cff2 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 3240f38539 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 1a166e8301 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new 03fafade4f 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new e5d675fc3d 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 069526e6c8 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new f3f9e31f97 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new e9f1568ce7 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new a196938909 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 6f70ee0c05 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new 79cd224b78 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new 6db522c1d2 365: onsuccess: #2615: 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 (e371653135) \ 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 1812 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 31580 -> 31400 bytes 04-build_abe-stage1/console.log.xz | Bin 73324 -> 73504 bytes 06-build_abe-linux/console.log.xz | Bin 8588 -> 9044 bytes 07-build_abe-glibc/console.log.xz | Bin 244580 -> 246256 bytes 08-build_abe-stage2/console.log.xz | Bin 204348 -> 205868 bytes 09-build_abe-gdb/console.log.xz | Bin 38632 -> 38816 bytes 10-build_abe-qemu/console.log.xz | Bin 32188 -> 32524 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3936 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3120 -> 2696 bytes 13-check_regression/console.log.xz | Bin 6680 -> 6944 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 21 +- 13-check_regression/mail-body.txt | 77 +- 13-check_regression/results.compare | 39 +- 13-check_regression/results.compare2 | 101 +- 13-check_regression/results.regressions | 39 +- 14-update_baseline/console.log | 70 +- 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 | 79 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 39 +- sumfiles/g++.log.xz | Bin 3376344 -> 3397092 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 3014968 -> 3037168 bytes sumfiles/gcc.sum | 4946 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1035284 -> 1049168 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2300 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215116 -> 215140 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2652 -> 2660 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 431140 -> 439796 bytes sumfiles/libstdc++.sum | 234 +- 43 files changed, 3074 insertions(+), 2674 deletions(-)