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 2653756e0 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards a1cd3b9af 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 4c297500c 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 525d7b214 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards cf393721f 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards f48d4cfe0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 3d17e3ae2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 77e8fdd15 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 1a0c35545 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 71eb9ef68 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 592b7bdd4 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f120722ce 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 0b3be45ea 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards cf7e0c580 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 3b0f4d27d 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 3fe11dfa7 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c0b9cf3e1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 958f2ab64 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 5339afa9d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 6471ab73b 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 077ed06ff 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards a4622ea93 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards fea6ee8e5 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 69004c824 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 7ee029fb8 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards b1277d5b3 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f7aa3d99f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 65bcd0b4b 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 970ed97a0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 90fdd4597 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 9e16b74ff 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6723c7101 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 860812c62 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards e5d578fcf 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b789fc4fa 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b648edd8c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards bb9dd63de 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dc559bcdb 74: onsuccess: 1: Successful build after linux: 44 commits discards 859eb3bbb 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 0c4767954 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9fb08a86 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3202fe833 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards b4d0cabfe 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 054343523 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4640c0ed0 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cb2367d13 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bdae685c7 65: onsuccess: 1: Successful build after gcc: 4 commits discards 386e69e63 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 37292ca1a 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7c279745e 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 9f9a4892f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards b8a0cc473 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards e5b5b8830 59: onsuccess: 1: Successful build after glibc: 2 commits discards d08f05e39 58: onsuccess: 1: Successful build after binutils: 2 commits discards d4292a6d0 57: onsuccess: 1: Successful build after gcc: 7 commits discards 832be2a5a 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4f354a785 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 17809806a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 883926b59 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 50e38fd43 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards fa19fe9cf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards dbba9723e 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c82fbc1a2 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c0187a331 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards adbf6161d 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards aba66b044 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards ec1cfd378 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 43351edc6 44: onsuccess: 1: Successful build after linux: 34 commits discards dc356c3e2 43: onsuccess: 1: Successful build after gcc: 2 commits discards 12e55a3ca 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 18390adce 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c4df25d9b 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5df8cb334 39: onsuccess: 1: Successful build after gcc: 2 commits discards a960c02bf 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 542ed5b25 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 62e87e515 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7b7a8075e 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 212d95f21 34: onsuccess: 1: Successful build after gcc: 3 commits discards 2721132c9 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a1805f971 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 35c3edb7c 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 117d0323a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards f27ef5eec 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 83549da4a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards fd09d07d5 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b79d229fc 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3f71968a9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e6628340 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d620ee714 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 565eda05e 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 80e47128d 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 560bd6340 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9c1073202 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 615f94b07 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards abb28b027 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5485e5fce 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e8345ea70 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 97d32c963 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3f60488da 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d47d06a24 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ecd1499b9 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 692a7b297 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d883ad4cf 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 922514159 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f16288576 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 885e72632 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 95edb6d53 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a88442cb0 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 78e1db6e8 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4484bc27c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 58486465d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 66cbf7731 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 568332bf7 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0d998eb37 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 472a336a6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6ee985183 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 18395aa3c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 84a239c2c 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 584f49b16 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 5a9fed3e9 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 78f22a30c 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new e4c3b9b12 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 66650d1f5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new bedc410cc 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 886c9aa96 34: onsuccess: 1: Successful build after gcc: 3 commits new ffb4d4073 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b5ce56310 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8bec2b164 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5aaa104ec 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 712efaf12 39: onsuccess: 1: Successful build after gcc: 2 commits new 6eedc47b6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2e012f614 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 51d43a3ce 42: onsuccess: 1: Successful build after baseline build: no n [...] new 633dd4c5f 43: onsuccess: 1: Successful build after gcc: 2 commits new 0978ee3bd 44: onsuccess: 1: Successful build after linux: 34 commits new 2b879b135 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a406f395a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 529f7b091 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 89bdc7700 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 292eb7d9f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7b664538c 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ac5f806d6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fea355f54 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 808650e54 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 26d104765 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new f080fd995 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0f6c71042 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1107bfec7 57: onsuccess: 1: Successful build after gcc: 7 commits new 7dbde7b62 58: onsuccess: 1: Successful build after binutils: 2 commits new 8a509c9b5 59: onsuccess: 1: Successful build after glibc: 2 commits new 76c41235f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 22cd9f145 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9498daa5a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 99f1924dd 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 23e73e0cc 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 72d646050 65: onsuccess: 1: Successful build after gcc: 4 commits new 61ca6ff7c 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f4b1a6ad1 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e0d9095bc 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6ddcd3834 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new b6dd5ad4d 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 95c6d6813 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 6559f6c78 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7ab7a2bc9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 4ee69596d 74: onsuccess: 1: Successful build after linux: 44 commits new d4bc53176 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2217cf696 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 215bf6d12 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 768d781a0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4d8f3ee3e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new aab558146 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 49288cf21 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new ea771383e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 61c010786 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 6b356500d 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f8b37c805 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 14ce53da4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new b1f1be9dd 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 9ae842e53 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ea54ee705 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 76f7c292b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 91b9e2e44 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7af75383d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new cd12590ba 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 6ff8d3470 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 3176ee40b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 0cff3bfca 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 3a98e5127 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new b7c9802fc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 87026f2c2 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 5628b8541 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 13cd70847 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 48465c5eb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 13995f1d8 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 063bb5e24 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 6952cceb6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 81fc44ba7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 4203b44f6 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 806587768 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 794ad5f87 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new f4ffb5d87 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 9e4967cec 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 4069d92ec 112: onsuccess: #1705: 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 (2653756e0) \ 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 1720 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29868 -> 30100 bytes 04-build_abe-stage1/console.log.xz | Bin 91072 -> 91476 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8292 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 234412 -> 234372 bytes 08-build_abe-stage2/console.log.xz | Bin 222944 -> 225192 bytes 09-build_abe-gdb/console.log.xz | Bin 37132 -> 37572 bytes 10-build_abe-qemu/console.log.xz | Bin 31280 -> 32200 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3860 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2540 -> 2600 bytes 13-check_regression/console.log.xz | Bin 6344 -> 6228 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 52 + 13-check_regression/results.compare | 59 +- 13-check_regression/results.compare2 | 377 +---- 13-check_regression/results.regressions | 52 + 14-update_baseline/console.log | 66 +- 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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 54 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 52 + sumfiles/g++.log.xz | Bin 2663728 -> 2654192 bytes sumfiles/g++.sum | 173 ++- sumfiles/gcc.log.xz | Bin 2231024 -> 2240440 bytes sumfiles/gcc.sum | 2417 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 879100 -> 886396 bytes sumfiles/gfortran.sum | 56 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201132 -> 201152 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422400 -> 417076 bytes sumfiles/libstdc++.sum | 20 +- 45 files changed, 1758 insertions(+), 1709 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