This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 2dbae0d63b 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards be9655459f 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] discards 41ebe6951b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards b89d9edd22 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 8e932b6835 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] discards 4bba01e7c2 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards fa1fdaacae 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 0a3b2ab817 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 7219e4079e 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 581e45c32f 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 7cbac490cc 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 2e7b3737e7 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 4cd1e403be 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 32cd61b861 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards e0de1b6d77 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 2b2054e3a6 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] discards 04ada6d4cc 116: onsuccess: #647: 1: Success after linux: 3 commits discards 1e6aeb12aa 115: onsuccess: #645: 1: Success after binutils: 27 commits discards b175c2d883 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards bfc822b064 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 4304dbccfd 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 7bee06f972 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] discards bc6f5986e0 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] discards e2993caf0b 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] discards c2d7b7085e 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] discards 6d0bfad489 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] discards ad515de011 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards a2d74f495a 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] discards d08233613c 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] discards 8777d96d34 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits discards a106341a9b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] discards 2db369ec13 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] discards ccd6ee6b7b 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] discards f0b0b8658f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] discards 51e87b2c3e 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] discards 41999ff7c6 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards cb87c431a6 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] discards 59f5807df8 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 1a59b4e3ef 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 515a419bbc 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 162f8d5335 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] discards 9c2ef71639 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] discards a0f31d8b71 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] discards 30c1fce85e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] discards 849aa217f9 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] discards d99a6836d9 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] discards eb32b20d85 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] discards 5e19683635 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] discards 97450b214f 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] discards 0dd98fdb7a 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] discards 29e1a0ee12 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] discards d73157d3ef 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] discards 9fdcc50072 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] discards f0775ee616 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] discards e75d1d60fa 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] discards 5cf1676726 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] discards 2a8ec092ba 76: onsuccess: #592: 1: Success after linux: 63 commits discards 6ec3a88ea9 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 921bb297cb 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 61491829b3 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] discards e15b332a88 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] discards f304b181b0 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] discards 5c4c276daa 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] discards 6e0a168994 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] discards c318535421 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] discards f319138675 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] discards 69f103fe73 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards c61fc843b4 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] discards 2a067db215 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] discards 97099850f2 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 993018ca09 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] discards 4c89cdcdb4 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] discards 2a413c9c5e 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] discards 1d1d521e92 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] discards fc30157a36 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] discards f0f3e83660 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] discards 531b431641 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] discards 368dfc116b 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] discards cba5fbb5d6 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] discards e9c148850f 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] discards 5034236444 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] discards f9c3da3ecf 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 1187b5ae6f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] discards cbb1ac8e51 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 2bbd36a82b 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 8e5e69edc4 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 033d378e6d 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] discards 74acb9b978 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] discards c84a113e4c 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards a0fcedd90a 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards a69b7337a7 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards dd50305d0d 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] discards 88ca3ef00d 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 5f1ff6d438 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] discards 97e58c1b14 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 99ceea4e46 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] discards 40b142abd1 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 3fb640a610 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 9cd620fe60 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 29486ddad5 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards b0504f8aa8 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 2ff79a1c79 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gdb [...] new 2d1e9e93b4 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new d59ee2f4a0 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 5afa6f222c 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new df63520056 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new c0f181a071 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gdb [...] new bdaca1ebb6 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 4ac49e3301 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gdb [...] new efcc537f7f 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 11da8c439a 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gdb [...] new 49e357be4e 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 6d9277ce2e 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new ac9a3f41f0 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new c3cd0279c2 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gdb [...] new 707aade7b8 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gdb [...] new ccc65e6af6 47: onsuccess: #556: 1: Success after binutils: 12 commits new 75f5243334 48: onsuccess: #559: 1: Success after binutils: 6 commits new e020ba8520 49: onsuccess: #562: 1: Success after binutils: 9 commits new 9b9a0d124f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gli [...] new cadbce5c76 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 12e86e6e5c 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gli [...] new eadda13e4a 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gdb [...] new 1eeddb7089 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gli [...] new a74ad1f576 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gli [...] new 54ad5726ef 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gli [...] new 0b6fdff899 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gli [...] new c0978c9194 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gli [...] new 84450c3958 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gli [...] new e4062e6a8a 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gli [...] new 678a197e91 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gli [...] new 1c452feac1 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gdb [...] new 29d9d37982 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 39bcf8bc6d 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gli [...] new f42f487a6b 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gdb [...] new 6d366f0156 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 6e2ffd2f4f 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gdb [...] new 6f9159f65e 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gli [...] new 7be1371160 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gdb [...] new afba553da7 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gli [...] new 94e7860f55 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gdb [...] new 4ee8685827 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gdb [...] new 267d263901 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gdb [...] new edf84bb125 74: onsuccess: #590: 1: Success after binutils: 16 commits new 7fcdd7b567 75: onsuccess: #591: 1: Success after gcc: 25 commits new 7ef4804898 76: onsuccess: #592: 1: Success after linux: 63 commits new 9e0f3d630e 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gli [...] new 75e497c2f4 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gli [...] new 5e4f3723e5 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gli [...] new 8eaa64b80c 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gli [...] new 69422aeda8 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gdb [...] new 111c63ff9b 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gli [...] new c43bd4cf7b 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gli [...] new 9c6d03106a 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gli [...] new a3ba799949 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gli [...] new 7a8dd91ed7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gli [...] new 8cc5d113f4 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gli [...] new 936c9e3f6f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gdb [...] new 38bdd0956e 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gdb [...] new 6a5b7a4c6f 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gli [...] new c067c61083 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gli [...] new fe6c6b23b9 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gli [...] new d5ff6eeb14 93: onsuccess: #613: 1: Success after binutils: 19 commits new dabc6fd9a4 94: onsuccess: #616: 1: Success after binutils: 2 commits new a76c7b6143 95: onsuccess: #619: 1: Success after binutils: 5 commits new 9445db8f95 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gli [...] new 6067889da5 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new eaa7d66588 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gdb [...] new 32be8a7840 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gli [...] new bc017ee48f 100: onsuccess: #625: 1: Success after binutils/gcc/linux/gd [...] new cbc6d3dc67 101: onsuccess: #627: 1: Success after binutils/gcc/linux/gd [...] new d954066905 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/gd [...] new 80718b3871 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 commits new 7c4c562614 104: onsuccess: #630: 1: Success after binutils/gcc/linux/gd [...] new bee4d02852 105: onsuccess: #631: 1: Success after binutils/gcc/linux/gd [...] new 54966f88b0 106: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new ce4a7f60a4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/gl [...] new a95cefb7ce 108: onsuccess: #637: 1: Success after binutils/gcc/linux/gl [...] new e975058422 109: onsuccess: #638: 1: Success after binutils/gcc/linux/gl [...] new bc1975f254 110: onsuccess: #639: 1: Success after binutils/gcc/linux/gd [...] new 7e786110e0 111: onsuccess: #640: 1: Success after binutils/gcc/linux/gd [...] new 3660e391fd 112: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new b7d3e7c506 113: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new f0ecb74733 114: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new bf46dd9318 115: onsuccess: #645: 1: Success after binutils: 27 commits new f554926291 116: onsuccess: #647: 1: Success after linux: 3 commits new ae19356323 117: onsuccess: #648: 1: Success after binutils/gcc/linux/gl [...] new 78c36eb813 118: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 8f34749dc5 119: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 4bef52ad3b 120: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new d93b7228f9 121: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new e427a60a3a 122: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 7c7a684879 123: onsuccess: #655: 1: Success after binutils: 22 commits new 0f65e783fe 124: onsuccess: #657: 1: Success after glibc: 2 commits new 4a61cc5fb1 125: onsuccess: #658: 1: Success after linux: 3224 commits new e86f527ad7 126: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new b03f433be7 127: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new febcfc6702 128: onsuccess: #661: 1: Success after binutils/gcc/linux/gl [...] new 7f125b857a 129: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new da402600f8 130: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 4dce76280c 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/gd [...] new c2d84f23ed 132: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new d4b81d4dfd 133: onsuccess: #666: 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 (2dbae0d63b) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]

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 1748 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 40076 -> 40144 bytes 04-build_abe-gcc/console.log.xz | Bin 215504 -> 216348 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9168 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 245040 -> 244724 bytes 08-build_abe-gdb/console.log.xz | Bin 39516 -> 39464 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3864 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2220 -> 2200 bytes 11-check_regression/console.log.xz | Bin 6192 -> 6040 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-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 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +-- sumfiles/binutils.log.xz | Bin 63324 -> 63148 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83872 -> 83828 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122520 -> 122320 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 406 insertions(+), 406 deletions(-)