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 ebe682f1e4e 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 425aa718a09 116: onsuccess: #647: 1: Success after linux: 3 commits discards b9efea2ebaf 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 3d1c6b1978c 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 475b75565c3 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 372aabe61c3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards a536973200c 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 9ae585592fc 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 37026280cd3 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 463982b9f89 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 8dd6ceb1c37 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 2741d1b9aac 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 08c12b9770c 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 16e72d2af5e 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 28021c6ff53 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards c200a3ad0a1 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards aa5f4e275c9 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 8d21514dee5 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 26c9996f138 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards d2bd927dbc7 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 474e43342cb 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 34831ad9db0 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 97967e3482c 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 35ce9177627 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 63a229be6c8 93: onsuccess: #613: 1: Success after binutils: 19 commits discards b14d28b0c9b 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 4dc9e3c3874 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 8a14a868c10 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards edec0dcc8b7 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards 342873e9f7f 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards f854a88c5b0 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards b066da6c34d 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 385af151006 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 14f67f1844e 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 04705bd8ed9 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards f642e645cc7 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards a29739692e0 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards efba6cb721c 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards a3d3b0089e6 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards cf547dbb0d4 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards ffa832739d0 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards 2eccc29619f 76: onsuccess: #592: 1: Success after linux: 63 commits discards 3139c0ff110 75: onsuccess: #591: 1: Success after gcc: 25 commits discards 010b0ba3fb4 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 633dfad914a 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 253d703beeb 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 70e5e1dda7a 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards ea5b8b75846 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 32d4c81d7e7 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards cfa72c07fed 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 07f26cceea7 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards b640260ef57 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 2dd074d80e1 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards abc90e43ba0 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards a80036e1b5b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards a2c56bcf454 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 29440c392ac 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards 4e9d40eead2 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards d757dc729fd 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards 6718013a9bf 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards a5e07122acc 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards ea991861b22 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards c8e76af0814 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 922c8f2c1b3 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 0d3bc9ca2de 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards e5559e4b2d8 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 61c2f139c07 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards ce492384c68 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 35164cfbe54 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 71a7133df50 48: onsuccess: #559: 1: Success after binutils: 6 commits discards d47b1dd12b4 47: onsuccess: #556: 1: Success after binutils: 12 commits discards 6ce7c6f2aad 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards fe4710fb634 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 545ba0c950e 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 754fb96e1a0 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 74178a2a1e0 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 78c2f7b61d2 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards f569c50bcca 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards cbe308f0232 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards d289e2c1771 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 55bdf01ca17 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 2e3cc5d451e 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 8dd4ea33cad 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards e4f5022159d 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 34cee96eb17 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards baa2fe92566 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 08cc25b0b67 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 6cad727facb 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 76dfd7a1cfb 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 17ce40050a2 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards ffe936898f9 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards 23d350b9cd9 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards a46829bed9f 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards 1ce147be02d 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 87bb0356122 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 33894d87efd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards 8d089a3d0e0 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards a405f12ed22 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 50ddc046c7e 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards b3a01732fc2 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards ac80ca1a40a 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new dcc1a6726cc 17: onsuccess: 1: Successful build after binutils/gcc/glibc [...] new 1409895d23a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new cc7ac122213 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new b8c207e323f 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new c6b680be29f 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 3b5addf7cad 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 89b89db7424 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new fb659c6d082 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 327cdf0966d 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new be21db34f02 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 8e50c930357 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new b6ede10b9f9 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new 832d8f02475 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 78aa7e8220e 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new bc27251fb24 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new a43ad256aa9 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 2fcf7607a0b 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 81d1aaa0e77 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 857a14fed9a 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 34979d67f9e 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 51f6531196d 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new c58f44544b2 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 67861d285e3 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new fb2f4794c29 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 396fb1af3b6 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 93f12820e64 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 6e88a063e32 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 786b543798b 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 07ab93b0fcf 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new c18b6326efc 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new fec983ee78e 47: onsuccess: #556: 1: Success after binutils: 12 commits new 2926cb353bc 48: onsuccess: #559: 1: Success after binutils: 6 commits new 6f966dfbc9c 49: onsuccess: #562: 1: Success after binutils: 9 commits new ce2dd7f5065 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 83bd261be6a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new d3e1d5e9801 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 64f34f7ed52 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new 9adc8f165cd 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new e613439241a 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 3aff274ca2f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new d7668e0ef60 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new c7411f2ca15 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 3e9175b4922 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new ec8e5bdfdb8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new da261f8a8d1 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new c844611469c 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 4eab4b86896 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new 82726474864 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new 635f808f7f3 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 511d92ce28e 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 85a4b36b129 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new e523022b160 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 4a562c84ba9 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new bf07218f587 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 4f7c8102e7f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 0974564e8d7 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 150b572d7ee 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new a843e472205 74: onsuccess: #590: 1: Success after binutils: 16 commits new 8ccefc92012 75: onsuccess: #591: 1: Success after gcc: 25 commits new e3434fa7589 76: onsuccess: #592: 1: Success after linux: 63 commits new 065c6cc3cb0 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new 3986183ba4e 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 81aacd17923 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new 24aaeeede24 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new b803a46edb8 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new e91056ba79c 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new 2aa69a08493 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 0fd047b086b 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 58d121e06df 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new ee2d4bafe41 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 14d55190ab2 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new c2216950321 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new af03d196dab 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new b15fd53a833 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f14f284e9c1 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new 3987c1beefc 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 154431d6047 93: onsuccess: #613: 1: Success after binutils: 19 commits new 7063d7396e4 94: onsuccess: #616: 1: Success after binutils: 2 commits new 0eac912b7d7 95: onsuccess: #619: 1: Success after binutils: 5 commits new 580affcf02a 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 436f869d423 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new 2e849db2a84 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new f045593c66e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 5c199c1998b 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 8e88255a830 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c309a7f2ae7 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new c928b19beeb 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new e307e251a25 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new b9098fd81b6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new f9fce36e61f 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new d01b3029ca6 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 52d42d761ec 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 65f3761434c 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 593bdf121b5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 1d35fec0b7c 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new adbe5ee1de9 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 0e45d3525b2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new a79a57d12e2 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4c4fa7d260c 115: onsuccess: #645: 1: Success after binutils: 27 commits new 66089b2964b 116: onsuccess: #647: 1: Success after linux: 3 commits new 0d17e7841d0 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 7cc2e1caefe 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...]

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 (ebe682f1e4e) \ 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 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 40060 -> 39432 bytes 04-build_abe-gcc/console.log.xz | Bin 215208 -> 214656 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8584 -> 8492 bytes 07-build_abe-glibc/console.log.xz | Bin 245244 -> 243300 bytes 08-build_abe-gdb/console.log.xz | Bin 39472 -> 38900 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3884 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2204 -> 2108 bytes 11-check_regression/console.log.xz | Bin 6268 -> 6232 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 40 ++-- 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 | 38 ++-- sumfiles/binutils.log.xz | Bin 63104 -> 63064 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81788 -> 81768 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121748 -> 121736 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 395 insertions(+), 395 deletions(-)