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 2adfa206a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards a8da0c901 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 7a8a678c1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 8b05a72c8 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4563482b0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards fd293db8b 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards ceb17611a 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards d80f5dee8 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 4715bb62c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 85665bc36 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards d39daa612 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards b7f5b3044 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 676f2a7a1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards e29c782e2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 8c371a4d3 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b340758fd 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 3d9feecf2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b525ff7e8 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e43e423aa 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f585e0e31 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards a059c3597 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards df2e3926f 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 5ac125375 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 9c0bb3f15 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 75acce622 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 429aa3bd2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7c4ea452c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 20902eae2 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards bb799d06e 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards faea5e214 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1e8b24dcc 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9744764c1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 9bc994461 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 244549c5b 74: onsuccess: 1: Successful build after linux: 44 commits discards ecd220042 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 7618648ec 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 48ff41a31 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 5699e31d1 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 37db33b53 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 263abe492 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 78526e194 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 459661493 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 93883b81c 65: onsuccess: 1: Successful build after gcc: 4 commits discards 7235f5ef8 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c7365b387 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 569d986a4 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards ad49bd104 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards cab83a459 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 62365ffb8 59: onsuccess: 1: Successful build after glibc: 2 commits discards 97434561f 58: onsuccess: 1: Successful build after binutils: 2 commits discards cb4c9a5b7 57: onsuccess: 1: Successful build after gcc: 7 commits discards 7ec77e4d2 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b9fb0cce6 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dbde0bb9b 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards b3db204ec 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards ac86fdf74 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 47d5a0ee8 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 18a202fd0 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e8539ce43 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 74347fdca 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 478444844 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d6f00e76f 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards faac3f953 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8b9abcf74 44: onsuccess: 1: Successful build after linux: 34 commits discards 02e416a11 43: onsuccess: 1: Successful build after gcc: 2 commits discards 20c8452a5 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 46dc21173 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f50318db8 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e6752971a 39: onsuccess: 1: Successful build after gcc: 2 commits discards 5ce2c9115 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 287623755 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5469dc6e4 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 83ef60dad 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4f1ca5579 34: onsuccess: 1: Successful build after gcc: 3 commits discards b6a2cd5d2 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 27a609e36 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 0490e0850 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 18bb267bc 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards b6197d919 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9ebbafc1a 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 21872ed29 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f89509425 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 895f20ff6 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e53bbc4bd 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7e1a6ca3c 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ac055f48 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e6016ee31 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards aef029d99 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ba30c93f 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dc516e545 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 30d0fc169 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b6b86948d 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards df214d17c 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a78ba5748 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 194de195c 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b9e70264c 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2ca5c67d6 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 17c1bd196 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7f3ea2cef 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8949ac312 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7ee3c50fb 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4e8d68c31 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b1bd5ec93 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 754cf1d35 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new df29d6e62 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 017711462 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2702f6e24 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 39e98d668 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 13b5ca9e9 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d0c32dab6 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 47e9b5d48 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c3185d909 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c77ce441e 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bffba1f36 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bf53d6289 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8990865bc 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fe76aa679 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4b1a46ad7 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f80d69371 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 78ef25771 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 278c6429d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 93066e3a5 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3d5cfdc0b 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new b46a09a3f 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d6dd9aa5f 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 7423ee347 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 0386b44fb 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 20a83cabe 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 98173f86a 34: onsuccess: 1: Successful build after gcc: 3 commits new c47939347 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c4a99a002 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new af5e81efd 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 4d2a67f9d 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0926811f2 39: onsuccess: 1: Successful build after gcc: 2 commits new a8a476f23 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 13fd4b7d4 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cca7ddfcf 42: onsuccess: 1: Successful build after baseline build: no n [...] new fbdc37a08 43: onsuccess: 1: Successful build after gcc: 2 commits new ce1fd4a5b 44: onsuccess: 1: Successful build after linux: 34 commits new 783fc2af4 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aa1edf1b7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new cb273f2b1 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 44bb62e32 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 5a0bdda25 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1fc83f040 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aad476cad 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f522c665a 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 178c6f9bc 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 45b033754 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 17f2e9332 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d9303275a 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 162262f7f 57: onsuccess: 1: Successful build after gcc: 7 commits new 5a13a4b0f 58: onsuccess: 1: Successful build after binutils: 2 commits new 9ca75f407 59: onsuccess: 1: Successful build after glibc: 2 commits new 0978232ba 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new efcbd7246 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 334b65668 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new fcbaf31e1 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 593983137 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 46c1ee477 65: onsuccess: 1: Successful build after gcc: 4 commits new 46d590cc3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new fad236719 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ce3b44949 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fb055d37c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 796697cd0 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 5c8d78ff5 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new d7046defd 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 797000d97 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 06beb469f 74: onsuccess: 1: Successful build after linux: 44 commits new 07c02e126 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c07372315 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 5f5311c5f 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cda3d90c5 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 05a42dbcc 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 26448a2df 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new a942f4209 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6201e12fa 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 26cb0e50f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new de56301f2 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 81a311ba2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new a5b605286 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 4c16895ba 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f231886ab 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new b1f2dc2d6 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 28898d677 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new f18290ada 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 32f5e7f15 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 9f02947a2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c50b0b2d2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new b4e32d403 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 48a721482 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new cbc16678f 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new a4ef74894 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 19a2cb2fb 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new ce19d36ce 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new c91c579b6 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0343da214 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 981dad3c3 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 632c818f9 104: onsuccess: #1697: 1: Success after gcc: 4 commits new e94b7c45d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 23cef4324 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 0c4a2a177 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 9ca7a17df 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 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 (2adfa206a) \ 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 1768 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30180 -> 30020 bytes 04-build_abe-stage1/console.log.xz | Bin 90908 -> 90960 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8296 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 233668 -> 234264 bytes 08-build_abe-stage2/console.log.xz | Bin 223788 -> 223336 bytes 09-build_abe-gdb/console.log.xz | Bin 37344 -> 37304 bytes 10-build_abe-qemu/console.log.xz | Bin 31304 -> 31392 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2792 -> 2644 bytes 13-check_regression/console.log.xz | Bin 5404 -> 4500 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 17 - 13-check_regression/mail-body.txt | 68 +- 13-check_regression/results.compare | 58 +- 13-check_regression/results.compare2 | 82 +- 13-check_regression/results.regressions | 51 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 51 - sumfiles/g++.log.xz | Bin 2658708 -> 2647860 bytes sumfiles/g++.sum | 150 +- sumfiles/gcc.log.xz | Bin 2209524 -> 2205712 bytes sumfiles/gcc.sum | 2512 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 879452 -> 884456 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201008 -> 201116 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2660 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 424208 -> 427144 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 1510 insertions(+), 1736 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