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 572a9511d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 703b5ba3f 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards f343c37c1 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f40d3d1fe 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 78e9234ca 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards a67e40d49 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 423d632b9 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 2fe4b80d6 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5e2b85aff 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 3bfe84bb1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 74cba0ee2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 5c55f26b5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards e65d59fec 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d8a7c5b7e 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 5f9edd828 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards e5d063b5c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 930fdea9a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards d21c3a7b5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9b6be0ed6 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 723f790c1 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 91e14651f 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ce8eb716f 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards fee763086 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards d92e4d0cf 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 5b7f4caea 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 24c24d32d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a533287e2 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9aea2efd3 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 119f191d5 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8ca1fc43a 74: onsuccess: 1: Successful build after linux: 44 commits discards 7293f0e69 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f0dc098a6 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 115de6c42 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 9bff44834 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 8eb679ff5 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 418322a8c 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e7c95c4e3 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 5a4f832a0 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7f59733fe 65: onsuccess: 1: Successful build after gcc: 4 commits discards 57ddab8a7 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 554aa3450 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 271b58c1a 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards b70a3141d 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 08cab8924 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 53fa26449 59: onsuccess: 1: Successful build after glibc: 2 commits discards 088972302 58: onsuccess: 1: Successful build after binutils: 2 commits discards a3a0d7ad0 57: onsuccess: 1: Successful build after gcc: 7 commits discards e7193d373 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 70f67c98b 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b2c1cd69d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 2e16f2d8e 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 44466bbf2 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 742bdf494 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 17320803f 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b8359bf09 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0732d90ee 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 3fa116c0d 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ba19fd793 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 673a5b625 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 8d924d2ad 44: onsuccess: 1: Successful build after linux: 34 commits discards 3416d7be0 43: onsuccess: 1: Successful build after gcc: 2 commits discards fe841ba8e 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 23a23a643 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 82cec5ea6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3698781ce 39: onsuccess: 1: Successful build after gcc: 2 commits discards 7ddbcc615 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7b0858065 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d9d8f85f4 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cb606bf67 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d2c3a527e 34: onsuccess: 1: Successful build after gcc: 3 commits discards 02662aa06 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 93ec0dc3c 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 89515ae64 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8c64d1d1a 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 6284647ae 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9364aa344 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards c0078cec1 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1ab54aa07 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards a0957fd78 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6455d4cd6 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 506c53687 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ca7955754 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 71dfc0984 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c3e6d037a 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 0fed02ad3 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5cd6a5330 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 27fc6bff8 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4264f6899 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1688a5605 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 4f12f92ff 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards be49792c9 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5d254fdad 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9106f8fb3 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ee50988fe 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 832e17817 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ee9bcd19f 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 162dbd4e5 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 69f9384f2 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards eb2e6b9e6 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e22409953 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 22581b48e 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 99c3d74fb 3: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 8e148508b 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 85caa0ff9 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e9ed7ecac 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 75dde4ec7 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6280aaa9e 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 00ea325bc 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 125ad721a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ca9a5cdd8 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 233320195 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3921d8682 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bc83519f0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2609a8393 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 69a4757ff 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new dab579f07 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5b42fe53b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b6958ecaf 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2dd167798 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7be95817c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 35d95f629 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1c0034631 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 57d13eeb5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ec54a6f85 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 87e53f2f7 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c09aa71bd 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ede47a1bd 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6ff172cce 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a74402856 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 5f22387c1 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ee10c44b5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0a131af09 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c8c54557d 34: onsuccess: 1: Successful build after gcc: 3 commits new 9f4a4b225 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 73a832a73 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2619c4c39 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2fff71aac 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ffd6ee2f1 39: onsuccess: 1: Successful build after gcc: 2 commits new 7247b3934 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 777a6e8fa 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b059f6bb8 42: onsuccess: 1: Successful build after baseline build: no n [...] new c4f2493c5 43: onsuccess: 1: Successful build after gcc: 2 commits new 45d25b40e 44: onsuccess: 1: Successful build after linux: 34 commits new e4edaa215 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2e99ce5e9 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new e89dde60c 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7520c904a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 1b384883b 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b63df51fe 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new b97175acf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 463e37143 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 134965146 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 38b08df35 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 805dd4b54 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3e775270b 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7c8011495 57: onsuccess: 1: Successful build after gcc: 7 commits new 6b858086a 58: onsuccess: 1: Successful build after binutils: 2 commits new 8a55d4d7d 59: onsuccess: 1: Successful build after glibc: 2 commits new 74bbe6f5f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 8f24d13ee 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d7c0807bd 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 1c43efaa2 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c9cf76439 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a3b4ff99f 65: onsuccess: 1: Successful build after gcc: 4 commits new 024d382f2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1dd647693 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 039e8a334 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5f08983c3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 5c7d2140a 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 91b4561f6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 9fb16a636 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dba325a11 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new b14d2c676 74: onsuccess: 1: Successful build after linux: 44 commits new 49f84d072 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fa7fcab94 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 3380bc01c 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 61d2f76c4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ec5dfbd66 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 8a1f84b98 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 5ebb5a84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new d476329e2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ed33d02ad 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new bd291c65e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 47da9a3b0 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 61b9c3fd1 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 427175eac 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new f8bd5478c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new db9f6efca 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 967c29c14 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 6cca1fc61 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new cbd945ccf 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new c306296b2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 974beb9e1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new d30cdf24a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 4557a80e0 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 85486502c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new f99f636bf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 99813c136 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new e79a0280f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 64a0c9043 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 8f438942e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new b5897afa8 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 355e53293 104: onsuccess: #1697: 1: Success after gcc: 4 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 (572a9511d) \ 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 1824 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 29824 -> 29936 bytes 04-build_abe-stage1/console.log.xz | Bin 90976 -> 90604 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8620 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 233924 -> 234112 bytes 08-build_abe-stage2/console.log.xz | Bin 223180 -> 223708 bytes 09-build_abe-gdb/console.log.xz | Bin 37132 -> 37100 bytes 10-build_abe-qemu/console.log.xz | Bin 31828 -> 31264 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2436 -> 2584 bytes 13-check_regression/console.log.xz | Bin 4608 -> 4208 bytes 13-check_regression/mail-body.txt | 50 - 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 24 +- 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 52 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2680256 -> 2648552 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2196224 -> 2229700 bytes sumfiles/gcc.sum | 2654 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 878412 -> 882076 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201128 -> 201196 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 422780 -> 418400 bytes sumfiles/libstdc++.sum | 16 +- 37 files changed, 1512 insertions(+), 1604 deletions(-)