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 22cde9678 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards 4693dec8a 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards e4fce6650 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 031e4a645 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards afc43149d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 4fd7231b7 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards c3c1cc7e2 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 413a33b95 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 96643cede 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 508eb97fd 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 2ce16402d 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 209a6e825 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards fd359246c 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 8bb5915de 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 286b3a818 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 8a7838888 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards f5e1c222f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards c7e9ea745 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 794b8c36e 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards f79627bea 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards e6bfa91c2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards a7afa17d1 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards d8158e1ae 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 2c3fdd83a 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards d9d29ba05 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards fb9287ca3 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards b3f4d22d0 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 27d07227f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 295ecd9cd 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 2479ded5d 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards e9cd8881e 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards f1c88847f 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 1030c666a 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards de988b29b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 8ba1a429c 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 8bd35a078 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards a4310865a 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 88287b657 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards fab0441a9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 71112db4d 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 9614535c1 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards aabf084d1 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ef819d1c8 74: onsuccess: 1: Successful build after linux: 44 commits discards 2b928f9b7 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards f2624098b 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 06b8f5407 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards f7116effe 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards d8239d019 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards f4cfbde4e 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards aaeea1b37 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a05ec0b8e 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 5d0b57414 65: onsuccess: 1: Successful build after gcc: 4 commits discards f3be12136 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 274e0abfe 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 06fb3435f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 05ab6deb3 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards f205147ab 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards d591bbb6e 59: onsuccess: 1: Successful build after glibc: 2 commits discards f86ce0ddc 58: onsuccess: 1: Successful build after binutils: 2 commits discards 1c205420b 57: onsuccess: 1: Successful build after gcc: 7 commits discards e95826e3b 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 726556444 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 00b896f85 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 33e6d7e76 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards b735aee8d 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards fd1da8a8d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 34a576b3e 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 34187088c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 91e3de6f2 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 2e48ad7ae 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 30bce21d6 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 7876718be 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 11c8948b3 44: onsuccess: 1: Successful build after linux: 34 commits discards acd27d260 43: onsuccess: 1: Successful build after gcc: 2 commits discards 6e3ddee65 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 4818e444e 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 965a6603e 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 072cc48ac 39: onsuccess: 1: Successful build after gcc: 2 commits discards 3765bd27e 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 14c802a55 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 690328bf9 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b1fd1a924 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bdab61e30 34: onsuccess: 1: Successful build after gcc: 3 commits discards 1f4563fd9 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b4c5948c1 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 271026865 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 85b7f6490 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards a7e3b6128 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f39b15d74 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards ccad3b1ea 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 4e7c335fa 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 009a97ee9 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 2be92279a 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 182f64879 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 98b2b03c8 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 995e3856c 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9b1d1b78c 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 073458d85 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards f9b709198 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 660e281be 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards def194b0e 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f0fe18dbb 16: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 56938f396 17: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 9d9a62b50 18: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 0ddd688cd 19: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 64b7c08db 20: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new bb1580caa 21: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 60ccc6d0b 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new df9fcd351 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 73f696291 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 6f1705793 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 612301f77 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new f892f4bec 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new f04c2546d 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 82eb75f1d 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ff45e3063 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 5953d169b 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cd0ad42f4 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 99db62b9a 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7a146f260 34: onsuccess: 1: Successful build after gcc: 3 commits new 2ac8ae3d9 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 1c6406344 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 24b7e5e09 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cfb55610a 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e236d677c 39: onsuccess: 1: Successful build after gcc: 2 commits new 9754dfaa1 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c5603f6a6 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5a6415405 42: onsuccess: 1: Successful build after baseline build: no n [...] new 9bc7f7a6f 43: onsuccess: 1: Successful build after gcc: 2 commits new 6d9b680a3 44: onsuccess: 1: Successful build after linux: 34 commits new 48a25e7c2 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5b471d52b 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 59ea8af1e 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 33a9dd23d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new e86f15bb9 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 635bad355 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3a421b6e4 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c473e7cdc 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new aecdbf064 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new e407ea976 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 43049cb4c 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 529143503 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new cff3d5f2a 57: onsuccess: 1: Successful build after gcc: 7 commits new c2c6da933 58: onsuccess: 1: Successful build after binutils: 2 commits new cb8d7c502 59: onsuccess: 1: Successful build after glibc: 2 commits new 33dd0a0c0 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 8c16362f3 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 49e75038d 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new b76f299a5 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new caf5fe2cb 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 0d8bbdbfb 65: onsuccess: 1: Successful build after gcc: 4 commits new e12df9392 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d3208856f 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd0f1ed12 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d889bb791 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new ade457bcd 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new 6048bbed2 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 161f0b0fe 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a93dfd3a4 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 6af7a6315 74: onsuccess: 1: Successful build after linux: 44 commits new 9914f614d 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 5e7a232c4 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 294bd4eef 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 688a30a9d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d6d0c8d6b 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 4cd92e531 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 358b9d694 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 62777da00 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new d07739e82 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 55ff771f8 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 2ef0a0b17 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 1f1c000ba 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 0758b62ed 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 16d045c1f 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new aa84558d0 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 46300ab7d 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d6bfd23fa 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new cdebd7243 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 0703c62a5 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9cc2a212c 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new b1873dc42 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 8ca457749 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ca377744b 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 0387bccd1 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 89b26baea 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new 44233cc7d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 20126e09a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 8e85ee96d 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new b1a22d329 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new fdf846826 104: onsuccess: #1697: 1: Success after gcc: 4 commits new f0797fe2d 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 575ca6dca 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 7312d445c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new d764dd4c4 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new b6ae48c3a 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 834b6277b 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 08bc6a718 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 8f039ea1a 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 701e26035 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new d9d565a8a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new 304fcf8a8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new c040422e7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 2372f0fa8 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...]

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 (22cde9678) \ 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 1752 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30492 -> 29904 bytes 04-build_abe-stage1/console.log.xz | Bin 91148 -> 90852 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8572 -> 8592 bytes 07-build_abe-glibc/console.log.xz | Bin 233956 -> 234112 bytes 08-build_abe-stage2/console.log.xz | Bin 224564 -> 223148 bytes 09-build_abe-gdb/console.log.xz | Bin 37412 -> 37108 bytes 10-build_abe-qemu/console.log.xz | Bin 31924 -> 31488 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3916 -> 3904 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2664 -> 2444 bytes 13-check_regression/console.log.xz | Bin 6124 -> 4908 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 72 +- 13-check_regression/results.compare | 31 +- 13-check_regression/results.compare2 | 30 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 74 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 - sumfiles/g++.log.xz | Bin 2659592 -> 2686320 bytes sumfiles/g++.sum | 106 +- sumfiles/gcc.log.xz | Bin 2236176 -> 2197952 bytes sumfiles/gcc.sum | 2612 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 879836 -> 891892 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201056 -> 201156 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 423440 -> 421040 bytes sumfiles/libstdc++.sum | 14 +- 44 files changed, 1504 insertions(+), 1676 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions