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 766295035049 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 64c8f2cfc29c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 87d9ccb86d2a 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards b8eda383c99e 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards eef572e8a600 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards 7e0f8c219a3a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards d7f9517b60f9 125: onsuccess: #658: 1: Success after linux: 3224 commits discards f7637c814c85 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 4849f5a59edc 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 3e6c5f2db956 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards fd5f483e00af 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards efc477c0e91a 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 0e40727cbd79 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 44a853aff1fe 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 6edf1b2705b2 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 2ec19ce1416c 116: onsuccess: #647: 1: Success after linux: 3 commits discards 12c123d02083 115: onsuccess: #645: 1: Success after binutils: 27 commits discards b60f3506d010 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards e5f8874ef003 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 3fc17744dfe2 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 7716603491d1 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards 23afd67168dd 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards 6c57689e2345 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards c3a21ca5db87 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards ac9a0019eea4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 1a9b58ef6f5e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 960a8ec92587 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 7047b0a2283d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards 6d3cdfa04b8e 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] discards 2987078a2191 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] discards 08f77262610e 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 91503f423f31 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 8abfea436ee3 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards d9abb1338a72 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 6a4e83e093fc 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 1fe35031ca25 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards dca4608027de 95: onsuccess: #619: 1: Success after binutils: 5 commits discards e81dc12dccce 94: onsuccess: #616: 1: Success after binutils: 2 commits discards d5094ac6397f 93: onsuccess: #613: 1: Success after binutils: 19 commits discards a19666f8d756 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards dfef163f1230 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards d4f292b033bd 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards c8c26d26fafa 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 985ffc051e4f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards ab902d319126 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 172f8a59d120 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards dbeb39b2f2d2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 07782e0552d8 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 0a6ae4378c1e 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 49e0842d24ca 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards c83667f99d78 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 0c4ac9747c8f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 884ed3200fb9 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards ab7d00375b11 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5c901b77fa03 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 7dfa5c1f9bfa 76: onsuccess: #592: 1: Success after linux: 63 commits discards 6e7dbf42e700 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 859acebf987f 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 8aa5d48f9ff9 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards b7d71134aaf2 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 26d937dc95ee 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 972d07a90cab 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards 9a023f3d35d1 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 4c2ad822ebed 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards 350875b4b851 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards d3e369ba5e39 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards cf65efee6ab9 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards f2c5edb6d31e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 0cba8671547b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 0674746c39f9 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 64a8a982130e 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards deb08ddbf496 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards fa38a2c6a938 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 68f7ec1dc488 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards 210c6b6e1f2e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 0a15426c35ed 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 8b2ed89057ea 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 0875a840816a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards d1f1f0eefac3 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 3e7dd98315c8 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards b96a9f50f42e 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 835e5e5d6f7f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 6b4ddb5f84a5 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 28778f95f5f2 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 767367122681 47: onsuccess: #556: 1: Success after binutils: 12 commits discards a1c57f61255e 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards 63cb332ceb8c 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 088abfb9435a 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 67a7d980af99 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards a4e69ee0aea6 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 332cb82de57e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] discards 7271e329983d 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 5e5d2266389e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] discards 3f4949e4dfb3 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards 70dd465d1248 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] discards 319ce81d23c1 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 5307b4cace41 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 2a2931faa8a8 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards 233b84402dfa 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards 0234014e831a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards c9808e2003d8 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 3f24087a2e3a 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new b0504f8aa8b5 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 29486ddad58e 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new 9cd620fe602f 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 3fb640a610cb 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 40b142abd1c4 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 99ceea4e46a2 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] new 97e58c1b148e 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 5f1ff6d4385b 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] new 88ca3ef00d3c 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new dd50305d0d2c 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] new a69b7337a72f 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new a0fcedd90a39 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new c84a113e4c6e 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 74acb9b97824 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 033d378e6d57 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 8e5e69edc420 47: onsuccess: #556: 1: Success after binutils: 12 commits new 2bbd36a82bc8 48: onsuccess: #559: 1: Success after binutils: 6 commits new cbb1ac8e5174 49: onsuccess: #562: 1: Success after binutils: 9 commits new 1187b5ae6fba 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new f9c3da3ecf34 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 5034236444b6 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new e9c148850f4e 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new cba5fbb5d643 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 368dfc116b9e 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 531b43164139 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new f0f3e836607b 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new fc30157a368b 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 1d1d521e921a 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 2a413c9c5e0b 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 4c89cdcdb448 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 993018ca0956 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 97099850f209 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 2a067db2154b 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new c61fc843b4a9 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new 69f103fe739d 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new f3191386759f 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new c318535421f2 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 6e0a16899466 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 5c4c276daa07 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new f304b181b0f2 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new e15b332a88fa 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 61491829b310 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 921bb297cb46 74: onsuccess: #590: 1: Success after binutils: 16 commits new 6ec3a88ea93e 75: onsuccess: #591: 1: Success after gcc: 25 commits new 2a8ec092ba94 76: onsuccess: #592: 1: Success after linux: 63 commits new 5cf167672653 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e75d1d60fa23 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new f0775ee616a3 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 9fdcc5007247 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new d73157d3efe9 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 29e1a0ee12dd 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 0dd98fdb7ab5 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 97450b214fa0 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 5e19683635ea 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new eb32b20d85a7 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new d99a6836d9cf 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 849aa217f9e0 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 30c1fce85ee8 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new a0f31d8b71f6 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 9c2ef716390c 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 162f8d53352a 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 515a419bbce2 93: onsuccess: #613: 1: Success after binutils: 19 commits new 1a59b4e3efab 94: onsuccess: #616: 1: Success after binutils: 2 commits new 59f5807df89d 95: onsuccess: #619: 1: Success after binutils: 5 commits new cb87c431a608 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 41999ff7c696 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 51e87b2c3edc 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new f0b0b8658f65 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new ccd6ee6b7bdd 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 2db369ec1357 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new a106341a9bfb 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] new 8777d96d34e1 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] new d08233613c70 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new a2d74f495a95 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new ad515de011b3 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new 6d0bfad489e7 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new c2d7b7085e30 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new e2993caf0bd7 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new bc6f5986e098 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 7bee06f972cf 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 4304dbccfd12 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new bfc822b064a0 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new b175c2d883c5 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 1e6aeb12aab3 115: onsuccess: #645: 1: Success after binutils: 27 commits new 04ada6d4cc58 116: onsuccess: #647: 1: Success after linux: 3 commits new 2b2054e3a61c 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new e0de1b6d7796 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 32cd61b86119 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 4cd1e403be16 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new 2e7b3737e7a9 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 7cbac490ccf0 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 581e45c32f8f 123: onsuccess: #655: 1: Success after binutils: 22 commits new 7219e4079e45 124: onsuccess: #657: 1: Success after glibc: 2 commits new 0a3b2ab81720 125: onsuccess: #658: 1: Success after linux: 3224 commits new fa1fdaacae88 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 4bba01e7c28e 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 8e932b6835f3 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new b89d9edd2207 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 41ebe6951b2b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new be9655459fc2 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 2dbae0d63be6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...]
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 (766295035049) \ 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 1732 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40332 -> 40076 bytes 04-build_abe-gcc/console.log.xz | Bin 213708 -> 215504 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8624 -> 9168 bytes 07-build_abe-glibc/console.log.xz | Bin 243628 -> 245040 bytes 08-build_abe-gdb/console.log.xz | Bin 39552 -> 39516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3840 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2244 -> 2220 bytes 11-check_regression/console.log.xz | Bin 5704 -> 6192 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 27 +-- 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 63208 -> 63324 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83832 -> 83872 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 122320 -> 122520 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 410 insertions(+), 423 deletions(-)