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 4295f79e55 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards c64c22092d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 0693167dcc 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 5c1c8749fa 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 911cf1e730 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards d6e23de3b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 9673b4cc42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f5f564fb9d 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards bbfb5000fa 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 6285072f5c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 0ba3f4642e 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 83ea0d70d6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards d7db83f7f7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 5f91c72652 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ed9e5bd445 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 23173bc951 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 179c13da99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards f102c71c4b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 5d6bfd2170 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 7a5737bed3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 2e74e36ed4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 944337a501 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 1352b2982d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards ecba37b355 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 36ea96096f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 28167d145b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 464be1435f 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 66682a5ff4 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 41b9ee528a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9bae6315e6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 17d6d23b8f 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards c5ebc13203 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 9be404302d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 3cd06bb21a 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 501ecb0583 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 53950fe463 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 7197b48fdb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3241b3011a 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3904cd9199 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards 913056ecb7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 67b22e9815 74: onsuccess: 1: Successful build after linux: 44 commits discards 07d8f0077b 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f925c969a2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d52b457973 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 196f77858c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 7c6e19a12f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 2b3791ce55 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37d0ae7cdb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b707dcaf7e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b42214a025 65: onsuccess: 1: Successful build after gcc: 4 commits discards 6692fd55c3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 25df9e05b2 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1c040fdc30 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 3bd541f569 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 3ea7cb212e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 31d0cb7495 59: onsuccess: 1: Successful build after glibc: 2 commits discards febc09e666 58: onsuccess: 1: Successful build after binutils: 2 commits discards cd9a5dde46 57: onsuccess: 1: Successful build after gcc: 7 commits discards 6acb25b3b1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b0616415b0 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c26ec39f6 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 99efa48a61 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 754affe219 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards bc0ee367a1 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards fc9fb03bcc 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards beac5ff029 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 194c676161 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards e30d41c173 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 36e067856a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 8f143a9d02 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 357bcc321a 44: onsuccess: 1: Successful build after linux: 34 commits discards d553567c8d 43: onsuccess: 1: Successful build after gcc: 2 commits discards 39209c36b4 42: onsuccess: 1: Successful build after baseline build: no [...] discards 411891ee81 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6da93313bb 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8c2a772e97 39: onsuccess: 1: Successful build after gcc: 2 commits discards 3cf3c450d8 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4b66e64b86 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards d3c8b43079 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 77dd8e85c0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 498b1348a1 34: onsuccess: 1: Successful build after gcc: 3 commits discards 63b7405b6d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7b66b72009 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 12d156e026 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards c3a92baafe 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards f347b0c8b0 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards eb121694e2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards c1b87eb841 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7f20773363 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 914dd2871f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a76d46e59a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 513c4ac70e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d414b4cf9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9186d1ce2c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bbd0ad04ab 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 900e54b311 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards da56d38615 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 92446d3c90 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4b7894a323 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1055b92185 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0d27672b2a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d0b2104d5e 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c37f6dd739 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c1990a215b 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6fa90aaea6 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 885365f013 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dbcc7e1b04 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bcb4b33d98 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c348cff7a7 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ea0a43e52d 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1d538682a1 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9cad606403 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dff22a8816 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ddd7d5328d 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 37fd1ed701 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53560cddd2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e3e6afbd28 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 41223042b8 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new a898b3866b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 2ff0c5658a 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new ad6ef1572a 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0e4a21757c 34: onsuccess: 1: Successful build after gcc: 3 commits new c139193a7c 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 1f280f8e14 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cf21f7e836 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 46e8555097 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 961b4e4771 39: onsuccess: 1: Successful build after gcc: 2 commits new dde7048ea1 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b63a42b384 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e35e72af2b 42: onsuccess: 1: Successful build after baseline build: no [...] new b85a38097c 43: onsuccess: 1: Successful build after gcc: 2 commits new a1263b2ab5 44: onsuccess: 1: Successful build after linux: 34 commits new 55eec78d72 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 37091e3372 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 5b24dd1667 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 14a677087c 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new e3cc5ab46e 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6c0e1c5715 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f3a56eac37 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 9030bb9ec1 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new c1abade936 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new f85031977a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new f5423acd8a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3c236f934f 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 52429cad71 57: onsuccess: 1: Successful build after gcc: 7 commits new 73014c8f01 58: onsuccess: 1: Successful build after binutils: 2 commits new 36f7d44f6a 59: onsuccess: 1: Successful build after glibc: 2 commits new cd847ce8e9 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new ed9271ca96 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new e50ed1f887 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new c690072421 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0c07987928 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 68b7657cea 65: onsuccess: 1: Successful build after gcc: 4 commits new a20e4cbb95 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 528dec24fb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 33e9b715df 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 05dce66314 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new f9e416aab1 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new e6d7dd6d8d 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 257656f603 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4eca1653c8 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e84c5ee539 74: onsuccess: 1: Successful build after linux: 44 commits new a8607140ae 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cae37149f4 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 633a76f092 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new edf4420d0d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 6dc9581d31 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new a32035bac2 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 173cafbcce 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 7932f56e82 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d2e83efa2f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 97d60c5edf 84: onsuccess: 1: Success after gcc/glibc: 9 commits new b3f8a9c342 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 8b51e4710a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2eb5e1a2d2 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 09069ef13e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new a6080c82bd 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 56e258142f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new abeecc1480 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new c23a748906 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 030c257708 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 17dbba7a4a 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new ced4d781b3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 4ea3858454 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ada44696e3 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 47e7a1003c 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 358ae9079e 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new d297d07d69 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 39b548c971 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ea4ee4c261 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 204465d41e 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new c89b44bc43 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f075624441 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8169e93820 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new e7d901c2b5 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new e9677b8b07 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 35943c8bd5 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 499cc9eb9c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 99961427b8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 2bdc20b1d3 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 0058ae816e 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 60c696e45c 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new 8951cb1211 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...]

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 (4295f79e55) \ 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 1688 -> 1884 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 30628 -> 29952 bytes 04-build_abe-stage1/console.log.xz | Bin 91212 -> 90564 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 8600 bytes 07-build_abe-glibc/console.log.xz | Bin 234380 -> 233832 bytes 08-build_abe-stage2/console.log.xz | Bin 223076 -> 222932 bytes 09-build_abe-gdb/console.log.xz | Bin 37664 -> 37220 bytes 10-build_abe-qemu/console.log.xz | Bin 31488 -> 30924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2644 bytes 13-check_regression/console.log.xz | Bin 4900 -> 5632 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 11 +- 13-check_regression/mail-body.txt | 80 +- 13-check_regression/results.compare | 50 +- 13-check_regression/results.compare2 | 75 +- 13-check_regression/results.regressions | 50 +- 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 | 82 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 50 +- sumfiles/g++.log.xz | Bin 2679412 -> 2678388 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2204080 -> 2207716 bytes sumfiles/gcc.sum | 2613 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 880428 -> 882024 bytes sumfiles/gfortran.sum | 79 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201120 -> 201344 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 421828 -> 421944 bytes sumfiles/libstdc++.sum | 14 +- 43 files changed, 1790 insertions(+), 1580 deletions(-)