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 8951cb121 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 60c696e45 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 0058ae816 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 2bdc20b1d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 99961427b 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards 499cc9eb9 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 35943c8bd 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards e9677b8b0 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards e7d901c2b 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 8169e9382 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards f07562444 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards c89b44bc4 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 204465d41 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards ea4ee4c26 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 39b548c97 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards d297d07d6 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards 358ae9079 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 47e7a1003 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards ada44696e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 4ea385845 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards ced4d781b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 17dbba7a4 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 030c25770 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards c23a74890 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards abeecc148 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 56e258142 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a6080c82b 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 09069ef13 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2eb5e1a2d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 8b51e4710 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards b3f8a9c34 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 97d60c5ed 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards d2e83efa2 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 7932f56e8 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 173cafbcc 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a32035bac 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 6dc9581d3 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards edf4420d0 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 633a76f09 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cae37149f 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards a8607140a 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e84c5ee53 74: onsuccess: 1: Successful build after linux: 44 commits discards 4eca1653c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 257656f60 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e6d7dd6d8 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards f9e416aab 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 05dce6631 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 33e9b715d 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 528dec24f 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a20e4cbb9 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 68b7657ce 65: onsuccess: 1: Successful build after gcc: 4 commits discards 0c0798792 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c69007242 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e50ed1f88 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards ed9271ca9 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards cd847ce8e 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 36f7d44f6 59: onsuccess: 1: Successful build after glibc: 2 commits discards 73014c8f0 58: onsuccess: 1: Successful build after binutils: 2 commits discards 52429cad7 57: onsuccess: 1: Successful build after gcc: 7 commits discards 3c236f934 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f5423acd8 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f85031977 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards c1abade93 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 9030bb9ec 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards f3a56eac3 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6c0e1c571 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e3cc5ab46 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 14a677087 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 5b24dd166 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 37091e337 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 55eec78d7 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a1263b2ab 44: onsuccess: 1: Successful build after linux: 34 commits discards b85a38097 43: onsuccess: 1: Successful build after gcc: 2 commits discards e35e72af2 42: onsuccess: 1: Successful build after baseline build: no n [...] discards b63a42b38 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dde7048ea 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 961b4e477 39: onsuccess: 1: Successful build after gcc: 2 commits discards 46e855509 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards cf21f7e83 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 1f280f8e1 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c139193a7 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 0e4a21757 34: onsuccess: 1: Successful build after gcc: 3 commits discards ad6ef1572 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 2ff0c5658 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards a898b3866 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 41223042b 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards e3e6afbd2 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 53560cddd 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 37fd1ed70 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ddd7d5328 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dff22a881 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9cad60640 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 1d538682a 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards ea0a43e52 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c348cff7a 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards bcb4b33d9 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards dbcc7e1b0 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 885365f01 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 6fa90aaea 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c1990a215 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c37f6dd73 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new fcf74f047 15: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new def194b0e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 660e281be 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f9b709198 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 073458d85 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9b1d1b78c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 995e3856c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 98b2b03c8 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 182f64879 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2be92279a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 009a97ee9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 4e7c335fa 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new ccad3b1ea 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f39b15d74 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new a7e3b6128 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 85b7f6490 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 271026865 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b4c5948c1 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 1f4563fd9 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bdab61e30 34: onsuccess: 1: Successful build after gcc: 3 commits new b1fd1a924 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 690328bf9 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 14c802a55 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 3765bd27e 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 072cc48ac 39: onsuccess: 1: Successful build after gcc: 2 commits new 965a6603e 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 4818e444e 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 6e3ddee65 42: onsuccess: 1: Successful build after baseline build: no n [...] new acd27d260 43: onsuccess: 1: Successful build after gcc: 2 commits new 11c8948b3 44: onsuccess: 1: Successful build after linux: 34 commits new 7876718be 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 30bce21d6 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 2e48ad7ae 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 91e3de6f2 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 34187088c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 34a576b3e 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fd1da8a8d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b735aee8d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 33e6d7e76 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new 00b896f85 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 726556444 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e95826e3b 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1c205420b 57: onsuccess: 1: Successful build after gcc: 7 commits new f86ce0ddc 58: onsuccess: 1: Successful build after binutils: 2 commits new d591bbb6e 59: onsuccess: 1: Successful build after glibc: 2 commits new f205147ab 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 05ab6deb3 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 06fb3435f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 274e0abfe 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f3be12136 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5d0b57414 65: onsuccess: 1: Successful build after gcc: 4 commits new a05ec0b8e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new aaeea1b37 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new f4cfbde4e 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d8239d019 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new f7116effe 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 06b8f5407 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new f2624098b 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2b928f9b7 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new ef819d1c8 74: onsuccess: 1: Successful build after linux: 44 commits new aabf084d1 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9614535c1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 71112db4d 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fab0441a9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 88287b657 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new a4310865a 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 8bd35a078 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 8ba1a429c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new de988b29b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 1030c666a 84: onsuccess: 1: Success after gcc/glibc: 9 commits new f1c88847f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new e9cd8881e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 2479ded5d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 295ecd9cd 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 27d07227f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new b3f4d22d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fb9287ca3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new d9d29ba05 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 2c3fdd83a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d8158e1ae 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new a7afa17d1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new e6bfa91c2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new f79627bea 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 794b8c36e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new c7e9ea745 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new f5e1c222f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 8a7838888 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 286b3a818 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 8bb5915de 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new fd359246c 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 209a6e825 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 2ce16402d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 508eb97fd 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 96643cede 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 413a33b95 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new c3c1cc7e2 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 4fd7231b7 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new afc43149d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 031e4a645 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new e4fce6650 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 4693dec8a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 22cde9678 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...]

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 (8951cb121) \ 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 1884 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 29952 -> 30492 bytes 04-build_abe-stage1/console.log.xz | Bin 90564 -> 91148 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 233832 -> 233956 bytes 08-build_abe-stage2/console.log.xz | Bin 222932 -> 224564 bytes 09-build_abe-gdb/console.log.xz | Bin 37220 -> 37412 bytes 10-build_abe-qemu/console.log.xz | Bin 30924 -> 31924 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2644 -> 2664 bytes 13-check_regression/console.log.xz | Bin 5632 -> 6124 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 11 +- 13-check_regression/mail-body.txt | 94 +- 13-check_regression/results.compare | 46 +- 13-check_regression/results.compare2 | 71 +- 13-check_regression/results.regressions | 46 +- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 96 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +- results | 46 +- sumfiles/g++.log.xz | Bin 2678388 -> 2659592 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2207716 -> 2236176 bytes sumfiles/gcc.sum | 2390 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 882024 -> 879836 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201344 -> 201056 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2672 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421944 -> 423440 bytes sumfiles/libstdc++.sum | 6 +- 45 files changed, 1395 insertions(+), 1553 deletions(-)