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 4069d92ec 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 9e4967cec 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards f4ffb5d87 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 794ad5f87 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 806587768 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 4203b44f6 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 81fc44ba7 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 6952cceb6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 063bb5e24 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 13995f1d8 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 48465c5eb 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 13cd70847 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 5628b8541 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 87026f2c2 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards b7c9802fc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 3a98e5127 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 0cff3bfca 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 3176ee40b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 6ff8d3470 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards cd12590ba 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 7af75383d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 91b9e2e44 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 76f7c292b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ea54ee705 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9ae842e53 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards b1f1be9dd 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 14ce53da4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f8b37c805 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6b356500d 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 61c010786 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ea771383e 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 49288cf21 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards aab558146 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 4d8f3ee3e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 768d781a0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 215bf6d12 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2217cf696 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards d4bc53176 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4ee69596d 74: onsuccess: 1: Successful build after linux: 44 commits discards 7ab7a2bc9 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6559f6c78 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 95c6d6813 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards b6dd5ad4d 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 6ddcd3834 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards e0d9095bc 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f4b1a6ad1 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 61ca6ff7c 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 72d646050 65: onsuccess: 1: Successful build after gcc: 4 commits discards 23e73e0cc 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 99f1924dd 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9498daa5a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 22cd9f145 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 76c41235f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 8a509c9b5 59: onsuccess: 1: Successful build after glibc: 2 commits discards 7dbde7b62 58: onsuccess: 1: Successful build after binutils: 2 commits discards 1107bfec7 57: onsuccess: 1: Successful build after gcc: 7 commits discards 0f6c71042 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f080fd995 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 26d104765 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 808650e54 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards fea355f54 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards ac5f806d6 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7b664538c 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 292eb7d9f 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 89bdc7700 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 529f7b091 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a406f395a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2b879b135 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0978ee3bd 44: onsuccess: 1: Successful build after linux: 34 commits discards 633dd4c5f 43: onsuccess: 1: Successful build after gcc: 2 commits discards 51d43a3ce 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 2e012f614 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6eedc47b6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 712efaf12 39: onsuccess: 1: Successful build after gcc: 2 commits discards 5aaa104ec 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8bec2b164 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b5ce56310 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ffb4d4073 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 886c9aa96 34: onsuccess: 1: Successful build after gcc: 3 commits discards bedc410cc 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 66650d1f5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards e4c3b9b12 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 78f22a30c 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 5a9fed3e9 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 584f49b16 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 84a239c2c 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 18395aa3c 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6ee985183 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 472a336a6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0d998eb37 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 568332bf7 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 66cbf7731 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 58486465d 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4484bc27c 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 78e1db6e8 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a88442cb0 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 95edb6d53 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 885e72632 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f16288576 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 922514159 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d883ad4cf 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6674be656 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 63ebf0ecd 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f9463dbc5 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9635768f2 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3349f07ac 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5fd05823b 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5996e6c33 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1f0306e31 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ac86660e0 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a5b026a0f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 050d91a5a 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 312432441 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4f605c4c5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5ac281dc3 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f3fc8cd40 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8882953cd 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5369d3f81 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 1edae6fed 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a5000258a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 5c132cdff 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6f89f2ac8 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 7f85a0750 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b4cd729df 34: onsuccess: 1: Successful build after gcc: 3 commits new 5e20a0aab 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 86f71614b 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 80e4c8efa 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3588d55f7 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4135e7ecf 39: onsuccess: 1: Successful build after gcc: 2 commits new 05b3c2023 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 79b589218 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fd47015e0 42: onsuccess: 1: Successful build after baseline build: no n [...] new 4a352f94c 43: onsuccess: 1: Successful build after gcc: 2 commits new b10599e46 44: onsuccess: 1: Successful build after linux: 34 commits new 14771cb8c 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c6fe50757 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 73465146f 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3870f3f5c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 12dcaae15 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ff57b5af5 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5df98d938 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 47760fcb6 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 39490e72a 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new af8b1494c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 7b705db69 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 27c6de0ec 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 78ca191fa 57: onsuccess: 1: Successful build after gcc: 7 commits new 8eca1a533 58: onsuccess: 1: Successful build after binutils: 2 commits new 9095ac84a 59: onsuccess: 1: Successful build after glibc: 2 commits new d6672f473 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 38966550e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new f4c507286 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 260f97384 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8cdc37360 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f34ae2758 65: onsuccess: 1: Successful build after gcc: 4 commits new 6b329a0e8 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5a1921a3e 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ea3041146 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new edab5e8fa 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new c421ba37f 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 41c7d4864 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 96cea62da 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 283c253fe 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b65342b63 74: onsuccess: 1: Successful build after linux: 44 commits new af6e82a0f 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dc3c53e1c 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 3061d0d95 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 64177f9b9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5fde20a10 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new b28fcd4e3 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new a92c27a27 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 945df3878 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new dd3b45f29 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new f9588534a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new dc29b3727 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 2793f6b0b 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new e1ed1cdac 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new dac8a23b4 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 50ba667c4 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new cf8405832 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 66461f32d 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 4b0b47775 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 66a25430e 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d06df4a3b 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 65ea89aa3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new dbffd9297 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ad755c992 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 440160442 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 2b55511cc 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 89d939206 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new d87ac6d9c 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 2974d223d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 96866fb51 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 0e6b0a8be 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 7e7459464 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 0c04283f5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new da03a8dd6 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new fc1f51fd4 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new c7e28edc9 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 2d264280b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new b9dd1d08e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new f7c837b9a 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 3086a162c 113: onsuccess: #1706: 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 (4069d92ec) \ 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 1712 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30100 -> 30396 bytes 04-build_abe-stage1/console.log.xz | Bin 91476 -> 92344 bytes 06-build_abe-linux/console.log.xz | Bin 8612 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 234372 -> 235496 bytes 08-build_abe-stage2/console.log.xz | Bin 225192 -> 226924 bytes 09-build_abe-gdb/console.log.xz | Bin 37572 -> 37960 bytes 10-build_abe-qemu/console.log.xz | Bin 32200 -> 31136 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2600 -> 2464 bytes 13-check_regression/console.log.xz | Bin 6228 -> 6340 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 82 +- 13-check_regression/results.compare | 32 +- 13-check_regression/results.compare2 | 93 +- 13-check_regression/results.regressions | 32 +- 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/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 84 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 32 +- sumfiles/g++.log.xz | Bin 2654192 -> 2663468 bytes sumfiles/g++.sum | 17 +- sumfiles/gcc.log.xz | Bin 2240440 -> 2235456 bytes sumfiles/gcc.sum | 1864 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 886396 -> 879044 bytes sumfiles/gfortran.sum | 25 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201152 -> 201100 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 417076 -> 422724 bytes sumfiles/libstdc++.sum | 12 +- 43 files changed, 1228 insertions(+), 1177 deletions(-)