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-arm in repository toolchain/ci/base-artifacts.

discards 9ca7a17df 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 0c4a2a177 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 23cef4324 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards e94b7c45d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 632c818f9 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 981dad3c3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 0343da214 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards c91c579b6 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ce19d36ce 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 19a2cb2fb 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards a4ef74894 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards cbc16678f 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 48a721482 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards b4e32d403 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards c50b0b2d2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 9f02947a2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 32f5e7f15 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards f18290ada 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 28898d677 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b1f2dc2d6 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f231886ab 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 4c16895ba 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards a5b605286 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 81a311ba2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards de56301f2 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 26cb0e50f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6201e12fa 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a942f4209 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 26448a2df 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 05a42dbcc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards cda3d90c5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5f5311c5f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c07372315 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 07c02e126 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 06beb469f 74: onsuccess: 1: Successful build after linux: 44 commits discards 797000d97 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards d7046defd 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5c8d78ff5 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 796697cd0 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards fb055d37c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards ce3b44949 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fad236719 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 46d590cc3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 46c1ee477 65: onsuccess: 1: Successful build after gcc: 4 commits discards 593983137 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fcbaf31e1 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 334b65668 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards efcbd7246 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 0978232ba 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9ca75f407 59: onsuccess: 1: Successful build after glibc: 2 commits discards 5a13a4b0f 58: onsuccess: 1: Successful build after binutils: 2 commits discards 162262f7f 57: onsuccess: 1: Successful build after gcc: 7 commits discards d9303275a 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 17f2e9332 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 45b033754 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 178c6f9bc 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards f522c665a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards aad476cad 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1fc83f040 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5a0bdda25 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 44bb62e32 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards cb273f2b1 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards aa1edf1b7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 783fc2af4 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ce1fd4a5b 44: onsuccess: 1: Successful build after linux: 34 commits discards fbdc37a08 43: onsuccess: 1: Successful build after gcc: 2 commits discards cca7ddfcf 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 13fd4b7d4 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a8a476f23 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0926811f2 39: onsuccess: 1: Successful build after gcc: 2 commits discards 4d2a67f9d 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards af5e81efd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c4a99a002 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c47939347 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 98173f86a 34: onsuccess: 1: Successful build after gcc: 3 commits discards 20a83cabe 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0386b44fb 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 7423ee347 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d6dd9aa5f 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards b46a09a3f 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3d5cfdc0b 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 93066e3a5 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 278c6429d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 78ef25771 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f80d69371 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4b1a46ad7 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fe76aa679 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8990865bc 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bf53d6289 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bffba1f36 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c77ce441e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c3185d909 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 47e9b5d48 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d0c32dab6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 13b5ca9e9 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 39e98d668 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2702f6e24 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 017711462 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards df29d6e62 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 754cf1d35 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b1bd5ec93 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e81e93833 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b5bf2f5c0 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1b87749ee 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 20a40e6b5 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ecb73fe8d 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 440298000 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ebe00b7b0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3d55efa68 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bb2c87e6a 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 912ec8175 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7c1455cb4 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 864f261d2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2f83b686c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2672d8ad7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 219ace4f5 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3a0d84401 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cd1f52923 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 755d798e0 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 08a4f4f91 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new aecff2c80 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3530e8c22 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new e1faf2793 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9dada8dc0 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 53f248e33 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4589d3c5d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 30a0964f3 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2fb4fbe83 34: onsuccess: 1: Successful build after gcc: 3 commits new 9725d02e8 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e67f77fed 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a6d08e445 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 87df3bb18 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f7f12be98 39: onsuccess: 1: Successful build after gcc: 2 commits new 42b64d810 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 09226cc91 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7d5ee7120 42: onsuccess: 1: Successful build after baseline build: no n [...] new 95c50d4ae 43: onsuccess: 1: Successful build after gcc: 2 commits new 2a1a7a3ac 44: onsuccess: 1: Successful build after linux: 34 commits new 37ad44aaf 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 37f93e52c 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 9f95e51b4 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 40002747d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new b9c460e71 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 619332fb8 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 476c521fb 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e9ed708f9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new b7857b72f 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 3a7deafe2 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new e74253e3f 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a5344e841 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cbbf13e2f 57: onsuccess: 1: Successful build after gcc: 7 commits new fccac368e 58: onsuccess: 1: Successful build after binutils: 2 commits new 0cd66e55e 59: onsuccess: 1: Successful build after glibc: 2 commits new c0fc17ad1 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 46637b510 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9e59dca1a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new d13ae8387 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 346b56586 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 64835cb16 65: onsuccess: 1: Successful build after gcc: 4 commits new ce1ef78f7 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fdd38d0fc 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 795ef3552 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 87c52d491 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new feb2d69e9 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 5bb36d864 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 89839e95d 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 21d552ea9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 54f6a9ba7 74: onsuccess: 1: Successful build after linux: 44 commits new 70e7b297e 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f0fefffbe 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 2cac64ed6 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1e23d673a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 467299563 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 44b933d14 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 605c788fc 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 422c227d5 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 0734b5e5f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6e5e36eee 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 69a7facb0 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 440b0c60c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new a3bc9a7a0 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f52ba8e6d 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ffcb0c372 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ca3c5e7ad 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 4df8258cf 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 75fd9adb6 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 123864948 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 547551eb5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 1a95a2dbd 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new ff6cafdc5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 621b30b1f 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new b80fae97f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 008b937fa 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 6157e1c04 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new ba9b9df76 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b1b01221c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new cff8d0843 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 61b3366bf 104: onsuccess: #1697: 1: Success after gcc: 4 commits new bcbcb53b4 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new cfb1f692f 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new a7ae8203b 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 4bc143d9b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new e8aa5239a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits

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 (9ca7a17df) \ 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 1688 -> 1848 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30020 -> 29892 bytes 04-build_abe-stage1/console.log.xz | Bin 90960 -> 90672 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8288 -> 8276 bytes 07-build_abe-glibc/console.log.xz | Bin 234264 -> 233140 bytes 08-build_abe-stage2/console.log.xz | Bin 223336 -> 223564 bytes 09-build_abe-gdb/console.log.xz | Bin 37304 -> 37136 bytes 10-build_abe-qemu/console.log.xz | Bin 31392 -> 31268 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2440 bytes 13-check_regression/console.log.xz | Bin 4500 -> 4512 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 77 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 47 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/mail-body.txt | 77 +- manifest.sh | 30 +- results | 26 + sumfiles/g++.log.xz | Bin 2647860 -> 2658232 bytes sumfiles/g++.sum | 124 +- sumfiles/gcc.log.xz | Bin 2205712 -> 2228376 bytes sumfiles/gcc.sum | 2728 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 884456 -> 883228 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201116 -> 201220 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2660 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 427144 -> 428396 bytes sumfiles/libstdc++.sum | 18 +- 41 files changed, 1696 insertions(+), 1689 deletions(-) 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