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 5eee49435 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards 3b31328ce 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards e42a6a4cd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 7b4d7d5d7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards d56b9fa94 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 0f2bd9f18 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 606657068 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 7b2989576 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards de8da2c43 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards cfd9633f8 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 1acba66f5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 314680c66 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards ca0acc48e 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 5848b94ba 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards fbbd4aaa3 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards a2f6d4d09 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards a15639085 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards abb42dd2a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 06d7f906a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e65a4cd20 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 863533311 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards a49fe621c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 4dd84ef20 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 2f6b61209 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a6a343160 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 72d1da76e 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 1cbf3cb75 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards beb649489 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 8796c28f0 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 451c35959 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 9b737f5a8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e71c5736d 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 49a75a010 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 332fc6944 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 5ee245671 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 2b449b0a4 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 1d2fdf91f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 5de05162f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 2b69b0fd1 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ae093f858 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards c16990a3d 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards b5d4a1410 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1fc3c9791 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f6e920241 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 3e5e083ad 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9d11781cc 74: onsuccess: 1: Successful build after linux: 44 commits discards 3268a2560 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 2490b0279 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7e1166dae 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 3980ce15f 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards b3105e237 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 773be991a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 67800a782 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9f5386ab 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 179bc2e62 65: onsuccess: 1: Successful build after gcc: 4 commits discards 22d2af539 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a3ceefbc4 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a57697b96 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 7fa83bf2b 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9b61c9f47 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9ec81ee78 59: onsuccess: 1: Successful build after glibc: 2 commits discards 282838ae8 58: onsuccess: 1: Successful build after binutils: 2 commits discards 0bb728355 57: onsuccess: 1: Successful build after gcc: 7 commits discards 6fa70e3f9 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 712ad4f26 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8db389579 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards cffdcdfbe 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 91341f894 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards e747c395e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 87cfc5046 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 377dfcf0e 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 664c15179 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 0c4eb4d95 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4c09c1521 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2e276e379 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 03cfd693a 44: onsuccess: 1: Successful build after linux: 34 commits discards b3678b7cf 43: onsuccess: 1: Successful build after gcc: 2 commits discards e1a691ea9 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 6e0f910d9 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 805f55b30 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 58804fa87 39: onsuccess: 1: Successful build after gcc: 2 commits discards d18c60efa 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a0a622bd5 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards e95117588 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5ff7f484c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f8751408b 34: onsuccess: 1: Successful build after gcc: 3 commits discards 4eb590d39 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 186bff417 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 23b372b20 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 99e551480 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 02e2da320 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f51d218c1 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 8e63d3709 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1f9088d70 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 01b309d12 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6e3cb7561 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 17fa8e6fb 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a2ac290a2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 94a7a5c27 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 883d4f6ee 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b8c4afc7a 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5493d34d2 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9a007a697 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 66aeb1d4f 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b5d3969c9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6e855d221 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b9998e2af 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 76af08d71 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5e5f3b1e3 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f0a438f08 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 59b14e109 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new f68ae2c1e 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cfd427be3 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new b7f13cc06 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a2cd69e24 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new d95552334 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c4e0195e5 34: onsuccess: 1: Successful build after gcc: 3 commits new 45451b5cd 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 659e8c990 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c80680021 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e472062a9 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 790984d2d 39: onsuccess: 1: Successful build after gcc: 2 commits new c539472f5 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 81ef9bd52 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a8d8faccf 42: onsuccess: 1: Successful build after baseline build: no n [...] new 6e1192658 43: onsuccess: 1: Successful build after gcc: 2 commits new 8e0a1c2a8 44: onsuccess: 1: Successful build after linux: 34 commits new f4ec3fd84 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d57c27aff 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new d1543f6f7 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new da86da570 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 6379d45be 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ddee9d582 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 112951b06 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 9b4148e59 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 20c2afa76 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 68b0edb93 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 2c962715d 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e806de8a9 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ce67293d4 57: onsuccess: 1: Successful build after gcc: 7 commits new 57c6c1285 58: onsuccess: 1: Successful build after binutils: 2 commits new 993cb7230 59: onsuccess: 1: Successful build after glibc: 2 commits new 2ce99b79d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 3f73fbdf9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 121aee673 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 0d292a008 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a513d5cbc 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d2c9f5164 65: onsuccess: 1: Successful build after gcc: 4 commits new 5bd301bc3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d29b2b9a4 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c89ffff3a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 76e869f38 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new bbdd4f8ef 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 1bbf45f94 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 51a65f188 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cbc1cb86e 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 40d211043 74: onsuccess: 1: Successful build after linux: 44 commits new b85b0e3c0 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 168df3119 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 04f433d63 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 463c2415a 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cd79f331a 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 7b659a6dc 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 607d8be8b 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 01a4526e5 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1b5b575c9 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 5ead184d6 84: onsuccess: 1: Success after gcc/glibc: 9 commits new cbee85da6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new fc8975484 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2d85a3bbe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 3aca5cb93 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 2f9624dcf 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f1930121b 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b4391ae68 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 9ca037e35 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new b9fa43af7 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 1aa99a1df 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new faed20e4e 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new ea8feb0dc 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new fb2259f5c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 4dd3ae978 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 46090094f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 27a2df966 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 598a8fc9a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b16a78a43 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new e04b33fd1 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new ace8fdd15 104: onsuccess: #1697: 1: Success after gcc: 4 commits new dda2bfc9d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new c655dad47 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new cac44c007 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 2eba566b5 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 69d9f93d3 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 210deb0d8 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 70b3063a3 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 6f0a0b944 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 5edc62e08 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 8ef15db9b 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 8e1398106 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 2a12462e9 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 5c1146216 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new ab91e4b90 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 3744ea364 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 6cf93a4fe 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/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 (5eee49435) \ 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 1684 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 29988 -> 31136 bytes 04-build_abe-stage1/console.log.xz | Bin 90892 -> 91220 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 9264 bytes 07-build_abe-glibc/console.log.xz | Bin 234352 -> 234064 bytes 08-build_abe-stage2/console.log.xz | Bin 225100 -> 225256 bytes 09-build_abe-gdb/console.log.xz | Bin 37312 -> 38260 bytes 10-build_abe-qemu/console.log.xz | Bin 31448 -> 31348 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3908 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2968 -> 2624 bytes 13-check_regression/console.log.xz | Bin 5616 -> 6456 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 | 25 +- 13-check_regression/results.compare2 | 199 ++- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 26 - sumfiles/g++.log.xz | Bin 2664008 -> 2684556 bytes sumfiles/g++.sum | 32 +- sumfiles/gcc.log.xz | Bin 2233884 -> 2216340 bytes sumfiles/gcc.sum | 2082 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 880560 -> 881176 bytes sumfiles/gfortran.sum | 17 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201052 -> 201032 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420272 -> 422452 bytes sumfiles/libstdc++.sum | 122 +- 44 files changed, 1411 insertions(+), 1333 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