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 056c5b526a 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards 6046046fdb 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards c7eded4da4 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards fa309b4978 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 1d353228e0 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards f37615d749 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 4e60625d21 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 7ecdd53989 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards d44fe46c63 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards ecf11f0103 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards ac7bf5f077 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards fa51e571f8 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 5006b9192d 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 1ef7408598 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 21305bc46b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 20aa1eddbd 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 849d3c106f 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards e1301cf110 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 747f4b368d 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards b732d2b1cb 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards bbb98d00ae 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 6a2f138805 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards c65a74e7ef 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards f6caa03b4c 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 4bff4bb805 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 8e19c12abf 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards ac0ee68564 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 024dbe57c3 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 89f3fd5272 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards c34671f9a5 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 6de8fe0c69 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 15de38add4 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 367ae756c5 295: onsuccess: #2545: 1: Success after linux: 10 commits discards ed72e38e16 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards bcf755e41d 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 0338675771 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 8fed5fd7c8 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards db061243e3 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 9eae1c3684 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards 296b329375 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards f69576c859 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards e303bd7d52 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards ca2436dd05 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 50f00a6016 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 8e39294a71 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards f9d36d155f 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 1735ab741f 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 1f89bf4d73 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 86b08fcdd8 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 17c4f40294 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards d033a374dc 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 6fa6f50989 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 0c476774ea 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards f8fa05ca04 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 935c5e0cae 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards f2572ecff5 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 82d30e12b7 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 075d290272 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 74a4b6e486 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards f140197f84 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 2fc9380499 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 2d342cd439 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 783dbe68ae 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards fd879111a3 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 54c5159de6 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 7761fc96fa 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 6e4ddfd047 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 41f1dd639e 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards fa4ad76e96 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards ebb1b10155 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 407e9a65b1 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 3d50199b37 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards a393faabb8 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 55359c9a22 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards a3ca4eda76 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 23c9cc1206 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards 9b78e6a611 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards db257b10b1 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards cd205c6a3d 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 5dc58e0604 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 6f48251c0a 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 3c57e2412f 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards ab698ed49d 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards 7b6a5c60b0 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 2a0c2a759b 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards b023938b06 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 04d0b73e6d 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 40b58a5100 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards a37243ebeb 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 3ce67182aa 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 40e7ad8687 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 1d271d6520 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards e22f78ea74 235: onsuccess: #2483: 1: Success after linux: 108 commits discards c6f4141f86 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 6c9e3d8784 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards cabe258b8d 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards a3bfba99ef 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 82806ed22d 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 23c7343b66 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 398b866a0f 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 12ceaea462 227: onsuccess: #2474: 1: Success after gcc: 2 commits new e409a0f30a 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 207556b105 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 2d3ad36c66 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new afc7d922c2 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 42f8d4261e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 4c857af2a5 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 27ae4f2f4e 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new cd3ac70b31 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new fd223bed6a 235: onsuccess: #2483: 1: Success after linux: 108 commits new 16ec8bbd2a 236: onsuccess: #2484: 1: Success after gcc: 2 commits new d29ca30528 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 7079338564 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 89a80442d4 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 44450ed398 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new c4471e7b58 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 3ba839e552 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new fb0cb4e063 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 6aec3131f7 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 05dee471bb 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 45ea7d258f 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new f24fc67540 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new eec57070a5 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new b96d02580c 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new f861936704 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new fd95ab4375 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 0dcd2be1e0 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new bf0d16d52d 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 92b0499d2e 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 59a8535165 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 44c8d22845 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 6e0f121338 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new c3078077a7 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new 836595d7e9 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 1603cbd577 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 937f8938dd 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 1b603928a2 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new b4d603da7a 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 79867531db 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 9d7b65ab0e 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 3bacb0380a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 10a68a0259 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 6304f0e997 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new efd4649cf3 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 7b35516c20 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 481d6f38dc 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new b13ac0d40d 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new c97895b9fc 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 313e335104 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new d53a3e916c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 0be81f856d 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 96eb7cad6d 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new e3afd445f8 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new b378d0d2a1 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 384ee88043 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 5241af0f8d 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 9c7bb86520 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new c36116467f 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 18ce5d8457 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new c96e5b7d7b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new cf4ec3bf03 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 89546c211a 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new cac09cce97 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new d9ffc603f3 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7e62ca9fb8 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new a7cabd6bf9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 3485dff056 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7f2d5806c3 293: onsuccess: #2542: 1: Success after gcc: 5 commits new fb7b2dfde4 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new bdb626b15d 295: onsuccess: #2545: 1: Success after linux: 10 commits new 004a9cad34 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new d67c726bb7 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 247c81c267 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 064c862206 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new c67aef9344 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 813590df2e 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 653718830e 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new a1e90242d3 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 6994f08222 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 5d481041d9 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new e6efc1bbb3 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 8937932d03 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 7584f18eae 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 68620e8dec 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 4c91b9d5c4 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 409f98a122 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new fb218dc00a 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new b8998743a8 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 53d78031f0 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c5db2b701c 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new e2d26ee213 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 25010d59a8 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new cdcca11626 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new 33c8106d08 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new 3a7b60cb44 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new c71161a045 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 4f1a1f11f1 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new da02d95e95 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 77f8c2c4f1 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 83e648c744 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new 60a971f604 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 5c84c8e971 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 884786236c 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/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 (056c5b526a) \ 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 -> 1836 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32924 -> 32120 bytes 04-build_abe-stage1/console.log.xz | Bin 75280 -> 73528 bytes 06-build_abe-linux/console.log.xz | Bin 8788 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 245796 -> 245220 bytes 08-build_abe-stage2/console.log.xz | Bin 205512 -> 204764 bytes 09-build_abe-gdb/console.log.xz | Bin 39692 -> 39772 bytes 10-build_abe-qemu/console.log.xz | Bin 31712 -> 31984 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3936 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3720 -> 3276 bytes 13-check_regression/console.log.xz | Bin 12448 -> 7640 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 462 +--- 13-check_regression/mail-body.txt | 181 +- 13-check_regression/results.compare | 515 +--- 13-check_regression/results.compare2 | 906 +------ 13-check_regression/results.regressions | 126 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 183 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 126 +- sumfiles/g++.log.xz | Bin 3418528 -> 3425416 bytes sumfiles/g++.sum | 22 +- sumfiles/gcc.log.xz | Bin 3039208 -> 3038464 bytes sumfiles/gcc.sum | 4418 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1039004 -> 1041200 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214412 -> 214900 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2696 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436212 -> 430540 bytes sumfiles/libstdc++.sum | 16 +- 44 files changed, 2695 insertions(+), 4403 deletions(-)