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 540b502bb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards b5966c6e0 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 45dd3962e 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards c11ead225 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 1b9e7ce7b 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards e8cd02dba 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 2495f8e32 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards f72fb1a12 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 9a3faea42 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards fc905802f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 7ec3e8270 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 3224fafb1 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 8dddece1c 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6a5bebd83 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards cfac44895 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d2be5ece1 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 46b2a0547 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards fad85e830 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 7d998b7df 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a3b0424d9 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards d379c8165 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 1999d6cd8 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 8b05ac6fa 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards d0b6c70c1 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards d70a39e36 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 9843ccd2f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ce1aa17d4 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards a9e2a1563 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ba4b0ed73 74: onsuccess: 1: Successful build after linux: 44 commits discards 45e892c88 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 57bda489c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9600739c6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 956b059d1 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards d07f67f38 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 691f2c007 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8fe0db1cc 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d09e1a731 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards cadc0706f 65: onsuccess: 1: Successful build after gcc: 4 commits discards 2ba8a9a5f 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards be93876c4 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d817d6260 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards c06903947 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 32ebde312 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards bf135b563 59: onsuccess: 1: Successful build after glibc: 2 commits discards dacf2c7b9 58: onsuccess: 1: Successful build after binutils: 2 commits discards 606d6fb32 57: onsuccess: 1: Successful build after gcc: 7 commits discards f087c81c8 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 46069769d 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 33361281b 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards e8c418d05 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 0512edfcb 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 40d145d2c 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ceb1e6c98 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 98e8b1ede 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 858aab0eb 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 024d2bc7a 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 56d903657 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards a722c48ee 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2eef07f01 44: onsuccess: 1: Successful build after linux: 34 commits discards 257e86b5c 43: onsuccess: 1: Successful build after gcc: 2 commits discards 7bd3b438a 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 6ea88d485 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5b53be87d 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 013783dd2 39: onsuccess: 1: Successful build after gcc: 2 commits discards cf207565e 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 71eaeca18 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8efe80c89 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fb2b8a4e7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 831f9924d 34: onsuccess: 1: Successful build after gcc: 3 commits discards bf4b1bf7d 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dc87a62da 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 88fa9f012 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 91e855676 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards a38474850 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fbb79d656 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9945b0b58 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 42db21b2c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a73af8f63 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f51b5d497 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1e905eda2 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 788a8e2c0 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e0118101e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 59eaf267c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4a1a0c35d 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f36a8fef0 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9e4ea0ae8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5bddf12ac 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 08ace893d 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8461b2a80 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f1b3186f9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 96c25eb44 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a197fbc86 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cec5cd1eb 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 30a69b595 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a2e72bac6 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f2e9e5958 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e08f5946f 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards db6dca619 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 108bb326c 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e9404c1ea 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c81612245 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8d1b903a9 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 22581b48e 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e22409953 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eb2e6b9e6 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 69f9384f2 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 162dbd4e5 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ee9bcd19f 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 832e17817 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ee50988fe 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9106f8fb3 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5d254fdad 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new be49792c9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4f12f92ff 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1688a5605 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4264f6899 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 27fc6bff8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5cd6a5330 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0fed02ad3 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c3e6d037a 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 71dfc0984 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ca7955754 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 506c53687 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6455d4cd6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a0957fd78 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1ab54aa07 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c0078cec1 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9364aa344 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6284647ae 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8c64d1d1a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 89515ae64 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 93ec0dc3c 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 02662aa06 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d2c3a527e 34: onsuccess: 1: Successful build after gcc: 3 commits new cb606bf67 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d9d8f85f4 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7b0858065 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7ddbcc615 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3698781ce 39: onsuccess: 1: Successful build after gcc: 2 commits new 82cec5ea6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 23a23a643 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fe841ba8e 42: onsuccess: 1: Successful build after baseline build: no n [...] new 3416d7be0 43: onsuccess: 1: Successful build after gcc: 2 commits new 8d924d2ad 44: onsuccess: 1: Successful build after linux: 34 commits new 673a5b625 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ba19fd793 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 3fa116c0d 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0732d90ee 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new b8359bf09 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 17320803f 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 742bdf494 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 44466bbf2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 2e16f2d8e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new b2c1cd69d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 70f67c98b 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e7193d373 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a3a0d7ad0 57: onsuccess: 1: Successful build after gcc: 7 commits new 088972302 58: onsuccess: 1: Successful build after binutils: 2 commits new 53fa26449 59: onsuccess: 1: Successful build after glibc: 2 commits new 08cab8924 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new b70a3141d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 271b58c1a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 554aa3450 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 57ddab8a7 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7f59733fe 65: onsuccess: 1: Successful build after gcc: 4 commits new 5a4f832a0 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e7c95c4e3 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 418322a8c 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8eb679ff5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 9bff44834 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 115de6c42 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new f0dc098a6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7293f0e69 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 8ca1fc43a 74: onsuccess: 1: Successful build after linux: 44 commits new 119f191d5 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9aea2efd3 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new a533287e2 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 24c24d32d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5b7f4caea 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new d92e4d0cf 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new fee763086 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ce8eb716f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 91e14651f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 723f790c1 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 9b6be0ed6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new d21c3a7b5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 930fdea9a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e5d063b5c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 5f9edd828 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d8a7c5b7e 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new e65d59fec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 5c55f26b5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 74cba0ee2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 3bfe84bb1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 5e2b85aff 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 2fe4b80d6 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 423d632b9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new a67e40d49 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 78e9234ca 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new f40d3d1fe 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new f343c37c1 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 703b5ba3f 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 572a9511d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...]

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 (540b502bb) \ 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 1724 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30388 -> 29824 bytes 04-build_abe-stage1/console.log.xz | Bin 90804 -> 90976 bytes 06-build_abe-linux/console.log.xz | Bin 8636 -> 8620 bytes 07-build_abe-glibc/console.log.xz | Bin 233792 -> 233924 bytes 08-build_abe-stage2/console.log.xz | Bin 223072 -> 223180 bytes 09-build_abe-gdb/console.log.xz | Bin 37408 -> 37132 bytes 10-build_abe-qemu/console.log.xz | Bin 31772 -> 31828 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3208 -> 2436 bytes 13-check_regression/console.log.xz | Bin 12844 -> 4608 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 8 - 13-check_regression/mail-body.txt | 87 +- 13-check_regression/results.compare | 49 +- 13-check_regression/results.compare2 | 1216 +------------------ 13-check_regression/results.regressions | 50 - 14-update_baseline/console.log | 38 +- 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 | 89 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 50 - sumfiles/g++.log.xz | Bin 2649240 -> 2680256 bytes sumfiles/g++.sum | 10 +- sumfiles/gcc.log.xz | Bin 2233900 -> 2196224 bytes sumfiles/gcc.sum | 2024 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 879656 -> 878412 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201168 -> 201128 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 423396 -> 422780 bytes sumfiles/libstdc++.sum | 2 +- 44 files changed, 1132 insertions(+), 2558 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions