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_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 1daf73cc4cd 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] discards cd2b878c93b 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards 081ea81fa61 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards a82982046f9 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] discards 691d8074386 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 52cca8d9c0f 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards ea54cd411d6 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 6ff460edd89 127: force: #27: : Failure after baseline build: no new commits discards d2013b119af 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards f99e854b845 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c2d40351c88 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 1394efc8ae3 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 78469b62fae 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards e6a660a0cee 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b5ddc6ec2d9 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 7a69472410d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards db6c0315673 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 42da9db0f3f 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards e62461b5837 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 44234ba5492 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 956ab3fb286 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a3bf144f8ea 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 9f0952c1085 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 99f0a26f651 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ea80f8584be 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4590b9f0618 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards fcab0145ff4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards e6434e5a3c5 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 995ab7f9491 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards ef01baa28c4 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards d048487701d 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 7c848d22e16 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 1badd0a7303 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 40e126febac 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards fef67bbe2a6 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 77e8531780b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards c8bf68f800b 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 69b35874e26 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 816345db71f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 0b0a441633e 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 66e53ba9346 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards fbd63f49f54 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 4f16afde8a4 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards dcf10f270c3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards a9f80367233 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards af3401b7b28 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 590f67e3f7a 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 26e7bec15ef 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 478bb58c020 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards fdb6e138b78 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards 3b9b723a2a2 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 93b879eacb8 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 234eea0ebdd 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 88f6ba24a76 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards c6d14a02f11 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 5b70d6aa65e 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards e9a1d21b29e 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards cab80db1dce 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards fcdec097b93 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 3e5078896a3 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards d5ef13ba535 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards ec8404b37f0 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 8e6f24a7a8a 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 32c9dd66227 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards ef15aaab483 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards e352d653bcd 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 81517a0f879 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 9b57cad4e6a 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 35e97ef022a 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 8440114a98b 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards 1c84caa6a37 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 00a19500e47 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards ba9a2216660 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards 096bd88574d 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 2f513612a89 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards f1f809a51e6 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards 610b11c0b14 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 5182f5d0638 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards ec6f4351109 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 56c46810313 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 3c6484a3e0c 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards bdd3f390e41 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards eafcdcd7f07 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards e5713976064 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards e363a962a48 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 4e782546ec1 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards cfc8c61d923 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 2165c934cd9 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 40ce74f976d 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards fdb50ed16ef 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 39b0494f331 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards c1c8cd0ff91 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 3bfd5a2e769 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 45ac9232024 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 07c7865cf6e 40: onsuccess: #49: 1: Success after linux: 219 commits discards 984247b70f9 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 1f5f16f8729 38: onsuccess: #46: 1: Success after binutils: 26 commits discards b3329a80947 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 9bd30dfe31a 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards d1a2f134558 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards c5ee73a0810 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new faf20f16f9d 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 7f72447fa70 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new da658c1a8b0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 2ba92a7fcc6 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new cb5cb79d8c2 38: onsuccess: #46: 1: Success after binutils: 26 commits new 7fc6e21345e 39: onsuccess: #48: 1: Success after glibc: 2 commits new 3efcc8e43a7 40: onsuccess: #49: 1: Success after linux: 219 commits new 6ee7038111c 41: onsuccess: #51: 1: Success after binutils: 12 commits new 2984c680c0e 42: onsuccess: #53: 1: Success after linux: 3008 commits new 49ab6480b85 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 3207acaf125 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 14f49d2c77d 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 8278d8b9568 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 4773e6cef9f 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 25bfe7ac98f 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new b5aad7a75f1 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new b45ea336fb0 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new f613e1d9803 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new cf5a62d0253 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 1b2d4f2ff98 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new b54b18c9ace 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 861cc7b26ce 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 32b1b647aa1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 4dd93c2f11b 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new d296ced5e85 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 462ac882a08 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 8f5b31f0b6e 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new a63af07a76c 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new af99b6e33c3 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new 1d7bac9cd33 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 5fd204b2e7b 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 94b47fddd4e 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 8724458290f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new e4da660a61f 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 6e0eba2c93c 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 5b266fe2a69 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 21a9a6e76c9 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new e655faf2187 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 0defb7a9366 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 57381f64834 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 8ff33eb12a1 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 6eb50a9cf61 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 7dc5c8d136f 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new def66ec8900 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new b79c6ff804c 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new d07768cf324 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 8dfe94e2c37 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 76e2d6833db 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 8692cff91c7 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 7e3a61116b1 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new dbd5ea53691 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new df64d47f86d 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new a9ccbca1a32 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 1957feeea46 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 6dc3d0e014e 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 8aeaacd3f3a 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new cbfc34f21ef 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 0c1e52bc512 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 478e19755d4 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new ef4b8c55303 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new fa332402fc3 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 80cf6db92e5 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 1fc09f9cded 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 30acd4e1820 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 4a9bd653a3c 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 1156ea0a3bb 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new 24ffe8d1540 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new c275eac6135 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 5e4b4d791e0 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new e604f09d28d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 4fdea68cb00 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new c55415a1020 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new e6e5c8478fa 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 302748b7971 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 3e5ea2b28c8 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 48a1ee09bd4 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 97e33459ed0 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 2aac504853d 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a99d1ba5013 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 158b148278b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 43a38cf9639 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4d7aceb7e9d 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 649b2a6d59d 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 7fe366b30a7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 3db78a06129 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new d0611ce7f15 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 65f6a225df6 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new a4080dc92d3 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new eedb95ec3f6 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 19c3b081bce 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new b631558e420 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 83181454610 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 66f54e5e8a3 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 3bc1e4d5c6f 127: force: #27: : Failure after baseline build: no new commits new a85c04dbb65 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new d59cefc8443 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new ea54621a601 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 8206be55e41 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gl [...] new ffe8aac3cb7 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 579bf51beda 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 59e6dffdbde 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gd [...] new 54955ccb3f7 135: onsuccess: #38: 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 (1daf73cc4cd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 2032 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 35088 -> 35352 bytes 04-build_abe-gcc/console.log.xz | Bin 203064 -> 203872 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8360 -> 8176 bytes 07-build_abe-glibc/console.log.xz | Bin 241432 -> 241448 bytes 08-build_abe-gdb/console.log.xz | Bin 34696 -> 34780 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2648 -> 3068 bytes 11-check_regression/console.log.xz | Bin 4308 -> 4660 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- 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/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++--------- sumfiles/gdb.log.xz | Bin 14672 -> 14652 bytes sumfiles/gdb.sum | 4 +- 25 files changed, 67 insertions(+), 67 deletions(-)