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 92e78da9ba 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards d8412657e0 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 1329681a0b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 736a47c08d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 394aafc0c0 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 4cb2478226 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards ab9460b1d9 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 0bbccd5494 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 9ddf15528c 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 534753df5d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 6983c87402 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7d359056c8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 44f47e2b9c 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 78d2df76d2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 48436c5297 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 7745bb3632 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 929d552e48 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 24d8cfb1fd 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 6cc8facd70 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 194c636aa8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards ea4b07ecab 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 467ca08031 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 7f0d0cd48c 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 19fb2ffa3f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards a80cf3b0cb 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 6d54a0ea2f 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 5fbe2cb755 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 34409ebc6e 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 25517ec4a1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 347fd28641 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards dd7dd00e2c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 76bfeab4ce 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 874e177733 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 0b4a9d3f94 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 8036372e53 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards e0a1250b8e 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 9171959b6f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards ebe94f93e3 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 62bf2d0fe4 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards b38fe65826 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards e35422d0ca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 45ed3070a4 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b5120a0559 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 485409970a 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f69cfa089f 74: onsuccess: 1: Successful build after linux: 44 commits discards 53fc45885f 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards be41052664 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d934242517 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards dd08703d39 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards da368d2445 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards c7016c4c01 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e1123edc2 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ef0df15bb5 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 26256efc24 65: onsuccess: 1: Successful build after gcc: 4 commits discards acff7919c3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1263774490 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69af3079fc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 4c6f477672 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards cde0892cc8 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards fb3cb6f818 59: onsuccess: 1: Successful build after glibc: 2 commits discards bcbc1569a3 58: onsuccess: 1: Successful build after binutils: 2 commits discards 0861361722 57: onsuccess: 1: Successful build after gcc: 7 commits discards d761aacdae 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 79c43450b8 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards be44f4e9d9 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 16dea68c01 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 53c4045ee8 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 4c1f8280c2 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards bc4a3d07b4 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 69c8c7f8e0 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 588600ccc9 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 1db8482bf1 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a2842c188 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards a715394b37 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 38491c21f0 44: onsuccess: 1: Successful build after linux: 34 commits discards a3308d4481 43: onsuccess: 1: Successful build after gcc: 2 commits discards 517dad31c9 42: onsuccess: 1: Successful build after baseline build: no [...] discards 1069f85801 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a17cffb2f 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7ba150a97d 39: onsuccess: 1: Successful build after gcc: 2 commits discards 21b73198c9 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3818138c33 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7df5a5c0c1 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7cbcd2b741 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 0ad96e77e7 34: onsuccess: 1: Successful build after gcc: 3 commits discards e6e55b447a 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 688e88adba 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards fc6ba821c0 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 23b5718d9e 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 2064a10c4b 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0219b582a8 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards bb3a786868 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 8f0da9d19e 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d5a7421770 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dd962e834e 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4ff9bf1853 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bfb9e172cb 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 45f3f2c50c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c6f7da602e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e904360240 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7b881017fd 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b53d03bb6e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b8c4afc7af 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 883d4f6ee3 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 94a7a5c276 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a2ac290a24 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 17fa8e6fb8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6e3cb75615 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 01b309d12e 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1f9088d70f 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8e63d37091 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new f51d218c12 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 02e2da320a 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 99e5514804 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 23b372b201 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 186bff417f 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 4eb590d39a 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f8751408be 34: onsuccess: 1: Successful build after gcc: 3 commits new 5ff7f484c9 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new e951175883 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a0a622bd58 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d18c60efae 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 58804fa874 39: onsuccess: 1: Successful build after gcc: 2 commits new 805f55b300 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6e0f910d9e 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e1a691ea91 42: onsuccess: 1: Successful build after baseline build: no [...] new b3678b7cfd 43: onsuccess: 1: Successful build after gcc: 2 commits new 03cfd693af 44: onsuccess: 1: Successful build after linux: 34 commits new 2e276e3791 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c09c1521d 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 0c4eb4d950 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 664c151794 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 377dfcf0e8 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 87cfc50460 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e747c395ea 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 91341f894a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new cffdcdfbed 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 8db3895798 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 712ad4f267 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6fa70e3f94 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0bb7283556 57: onsuccess: 1: Successful build after gcc: 7 commits new 282838ae8c 58: onsuccess: 1: Successful build after binutils: 2 commits new 9ec81ee784 59: onsuccess: 1: Successful build after glibc: 2 commits new 9b61c9f475 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 7fa83bf2b0 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new a57697b96d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new a3ceefbc4c 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 22d2af5391 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 179bc2e629 65: onsuccess: 1: Successful build after gcc: 4 commits new b9f5386abe 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 67800a7822 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 773be991aa 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b3105e237d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 3980ce15f5 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 7e1166dae8 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 2490b0279a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3268a25606 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 9d11781cc5 74: onsuccess: 1: Successful build after linux: 44 commits new 3e5e083add 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f6e9202413 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 1fc3c97917 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5d4a1410e 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c16990a3d4 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new ae093f8586 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 2b69b0fd15 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 5de05162f9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 1d2fdf91fc 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 2b449b0a45 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 5ee245671b 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 332fc69444 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 49a75a010a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new e71c5736d3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 9b737f5a81 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 451c359590 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8796c28f04 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new beb6494897 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 1cbf3cb756 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 72d1da76e0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new a6a3431600 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 2f6b612096 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 4dd84ef20e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new a49fe621cc 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 8635333112 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new e65a4cd20a 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 06d7f906a6 101: onsuccess: #1693: 1: Success after glibc: 14 commits new abb42dd2af 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a156390853 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new a2f6d4d090 104: onsuccess: #1697: 1: Success after gcc: 4 commits new fbbd4aaa36 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 5848b94ba2 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new ca0acc48e2 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 314680c66c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 1acba66f55 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new cfd9633f8a 110: onsuccess: #1703: 1: Success after gcc: 6 commits new de8da2c431 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 7b2989576b 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 6066570682 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 0f2bd9f18f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new d56b9fa949 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 7b4d7d5d7d 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new e42a6a4cd4 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 3b31328ce6 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 5eee494353 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...]
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 (92e78da9ba) \ 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 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29980 -> 29988 bytes 04-build_abe-stage1/console.log.xz | Bin 90780 -> 90892 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8564 -> 8584 bytes 07-build_abe-glibc/console.log.xz | Bin 233976 -> 234352 bytes 08-build_abe-stage2/console.log.xz | Bin 223588 -> 225100 bytes 09-build_abe-gdb/console.log.xz | Bin 37092 -> 37312 bytes 10-build_abe-qemu/console.log.xz | Bin 31536 -> 31448 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2968 bytes 13-check_regression/console.log.xz | Bin 4288 -> 5616 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 66 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 26 + sumfiles/g++.log.xz | Bin 2658324 -> 2664008 bytes sumfiles/g++.sum | 142 +- sumfiles/gcc.log.xz | Bin 2233248 -> 2233884 bytes sumfiles/gcc.sum | 2763 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 882700 -> 880560 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201220 -> 201052 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424220 -> 420272 bytes sumfiles/libstdc++.sum | 10 +- 44 files changed, 1724 insertions(+), 1563 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