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 cc17bcb0d 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] discards 51e27da21 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] discards ee0bfe16f 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] discards 6a9667b0e 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] discards 160888ce2 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] discards 2c2849f0d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards febff4038 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] discards 57ea2ffd6 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] discards d7a5b89cf 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits discards dc3b375bc 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] discards 42a4c7a6f 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] discards 78b0b9b1c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] discards 4481c8678 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] discards fc8b989eb 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards f53f2e205 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cf72f252b 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 6eae883c3 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] discards 5c591ccc1 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] discards abfc5ddc2 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] discards 2a5c3272d 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4f758614d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] discards 7f5f6d7ec 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] discards 2432e9aab 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e714c77b5 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] discards ca3870ab0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] discards c8c3a7090 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] discards 478c74a71 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] discards 8aa956030 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 6e6d1d45c 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] discards c3e6cf025 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] discards 795402db8 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 5d3900b38 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] discards af27b2637 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 632b153f1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards b8b80364e 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards aaa181510 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 8ca402148 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 8dc347515 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 93921b1ea 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards e52dc2e2d 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards a9ab0dd4c 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 6ec0bb130 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 0270fc55e 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 38ff74b06 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] discards 068c4e173 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits discards 74588c6b9 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards bcf0fbe40 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 34222d04d 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits discards 09359b31d 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards af3997333 74: onsuccess: 1: Successful build after linux: 44 commits discards 817d7950c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 5dac47b73 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards ba9b43904 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits discards 398aea4a3 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] discards 7bfaf003c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits discards 853253fcb 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e6148b427 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 3202be04d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 330a21264 65: onsuccess: 1: Successful build after gcc: 4 commits discards a931cd649 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards f0e5deb09 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 442da472f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] discards 6f309f9dc 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 35531e783 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 425ce3ea3 59: onsuccess: 1: Successful build after glibc: 2 commits discards b8ffa14ce 58: onsuccess: 1: Successful build after binutils: 2 commits discards 58e3c1bc9 57: onsuccess: 1: Successful build after gcc: 7 commits discards c7ceed897 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e536191c1 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards d8f5573c2 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 50fe527ce 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] discards d07f7405e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits discards a344f16b4 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d336dba99 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a69be3069 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards d694ab6b8 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits discards 0e7e2f26a 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1fd08dde7 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 3a3a4ec6e 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 1b79f6fc1 44: onsuccess: 1: Successful build after linux: 34 commits discards 4e9a9e098 43: onsuccess: 1: Successful build after gcc: 2 commits discards 94ad81bf8 42: onsuccess: 1: Successful build after baseline build: no n [...] discards fe224d46f 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 016c0e8fb 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 618032b17 39: onsuccess: 1: Successful build after gcc: 2 commits discards 8c32cee33 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 98803be80 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a874e1b13 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 545b32d17 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards a088ecc08 34: onsuccess: 1: Successful build after gcc: 3 commits discards ce49020bb 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards dfb9ab794 32: onsuccess: 1: Successful build after gcc/linux: 17 commits discards 146725e3a 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards 8d13d7625 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits discards baf75111b 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 7aae42b72 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] discards 65dca3e12 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] discards c1bca36e0 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards 94d1d7a46 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards b0267f0f5 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 discards c0f842d8b 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 10bf4dfa5 23: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 400806b5f 24: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new a1b3e7204 25: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 2b9f8f8c8 26: onsuccess: binutils-gcc-linux-glibc-gdb-qemu: 1 new 5ef301488 27: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 32276625e 28: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 07984f40f 29: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2f873fa46 30: onsuccess: 1: Successful build after gcc/qemu: 3 commits new df4861eef 31: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new b346af96e 32: onsuccess: 1: Successful build after gcc/linux: 17 commits new 0005672bd 33: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 57b66db3d 34: onsuccess: 1: Successful build after gcc: 3 commits new b118770ed 35: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ee58f11ed 36: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 33c873156 37: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new 02182fecf 38: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new efb64e088 39: onsuccess: 1: Successful build after gcc: 2 commits new a6b5c4e72 40: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 2636640f3 41: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a8d9133b8 42: onsuccess: 1: Successful build after baseline build: no n [...] new 399f5b106 43: onsuccess: 1: Successful build after gcc: 2 commits new 7ad547a5b 44: onsuccess: 1: Successful build after linux: 34 commits new 785a12f70 45: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 06a3a6a2a 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new a3af03175 47: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 671ff536d 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 commits new 4c4f0ac82 49: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new ecb16f14b 50: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd7a2bf2e 51: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new c3f3e6c08 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 commits new f23f5c1c5 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 11 [...] new fea5c7955 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b99573bfd 55: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3f946d6c5 56: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 17eec5513 57: onsuccess: 1: Successful build after gcc: 7 commits new 7c1578770 58: onsuccess: 1: Successful build after binutils: 2 commits new e719a90bf 59: onsuccess: 1: Successful build after glibc: 2 commits new ee1e6db7d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 2a6bf4391 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qem [...] new 5b99bef05 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 23 [...] new 2c0f53d65 63: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 01e2800c2 64: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new c6932390a 65: onsuccess: 1: Successful build after gcc: 4 commits new cc16f96b3 66: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new dc5173138 67: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dd15e0c06 68: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 634d523c1 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 commits new f82c035e6 70: onsuccess: 1: Successful build after gcc: Require fgraphi [...] new c7ea99df3 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 commits new 30b3196b1 72: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 33acda8e4 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new a54224135 74: onsuccess: 1: Successful build after linux: 44 commits new 4898ced99 75: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e36b4ff52 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 commits new 929e5d238 77: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 262023bd2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/g [...] new cd5ad136c 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 commits new c28d77d88 80: onsuccess: 1: Successful build after gcc: libsanitizer: e [...] new 7bc67ea73 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new f879448ca 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new e6717fd33 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 2b7ff7148 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 006281681 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 41331744a 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 215edec3a 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 1c8216536 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 251539605 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new d7a79745a 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new c912562c2 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 7bd2195f5 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gdb [...] new 0a681be15 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9e04678d0 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gdb [...] new b350273bf 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gdb [...] new fb7c9c1a5 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 80d01fc73 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gdb [...] new 8c4d20c10 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gdb [...] new 3caa2c447 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gdb [...] new c8bf6a03c 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/gd [...] new dd433b442 101: onsuccess: #1693: 1: Success after glibc: 14 commits new b693ec556 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/gl [...] new 6e96051c6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/gd [...] new 8de2316ca 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 2a25fd9ac 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddeed [...] new f3a5d2551 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/gd [...] new 0ce2c4929 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/gd [...] new 226aadc42 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 03b25f166 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fa5322b39 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 7c52dee1c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/gd [...] new 3c38dacce 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/gl [...] new 6b6de671e 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/gd [...] new 787c0b6ac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: 1 [...] new fca47379d 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 commits new 7005d8bef 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/gl [...] new 1b1685a57 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qemu [...] new fb01ee06b 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 75f39fff4 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/gd [...] new 0a0aa5ee4 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/gd [...] new 5605e65c8 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/gl [...] new 97f8f6190 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/gl [...] new 6ac2284ce 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/gd [...] new 2f260e26c 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 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 (cc17bcb0d) \ 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 1692 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 29980 -> 30032 bytes 04-build_abe-stage1/console.log.xz | Bin 90796 -> 90540 bytes 06-build_abe-linux/console.log.xz | Bin 8844 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 233684 -> 233776 bytes 08-build_abe-stage2/console.log.xz | Bin 222864 -> 223020 bytes 09-build_abe-gdb/console.log.xz | Bin 37112 -> 37228 bytes 10-build_abe-qemu/console.log.xz | Bin 30940 -> 31256 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3852 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2432 -> 2440 bytes 13-check_regression/console.log.xz | Bin 7100 -> 5348 bytes 13-check_regression/results.compare | 14 + 13-check_regression/results.compare2 | 698 +--------- 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- sumfiles/g++.log.xz | Bin 2684376 -> 2651708 bytes sumfiles/g++.sum | 34 +- sumfiles/gcc.log.xz | Bin 2199756 -> 2207648 bytes sumfiles/gcc.sum | 2256 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 882348 -> 879888 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201156 -> 201268 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 419880 -> 426708 bytes sumfiles/libstdc++.sum | 8 +- 36 files changed, 1230 insertions(+), 1894 deletions(-)