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 1e9c64d363 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards fb6bfd076b 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards c15f2888e3 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 59c0025d9b 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 59e23ea60a 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards 793f095f79 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 9e2ad3a3df 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8f775ad77e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards c96b2bac24 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards 3b066be918 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 5bdfe744a1 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards c81bd5f8c0 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards ba18121b18 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards f09b7915c3 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 60aefc40d1 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards c057f12cf4 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards 26b2b14ed0 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards 866b8c02f4 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards 1442f65422 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 8148a52b11 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards eb6a9c2532 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 48749cc1a7 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 110bd75530 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards b68df41533 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards 480f05a7d8 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards efb708d038 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards 778bc20882 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards c36da28e13 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards ef84f80249 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards ebc07ab780 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards c28c30f52c 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards db317c6279 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards 359b377799 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 55d6ffd7e1 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards be1c75e9fa 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 3190c4c5ce 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards 5580f59d25 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 7e86209542 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 3a5eb6d1be 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 6720866b07 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 7eeb29518b 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards b10ba5adf7 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards 0d8232bce4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards b1a51b4308 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards baad39b4c1 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 7966306e60 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards bd725d45cb 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2285f61db0 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards b40432bbdc 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 796d4f1420 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 58b08c64d8 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards c6ca391a84 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 3390a35b03 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 8e9d1c96fd 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 3a4b36fcf6 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards a26660c0d7 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards d046ef8b52 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards e6bb510431 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 74110203e1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 573dc4bf42 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards f71d2db5df 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 05cd85d9b3 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 3a7bd8db3f 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 936882ee3a 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 1d9101c72d 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 615be6d9ef 295: onsuccess: #2545: 1: Success after linux: 10 commits discards bd423a54e5 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 8b779876b6 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 4118f0afb3 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 546a15ff18 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 28749f5ff1 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards e970da7027 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards c3195ca5f8 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards b24aff1296 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 5e6b17807c 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 9793e362ab 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 4c95b0431b 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 5d5b8e996c 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 4a48c80af1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 74acd8e260 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards cb91fa0ddf 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards a328bb70c5 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a68ca9a06b 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 851917da2b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards a0dad18183 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 4450be823c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 2f1d45a9d9 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 275e5232bb 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 780872024b 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards a27de2c990 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards 4e19df0ce2 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 3d7991a5b7 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 63a3214fc5 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 559ad33618 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 6dbaf3f2c1 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 745573728c 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards d89f660687 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards d95e83c5a8 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 36ca46d82e 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 755a54b6db 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 367e071176 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new ffd8c5b93e 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new 4de55374a1 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 6d507ae23a 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new d1d08b110c 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new a7c9afaebe 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new fbfc5363d0 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new da910096d4 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new e028661863 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 0392451f59 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 119e9d69e1 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 556e190717 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new f0e9f52587 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 9aa1db66a6 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 5fb94dcf57 273: onsuccess: #2521: 1: Success after gcc: 2 commits new fade5b650f 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 03b0907687 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new 8e3798162d 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 8fdf2a6229 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new d3a4ea9814 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 3e0458b799 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 035fd31150 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new e3bbe72c5b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 32efe5f66b 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 8284d5ff22 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 68e9a27b32 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new c8415a5d8b 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new cd59f432a4 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 5cfe35c38c 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new d669ae3fe5 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 0ed4ce9bd2 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new de0077b1f0 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 48c8cf03d9 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 09ba784db3 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 7172291842 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 2fb62d1b4c 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 2d93b541b6 295: onsuccess: #2545: 1: Success after linux: 10 commits new 01e7b4b0d9 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 5223338869 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new 9a9e1aa4b4 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 697e959622 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 055d258c3f 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 55b8a490b9 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 113f1a886d 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new b0c0dde150 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 57f581dd6a 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 4c21113434 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 393b538219 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 660452b106 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 740396e9a6 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 1d3945ae3a 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 7727c4af8f 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new d9723501b1 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 31f1c170f4 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 013ba78b8b 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new d506dd3510 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new c224df5cea 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 04340573ad 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new 58fca178f3 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new de396175a9 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new db889c54d8 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ed7d857279 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 04733f7b88 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new e998fcdd7c 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 31cc0c8f2d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new eb93949b39 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 8cefb53f1f 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new ea3ab8a648 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new bcc8564b40 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new ef6d2b437f 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new 6a3ec9e172 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new 1ffb9b4ab5 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 2bd0196276 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new 4673500cb2 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new aafaa08496 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 4f70e51d24 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new b59512aa3b 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new b318567084 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 9516bc8f0d 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new 89fbaea43b 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 8cb99e6e15 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 9cc7b851a6 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 12457734e9 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new 214d64aa8b 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new a7a286c1e8 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 2e5e6f1d12 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new b7a1535e04 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new e70a486d03 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 6e87d11791 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new e25818683a 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new c44fc7c203 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 6462d63181 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 98bfd94f06 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new eddc8cb2d0 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 74cf406cbf 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 4b910e17de 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 3f6964891e 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new 4ef8778d3f 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new afc6569387 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new c593148616 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new 7070ef7746 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new fe13930652 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 2cee3e4e42 361: onsuccess: #2611: 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 (1e9c64d363) \ 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 1828 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 31224 -> 31536 bytes 04-build_abe-stage1/console.log.xz | Bin 73320 -> 73232 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8868 bytes 07-build_abe-glibc/console.log.xz | Bin 244952 -> 244596 bytes 08-build_abe-stage2/console.log.xz | Bin 204616 -> 204800 bytes 09-build_abe-gdb/console.log.xz | Bin 38484 -> 38928 bytes 10-build_abe-qemu/console.log.xz | Bin 31972 -> 32320 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3912 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3148 -> 3024 bytes 13-check_regression/console.log.xz | Bin 7004 -> 7988 bytes 13-check_regression/fails.sum | 12 +- 13-check_regression/mail-body.txt | 35 +- 13-check_regression/results.compare | 17 +- 13-check_regression/results.compare2 | 122 +- 13-check_regression/results.regressions | 17 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 37 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 17 +- sumfiles/g++.log.xz | Bin 3388792 -> 3383556 bytes sumfiles/g++.sum | 54 +- sumfiles/gcc.log.xz | Bin 3019948 -> 3022068 bytes sumfiles/gcc.sum | 5172 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1032816 -> 1037960 bytes sumfiles/gfortran.sum | 54 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 215264 -> 215176 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 429332 -> 434856 bytes sumfiles/libstdc++.sum | 57 +- 44 files changed, 2889 insertions(+), 2817 deletions(-)