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 e8aa5239a3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 4bc143d9b7 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards a7ae8203bf 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards cfb1f692f2 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards bcbcb53b4f 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 61b3366bfa 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards cff8d08434 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards b1b01221ce 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards ba9b9df76f 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6157e1c04c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 008b937fa2 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards b80fae97f8 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 621b30b1fb 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards ff6cafdc50 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 1a95a2dbdb 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 547551eb56 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 1238649484 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 75fd9adb63 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 4df8258cf4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards ca3c5e7ad6 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ffcb0c3721 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f52ba8e6da 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards a3bc9a7a01 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 440b0c60c1 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 69a7facb0b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6e5e36eeec 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 0734b5e5fd 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 422c227d5b 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 605c788fce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 44b933d148 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 4672995634 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 1e23d673ac 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2cac64ed6d 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f0fefffbe5 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 70e7b297e7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 54f6a9ba72 74: onsuccess: 1: Successful build after linux: 44 commits discards 21d552ea9b 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 89839e95d3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5bb36d864c 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards feb2d69e96 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 87c52d491e 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 795ef35526 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards fdd38d0fc9 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ce1ef78f70 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 64835cb164 65: onsuccess: 1: Successful build after gcc: 4 commits discards 346b565862 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d13ae8387b 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e59dca1ac 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 46637b510f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c0fc17ad1b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 0cd66e55e5 59: onsuccess: 1: Successful build after glibc: 2 commits discards fccac368eb 58: onsuccess: 1: Successful build after binutils: 2 commits discards cbbf13e2ff 57: onsuccess: 1: Successful build after gcc: 7 commits discards a5344e841c 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e74253e3fb 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a7deafe29 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards b7857b72fe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards e9ed708f90 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 476c521fb7 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 619332fb8f 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9c460e71d 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 40002747d1 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 9f95e51b4a 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37f93e52cf 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 37ad44aaf8 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2a1a7a3acd 44: onsuccess: 1: Successful build after linux: 34 commits discards 95c50d4aee 43: onsuccess: 1: Successful build after gcc: 2 commits discards 7d5ee71205 42: onsuccess: 1: Successful build after baseline build: no [...] discards 09226cc914 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 42b64d8107 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f7f12be98a 39: onsuccess: 1: Successful build after gcc: 2 commits discards 87df3bb187 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a6d08e4458 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e67f77feda 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9725d02e8f 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 2fb4fbe83f 34: onsuccess: 1: Successful build after gcc: 3 commits discards 30a0964f36 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4589d3c5d3 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 53f248e33a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 9dada8dc06 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards e1faf27939 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3530e8c22d 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards aecff2c80c 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 08a4f4f91b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 755d798e0c 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards cd1f52923a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3a0d844018 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 219ace4f59 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2672d8ad73 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2f83b686cd 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 864f261d26 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7c1455cb46 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 912ec81752 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bb2c87e6aa 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3d55efa68f 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ebe00b7b0f 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4402980006 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ecb73fe8dd 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 20a40e6b50 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1b87749ee9 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b5bf2f5c05 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0f7cb3eb2d 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f9c38b6dbd 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7a0d1619ef 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5dbe0e46e2 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7a869130f8 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d058c63a71 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 78ff9d81e6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 38f607bf0b 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9b032be791 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c44caae9db 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 434333c2a2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c4f176c6bf 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 428a2cf1c7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e0de9509c5 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d7648c1e74 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b78bfbec94 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d99a98b5ea 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ce2820ce27 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5d47286950 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 8dd0206522 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7e4d835c8a 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d389353815 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new db196ed8d4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new edb9b6047c 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 1c839e260d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 064acc4e01 34: onsuccess: 1: Successful build after gcc: 3 commits new 4eb0fa4c0b 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 0bc95ea953 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ea031f9a45 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 29d4da9052 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ccfa3f7ba 39: onsuccess: 1: Successful build after gcc: 2 commits new 062aacd104 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1cf83a85d5 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 21cf542692 42: onsuccess: 1: Successful build after baseline build: no [...] new f6316105ee 43: onsuccess: 1: Successful build after gcc: 2 commits new b361c4cf61 44: onsuccess: 1: Successful build after linux: 34 commits new 5af95da120 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0001c0d01d 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new a29d8741ad 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 986a847787 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 99c3db5ce8 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new effbc9faef 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9e5385ae7a 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7c335b1263 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new e3aa4ccdde 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new d39861fddb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new f5c386a42c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8554019c31 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9925ad7562 57: onsuccess: 1: Successful build after gcc: 7 commits new a839734c18 58: onsuccess: 1: Successful build after binutils: 2 commits new 50b53e0458 59: onsuccess: 1: Successful build after glibc: 2 commits new 31da8af415 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 5065db95d7 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 54c65cfd67 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new e697460749 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 28db31daa4 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 69f7ada228 65: onsuccess: 1: Successful build after gcc: 4 commits new 79069dea3d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new a137a4ab88 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ba9080721 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4a9a7a82f8 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 9ff57290e7 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new c26ed4d636 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ddb1151e5c 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5b80c6cb8d 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new dc6a125b29 74: onsuccess: 1: Successful build after linux: 44 commits new 3ca8bdcef0 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8b3db4c79b 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new a7529367d0 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5d940de605 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2e9a1c812f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 6c574750bc 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new df23fda312 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6161485d75 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 40bd38962b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3d02ba50a6 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 68e9d22f5c 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 9b569dc3d8 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new a2cc25fa8f 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new a8584f8901 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 152083d5a1 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9b964a0526 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 4688dccb6d 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f568547e25 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new e6e303149d 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9a42235c85 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 6f99a0379d 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new c30f9d680d 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 76c2c9ca68 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new fcc83d684e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 0dc1a7c3ab 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new f28bb5ab7f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new be5dcce928 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 5c74bed680 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 743d2a495f 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 7be0512a0f 104: onsuccess: #1697: 1: Success after gcc: 4 commits new cab415c170 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 5d81d763fc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 918a8144e0 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 8e8da41c16 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new f787539b12 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 66cb37f4aa 110: onsuccess: #1703: 1: Success after gcc: 6 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 (e8aa5239a3) \ 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 1848 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 29892 -> 29940 bytes 04-build_abe-stage1/console.log.xz | Bin 90672 -> 91000 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8276 -> 8328 bytes 07-build_abe-glibc/console.log.xz | Bin 233140 -> 233348 bytes 08-build_abe-stage2/console.log.xz | Bin 223564 -> 224304 bytes 09-build_abe-gdb/console.log.xz | Bin 37136 -> 37152 bytes 10-build_abe-qemu/console.log.xz | Bin 31268 -> 31308 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2440 -> 2692 bytes 13-check_regression/console.log.xz | Bin 4512 -> 4428 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 37 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results | 26 - sumfiles/g++.log.xz | Bin 2658232 -> 2686540 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 2228376 -> 2211016 bytes sumfiles/gcc.sum | 2438 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 883228 -> 877372 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201220 -> 201132 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 428396 -> 419936 bytes sumfiles/libstdc++.sum | 16 +- 41 files changed, 1451 insertions(+), 1518 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