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 dafa76de5fdd 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 2f325ccd1596 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 59a0c8e869d0 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards beedafcec486 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards b975ecc36e26 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 004d15d9f404 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 3e41b84a6f93 124: onsuccess: #657: 1: Success after glibc: 2 commits discards fa152f9f5b3f 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 1199de66fec6 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards 0e22a16b0759 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards afad14f8e94f 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 853c1d19c149 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards a838c3a3dae0 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 2b09cd90f023 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 262b74bfcc57 116: onsuccess: #647: 1: Success after linux: 3 commits discards 6642d5dd89b0 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 77f6e0d0f6c3 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 1358e25d44ad 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 6c765f2c7640 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards b205385177a7 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards a87943966fa5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards a450a9ff9db7 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards 273423be3f92 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards f0ce772b8654 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 5083540ee17b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 189d05e3a3aa 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 928d9db32d6d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards db53f46d0d8c 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] discards 940a4ad17f7b 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] discards 9d4dbf8b4d78 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 38bd5b1c758d 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] discards 007c5ac2a80f 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 49bad25295c7 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 4854ef46770d 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 44fe8f970c7b 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 76ccf3eb5ac3 95: onsuccess: #619: 1: Success after binutils: 5 commits discards fbcf1503eef8 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 5ce57a07e031 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 4aa903315259 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards f823fc1fc0a7 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 328d1ac4c3f5 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 2bf65482f42d 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 3002065e3b3c 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 63a93a8ad820 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0d3b7ee52952 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 5b98301034a0 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards c845fb30d04b 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards a962f2f7458b 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] discards 8dbc5cc211e0 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] discards 8df301282b19 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 129e63ec1d54 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 0025db812c0b 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 1fa3b9ed858c 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards c22fe5b9fecc 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 4d2224e53cfa 76: onsuccess: #592: 1: Success after linux: 63 commits discards 73226cfdab82 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 94f20b15b2d4 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 1ed5f3e3d3a0 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] discards f78934378a1c 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] discards 835b7acb8c1e 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] discards 3830f989b289 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] discards f9a1b85c0fdd 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] discards 56c52bf010f7 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] discards e8f6aea0075d 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] discards 52b7c15685d5 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] discards 89849ef6f361 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] discards 772316f8c63e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards aec94c16321c 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 3bc1ae45f2b7 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards dd50c64d9040 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 9a57fcb74bf6 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] discards 2ef50d79c47c 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards 2dd7999b6caf 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards ce65968c9641 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 5fd970252bfc 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 33f8ee29fa15 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards fa831e897668 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] discards 639fb56cf48c 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 590978d82d2e 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards f7094224e705 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards 6eeefa7d37e8 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards ba167f8ffbbe 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 2fe266b117c4 48: onsuccess: #559: 1: Success after binutils: 6 commits discards 0d27c7370ce9 47: onsuccess: #556: 1: Success after binutils: 12 commits discards e6bf66277ade 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] discards cdb1f0b82ea8 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 6cf52f2decab 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 09c79b5d8277 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] discards a4e2ce686c86 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] discards 736c33dec853 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] discards 521aea1d7ff6 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] discards 9ef5c5860d7e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] discards 7193d58d05be 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] discards cd414867c410 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] discards ac848c950dde 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] discards 5f6955e7d2c3 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] discards 960b14a4b616 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] discards aaaef3041302 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] discards 01b6e8dd7ac6 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] discards ecf5ec7c0c98 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] discards 2c6735c55f76 30: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new 05bd30460ffb 30: onsuccess: #537: 1: Success after binutils/gcc/linux/g [...] new c9808e2003d8 31: onsuccess: #538: 1: Success after binutils/gcc/linux/g [...] new 0234014e831a 32: onsuccess: #539: 1: Success after binutils/gcc/linux/g [...] new 233b84402dfa 33: onsuccess: #540: 1: Success after binutils/gcc/linux/g [...] new 2a2931faa8a8 34: onsuccess: #541: 1: Success after binutils/gcc/linux/g [...] new 5307b4cace41 35: onsuccess: #542: 1: Success after binutils/gcc/linux/g [...] new 319ce81d23c1 36: onsuccess: #543: 1: Success after binutils/gcc/linux/g [...] new 70dd465d1248 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/g [...] new 3f4949e4dfb3 38: onsuccess: #545: 1: Success after binutils/gcc/linux/g [...] new 5e5d2266389e 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/g [...] new 7271e329983d 40: onsuccess: #547: 1: Success after binutils/gcc/linux/g [...] new 332cb82de57e 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/g [...] new a4e69ee0aea6 42: onsuccess: #549: 1: Success after binutils/gcc/linux/g [...] new 67a7d980af99 43: onsuccess: #550: 1: Success after binutils/gcc/linux/g [...] new 088abfb9435a 44: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 63cb332ceb8c 45: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new a1c57f61255e 46: onsuccess: #554: 1: Success after binutils/gcc/linux/g [...] new 767367122681 47: onsuccess: #556: 1: Success after binutils: 12 commits new 28778f95f5f2 48: onsuccess: #559: 1: Success after binutils: 6 commits new 6b4ddb5f84a5 49: onsuccess: #562: 1: Success after binutils: 9 commits new 835e5e5d6f7f 50: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new b96a9f50f42e 51: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 3e7dd98315c8 52: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new d1f1f0eefac3 53: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new 0875a840816a 54: onsuccess: #568: 1: Success after binutils/gcc/linux/g [...] new 8b2ed89057ea 55: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new 0a15426c35ed 56: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new 210c6b6e1f2e 57: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 68f7ec1dc488 58: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new fa38a2c6a938 59: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new deb08ddbf496 60: onsuccess: #574: 1: Success after binutils/gcc/linux/g [...] new 64a8a982130e 61: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 0674746c39f9 62: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 0cba8671547b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new f2c5edb6d31e 64: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new cf65efee6ab9 65: onsuccess: #580: 1: Success after binutils/gcc/linux/g [...] new d3e369ba5e39 66: onsuccess: #581: 1: Success after binutils/gcc/linux/g [...] new 350875b4b851 67: onsuccess: #582: 1: Success after binutils/gcc/linux/g [...] new 4c2ad822ebed 68: onsuccess: #583: 1: Success after binutils/gcc/linux/g [...] new 9a023f3d35d1 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/g [...] new 972d07a90cab 70: onsuccess: #585: 1: Success after binutils/gcc/linux/g [...] new 26d937dc95ee 71: onsuccess: #586: 1: Success after binutils/gcc/linux/g [...] new b7d71134aaf2 72: onsuccess: #587: 1: Success after binutils/gcc/linux/g [...] new 8aa5d48f9ff9 73: onsuccess: #588: 1: Success after binutils/gcc/linux/g [...] new 859acebf987f 74: onsuccess: #590: 1: Success after binutils: 16 commits new 6e7dbf42e700 75: onsuccess: #591: 1: Success after gcc: 25 commits new 7dfa5c1f9bfa 76: onsuccess: #592: 1: Success after linux: 63 commits new 5c901b77fa03 77: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new ab7d00375b11 78: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 884ed3200fb9 79: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 0c4ac9747c8f 80: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new c83667f99d78 81: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 49e0842d24ca 82: onsuccess: #598: 1: Success after binutils/gcc/linux/g [...] new 0a6ae4378c1e 83: onsuccess: #599: 1: Success after binutils/gcc/linux/g [...] new 07782e0552d8 84: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new dbeb39b2f2d2 85: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new 172f8a59d120 86: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new ab902d319126 87: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 985ffc051e4f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new c8c26d26fafa 89: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new d4f292b033bd 90: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new dfef163f1230 91: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new a19666f8d756 92: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new d5094ac6397f 93: onsuccess: #613: 1: Success after binutils: 19 commits new e81dc12dccce 94: onsuccess: #616: 1: Success after binutils: 2 commits new dca4608027de 95: onsuccess: #619: 1: Success after binutils: 5 commits new 1fe35031ca25 96: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 6a4e83e093fc 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new d9abb1338a72 98: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 8abfea436ee3 99: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 91503f423f31 100: onsuccess: #625: 1: Success after binutils/gcc/linux/ [...] new 08f77262610e 101: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new 2987078a2191 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/ [...] new 6d3cdfa04b8e 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 6 [...] new 7047b0a2283d 104: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new 960a8ec92587 105: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new 1a9b58ef6f5e 106: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new ac9a0019eea4 107: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new c3a21ca5db87 108: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new 6c57689e2345 109: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new 23afd67168dd 110: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 7716603491d1 111: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new 3fc17744dfe2 112: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new e5f8874ef003 113: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new b60f3506d010 114: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 12c123d02083 115: onsuccess: #645: 1: Success after binutils: 27 commits new 2ec19ce1416c 116: onsuccess: #647: 1: Success after linux: 3 commits new 6edf1b2705b2 117: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new 44a853aff1fe 118: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 0e40727cbd79 119: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new efc477c0e91a 120: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new fd5f483e00af 121: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 3e6c5f2db956 122: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 4849f5a59edc 123: onsuccess: #655: 1: Success after binutils: 22 commits new f7637c814c85 124: onsuccess: #657: 1: Success after glibc: 2 commits new d7f9517b60f9 125: onsuccess: #658: 1: Success after linux: 3224 commits new 7e0f8c219a3a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new eef572e8a600 127: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new b8eda383c99e 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 87d9ccb86d2a 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 64c8f2cfc29c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 766295035049 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...]
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 (dafa76de5fdd) \ 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 1744 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 40040 -> 40332 bytes 04-build_abe-gcc/console.log.xz | Bin 213568 -> 213708 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 243232 -> 243628 bytes 08-build_abe-gdb/console.log.xz | Bin 39048 -> 39552 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3832 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2136 -> 2244 bytes 11-check_regression/console.log.xz | Bin 5612 -> 5704 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 27 ++- 12-update_baseline/console.log | 34 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +-- sumfiles/binutils.log.xz | Bin 63044 -> 63208 bytes sumfiles/binutils.sum | 62 ++--- sumfiles/gas.log.xz | Bin 83828 -> 83832 bytes sumfiles/gas.sum | 272 +++++++++++----------- sumfiles/ld.log.xz | Bin 121716 -> 122320 bytes sumfiles/ld.sum | 360 ++++++++++++++--------------- 29 files changed, 412 insertions(+), 399 deletions(-)