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 bf3bec12f14 127: force: #27: : Failure after baseline build: no new commits discards 32396829936 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ef24b14f91e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 4da674099a7 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 6d1cf9dac0d 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 3e51cf9bbce 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 2d0506b2d72 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 041902c9579 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 363c5c9188b 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 6428b9e90f8 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 96f1963ddfa 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 7b3b5ad2001 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e267a4bfcc2 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 00f5fbcd4ec 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a8e8f534ce0 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 73dd078c642 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ded5f0573d1 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 75509c474d1 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 3d711e37daa 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards aba6544afa8 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 1d9ac0bff9e 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards ba3a7275432 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] discards 78b0709bdd7 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 29ef675bf88 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] discards ac18600442d 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] discards 727638960e6 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] discards 12063313878 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] discards 1f8b4a70b45 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] discards b523485b34c 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] discards c96f11812e3 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] discards 8d10a17e0d5 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] discards 9a37954a35d 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] discards 6189d701dd3 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] discards 6aa10ec8c57 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards e8dd8c73765 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards ce8df79a1fa 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] discards 226fb7afe65 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 8f74dd31fdd 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 0c8e3f20211 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] discards ef76228d24d 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards c9fd886945e 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards c8aaee03300 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] discards dc6b8b439dd 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] discards d6ab0efb3b2 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards e181f3ebc6f 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards d99c77be83f 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] discards b89b87f1224 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards c5bf6c82369 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 78ed5e20c2b 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 2ccce22d3c9 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards aae718a35c0 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] discards 1eda85ec53e 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] discards bc1eff16c86 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] discards 66296c211fd 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards cb1b2e6654d 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 444506f8cf2 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] discards 5a12cd5eead 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] discards cd0644cb9ea 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] discards a1cdb1b4823 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 28adf79126b 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] discards 3aae7e308ea 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards cc2b6d7fece 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] discards cc4529b5774 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] discards f208d53d1fe 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] discards 59dca166421 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 7f3259f8ae5 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] discards f5d8ef02e3e 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] discards f9040b700e1 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] discards c17c1b1f3ea 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] discards befe0b88eac 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards e4fa956cfc3 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards d4ad047f1f1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 01d0e52b7b9 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] discards 9c8c20c6066 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards e96b47144ba 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards fb40931d277 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 4d41d80b2d9 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] discards 37ef82075c2 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] discards 2b71054d782 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] discards 40959f4b766 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] discards ad502572639 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards e7bd8d53418 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 6e4fbb70516 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] discards f95e345aca2 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 3354cbeae72 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 8b79af23729 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 859aa3c8107 41: onsuccess: #51: 1: Success after binutils: 12 commits discards 62c327d3c62 40: onsuccess: #49: 1: Success after linux: 219 commits discards ac54dac0339 39: onsuccess: #48: 1: Success after glibc: 2 commits discards cd977ba6416 38: onsuccess: #46: 1: Success after binutils: 26 commits discards ea51b5d83a2 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 6d688266b1b 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 20ab8601f86 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards fe6bc565882 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 97c7ea9d717 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] discards c7825971591 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 15a01cb05ba 31: onsuccess: #38: 1: Success after linux: 12 commits discards 6022d72008f 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 8a64e46c146 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 4ebaaac3450 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards c2e4687858f 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 1ac51c8bcf5 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new fb084d6352c 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 680974b07ab 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new ca63d03fd69 30: onsuccess: #36: 1: Success after binutils: 18 commits new 79a575234ad 31: onsuccess: #38: 1: Success after linux: 12 commits new b49f0e41b6f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new f008f32aedc 33: onsuccess: #40: 1: Success after binutils/gcc/linux/gli [...] new 89b4621f295 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new a57ae854229 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 8fd05c233b0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 750eea8a6bf 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 02785b88bf7 38: onsuccess: #46: 1: Success after binutils: 26 commits new c8f5f78a986 39: onsuccess: #48: 1: Success after glibc: 2 commits new 81249fa7a96 40: onsuccess: #49: 1: Success after linux: 219 commits new 34687773cf0 41: onsuccess: #51: 1: Success after binutils: 12 commits new 6633c87d616 42: onsuccess: #53: 1: Success after linux: 3008 commits new 9d466cdda6f 43: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 259ccf57113 44: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 2318e13c562 45: onsuccess: #56: 1: Success after binutils/gcc/linux/gli [...] new 54d857c8c0b 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 53a43c5cd4d 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 487d075d749 48: onsuccess: #59: 1: Success after binutils/gcc/linux/gli [...] new 23717fe11e9 49: onsuccess: #60: 1: Success after binutils/gcc/linux/gli [...] new 0c796b48a47 50: onsuccess: #61: 1: Success after binutils/gcc/linux/gli [...] new b9f58cdc94e 51: onsuccess: #62: 1: Success after binutils/gcc/linux/gli [...] new 2070d55f6ef 52: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 2b57094abe3 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 6f2e931491a 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 7915c19e3e8 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb [...] new cd3253ebc8f 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 7222a82d007 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new a784fb7a009 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 4af083bb590 59: onsuccess: #70: 1: Success after binutils/gcc/linux/gli [...] new 0fad34f0fbc 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb [...] new cb8a4fd7817 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb [...] new 3eabddbaba7 62: onsuccess: #74: 1: Success after binutils/gcc/linux/gli [...] new d1780c5b33c 63: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new e92534bfd13 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb [...] new 093ec7df738 65: onsuccess: #78: 1: Success after binutils/gcc/linux/gli [...] new 0bb6c97956c 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb [...] new 5a22c2fe951 67: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new f5ccd067471 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb [...] new e822d6d07c2 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 167ff423f93 70: onsuccess: #83: 1: Success after binutils/gcc/linux/gli [...] new 4c6c3aaa76e 71: onsuccess: #84: 1: Success after binutils/gcc/linux/gli [...] new ed71645ca53 72: onsuccess: #85: 1: Success after binutils/gcc/linux/gli [...] new 87212ec78ce 73: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 34e03cc75e7 74: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 5f2ec339183 75: onsuccess: #88: 1: Success after binutils/gcc/linux/gli [...] new 747d0718a9a 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb [...] new 107e33bbda8 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb [...] new b071a622eac 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 345d1aac61d 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 6578202a241 80: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 195fefb4fea 81: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new c781b42a511 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb [...] new 0fe8ea58eb3 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new e89018dd1e6 84: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 871cd758966 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb [...] new c301880ee01 86: onsuccess: #99: 1: Success after binutils/gcc/linux/gli [...] new 4f2bce2e4e0 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 5a2e38cb161 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new be9d34e3a01 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gl [...] new 7fcde03b719 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 43fea7dac28 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new b79f523116f 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gl [...] new a81c9d481cd 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 476cd4e3a5f 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new e8ba15158c1 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gl [...] new f75dc9c4d7f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gd [...] new 8b1609415d2 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gl [...] new 92bec2705d8 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gl [...] new 73bf356be7a 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gl [...] new d4217517b01 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 [...] new 6b7a70e21a8 101: onsuccess: #116: 1: Success after binutils/gcc/linux/g [...] new 4d64dfd0d1d 102: onsuccess: #117: 1: Success after binutils/gcc/linux/g [...] new 94f7591ceb7 103: onsuccess: #118: 1: Success after binutils/gcc/linux/g [...] new 0a69782d6cd 104: onsuccess: #119: 1: Success after binutils/gcc/linux/g [...] new 1fca9b3bcb7 105: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new e461cb0e439 106: onsuccess: #121: 1: Success after binutils/gcc/linux/g [...] new 7563a6a50ff 107: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8fab955e35b 108: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new ad9e6102252 109: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new ce15274f174 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new ede6f4f0f13 111: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 85378294026 112: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 9d3fee535a4 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new d30b1c9ef92 114: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7ba2d5cab00 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 170d2f2aab1 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 74758a2a2b7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new a9cdb1056ab 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b9707e98e19 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 35167f932ba 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new e0a0eb86cec 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b699646ef34 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new fb0b29ef802 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 614c5decd3c 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 71cf80453d7 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 937068ad406 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 7c4993fd421 127: force: #27: : Failure after baseline build: no new commits new 2014be27eea 128: onsuccess: #29: 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 (bf3bec12f14) \ 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 1932 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 3444 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 39156 -> 35316 bytes 04-build_abe-gcc/console.log.xz | Bin 204728 -> 203656 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8800 -> 9884 bytes 07-build_abe-glibc/console.log.xz | Bin 245664 -> 242448 bytes 08-build_abe-gdb/console.log.xz | Bin 38932 -> 34996 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3792 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1348 -> 3076 bytes 11-check_regression/console.log.xz | Bin 2564 -> 4040 bytes 11-check_regression/jira-body.txt | 2 +- 11-check_regression/mail-body.txt | 10 +- 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results.regressions | 2 - 12-update_baseline/console.log | 38 +-- 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 | 10 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +-- results | 4 +- sumfiles/gdb.log.xz | Bin 0 -> 11924 bytes sumfiles/gdb.sum | 396 ++++++++++++++++++++++++++++++++ 28 files changed, 455 insertions(+), 58 deletions(-) delete mode 100644 11-check_regression/results.regressions create mode 100644 sumfiles/gdb.log.xz create mode 100644 sumfiles/gdb.sum