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 7cc2e1caefe 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 0d17e7841d0 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 66089b2964b 116: onsuccess: #647: 1: Success after linux: 3 commits discards 4c4fa7d260c 115: onsuccess: #645: 1: Success after binutils: 27 commits discards a79a57d12e2 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 0e45d3525b2 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards adbe5ee1de9 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 1d35fec0b7c 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 593bdf121b5 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 65f3761434c 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 52d42d761ec 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards d01b3029ca6 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards f9fce36e61f 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards b9098fd81b6 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards e307e251a25 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards c928b19beeb 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] discards c309a7f2ae7 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] discards 8e88255a830 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 5c199c1998b 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards f045593c66e 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 2e849db2a84 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] discards 436f869d423 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits discards 580affcf02a 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 0eac912b7d7 95: onsuccess: #619: 1: Success after binutils: 5 commits discards 7063d7396e4 94: onsuccess: #616: 1: Success after binutils: 2 commits discards 154431d6047 93: onsuccess: #613: 1: Success after binutils: 19 commits discards 3987c1beefc 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards f14f284e9c1 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards b15fd53a833 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards af03d196dab 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] discards c2216950321 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] discards 14d55190ab2 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] discards ee2d4bafe41 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 58d121e06df 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] discards 0fd047b086b 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards 2aa69a08493 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards e91056ba79c 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] discards b803a46edb8 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 24aaeeede24 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] discards 81aacd17923 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards 3986183ba4e 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 065c6cc3cb0 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] discards e3434fa7589 76: onsuccess: #592: 1: Success after linux: 63 commits discards 8ccefc92012 75: onsuccess: #591: 1: Success after gcc: 25 commits discards a843e472205 74: onsuccess: #590: 1: Success after binutils: 16 commits discards 150b572d7ee 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 0974564e8d7 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] discards 4f7c8102e7f 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] discards bf07218f587 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards 4a562c84ba9 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards e523022b160 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 85a4b36b129 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] discards 511d92ce28e 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] discards 635f808f7f3 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] discards 82726474864 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] discards 4eab4b86896 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] discards c844611469c 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards da261f8a8d1 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] discards ec8e5bdfdb8 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 3e9175b4922 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] discards c7411f2ca15 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] discards d7668e0ef60 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] discards 3aff274ca2f 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] discards e613439241a 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] discards 9adc8f165cd 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] discards 64f34f7ed52 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] discards d3e1d5e9801 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 83bd261be6a 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards ce2dd7f5065 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 6f966dfbc9c 49: onsuccess: #562: 1: Success after binutils: 9 commits discards 2926cb353bc 48: onsuccess: #559: 1: Success after binutils: 6 commits discards fec983ee78e 47: onsuccess: #556: 1: Success after binutils: 12 commits discards c18b6326efc 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] discards 07ab93b0fcf 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 786b543798b 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6e88a063e32 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 93f12820e64 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 396fb1af3b6 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] discards fb2f4794c29 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards 67861d285e3 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] discards c58f44544b2 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 51f6531196d 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] discards 34979d67f9e 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 857a14fed9a 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards 81d1aaa0e77 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] discards 2fcf7607a0b 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] discards a43ad256aa9 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards bc27251fb24 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] discards 78aa7e8220e 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] discards 832d8f02475 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards b6ede10b9f9 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] discards 8e50c930357 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] discards be21db34f02 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 327cdf0966d 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] discards fb659c6d082 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] discards 89b89db7424 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] discards 3b5addf7cad 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] discards c6b680be29f 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards b8c207e323f 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards cc7ac122213 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] discards 1409895d23a 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 677c2a64300 18: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9145a24f488 19: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 633c2365292 20: onsuccess: 1: Successful build after binutils/gcc/linux [...] new dadc12141b4 21: onsuccess: 1: Successful build after binutils/gcc/linux [...] new 9c568b2bb7c 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gd [...] new 3c1c220de0f 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 129 [...] new bfa5b55b599 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 216 [...] new 05f91788542 25: onsuccess: #532: 1: Success after binutils/gcc/linux/gd [...] new ecba04c6288 26: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new 8319cfe3664 27: onsuccess: #534: 1: Success after binutils/gcc/linux/gl [...] new 4b59b706960 28: onsuccess: #535: 1: Success after binutils/gcc/linux/gl [...] new a93e427d827 29: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new 74b22a9c262 30: onsuccess: #537: 1: Success after binutils/gcc/linux/gl [...] new 755f447c542 31: onsuccess: #538: 1: Success after binutils/gcc/linux/gl [...] new 07ab8db6f43 32: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new 56f32fd9d17 33: onsuccess: #540: 1: Success after binutils/gcc/linux/gl [...] new 240236d6ef7 34: onsuccess: #541: 1: Success after binutils/gcc/linux/gl [...] new 9b69d05756b 35: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new 8907e5dab75 36: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new b4ce1f268af 37: onsuccess: #544: 1: Success after binutils/gcc/glibc/gd [...] new bf166efaa7b 38: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 828ab508b40 39: onsuccess: #546: 1: Success after binutils/gcc/glibc/gd [...] new 7fb75d58092 40: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new 32d270cb9f3 41: onsuccess: #548: 1: Success after binutils/gcc/glibc/gd [...] new 423307d452a 42: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new d38ff152ecf 43: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new df33477decc 44: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 5313f51ef81 45: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 336717b9392 46: onsuccess: #554: 1: Success after binutils/gcc/linux/gd [...] new 61125fed0c6 47: onsuccess: #556: 1: Success after binutils: 12 commits new 64446f49b02 48: onsuccess: #559: 1: Success after binutils: 6 commits new 82a811d8bac 49: onsuccess: #562: 1: Success after binutils: 9 commits new f1f0666a67d 50: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new 937468925c3 51: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new cdac9165b3e 52: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 69f2c6ad17f 53: onsuccess: #567: 1: Success after binutils/gcc/linux/gd [...] new b2ac78f27f0 54: onsuccess: #568: 1: Success after binutils/gcc/linux/gl [...] new c0a8c21f199 55: onsuccess: #569: 1: Success after binutils/gcc/linux/gl [...] new 338a6f75119 56: onsuccess: #570: 1: Success after binutils/gcc/linux/gl [...] new 087c37b79ce 57: onsuccess: #571: 1: Success after binutils/gcc/linux/gl [...] new a3c251409f5 58: onsuccess: #572: 1: Success after binutils/gcc/linux/gl [...] new 94ee4fd9043 59: onsuccess: #573: 1: Success after binutils/gcc/linux/gl [...] new a2d2e451a15 60: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 6e3e1bb0509 61: onsuccess: #575: 1: Success after binutils/gcc/linux/gl [...] new cd44cc46d8a 62: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new a502dc5ba2b 63: onsuccess: #577: 1: Success after binutils/gcc/linux/gl [...] new dbbcc7aef85 64: onsuccess: #579: 1: Success after binutils/gcc/linux/gl [...] new ab0b1f6bb2a 65: onsuccess: #580: 1: Success after binutils/gcc/linux/gd [...] new 68595dabe1f 66: onsuccess: #581: 1: Success after binutils/gcc/linux/gl [...] new 7aa7dc652fa 67: onsuccess: #582: 1: Success after binutils/gcc/linux/gd [...] new 9b704c4e6a7 68: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 706ccd14d9f 69: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 254c02ae705 70: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 98ea0445e69 71: onsuccess: #586: 1: Success after binutils/gcc/linux/gd [...] new 013b2ca43f0 72: onsuccess: #587: 1: Success after binutils/gcc/linux/gd [...] new 4ac18152d9a 73: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new 75929514756 74: onsuccess: #590: 1: Success after binutils: 16 commits new b7c8c8b2f1d 75: onsuccess: #591: 1: Success after gcc: 25 commits new 63ebc4a5535 76: onsuccess: #592: 1: Success after linux: 63 commits new e16ec1e3c1b 77: onsuccess: #593: 1: Success after binutils/gcc/linux/gl [...] new b92de406af6 78: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new d4fc05bf238 79: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new cd4ecfad167 80: onsuccess: #596: 1: Success after binutils/gcc/linux/gl [...] new 7cd23c66665 81: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new 37687fb41d6 82: onsuccess: #598: 1: Success after binutils/gcc/linux/gl [...] new c82aaf3bce8 83: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 3b72c445e20 84: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new 82378839dca 85: onsuccess: #601: 1: Success after binutils/gcc/linux/gl [...] new 1e0475beabc 86: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new adfb0040888 87: onsuccess: #603: 1: Success after binutils/gcc/linux/gl [...] new bf3ef99b3ae 88: onsuccess: #604: 1: Success after binutils/gcc/linux/gd [...] new 5c43fdf0c8c 89: onsuccess: #605: 1: Success after binutils/gcc/linux/gd [...] new ac93858956b 90: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new f33dd3c08ad 91: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new f3121bcef8d 92: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new 135e4ae1d22 93: onsuccess: #613: 1: Success after binutils: 19 commits new f06b1ce7baa 94: onsuccess: #616: 1: Success after binutils: 2 commits new 14525a54403 95: onsuccess: #619: 1: Success after binutils: 5 commits new d50cc8754f4 96: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 9a2becf7528 97: onsuccess: #622: 1: Success after binutils/gcc/gdb: 8 commits new ed5441d2023 98: onsuccess: #623: 1: Success after binutils/gcc/linux/gd [...] new 62d87568725 99: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new ed60488d457 100: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 794492c7f34 101: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new c00096b3c86 102: onsuccess: #628: 1: Success after binutils/gcc/glibc/g [...] new d8263ba7ee5 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new fe7ea3db605 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 94be13e2aa9 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 6349657b615 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 36157e439cd 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new dc575cc00f0 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new df0c1aeef2a 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 804ec9b313a 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 82828c3f612 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 55d45af18b0 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 23d5e9901cf 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 88929682728 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new bb5c3477b42 115: onsuccess: #645: 1: Success after binutils: 27 commits new 691aa59ea69 116: onsuccess: #647: 1: Success after linux: 3 commits new b92f220e5fe 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 0dbbc43161a 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7910e088d1b 119: onsuccess: #650: 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 (7cc2e1caefe) \ 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 1724 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 39432 -> 40108 bytes 04-build_abe-gcc/console.log.xz | Bin 214656 -> 216348 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8856 bytes 07-build_abe-glibc/console.log.xz | Bin 243300 -> 243476 bytes 08-build_abe-gdb/console.log.xz | Bin 38900 -> 38844 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3888 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2108 -> 2060 bytes 11-check_regression/console.log.xz | Bin 6232 -> 6140 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 38 ++-- 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 63064 -> 63292 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 81768 -> 81800 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 121736 -> 121736 bytes sumfiles/ld.sum | 346 ++++++++++++++--------------- 30 files changed, 394 insertions(+), 394 deletions(-)