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 1e6634ec1 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards b0a20b9d1 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards a75796f09 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards d77b2157d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards 8f44f8465 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 778ef6c1f 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards f68e9fec5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards 1e24a6418 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards 9df9d0c34 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 5eafc6001 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 1ba3d6caa 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 3a103bfd8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards a5d202fd8 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 2e6c8aea7 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards 9f2f64a29 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7708cfb09 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 1cb097d98 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards 1ab24f2e4 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards f5c6f25cc 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards a09d99b55 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 0d243243c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 330f824c2 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 9e9019db4 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards a2dcf7bec 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards 599a1a9a9 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 1e75a4b03 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 6030347ce 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 8fe73609c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards 037f72ed6 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards bc0a67627 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards b64df1916 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards 3e2def9a1 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards d60f2d2a2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ea8a0d046 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 338916d5c 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards fa2606fcc 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 32bc3d8b4 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 2c1eeafee 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards feac2fc63 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards 1b76dc1d0 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 0073238a6 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a62de56b0 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 90abb185a 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 1c7fb87f7 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 5c4a3275d 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 7289a41f9 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 57a21573d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 3dfc5764a 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 49195f235 74: onsuccess: 1: Successful build after linux: 44 commits discards 6ee25a807 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 4e5939d70 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ce708713e 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 904643213 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 675f095bc 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 4d7608b2a 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 059eccacd 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 505a4316b 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ce22f2ced 65: onsuccess: 1: Successful build after gcc: 4 commits discards 10bc9b9b8 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4bee82a48 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b52b9d160 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards fd777f81f 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 9d1dbd2b8 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 453be4d9e 59: onsuccess: 1: Successful build after glibc: 2 commits discards 57265a09e 58: onsuccess: 1: Successful build after binutils: 2 commits discards e458109a1 57: onsuccess: 1: Successful build after gcc: 7 commits discards 0c940ed97 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 162281bbc 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a8a65e0c0 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 567080e40 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards 3c7abe532 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards 86903039d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 3f4d848fd 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f65f2e435 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8c32b0bcc 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards c767289c4 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 214a5b950 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 2a7438e41 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7e72073f5 44: onsuccess: 1: Successful build after linux: 34 commits discards d3bf6e864 43: onsuccess: 1: Successful build after gcc: 2 commits discards aff9593b6 42: onsuccess: 1: Successful build after baseline build: no n [...] discards 260c9806e 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1a50ec567 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 723b5d9d9 39: onsuccess: 1: Successful build after gcc: 2 commits discards 2c0d84ce3 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a64dfebcc 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 95352be29 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f21730a09 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards ff8ca7b2c 34: onsuccess: 1: Successful build after gcc: 3 commits discards 52e2e9dc2 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 63f75c6ec 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 3f7326033 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 6bae8b85c 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards 695bc0b80 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 4aaf013d2 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 22d252f56 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 20bac3262 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 9672090d2 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 453e34e25 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b1781df77 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c196afd92 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new d417405d2 22: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c0f842d8b 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new b0267f0f5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 94d1d7a46 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new c1bca36e0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 65dca3e12 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 7aae42b72 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new baf75111b 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 8d13d7625 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new 146725e3a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dfb9ab794 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new ce49020bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a088ecc08 34: onsuccess: 1: Successful build after gcc: 3 commits new 545b32d17 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new a874e1b13 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 98803be80 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 8c32cee33 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 618032b17 39: onsuccess: 1: Successful build after gcc: 2 commits new 016c0e8fb 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new fe224d46f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 94ad81bf8 42: onsuccess: 1: Successful build after baseline build: no n [...] new 4e9a9e098 43: onsuccess: 1: Successful build after gcc: 2 commits new 1b79f6fc1 44: onsuccess: 1: Successful build after linux: 34 commits new 3a3a4ec6e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1fd08dde7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new 0e7e2f26a 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new d694ab6b8 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new a69be3069 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d336dba99 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a344f16b4 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new d07f7405e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new 50fe527ce 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new d8f5573c2 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new e536191c1 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c7ceed897 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 58e3c1bc9 57: onsuccess: 1: Successful build after gcc: 7 commits new b8ffa14ce 58: onsuccess: 1: Successful build after binutils: 2 commits new 425ce3ea3 59: onsuccess: 1: Successful build after glibc: 2 commits new 35531e783 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 6f309f9dc 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 442da472f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new f0e5deb09 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a931cd649 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 330a21264 65: onsuccess: 1: Successful build after gcc: 4 commits new 3202be04d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new e6148b427 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 853253fcb 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7bfaf003c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new 398aea4a3 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new ba9b43904 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 5dac47b73 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 817d7950c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new af3997333 74: onsuccess: 1: Successful build after linux: 44 commits new 09359b31d 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 34222d04d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new bcf0fbe40 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 74588c6b9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 068c4e173 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new 38ff74b06 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 0270fc55e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 6ec0bb130 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new a9ab0dd4c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new e52dc2e2d 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 93921b1ea 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 8dc347515 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 8ca402148 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new aaa181510 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new b8b80364e 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 632b153f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new af27b2637 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 5d3900b38 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 795402db8 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new c3e6cf025 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new 6e6d1d45c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new 8aa956030 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 478c74a71 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new c8c3a7090 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new ca3870ab0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new e714c77b5 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new 2432e9aab 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 7f5f6d7ec 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 4f758614d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 2a5c3272d 104: onsuccess: #1697: 1: Success after gcc: 4 commits new abfc5ddc2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new 5c591ccc1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 6eae883c3 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new cf72f252b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new f53f2e205 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fc8b989eb 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 4481c8678 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 78b0b9b1c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 42a4c7a6f 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new dc3b375bc 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new d7a5b89cf 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 57ea2ffd6 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new febff4038 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new 2c2849f0d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 160888ce2 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 6a9667b0e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new ee0bfe16f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new 51e27da21 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new cc17bcb0d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...]

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 (1e6634ec1) \ 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 1736 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29996 -> 29980 bytes 04-build_abe-stage1/console.log.xz | Bin 90832 -> 90796 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8952 -> 8844 bytes 07-build_abe-glibc/console.log.xz | Bin 233688 -> 233684 bytes 08-build_abe-stage2/console.log.xz | Bin 224692 -> 222864 bytes 09-build_abe-gdb/console.log.xz | Bin 37204 -> 37112 bytes 10-build_abe-qemu/console.log.xz | Bin 31224 -> 30940 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2752 -> 2432 bytes 13-check_regression/console.log.xz | Bin 7292 -> 7100 bytes 13-check_regression/results.compare | 64 +- 13-check_regression/results.compare2 | 825 +++++++-- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2663288 -> 2684376 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2227740 -> 2199756 bytes sumfiles/gcc.sum | 3284 ++++++++++++++++++++------------- sumfiles/gfortran.log.xz | Bin 882820 -> 882348 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 201120 -> 201156 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 426244 -> 419880 bytes sumfiles/libstdc++.sum | 15 +- 39 files changed, 2840 insertions(+), 1658 deletions(-)