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 2c32d35a92 480: force: #68: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 691bc7ca7a 479: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 874d5ab9c9 478: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards cd8ef88dea 477: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 34e4c4976b 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a51e88ee61 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards ce2fda63ee 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d8f9324eb5 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b8d099aa05 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a8c481c551 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a2e741c2a8 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards e12b1cb55d 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards cafd71dacf 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards c680391179 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards d3dad75313 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 53bd094a26 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 49ca62e166 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 867d232dc7 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards abc26093c0 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards fe7bbd72a9 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards b6703178c9 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards b132e44a2d 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards f3039bc387 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 45bbb552d0 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 28c5ecbfb1 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards a703d670b5 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 47d43d0ecd 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c2f891fbd9 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 6847908a10 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards fa2c72cc23 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards fb1a1f681f 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 272b55c0e9 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 501f091d15 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 6ce4176995 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 9f489e7392 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards e2cc7cc213 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards d04d0ffea2 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards d93ff24854 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards 0e4b16a5ac 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 79bc696721 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 921a757c26 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards fcaf97f36c 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 2907b1c1f0 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards cb16d6fe99 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards a2b852827d 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 946052e2f4 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 19c8240133 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards a849d80b74 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards ef173afebb 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] discards 39a7de9ab8 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 35c94aded5 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 14326b964b 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] discards 2376ad3c28 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] discards aae982138f 427: onsuccess: #7: 1: Success after linux: 26 commits discards 54f90d48a6 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 7dde1ddc84 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] discards db3398a41d 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards ecde0d23c9 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards ec0fccd121 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 0a55c544aa 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] discards 728f2d23c4 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] discards b101773acf 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] discards 80a0f38bfd 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] discards e61b17ccc0 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] discards f83c5d14ee 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] discards 64eb40f9b9 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] discards d1be86b18d 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] discards f0be39ad4c 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] discards 4dfa6bd60d 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] discards fa073e624f 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits discards c25d75d119 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] discards 5f3a566550 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] discards 23be2e5495 408: onsuccess: #2662: 1: Success after linux: 11 commits discards f1d483169d 407: onsuccess: #2661: 1: Success after gcc: 7 commits discards a2d3ed1aba 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits discards 6b15751ca2 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] discards 2fcedf6131 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] discards 368f17d338 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] discards 12a1ca0cd2 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] discards ab0fab2734 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] discards e5f64876de 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] discards 08b2ad96ca 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] discards 9afe990c9c 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] discards feac3cc971 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] discards c1f2be8961 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] discards 508fffdf59 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] discards 79574a9be5 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] discards a427df0610 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] discards 4abbde3f17 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] discards 3e5b8f389f 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] discards a7235faae4 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits discards 26b14bbcdc 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] discards 304a39af83 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits discards 346cf93bdd 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] discards b43c9d3f61 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] discards 0492088b0f 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] discards 5a6d2e4231 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] discards 6ffa6b82ba 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] discards 7277b282c6 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] discards c61ff2506d 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] discards b8ec12f3bc 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 17ea3aa626 380: onsuccess: #2631: 1: Success after binutils/gcc/linux/g [...] new 9d64d2e8d6 381: onsuccess: #2632: 1: Success after binutils/gcc/gdb/qem [...] new 1889319432 382: onsuccess: #2633: 1: Success after binutils/gcc/linux/g [...] new ac3ba248d3 383: onsuccess: #2634: 1: Success after binutils/gcc/linux/g [...] new c7e44fa357 384: onsuccess: #2635: 1: Success after binutils/gcc/gdb: 10 [...] new 978fd6f52f 385: onsuccess: #2636: 1: Success after binutils/gcc/gdb: 10 [...] new 19dfb42aee 386: onsuccess: #2637: 1: Success after binutils/gcc/linux/g [...] new d884fe97fc 387: onsuccess: #2638: 1: Success after binutils/gcc/gdb: 11 [...] new be667781d4 388: onsuccess: #2639: 1: Success after gcc/glibc: 44 commits new 130bea546d 389: onsuccess: #2640: 1: Success after binutils/gcc/linux/g [...] new 2f7acfc54e 390: onsuccess: #2641: 1: Success after binutils/gcc/gdb: 6 commits new 207082b6e0 391: onsuccess: #2642: 1: Success after binutils/gcc/gdb: 28 [...] new 94a55fa6d8 392: onsuccess: #2643: 1: Success after binutils/gcc/linux/g [...] new 8bdeadb496 393: onsuccess: #2645: 1: Success after binutils/gcc/linux/g [...] new 5e2710f9b5 394: onsuccess: #2646: 1: Success after binutils/gcc/glibc/g [...] new 06f2f295c0 395: onsuccess: #2647: 1: Success after binutils/gcc/glibc/g [...] new a6215a57fe 396: onsuccess: #2648: 1: Success after binutils/gcc/linux/g [...] new af2a59d4c3 397: onsuccess: #2649: 1: Success after binutils/gcc/gdb: 10 [...] new 52d33db375 398: onsuccess: #2650: 1: Success after binutils/gcc/gdb: 47 [...] new 40de9a6022 399: onsuccess: #2651: 1: Success after binutils/gcc/glibc/g [...] new 94d770ae3e 400: onsuccess: #2652: 1: Success after binutils/gcc/linux/g [...] new 6f87d9492f 401: onsuccess: #2654: 1: Success after binutils/gcc/gdb/qem [...] new 6faa966f61 402: onsuccess: #2656: 1: Success after binutils/gcc/linux/g [...] new 2fe0c58c88 403: onsuccess: #2657: 1: Success after binutils/gcc/linux/g [...] new 2fc81d06c6 404: onsuccess: #2658: 1: Success after binutils/gcc/glibc/g [...] new b99a9dbc6c 405: onsuccess: #2659: 1: Success after binutils/gcc/linux/g [...] new 848dfcbdde 406: onsuccess: #2660: 1: Success after gcc/linux: 10 commits new 2d586823f2 407: onsuccess: #2661: 1: Success after gcc: 7 commits new 6b3a7c1f61 408: onsuccess: #2662: 1: Success after linux: 11 commits new 4aa8bc4ebb 409: onsuccess: #2663: 1: Success after binutils/gcc/linux/g [...] new ed5fc11e62 410: onsuccess: #2664: 1: Success after binutils/gcc/linux/g [...] new 39c8e7c1f2 411: onsuccess: #2665: 1: Success after binutils/gcc/gdb: 5 commits new 90cf0ece03 412: onsuccess: #2666: 1: Success after binutils/gcc/glibc/g [...] new 9e87d6ca2b 413: onsuccess: #2667: 1: Success after binutils/gcc/linux/g [...] new f0dd2a192b 414: onsuccess: #2669: 1: Success after binutils/gcc/linux/g [...] new 05d130ea23 415: onsuccess: #2670: 1: Success after binutils/gcc/gdb/qem [...] new 968bde8772 416: onsuccess: #2671: 1: Success after binutils/gcc/linux/g [...] new 89280785b5 417: onsuccess: #2672: 1: Success after binutils/gcc/linux/g [...] new a52364cb56 418: onsuccess: #2673: 1: Success after binutils/gcc/gdb: 14 [...] new 0d51c8573b 419: onsuccess: #2674: 1: Success after binutils/gcc/linux/g [...] new f03f3c65a3 420: onsuccess: #2675: 1: Success after binutils/gcc/linux/g [...] new 767f432943 421: onsuccess: #2676: 1: Success after binutils/gcc/gdb: 22 [...] new 53743f6fc5 422: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new a79926c169 423: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 0954c5b6c7 424: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new db2ee3fc8b 425: onsuccess: #5: 1: Success after binutils/gcc/glibc/gdb/ [...] new 41298d0df1 426: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new d5ae7cb257 427: onsuccess: #7: 1: Success after linux: 26 commits new ca3c318e51 428: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: [...] new 238585070a 429: onsuccess: #9: 1: Success after binutils/gcc/linux/glib [...] new f698373c17 430: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 83ed81738d 431: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 4bb3801ff4 432: onsuccess: #12: 1: Success after binutils/gcc/linux/gdb [...] new 2860d9a2d5 433: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 009c4bf206 434: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new 63c05c0e7a 435: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new fbe0017ebe 436: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 5e25a43dbf 437: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new b67cc7eee6 438: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new b059401c89 439: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 333efad65c 440: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 3c0dd5f717 441: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new c058bb38c3 442: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new 12f3707292 443: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 916e9f24b1 444: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new ff020baa5c 445: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 52ba8728ce 446: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 2232fbd203 447: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 29ea39fe3a 448: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 0402fc19a9 449: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new c526f839a4 450: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new f5b19b7a9e 451: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 9712f5e808 452: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new a555c4312f 453: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 3a8f91a06a 454: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new e2ac4b054a 455: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new b9e79179c3 456: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 3749bfb069 457: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 8ad601fd37 458: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 94608bdcc9 459: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 9993d1b421 460: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 9dbd407507 461: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 7b0260274b 462: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new f57b5627cb 463: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 2ba9fcba20 464: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new dedbfcc2a7 465: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new d773129377 466: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 278cbe39d0 467: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 906da4a25d 468: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new e570e782b0 469: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 3d1debfd28 470: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 168c174abd 471: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3223c2d674 472: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3b339c562e 473: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7556061ea2 474: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 4e25cf12b7 475: onsuccess: #57: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f114ba95d0 476: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5e46f7c86a 477: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new ff9b5120e1 478: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new c3dcbeb54b 479: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new a8ca03cd48 480: force: #68: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 7a77ddae71 481: force: #74: 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 (2c32d35a92) \ 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 3409572 -> 3433616 bytes 00-sumfiles/gcc.log.0.xz | Bin 3037484 -> 3020712 bytes 00-sumfiles/gcc.log.1.xz | Bin 123748 -> 123428 bytes 00-sumfiles/gcc.sum.0 | 58 +- 00-sumfiles/gcc.sum.1 | 15 +- 00-sumfiles/gfortran.log.0.xz | Bin 1046348 -> 1044040 bytes 00-sumfiles/libatomic.log.0.xz | Bin 2316 -> 2312 bytes 00-sumfiles/libatomic.sum.0 | 2 +- 00-sumfiles/libgomp.log.0.xz | Bin 217952 -> 218044 bytes 00-sumfiles/libgomp.log.1.xz | Bin 0 -> 56148 bytes 00-sumfiles/libgomp.sum.0 | 7 +- 00-sumfiles/libgomp.sum.1 | 4399 +++++++++++++++++++++++++++++++ 00-sumfiles/libitm.log.0.xz | Bin 2680 -> 2676 bytes 00-sumfiles/libitm.sum.0 | 2 +- 00-sumfiles/libstdc++.log.0.xz | Bin 438592 -> 440644 bytes 00-sumfiles/libstdc++.log.1.xz | Bin 438468 -> 438240 bytes 00-sumfiles/libstdc++.sum.0 | 8 +- 01-reset_artifacts/console.log.xz | Bin 2236 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2412 -> 2468 bytes 03-build_abe-binutils/console.log.xz | Bin 27068 -> 27488 bytes 04-build_abe-stage1/console.log.xz | Bin 71068 -> 71104 bytes 06-build_abe-linux/console.log.xz | Bin 8648 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 241516 -> 241988 bytes 08-build_abe-stage2/console.log.xz | Bin 201500 -> 202320 bytes 09-build_abe-gdb/console.log.xz | Bin 34720 -> 34876 bytes 10-build_abe-qemu/console.log.xz | Bin 29836 -> 31492 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3940 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6408 -> 6456 bytes 12-build_abe-check_gcc/flaky.xfail | 2 +- 13-check_regression/console.log.xz | Bin 1572 -> 2164 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 38 +- 13-check_regression/results.regressions | 37 + 14-update_baseline/console.log | 72 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 30 +- mail/results.regressions | 37 + manifest.sh | 12 +- results | 37 + sumfiles/gcc.sum | 16 +- sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 7 +- sumfiles/libitm.sum | 2 +- sumfiles/xfails.xfail | 1 - 47 files changed, 4689 insertions(+), 136 deletions(-) create mode 100644 00-sumfiles/libgomp.log.1.xz create mode 100644 00-sumfiles/libgomp.sum.1 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 create mode 100644 mail/results.regressions