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-arm in repository toolchain/ci/base-artifacts.
discards 090d160c29f1 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 50045b96b953 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 20532bff82ac 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards da1f19a705c9 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 4e01f3501ccf 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards e02963839ba6 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 3dfe7c09e159 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 2bbc347bde38 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 51f9be6d9ccf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards bfde7589bb2f 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 9a2dbe92a38f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 6d51debbb828 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 5cf37d676d16 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 057724b1e35e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 631c0cf04723 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards e9d593c65fdd 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards edcb893f5de7 121: force: #26: : Failure after baseline build: no new commits discards 62c4a627f354 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 9bc991d0a65d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 18579ddf274f 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards cc39fde7028c 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 621dc9b12a5f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards f82fe94c0f2d 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 97153be525c9 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards b16cdda49d1c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 9ce1942e4b69 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 6fbfc7c7fa1b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards fb4a197ea1ab 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 13e0c268ebf2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards cd7af6475ae0 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 373b41504adb 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 9104da9d2837 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 071b4d46acea 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 33b8e1d234b8 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards a160d566b3cb 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards b395f059bfbd 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 3cdfd0995bda 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards 2f3d5f6bc8e5 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards 15a04fe24f07 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 58eeb703b460 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards 73de783ab917 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 3cd0643aa9f2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards a230646d4f3f 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards ea3b5c516829 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards 16aefb88a254 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 80bde34e7f09 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 4b0611191504 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 72001c02689e 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards ebc78ff55f07 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards eeac12c58643 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 346813260c7d 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 3a6ec04db157 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards 7c25567c3eec 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 7dfbc8e2f2ba 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 40ee9f2facd8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards eddaa635a37a 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 6a2784fa2bd9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards adfcb10c9177 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 42daccd496cc 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 6c78c2c440d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 82419aac2d03 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 07e23abf5c6c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards 06e5b083c7bb 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards 6482dc6a43ea 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards 07677c0cb618 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards dc51f158258d 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards ecb28d08a6c4 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 4c30f0137a81 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 9bb9f5c26d52 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards 8b9aefe61e9f 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards 2ea4c8c9151d 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 696dc0cfd616 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 66318d8fd972 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 1aa3cd96b1c5 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards 9f5628be5996 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 4aee9cbc08f6 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 7874eff2bd28 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards 917c731203cf 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards 42f8a9689dfb 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards bd47f71c84db 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards 812d6687691b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards cf92c0b97cd4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 1f3ade66d7c9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards fb84ced8f401 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards d305690bfa30 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 59e47b921042 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 3adbe3cb4fae 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards fdf93d178751 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards e64556752313 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 359aad3c43ca 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards ac8e50d5ba11 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards b7d236506cbd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards 84bdd935f70c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards 9d7228c4f430 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 4cc16bf36db1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards e98c21c1744d 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 64eb3bf15963 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards 56f491a8e4fd 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards b29f14e87431 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] discards a00d4f4524df 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] discards 8f901a61295c 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new 8bf3466af978 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gd [...] new fb9c40a4d459 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new 43c20fa45cd8 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 3666d86746ba 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new 042c3268fdb4 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new a024a10513ee 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 41f68badc447 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 33ef971256fd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 783bd1ac7bf3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new c12ff05ae0f5 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new 61c69f532a42 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new c51422b4aa90 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 912069084958 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new 7d5651c3706a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new ee3e650bf56b 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new b0b0dd8e23e8 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new 446d17d5eb77 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 41d9f84831b5 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new f5d061f66b18 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new 785cb3ee5258 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new 0b76ce3e2b35 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new d1952ff88172 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new e977ba8f3513 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new e794bdb6a176 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new f72bdeee05f7 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new 4aea8cc3106e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new d53206bcc2f2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 4a2a6c65ba8f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 3c9e1608c3e6 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new 53a7b7954cff 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 2d7bf98bbcb7 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new aa7bd43f1b17 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 01eb13ecbeec 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new 043a0496207c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new 3460b715b8e7 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new 047676ae0817 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new 765aca06e3cc 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new a13decf55288 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new ce5e3c861c2e 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 70cb8ac897d1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new 22bfde27a9ec 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new aca703e1b6d4 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 9489f38c424b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new 9b969fad3525 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new ae877c697a47 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new e664aaef3ab0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 1921944aa704 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 00fc7e0083a7 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new 73caff62771e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new db532b55f822 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new 900e078ea0fd 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new 5347079e8975 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 292e5f0b0edd 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new b153f5362810 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new 8c4c22b04d20 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new eaf1b2281060 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new f46ee4b8823b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new 271350d53076 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new d44df8d070ba 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new ca47f532249b 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new 1140a0552661 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 6a8639ef0114 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new b7c6d80b33d1 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 82ef1b75797e 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new d1979672df95 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new cf3f7cdd850c 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new 3ca6f48f2e9a 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new ddf59345a8af 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 573453f2bc41 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new ef2fcf008d44 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 4322f6fe3aed 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 8e15be964670 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 5592e2338917 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 8bd3716e7304 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 40333a07fe42 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new de654fcce8f9 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new a38648668796 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new e87898019f62 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 4ed39b880ca7 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 820ee632749b 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new b8c200e9ac6b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new fe1ed8dd8df0 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new d5c4dd7c8ae5 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new d2729fa74654 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 5518d7dfef6c 121: force: #26: : Failure after baseline build: no new commits new c42ff80abd8d 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 3676796d448e 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 3ac9702e4d40 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 6df11d6745f9 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new cc514fecdce4 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 79992d1f7a88 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new cf6eded33239 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 7c8c0e313bcf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new e1deb34fd70f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new c3607484e4d8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new a2b3577efbfe 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 20bcb68b252f 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new f0af3b7c4c0e 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 46a5f0da8b52 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 30c07fa204d7 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new d58bdff50b41 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new f9f8334e9bee 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/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 (090d160c29f1) \ 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 2072 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 49356 -> 49572 bytes 04-build_abe-gcc/console.log.xz | Bin 236412 -> 236344 bytes 06-build_abe-linux/console.log.xz | Bin 8480 -> 8740 bytes 07-build_abe-glibc/console.log.xz | Bin 232780 -> 233120 bytes 08-build_abe-gdb/console.log.xz | Bin 47332 -> 46644 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2784 -> 2760 bytes 11-check_regression/console.log.xz | Bin 4404 -> 5156 bytes 11-check_regression/results.compare2 | 4 +- 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/changes-list-long.txt | 46 +++++++++++++++-------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++-------- manifest.sh | 38 +++++++++---------- sumfiles/gdb.log.xz | Bin 14444 -> 14436 bytes sumfiles/gdb.sum | 4 +- 24 files changed, 111 insertions(+), 95 deletions(-)