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 f9f8334e9bee 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards d58bdff50b41 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 30c07fa204d7 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 46a5f0da8b52 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards f0af3b7c4c0e 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 20bcb68b252f 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards a2b3577efbfe 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards c3607484e4d8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards e1deb34fd70f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 7c8c0e313bcf 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards cf6eded33239 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 79992d1f7a88 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards cc514fecdce4 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 6df11d6745f9 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 3ac9702e4d40 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 3676796d448e 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards c42ff80abd8d 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 5518d7dfef6c 121: force: #26: : Failure after baseline build: no new commits discards d2729fa74654 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards d5c4dd7c8ae5 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards fe1ed8dd8df0 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards b8c200e9ac6b 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 820ee632749b 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 4ed39b880ca7 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards e87898019f62 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards a38648668796 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards de654fcce8f9 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 40333a07fe42 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 8bd3716e7304 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 5592e2338917 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 8e15be964670 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 4322f6fe3aed 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards ef2fcf008d44 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 573453f2bc41 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards ddf59345a8af 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 3ca6f48f2e9a 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards cf3f7cdd850c 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards d1979672df95 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards 82ef1b75797e 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards b7c6d80b33d1 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 6a8639ef0114 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards 1140a0552661 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards ca47f532249b 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards d44df8d070ba 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 271350d53076 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards f46ee4b8823b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards eaf1b2281060 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 8c4c22b04d20 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards b153f5362810 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards 292e5f0b0edd 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards 5347079e8975 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 900e078ea0fd 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards db532b55f822 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards 73caff62771e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards 00fc7e0083a7 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 1921944aa704 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards e664aaef3ab0 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards ae877c697a47 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards 9b969fad3525 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 9489f38c424b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards aca703e1b6d4 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards 22bfde27a9ec 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 70cb8ac897d1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards ce5e3c861c2e 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards a13decf55288 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards 765aca06e3cc 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards 047676ae0817 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards 3460b715b8e7 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 043a0496207c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 01eb13ecbeec 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards aa7bd43f1b17 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards 2d7bf98bbcb7 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 53a7b7954cff 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 3c9e1608c3e6 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 4a2a6c65ba8f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards d53206bcc2f2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards 4aea8cc3106e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards f72bdeee05f7 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards e794bdb6a176 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards e977ba8f3513 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards d1952ff88172 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards 0b76ce3e2b35 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards 785cb3ee5258 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards f5d061f66b18 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards 41d9f84831b5 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 446d17d5eb77 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards b0b0dd8e23e8 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards ee3e650bf56b 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 7d5651c3706a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards 912069084958 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards c51422b4aa90 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards 61c69f532a42 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards c12ff05ae0f5 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards 783bd1ac7bf3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards 33ef971256fd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 41f68badc447 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards a024a10513ee 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 042c3268fdb4 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards 3666d86746ba 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards 43c20fa45cd8 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] discards fb9c40a4d459 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new c2f5f5cb531d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gl [...] new 32c2a6a7417b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new a7adcde9a71a 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new 9ee6ebcaee76 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new 5f0c4d0f7918 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 0cc15a145fb7 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new d5e8c7738e41 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new b5ed899631f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new 42a9055997ea 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new a8edca4e70a4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 9c9f44ec62c3 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 8f57e4c9d124 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new ee2a81df7b96 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 4f9593f0d54d 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 41392b5f437e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new 29fe86cad227 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 34db341c95db 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 0cdebd4ccecb 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new d6f6a339422b 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new ca710f6dfb01 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 6cdded078304 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new f5df529c1504 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new ec7dc4cea767 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new 936cb9a82109 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new c41ca310e83e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new b9047781a7bc 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new 5648e572aa86 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 2cadc82af358 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new 1accf83478a2 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 0aefd4b0d9fb 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new 03ba639b6cf5 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 2f864923ba3b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new 1da943c6e9cb 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new 20582ebad288 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new bda27e28e289 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new 22cd425aa7e5 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new 25a171d40a67 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new bc56eb1fa9e8 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 68d658b81482 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new cf7469892586 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new 32b38d4924a6 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 3981b902c748 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new 0ca5dcbc3f74 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new 216a20fbcf45 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new baa0d94614dd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new 546929a510b1 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new f1d055b46b4a 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new ddce6d010579 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new 3d3b78bedd8b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new 376f2280d432 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new 6ef3d279b723 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 0bf97dfd86ee 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new 085f8db4c7d6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new 4ff60f965e48 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 3892206fd7ad 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new c9e11fc21fcf 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new 9c0fe1e7d304 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new b9537bb09304 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new 6bbb2113a8d3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new e47d26f0c991 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 63409d1ea467 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 62d0828d491a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new a647740b2a87 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new 808b04f36b90 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new b569507234be 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new 43acf098b379 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 0f953cf2ae35 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 931192cb22d1 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new dbfac6f43096 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new 432e57e1c96c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 462ee3d69fc2 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 7fcf81497654 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 73cf7b97adcf 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new df06dd7b6fc6 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new e9eafb230721 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new bfa420b075a9 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new bff703551579 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 98564d507ffb 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 509ea5856898 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 0e24906b7dc3 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 592daaa61864 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 157a818adf7d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new ce8b19569a07 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 516bc929b91e 121: force: #26: : Failure after baseline build: no new commits new 10425634ac94 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 91cfcafe6cd5 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 784996a26ba6 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new c73ea77ca354 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new d7dc948fca29 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 7fbfdfc836a7 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new fdc1406e5186 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 02558bcb44ed 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new b2903268a30c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new e1532fdbb6fc 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new cd4c715550de 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 5b905b0a9a70 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 51e9f80f9321 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 596964da860b 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new e863664a94f6 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 9884db755da0 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 6cb87958e4a2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new 4be8c788ccc4 139: onsuccess: #46: 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 (f9f8334e9bee) \ 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 2088 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 49572 -> 49760 bytes 04-build_abe-gcc/console.log.xz | Bin 236344 -> 235172 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8724 bytes 07-build_abe-glibc/console.log.xz | Bin 233120 -> 232148 bytes 08-build_abe-gdb/console.log.xz | Bin 46644 -> 47316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2760 -> 3336 bytes 11-check_regression/console.log.xz | Bin 5156 -> 4596 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 +- mail/changes-list-long.txt | 50 ++++++++++--------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +++++++++---------- manifest.sh | 34 ++++++++--------- sumfiles/gdb.log.xz | Bin 14436 -> 14444 bytes sumfiles/gdb.sum | 4 +- 25 files changed, 102 insertions(+), 114 deletions(-)