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 355e53293 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards b5897afa8 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 8f438942e 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 64a0c9043 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e79a0280f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 99813c136 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards f99f636bf 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 85486502c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 4557a80e0 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards d30cdf24a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 974beb9e1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards c306296b2 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards cbd945ccf 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 6cca1fc61 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 967c29c14 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards db9f6efca 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards f8bd5478c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 427175eac 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 61b9c3fd1 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 47da9a3b0 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards bd291c65e 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ed33d02ad 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards d476329e2 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 5ebb5a84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 8a1f84b98 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards ec5dfbd66 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 61d2f76c4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3380bc01c 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards fa7fcab94 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 49f84d072 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b14d2c676 74: onsuccess: 1: Successful build after linux: 44 commits discards dba325a11 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 9fb16a636 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 91b4561f6 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 5c7d2140a 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 5f08983c3 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 039e8a334 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1dd647693 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 024d382f2 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a3b4ff99f 65: onsuccess: 1: Successful build after gcc: 4 commits discards c9cf76439 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1c43efaa2 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d7c0807bd 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 8f24d13ee 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 74bbe6f5f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 8a55d4d7d 59: onsuccess: 1: Successful build after glibc: 2 commits discards 6b858086a 58: onsuccess: 1: Successful build after binutils: 2 commits discards 7c8011495 57: onsuccess: 1: Successful build after gcc: 7 commits discards 3e775270b 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 805dd4b54 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 38b08df35 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 134965146 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 463e37143 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards b97175acf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards b63df51fe 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1b384883b 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7520c904a 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards e89dde60c 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2e99ce5e9 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards e4edaa215 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 45d25b40e 44: onsuccess: 1: Successful build after linux: 34 commits discards c4f2493c5 43: onsuccess: 1: Successful build after gcc: 2 commits discards b059f6bb8 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 777a6e8fa 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7247b3934 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ffd6ee2f1 39: onsuccess: 1: Successful build after gcc: 2 commits discards 2fff71aac 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2619c4c39 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 73a832a73 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9f4a4b225 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c8c54557d 34: onsuccess: 1: Successful build after gcc: 3 commits discards 0a131af09 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ee10c44b5 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 5f22387c1 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a74402856 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 6ff172cce 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ede47a1bd 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards c09aa71bd 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 87e53f2f7 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ec54a6f85 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 57d13eeb5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1c0034631 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 35d95f629 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 7be95817c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2dd167798 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b6958ecaf 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 5b42fe53b 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dab579f07 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 69a4757ff 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2609a8393 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bc83519f0 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 3921d8682 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 233320195 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ca9a5cdd8 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 125ad721a 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 00ea325bc 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6280aaa9e 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 75dde4ec7 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards e9ed7ecac 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 85caa0ff9 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 8e148508b 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 02952b270 4: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 38ce50aba 5: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bc1fc1ff8 6: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new e2f900861 7: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 10060cc80 8: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fc830521f 9: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5d2fb5adc 10: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4bb73973f 11: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9058d8534 12: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 71fba10be 13: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fe1af4737 14: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 1d7c069fd 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 7b533289f 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 3ee584018 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 654a578d9 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 90e9fb4ef 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new af4ca2170 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ec5dd3bc4 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b6b166250 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5567efeb5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2859946ac 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d960e69e7 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 694d6e641 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new db8599848 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 04922eac4 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 12086263c 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new abaa879c5 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new ca117810d 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new bc9c3f88d 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 66adcbc76 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 55f85a64a 34: onsuccess: 1: Successful build after gcc: 3 commits new 7320212a0 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 5bef3afe2 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1067f8d56 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 71284b1ca 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 76b1a8268 39: onsuccess: 1: Successful build after gcc: 2 commits new 0872edfe6 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3c2b7164f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 80c2b8b9c 42: onsuccess: 1: Successful build after baseline build: no n [...] new 2efb1cb0d 43: onsuccess: 1: Successful build after gcc: 2 commits new a5a8d439e 44: onsuccess: 1: Successful build after linux: 34 commits new 49ca90bac 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 106028cbe 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new f7a9705b4 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 989a4c0d5 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 5a9c33c33 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 142c74349 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cc44e400d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e8a34802f 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 4494a3329 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new a659d827a 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 7a16d6512 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 38d62408c 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8814ce850 57: onsuccess: 1: Successful build after gcc: 7 commits new d4a318a89 58: onsuccess: 1: Successful build after binutils: 2 commits new 5a04a3e13 59: onsuccess: 1: Successful build after glibc: 2 commits new f2e221c2f 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new d434f299f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 516d6f989 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 8438c9efe 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ceb020f6a 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 983b8704e 65: onsuccess: 1: Successful build after gcc: 4 commits new 2b7ac22a3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 2ca9d87fc 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8a66b7e41 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aeb037162 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new e7061b86a 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 0698d8a49 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 6956e0c7c 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 26850f782 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new e713ea4f3 74: onsuccess: 1: Successful build after linux: 44 commits new 883a04577 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5c2a5d0a0 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new f9189ea2b 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7c77c41e4 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f7aeb4bcd 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new ada22226c 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 3b0df8fb5 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 169f751b0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new ec6bf14ec 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 4d74dd15b 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 9a523cace 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 7f58407c5 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 6eea6d8cd 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new b6ea361a3 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 6fbbad08c 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 9fae71028 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 22f50b40f 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new be905656a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 4147303ca 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 911863623 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 3d7f7c73f 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 334c1d440 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 8954a6670 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 38193003d 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new efdd1ba21 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 28845bfe0 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 4e1dc7e41 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 656f9a8b7 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 6f5f644f9 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new d9acabf6d 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f0a9d2fbe 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...]
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 (355e53293) \ 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 1700 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29936 -> 29736 bytes 04-build_abe-stage1/console.log.xz | Bin 90604 -> 90636 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8700 bytes 07-build_abe-glibc/console.log.xz | Bin 234112 -> 233660 bytes 08-build_abe-stage2/console.log.xz | Bin 223708 -> 223376 bytes 09-build_abe-gdb/console.log.xz | Bin 37100 -> 37064 bytes 10-build_abe-qemu/console.log.xz | Bin 31264 -> 31704 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2584 -> 2580 bytes 13-check_regression/console.log.xz | Bin 4208 -> 4272 bytes 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 35 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 22 +- sumfiles/g++.log.xz | Bin 2648552 -> 2656280 bytes sumfiles/g++.sum | 8 +- sumfiles/gcc.log.xz | Bin 2229700 -> 2194632 bytes sumfiles/gcc.sum | 2020 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 882076 -> 877180 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201196 -> 201108 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 418400 -> 422556 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 1101 insertions(+), 1086 deletions(-)