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 f0a9d2fbe 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards d9acabf6d 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 6f5f644f9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 656f9a8b7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 4e1dc7e41 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 28845bfe0 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards efdd1ba21 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 38193003d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 8954a6670 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 334c1d440 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 3d7f7c73f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 911863623 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 4147303ca 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards be905656a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 22f50b40f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 9fae71028 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 6fbbad08c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b6ea361a3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 6eea6d8cd 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 7f58407c5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9a523cace 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 4d74dd15b 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ec6bf14ec 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 169f751b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3b0df8fb5 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards ada22226c 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards f7aeb4bcd 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 7c77c41e4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards f9189ea2b 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5c2a5d0a0 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 883a04577 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e713ea4f3 74: onsuccess: 1: Successful build after linux: 44 commits discards 26850f782 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 6956e0c7c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0698d8a49 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards e7061b86a 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards aeb037162 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 8a66b7e41 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2ca9d87fc 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2b7ac22a3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 983b8704e 65: onsuccess: 1: Successful build after gcc: 4 commits discards ceb020f6a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8438c9efe 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 516d6f989 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards d434f299f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards f2e221c2f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 5a04a3e13 59: onsuccess: 1: Successful build after glibc: 2 commits discards d4a318a89 58: onsuccess: 1: Successful build after binutils: 2 commits discards 8814ce850 57: onsuccess: 1: Successful build after gcc: 7 commits discards 38d62408c 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7a16d6512 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a659d827a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 4494a3329 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards e8a34802f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards cc44e400d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 142c74349 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5a9c33c33 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 989a4c0d5 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards f7a9705b4 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 106028cbe 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 49ca90bac 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a5a8d439e 44: onsuccess: 1: Successful build after linux: 34 commits discards 2efb1cb0d 43: onsuccess: 1: Successful build after gcc: 2 commits discards 80c2b8b9c 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 3c2b7164f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 0872edfe6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 76b1a8268 39: onsuccess: 1: Successful build after gcc: 2 commits discards 71284b1ca 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1067f8d56 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5bef3afe2 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7320212a0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 55f85a64a 34: onsuccess: 1: Successful build after gcc: 3 commits discards 66adcbc76 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards bc9c3f88d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards ca117810d 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards abaa879c5 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 12086263c 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 04922eac4 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards db8599848 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 694d6e641 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards d960e69e7 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2859946ac 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5567efeb5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b6b166250 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ec5dd3bc4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards af4ca2170 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 90e9fb4ef 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 654a578d9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3ee584018 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7b533289f 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d7c069fd 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fe1af4737 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 71fba10be 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9058d8534 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4bb73973f 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5d2fb5adc 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards fc830521f 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 10060cc80 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e2f900861 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bc1fc1ff8 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 38ce50aba 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f5db6037f 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7465676c3 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c5875a60d 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 818201c92 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0f67fca95 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8b76c7fde 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6cc7c1a22 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1026504c7 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a29c18aac 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new eda44fe66 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2712d7b6a 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 01e6e3938 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5193ed429 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a6064e2f6 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 32c74b0b0 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2236cb17e 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8c5700423 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5e86024a6 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 25a73d5f8 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e7063eb68 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 52bb4dd59 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ae8f3d59b 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 59aff2dcf 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new db008e5e2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new c9420d769 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cb96c2bf4 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 7255ea3cc 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b650ad00d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 4397ffc73 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 45d7a55a6 34: onsuccess: 1: Successful build after gcc: 3 commits new 4fe49d9a5 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 25a28f43b 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 818e90bd9 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new de03bf3b2 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c145675fa 39: onsuccess: 1: Successful build after gcc: 2 commits new c9e1f3ad6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 43f4c842e 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0b44c1923 42: onsuccess: 1: Successful build after baseline build: no n [...] new 42ece4c6e 43: onsuccess: 1: Successful build after gcc: 2 commits new 5a0e42385 44: onsuccess: 1: Successful build after linux: 34 commits new 4c49f08f6 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c9607f5f1 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new a60c1a758 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f8bbe16bc 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 826750db4 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 05d990cd5 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 40e8a6746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 192559c1b 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 9150dce74 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new c2930cbfb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new d6a22debc 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 43597fc91 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b9a18d488 57: onsuccess: 1: Successful build after gcc: 7 commits new 2f3793e59 58: onsuccess: 1: Successful build after binutils: 2 commits new 26eb1864b 59: onsuccess: 1: Successful build after glibc: 2 commits new 948aea648 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 9fae3404e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new b0da992dd 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 92aabb69d 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fb1c0c38d 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8023dfd51 65: onsuccess: 1: Successful build after gcc: 4 commits new a3c0d849e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 6b91e4f9f 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 553f6e8f9 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b53781fcf 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new d4ebaa0de 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new ad25a1aeb 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 0177a41f9 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b3bab9d06 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 24f18710d 74: onsuccess: 1: Successful build after linux: 44 commits new 9ed5bd9cc 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new be113203e 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 3700eb112 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 21b0b4874 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5deb93c8c 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new c197bafc0 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 73be7b7eb 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 1bb731cb4 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 80ef7c947 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 74e377a22 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 8710f88e2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new bee4ee6a0 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new ca35406e9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 895338c08 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new d8382c41d 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ded1079cf 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new a26e61489 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new f4ce6d3f7 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 7093248b6 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 49dcdb198 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 0d8ff268a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new e81f6d71e 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ad7a3943c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new cabc41cb6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new a23636e8c 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new b48a4d6c6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 0232a8228 101: onsuccess: #1693: 1: Success after glibc: 14 commits new d799c6dde 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 9898da452 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 713c91de0 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 8ed1b6c33 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 68c6bc796 106: onsuccess: #1699: 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 (f0a9d2fbe) \ 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 1720 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29736 -> 29876 bytes 04-build_abe-stage1/console.log.xz | Bin 90636 -> 90268 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8304 bytes 07-build_abe-glibc/console.log.xz | Bin 233660 -> 234416 bytes 08-build_abe-stage2/console.log.xz | Bin 223376 -> 222976 bytes 09-build_abe-gdb/console.log.xz | Bin 37064 -> 37016 bytes 10-build_abe-qemu/console.log.xz | Bin 31704 -> 31872 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3900 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2580 -> 2436 bytes 13-check_regression/console.log.xz | Bin 4272 -> 5252 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 | 9 +- 13-check_regression/results.compare2 | 41 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 2656280 -> 2658780 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 2194632 -> 2230276 bytes sumfiles/gcc.sum | 2110 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 877180 -> 882176 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201108 -> 201292 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422556 -> 429104 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1268 insertions(+), 1151 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