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 2014be27eea 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 7c4993fd421 127: force: #27: : Failure after baseline build: no new commits discards 937068ad406 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 71cf80453d7 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 614c5decd3c 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards fb0b29ef802 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards b699646ef34 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards e0a0eb86cec 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 35167f932ba 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards b9707e98e19 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a9cdb1056ab 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 74758a2a2b7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 170d2f2aab1 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7ba2d5cab00 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards d30b1c9ef92 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 9d3fee535a4 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 85378294026 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ede6f4f0f13 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards ce15274f174 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ad9e6102252 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8fab955e35b 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 7563a6a50ff 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e461cb0e439 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 1fca9b3bcb7 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 0a69782d6cd 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards 94f7591ceb7 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 4d64dfd0d1d 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 6b7a70e21a8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards d4217517b01 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards 73bf356be7a 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards 92bec2705d8 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 8b1609415d2 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards f75dc9c4d7f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards e8ba15158c1 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 476cd4e3a5f 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards a81c9d481cd 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards b79f523116f 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 43fea7dac28 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 7fcde03b719 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards be9d34e3a01 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards 5a2e38cb161 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 4f2bce2e4e0 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards c301880ee01 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards 871cd758966 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards e89018dd1e6 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 0fe8ea58eb3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards c781b42a511 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards 195fefb4fea 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 6578202a241 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 345d1aac61d 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards b071a622eac 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 107e33bbda8 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 747d0718a9a 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards 5f2ec339183 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 34e03cc75e7 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 87212ec78ce 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards ed71645ca53 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 4c6c3aaa76e 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards 167ff423f93 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards e822d6d07c2 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards f5ccd067471 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 5a22c2fe951 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 0bb6c97956c 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards 093ec7df738 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards e92534bfd13 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards d1780c5b33c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 3eabddbaba7 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards cb8a4fd7817 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards 0fad34f0fbc 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards 4af083bb590 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards a784fb7a009 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 7222a82d007 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards cd3253ebc8f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 7915c19e3e8 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 6f2e931491a 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards 2b57094abe3 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 2070d55f6ef 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards b9f58cdc94e 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 0c796b48a47 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 23717fe11e9 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 487d075d749 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards 53a43c5cd4d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards 54d857c8c0b 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 2318e13c562 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards 259ccf57113 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 9d466cdda6f 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 6633c87d616 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 34687773cf0 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 81249fa7a96 40: onsuccess: #49: 1: Success after linux: 219 commits discards c8f5f78a986 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 02785b88bf7 38: onsuccess: #46: 1: Success after binutils: 26 commits discards 750eea8a6bf 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 8fd05c233b0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards a57ae854229 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 89b4621f295 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards f008f32aedc 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards b49f0e41b6f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 79a575234ad 31: onsuccess: #38: 1: Success after linux: 12 commits discards ca63d03fd69 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 680974b07ab 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards fb084d6352c 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 6cb1e7903d4 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 58898d3a8ed 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 7a4cb0c6437 30: onsuccess: #36: 1: Success after binutils: 18 commits new 95378671a4b 31: onsuccess: #38: 1: Success after linux: 12 commits new f70f819450a 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 0c87cd209f5 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new cdca95bf688 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 25ec0b33ebc 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 27e87b43078 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 87d3cc8d69b 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 3806f616a43 38: onsuccess: #46: 1: Success after binutils: 26 commits new f08f19e98f8 39: onsuccess: #48: 1: Success after glibc: 2 commits new a6fe5b2a5b0 40: onsuccess: #49: 1: Success after linux: 219 commits new ed3f5e31c85 41: onsuccess: #51: 1: Success after binutils: 12 commits new 862ed77a238 42: onsuccess: #53: 1: Success after linux: 3008 commits new dc9cd95182e 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 205d31cc8c8 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 0da973fd216 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 914d8a86e93 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 57f3daf3e85 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 544c7737259 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 64e3a472879 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new bf477443d41 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new 3a9aa2b28f5 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 2ff7f33c8ce 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 3eaf05b2bb2 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 1a6aad76897 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 975ee9c0271 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new 263d898badb 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new dc9cf329df7 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 1d85496f1e8 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new b0a173542e5 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new f77a4b0a2bd 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new f8d987a14c7 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 5b78d212d81 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new bbc43260179 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new e1f5bab7a1c 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new d4faca81703 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 0a35870d12c 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new dc4a2116703 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 6b85916fe4e 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new 3bf6923e4b2 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 8f11f73608e 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 61214d980f3 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new 9f0642b4bb9 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 00256ffd294 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new fc7e3efcc87 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new a097979830d 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 19954704c49 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new ccc45e76c80 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new 6e9459f5ca5 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 70c95762fa0 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new bef349af329 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new f41619a8a4b 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new c7321346c4a 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new af258b37509 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new cd88922cc32 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 8a076dd8191 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new 8b88998bd17 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 856bbd19a31 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new e44d2a4e659 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 24df5d86e1b 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 98d46f5f7b0 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 58e2ee289c8 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new cb2335ae92f 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new d30d9488e62 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 544dba220cc 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new b9dad0cee67 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new 26b3aa5060c 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 3551fca7b2c 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 398f49c81e9 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 14ca63aba96 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new ff905bf0325 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 3f909510b69 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 133b3b328ab 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 31049829a50 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 7a8f7648438 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 5d9dc3f78d6 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 4616aac39b1 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 901d58d9791 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new eaf5bec77b6 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 4a82aa07adc 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 089a0cb13fd 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 4441ed25cca 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5bfd80fac68 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4528c0624fe 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new ea4f077d71b 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7ef0cf2fcc3 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new ad34034d819 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ed0023294bb 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 52234a0c5eb 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 317c1eef185 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 0c0b77ff9c3 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new d429974ea64 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 61eeb1032ad 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 27bd0693541 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new e7966d13b8f 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new bccb1c59f6e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 9fa26186a33 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 018716eaac3 127: force: #27: : Failure after baseline build: no new commits new 46491eb352d 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 5d793451787 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...]

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 (2014be27eea) \ 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 1764 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 35316 -> 34964 bytes 04-build_abe-gcc/console.log.xz | Bin 203656 -> 204068 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9884 -> 8536 bytes 07-build_abe-glibc/console.log.xz | Bin 242448 -> 242292 bytes 08-build_abe-gdb/console.log.xz | Bin 34996 -> 34748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3792 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3076 -> 2752 bytes 11-check_regression/console.log.xz | Bin 4040 -> 5008 bytes 11-check_regression/mail-body.txt | 5 +-- 11-check_regression/results.compare | 7 ++++ 11-check_regression/results.compare2 | 61 ++++++++++++++++++++++++++++++ 12-update_baseline/console.log | 68 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 7 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++--------- results | 2 +- sumfiles/gdb.log.xz | Bin 11924 -> 14608 bytes sumfiles/gdb.sum | 19 ++++++++-- 27 files changed, 148 insertions(+), 69 deletions(-) create mode 100644 11-check_regression/results.compare create mode 100644 11-check_regression/results.compare2