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 3086a162c8 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards f7c837b9af 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards b9dd1d08ee 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 2d264280b3 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards c7e28edc9a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards fc1f51fd4b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards da03a8dd69 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 0c04283f5b 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 7e7459464e 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 0e6b0a8bef 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 96866fb516 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 2974d223db 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards d87ac6d9cd 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 89d9392063 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 2b55511cc8 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 4401604427 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards ad755c9925 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards dbffd9297f 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 65ea89aa34 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards d06df4a3b0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 66a25430e7 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 4b0b47775f 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 66461f32d5 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards cf8405832c 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 50ba667c47 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards dac8a23b4c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards e1ed1cdacf 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 2793f6b0b4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards dc29b3727d 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards f9588534a0 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards dd3b45f29d 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 945df38787 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a92c27a273 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards b28fcd4e34 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 5fde20a104 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards 64177f9b97 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3061d0d956 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards dc3c53e1c1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards af6e82a0fc 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b65342b63e 74: onsuccess: 1: Successful build after linux: 44 commits discards 283c253fef 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 96cea62da4 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 41c7d48649 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards c421ba37f0 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards edab5e8faa 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards ea30411463 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5a1921a3ee 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6b329a0e8a 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f34ae27587 65: onsuccess: 1: Successful build after gcc: 4 commits discards 8cdc37360e 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 260f97384a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f4c5072867 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 38966550ee 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards d6672f4730 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9095ac84a4 59: onsuccess: 1: Successful build after glibc: 2 commits discards 8eca1a533e 58: onsuccess: 1: Successful build after binutils: 2 commits discards 78ca191fad 57: onsuccess: 1: Successful build after gcc: 7 commits discards 27c6de0eca 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7b705db69c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards af8b1494cb 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 39490e72aa 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 47760fcb61 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 5df98d938d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ff57b5af51 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 12dcaae15e 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 3870f3f5ca 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 73465146fa 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c6fe507574 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 14771cb8c2 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b10599e46d 44: onsuccess: 1: Successful build after linux: 34 commits discards 4a352f94c3 43: onsuccess: 1: Successful build after gcc: 2 commits discards fd47015e02 42: onsuccess: 1: Successful build after baseline build: no [...] discards 79b589218a 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 05b3c2023a 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4135e7ecf4 39: onsuccess: 1: Successful build after gcc: 2 commits discards 3588d55f70 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80e4c8efa1 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 86f71614bf 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5e20a0aab0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b4cd729dff 34: onsuccess: 1: Successful build after gcc: 3 commits discards 7f85a07503 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6f89f2ac86 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 5c132cdff4 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a5000258a7 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 1edae6fed5 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5369d3f813 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8882953cde 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f3fc8cd403 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5ac281dc36 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4f605c4c51 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3124324417 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 050d91a5a9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a5b026a0f5 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ac86660e06 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1f0306e314 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5996e6c335 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5fd05823b0 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3349f07ac1 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9635768f28 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f9463dbc5d 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 63ebf0ecd5 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b6ae6a4e98 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0d27672b2a 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1055b92185 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4b7894a323 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 92446d3c90 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new da56d38615 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 900e54b311 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bbd0ad04ab 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9186d1ce2c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1d414b4cf9 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 513c4ac70e 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a76d46e59a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 914dd2871f 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7f20773363 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c1b87eb841 27: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new eb121694e2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new f347b0c8b0 29: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c3a92baafe 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 12d156e026 31: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7b66b72009 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 63b7405b6d 33: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 498b1348a1 34: onsuccess: 1: Successful build after gcc: 3 commits new 77dd8e85c0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new d3c8b43079 36: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4b66e64b86 37: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3cf3c450d8 38: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8c2a772e97 39: onsuccess: 1: Successful build after gcc: 2 commits new 6da93313bb 40: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 411891ee81 41: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 39209c36b4 42: onsuccess: 1: Successful build after baseline build: no [...] new d553567c8d 43: onsuccess: 1: Successful build after gcc: 2 commits new 357bcc321a 44: onsuccess: 1: Successful build after linux: 34 commits new 8f143a9d02 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 36e067856a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new e30d41c173 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 194c676161 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new beac5ff029 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new fc9fb03bcc 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bc0ee367a1 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 754affe219 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 99efa48a61 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 5c26ec39f6 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b0616415b0 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6acb25b3b1 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd9a5dde46 57: onsuccess: 1: Successful build after gcc: 7 commits new febc09e666 58: onsuccess: 1: Successful build after binutils: 2 commits new 31d0cb7495 59: onsuccess: 1: Successful build after glibc: 2 commits new 3ea7cb212e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 3bd541f569 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1c040fdc30 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 25df9e05b2 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6692fd55c3 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b42214a025 65: onsuccess: 1: Successful build after gcc: 4 commits new b707dcaf7e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 37d0ae7cdb 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2b3791ce55 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7c6e19a12f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 196f77858c 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new d52b457973 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new f925c969a2 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 07d8f0077b 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 67b22e9815 74: onsuccess: 1: Successful build after linux: 44 commits new 913056ecb7 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3904cd9199 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 3241b3011a 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 7197b48fdb 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 53950fe463 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 501ecb0583 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 3cd06bb21a 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 9be404302d 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new c5ebc13203 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 17d6d23b8f 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 9bae6315e6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 41b9ee528a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 66682a5ff4 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 464be1435f 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 28167d145b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 36ea96096f 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ecba37b355 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 1352b2982d 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 944337a501 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 2e74e36ed4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new 7a5737bed3 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 5d6bfd2170 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f102c71c4b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 179c13da99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 23173bc951 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new ed9e5bd445 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 5f91c72652 101: onsuccess: #1693: 1: Success after glibc: 14 commits new d7db83f7f7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 83ea0d70d6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 0ba3f4642e 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 6285072f5c 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new bbfb5000fa 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f5f564fb9d 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 9673b4cc42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new d6e23de3b0 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 911cf1e730 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 5c1c8749fa 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 0693167dcc 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new c64c22092d 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 4295f79e55 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...]

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 (3086a162c8) \ 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 1692 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30396 -> 30628 bytes 04-build_abe-stage1/console.log.xz | Bin 92344 -> 91212 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 235496 -> 234380 bytes 08-build_abe-stage2/console.log.xz | Bin 226924 -> 223076 bytes 09-build_abe-gdb/console.log.xz | Bin 37960 -> 37664 bytes 10-build_abe-qemu/console.log.xz | Bin 31136 -> 31488 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3872 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2464 -> 2436 bytes 13-check_regression/console.log.xz | Bin 6340 -> 4900 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 62 +- 13-check_regression/results.compare | 30 +- 13-check_regression/results.compare2 | 58 +- 13-check_regression/results.regressions | 30 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 64 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 30 +- sumfiles/g++.log.xz | Bin 2663468 -> 2679412 bytes sumfiles/g++.sum | 16 +- sumfiles/gcc.log.xz | Bin 2235456 -> 2204080 bytes sumfiles/gcc.sum | 2094 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 879044 -> 880428 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201100 -> 201120 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422724 -> 421828 bytes sumfiles/libstdc++.sum | 8 +- 41 files changed, 1192 insertions(+), 1322 deletions(-)