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 6847d8d12 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 2dfbe3f6f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards c64fbdcc3 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 877a19266 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 0e452e5c0 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards dfaa1447a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 6df4ca562 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards b4830d68d 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards d2696e85d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 1853cab70 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 0ae4b6077 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 59aa59fa4 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5d09f501b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 0cd0e3907 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d40542e33 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 6f11ecd25 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b1dce0ce1 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 810bb8e10 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 1e423bb4d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 49b443b55 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards d1970cc77 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6530cdb25 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 14edfce62 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards e1c791fd1 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 91f645574 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cdf70b895 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 4abedd5a4 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 95f6a300b 74: onsuccess: 1: Successful build after linux: 44 commits discards 5790f8c08 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 48f951c64 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 86b067285 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards c1fbe24be 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 5d10bf3fd 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards a76fb6978 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3101e4ce0 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5b12f244e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 609c86280 65: onsuccess: 1: Successful build after gcc: 4 commits discards a46f32a97 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 659e6ffe8 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 105e779e2 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 3132033f4 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 778717fc0 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards a37577950 59: onsuccess: 1: Successful build after glibc: 2 commits discards a0463854e 58: onsuccess: 1: Successful build after binutils: 2 commits discards c19d8296c 57: onsuccess: 1: Successful build after gcc: 7 commits discards a3e357cc4 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2f24f69ec 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d1935df8c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards a6d808975 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 238bee70c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 88c72ca63 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 29d2ef211 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a7e3eea77 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 81a58a7ee 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 5fcc8686b 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6a51f5658 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 7c5b0f333 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 51ab46709 44: onsuccess: 1: Successful build after linux: 34 commits discards f521a780f 43: onsuccess: 1: Successful build after gcc: 2 commits discards 09420c11f 42: onsuccess: 1: Successful build after baseline build: no n [...] discards d8c07bdcd 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 44e3d1b11 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 70f1887d4 39: onsuccess: 1: Successful build after gcc: 2 commits discards 8377983b4 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 497b114fd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8d7b043e7 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 64cbe11be 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f1b1120b0 34: onsuccess: 1: Successful build after gcc: 3 commits discards d7ef8109f 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 01cdbf133 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards d5c2a122e 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d87679178 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 9f2c60613 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 25da159ae 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards a72bae61f 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 01d383214 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fa9a7b096 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b07d60db8 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 00fb745ff 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a8d5fc0f9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 740e4d9d7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f81d6668c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a31c8e58a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4c4d166ad 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bb38408ee 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d1efdd4f0 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0c5cd7f51 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8cc1cec3d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e386290ca 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 705d12dac 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0a0656697 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5e1fff907 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bf3b784f9 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ba9cf493a 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2943524fd 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0c9862ae4 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3b047815a 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0e3f0a990 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 24f5facb0 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9432b2885 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2c6b4337c 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d742a56cc 1: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c81612245 2: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e9404c1ea 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 108bb326c 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new db6dca619 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e08f5946f 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f2e9e5958 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a2e72bac6 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 30a69b595 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new cec5cd1eb 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a197fbc86 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 96c25eb44 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f1b3186f9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8461b2a80 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 08ace893d 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5bddf12ac 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9e4ea0ae8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f36a8fef0 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4a1a0c35d 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 59eaf267c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e0118101e 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 788a8e2c0 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1e905eda2 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f51b5d497 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a73af8f63 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 42db21b2c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9945b0b58 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fbb79d656 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a38474850 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 91e855676 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 88fa9f012 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dc87a62da 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new bf4b1bf7d 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 831f9924d 34: onsuccess: 1: Successful build after gcc: 3 commits new fb2b8a4e7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8efe80c89 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 71eaeca18 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cf207565e 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 013783dd2 39: onsuccess: 1: Successful build after gcc: 2 commits new 5b53be87d 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6ea88d485 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7bd3b438a 42: onsuccess: 1: Successful build after baseline build: no n [...] new 257e86b5c 43: onsuccess: 1: Successful build after gcc: 2 commits new 2eef07f01 44: onsuccess: 1: Successful build after linux: 34 commits new a722c48ee 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 56d903657 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 024d2bc7a 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 858aab0eb 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 98e8b1ede 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ceb1e6c98 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 40d145d2c 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0512edfcb 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new e8c418d05 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 33361281b 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 46069769d 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f087c81c8 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 606d6fb32 57: onsuccess: 1: Successful build after gcc: 7 commits new dacf2c7b9 58: onsuccess: 1: Successful build after binutils: 2 commits new bf135b563 59: onsuccess: 1: Successful build after glibc: 2 commits new 32ebde312 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new c06903947 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d817d6260 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new be93876c4 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2ba8a9a5f 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cadc0706f 65: onsuccess: 1: Successful build after gcc: 4 commits new d09e1a731 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8fe0db1cc 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 691f2c007 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d07f67f38 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 956b059d1 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 9600739c6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 57bda489c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 45e892c88 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ba4b0ed73 74: onsuccess: 1: Successful build after linux: 44 commits new a9e2a1563 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ce1aa17d4 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 9843ccd2f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d70a39e36 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d0b6c70c1 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 8b05ac6fa 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 1999d6cd8 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d379c8165 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a3b0424d9 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 7d998b7df 84: onsuccess: 1: Success after gcc/glibc: 9 commits new fad85e830 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 46b2a0547 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new d2be5ece1 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new cfac44895 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 6a5bebd83 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8dddece1c 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 3224fafb1 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7ec3e8270 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new fc905802f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9a3faea42 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new f72fb1a12 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 2495f8e32 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new e8cd02dba 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 1b9e7ce7b 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new c11ead225 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 45dd3962e 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new b5966c6e0 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 540b502bb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...]

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 (6847d8d12) \ 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 1736 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29612 -> 30388 bytes 04-build_abe-stage1/console.log.xz | Bin 90816 -> 90804 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 235240 -> 233792 bytes 08-build_abe-stage2/console.log.xz | Bin 225696 -> 223072 bytes 09-build_abe-gdb/console.log.xz | Bin 37448 -> 37408 bytes 10-build_abe-qemu/console.log.xz | Bin 31864 -> 31772 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2456 -> 3208 bytes 13-check_regression/console.log.xz | Bin 4592 -> 12844 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 13 +- 13-check_regression/mail-body.txt | 88 +- 13-check_regression/results.compare | 43 +- 13-check_regression/results.compare2 | 1210 +++++++++++- 13-check_regression/results.regressions | 43 +- 14-update_baseline/console.log | 70 +- 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 | 90 +- mail/mail-subject.txt | 2 +- manifest.sh | 41 +- results | 43 +- sumfiles/g++.log.xz | Bin 2672612 -> 2649240 bytes sumfiles/g++.sum | 633 ++++-- sumfiles/gcc.log.xz | Bin 2206728 -> 2233900 bytes sumfiles/gcc.sum | 3235 +++++++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 880932 -> 879656 bytes sumfiles/gfortran.sum | 84 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 199688 -> 201168 bytes sumfiles/libgomp.sum | 67 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423600 -> 423396 bytes sumfiles/libstdc++.sum | 51 +- 46 files changed, 3876 insertions(+), 1865 deletions(-)