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 c440fbf2a6 479: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 64aad292c1 478: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards aafb0c4a43 477: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards c0c022654c 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ad1b226a87 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 94d78f4aeb 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d99745bfe2 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4ebc17859f 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards af14c910ba 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 414440e1a3 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards a3b0d7a939 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards b9e8af478a 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 1e3159127f 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards c95b1cee5f 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 9cead6db70 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 5e08a65215 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 4c33f491b1 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards fafe0756a3 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 7580aea5ec 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 53534e3714 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 78d888f89c 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 352f368f62 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards c4e7d7ae3f 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards a4b2c38bf3 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 1f6acc2116 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 1c3e788f2b 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards ee7a931381 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 1ad50a53f4 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards c54e99d9c6 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 7ba112fed6 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 475d0ac59d 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 1880db4d86 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 5a946a6a07 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards c9beaac9ae 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 6d0fd5c0e1 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards 6b51969be0 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards 3b74d65564 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards a45ab40991 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 9ed69cffdc 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards da2bf9cdfa 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards c74053c2dd 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 83fdb5cd78 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards cead5744ef 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 40c3f34395 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 09e02b0d7e 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 04373854b8 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 3a5d64bd5a 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards d634839754 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards 47222d7d25 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 3955d8d6db 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 82aca5a7af 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 9e6cb7978f 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards 054721a496 427: onsuccess: #7: 1: Success after linux: 26 commits discards 368d06f243 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards cfa6d52af5 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards acc389c7b5 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 667406bb8a 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 8be2b133ad 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 9de9c02539 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 1e53a4a16b 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards 0fea1755c7 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards d7fa759281 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards 127f299771 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards e9c4f6f83e 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 4f5ea3e715 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards 3e31811b66 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards a160e13733 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 269c6b675b 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards de5411c6d5 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards 39cc4faeab 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards c98e0bd4f5 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards f369dc2729 408: onsuccess: #2662: 1: Success after linux: 11 commits discards f6c05be69d 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards 40fa5b2192 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards fb9f473107 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards b396d442b2 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 0357fdf424 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 1f772852f7 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards 0585776520 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards 64ec80c051 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 0f4e51b371 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards b8a9af3d09 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards 0e8db05994 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards a438babb56 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 8e86d1faf2 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 19cd9b951a 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards bc81190210 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 2d17c0fff6 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 63f80dba85 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards 7918427ed8 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards e36cc78258 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 8bc166fda7 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 9bdf287735 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards 02f37003f4 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 54d6926fe3 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards f5af287ade 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 6dbb9aea00 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 94ef75864b 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards 7862c50f87 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards 04688bc47e 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] discards f8cf76c18c 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new 476d3d13e0 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] new b8ec12f3bc 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new c61ff2506d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 7277b282c6 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new 6ffa6b82ba 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new 5a6d2e4231 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 0492088b0f 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new b43c9d3f61 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new 346cf93bdd 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new 304a39af83 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 26b14bbcdc 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new a7235faae4 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 3e5b8f389f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 4abbde3f17 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new a427df0610 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 79574a9be5 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 508fffdf59 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new c1f2be8961 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new feac3cc971 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 9afe990c9c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 08b2ad96ca 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new e5f64876de 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new ab0fab2734 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 12a1ca0cd2 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 368f17d338 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 2fcedf6131 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new 6b15751ca2 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new a2d3ed1aba 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new f1d483169d 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 23be2e5495 408: onsuccess: #2662: 1: Success after linux: 11 commits new 5f3a566550 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new c25d75d119 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new fa073e624f 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 4dfa6bd60d 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new f0be39ad4c 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new d1be86b18d 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 64eb40f9b9 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new f83c5d14ee 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new e61b17ccc0 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new 80a0f38bfd 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new b101773acf 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new 728f2d23c4 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 0a55c544aa 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new ec0fccd121 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new ecde0d23c9 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new db3398a41d 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 7dde1ddc84 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 54f90d48a6 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new aae982138f 427: onsuccess: #7: 1: Success after linux: 26 commits new 2376ad3c28 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 14326b964b 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new 35c94aded5 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 39a7de9ab8 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new ef173afebb 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new a849d80b74 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 19c8240133 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 946052e2f4 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a2b852827d 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new cb16d6fe99 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 2907b1c1f0 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new fcaf97f36c 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 921a757c26 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 79bc696721 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 0e4b16a5ac 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new d93ff24854 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new d04d0ffea2 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new e2cc7cc213 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 9f489e7392 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 6ce4176995 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 501f091d15 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 272b55c0e9 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new fb1a1f681f 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new fa2c72cc23 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 6847908a10 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new c2f891fbd9 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 47d43d0ecd 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a703d670b5 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 28c5ecbfb1 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 45bbb552d0 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new f3039bc387 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new b132e44a2d 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b6703178c9 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new fe7bbd72a9 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new abc26093c0 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 867d232dc7 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 49ca62e166 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 53bd094a26 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d3dad75313 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new c680391179 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new cafd71dacf 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new e12b1cb55d 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new a2e741c2a8 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a8c481c551 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b8d099aa05 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d8f9324eb5 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ce2fda63ee 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new a51e88ee61 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 34e4c4976b 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cd8ef88dea 477: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 874d5ab9c9 478: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 691bc7ca7a 479: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 2c32d35a92 480: force: #68: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...]

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 (c440fbf2a6) \ 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: 00-sumfiles/g++.log.0.xz | Bin 3405888 -> 3409572 bytes 00-sumfiles/gcc.log.0.xz | Bin 3033920 -> 3037484 bytes 00-sumfiles/gcc.log.1.xz | Bin 124008 -> 123748 bytes 00-sumfiles/gcc.sum.0 | 16 ++--- 00-sumfiles/gfortran.log.0.xz | Bin 1047120 -> 1046348 bytes 00-sumfiles/libatomic.log.0.xz | Bin 2312 -> 2316 bytes 00-sumfiles/libatomic.sum.0 | 2 +- 00-sumfiles/libgomp.log.0.xz | Bin 217888 -> 217952 bytes 00-sumfiles/libgomp.sum.0 | 2 +- 00-sumfiles/libitm.log.0.xz | Bin 2676 -> 2680 bytes 00-sumfiles/libitm.sum.0 | 2 +- 00-sumfiles/libstdc++.log.0.xz | Bin 436868 -> 438592 bytes 00-sumfiles/libstdc++.log.1.xz | Bin 0 -> 438468 bytes 00-sumfiles/libstdc++.sum.0 | 8 +-- 00-sumfiles/{libstdc++.sum.0 => libstdc++.sum.1} | 12 +--- 01-reset_artifacts/console.log.xz | Bin 2228 -> 2236 bytes 02-prepare_abe/console.log.xz | Bin 2416 -> 2412 bytes 03-build_abe-binutils/console.log.xz | Bin 27256 -> 27068 bytes 04-build_abe-stage1/console.log.xz | Bin 71216 -> 71068 bytes 06-build_abe-linux/console.log.xz | Bin 8640 -> 8648 bytes 07-build_abe-glibc/console.log.xz | Bin 241704 -> 241516 bytes 08-build_abe-stage2/console.log.xz | Bin 201292 -> 201500 bytes 09-build_abe-gdb/console.log.xz | Bin 34912 -> 34720 bytes 10-build_abe-qemu/console.log.xz | Bin 29860 -> 29836 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3884 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6432 -> 6408 bytes 12-build_abe-check_gcc/flaky.xfail | 2 +- 13-check_regression/console.log.xz | Bin 1792 -> 1572 bytes 13-check_regression/results.compare | 34 ++--------- 13-check_regression/results.compare2 | 40 +++--------- 14-update_baseline/console.log | 74 +++++++++++------------ jenkins/notify.sh | 2 +- mail/results.compare | 34 ++--------- manifest.sh | 15 +++-- sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 2 +- sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.sum | 6 +- sumfiles/xfails.xfail | 22 ------- 39 files changed, 89 insertions(+), 188 deletions(-) create mode 100644 00-sumfiles/libstdc++.log.1.xz copy 00-sumfiles/{libstdc++.sum.0 => libstdc++.sum.1} (99%)