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 4be8c788ccc4 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...] discards 6cb87958e4a2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards 9884db755da0 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards e863664a94f6 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 596964da860b 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 51e9f80f9321 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 5b905b0a9a70 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards cd4c715550de 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards e1532fdbb6fc 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards b2903268a30c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 02558bcb44ed 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards fdc1406e5186 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 7fbfdfc836a7 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards d7dc948fca29 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards c73ea77ca354 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 784996a26ba6 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 91cfcafe6cd5 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 10425634ac94 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 516bc929b91e 121: force: #26: : Failure after baseline build: no new commits discards ce8b19569a07 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 157a818adf7d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 592daaa61864 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 0e24906b7dc3 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 509ea5856898 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 98564d507ffb 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards bff703551579 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards bfa420b075a9 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards e9eafb230721 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards df06dd7b6fc6 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 73cf7b97adcf 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 7fcf81497654 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 462ee3d69fc2 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 432e57e1c96c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards dbfac6f43096 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 931192cb22d1 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 0f953cf2ae35 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 43acf098b379 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards b569507234be 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 808b04f36b90 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards a647740b2a87 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards 62d0828d491a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 63409d1ea467 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards e47d26f0c991 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 6bbb2113a8d3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards b9537bb09304 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 9c0fe1e7d304 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards c9e11fc21fcf 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 3892206fd7ad 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 4ff60f965e48 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 085f8db4c7d6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards 0bf97dfd86ee 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards 6ef3d279b723 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 376f2280d432 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 3d3b78bedd8b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards ddce6d010579 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards f1d055b46b4a 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 546929a510b1 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards baa0d94614dd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 216a20fbcf45 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards 0ca5dcbc3f74 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 3981b902c748 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 32b38d4924a6 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards cf7469892586 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 68d658b81482 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards bc56eb1fa9e8 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards 25a171d40a67 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards 22cd425aa7e5 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards bda27e28e289 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards 20582ebad288 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 1da943c6e9cb 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 2f864923ba3b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards 03ba639b6cf5 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards 0aefd4b0d9fb 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 1accf83478a2 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 2cadc82af358 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 5648e572aa86 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards b9047781a7bc 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards c41ca310e83e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 936cb9a82109 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards ec7dc4cea767 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards f5df529c1504 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards 6cdded078304 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards ca710f6dfb01 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards d6f6a339422b 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 0cdebd4ccecb 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards 34db341c95db 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 29fe86cad227 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 41392b5f437e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 4f9593f0d54d 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards ee2a81df7b96 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards 8f57e4c9d124 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 9c9f44ec62c3 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards a8edca4e70a4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 42a9055997ea 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards b5ed899631f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards d5e8c7738e41 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 0cc15a145fb7 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards 5f0c4d0f7918 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 9ee6ebcaee76 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards a7adcde9a71a 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards 32c2a6a7417b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 68d633188d91 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 1a320ba9d4b3 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new e8f1857d8127 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new 5c4accbc205b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 804ea78032ad 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 808d7fc8e632 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 1261c0d8b502 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new d5392fef6ea4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new 776c7c0820f2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 4faec2c57b23 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 83ba67772ea1 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new 9bf117c1c97a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 338de21b1940 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 7188236cbc83 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new d55003ed1655 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 91d6c9af059b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 3f0db2db5eed 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new 4e86b436ffca 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new e88e03785df8 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 3c54f1a1f08e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new d043d728b9e5 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new 4f1f512e24af 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new 9c7e03859037 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new b083eff5eb4f 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new bfd3da78c850 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new b63e0e195848 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 82498b4454eb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new dba56efbb428 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 39d2e4cf36d7 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new deb82cf543fb 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 542477775d38 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new c06219f816ca 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new 06f9aa800e89 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new aeb24f8d4c2a 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new ab8ed3f6b01f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new a5d2194944bf 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new 0d85d4d65255 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 482d4e8880fd 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new b8b6b307c076 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new fca10c3319a5 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 6e632250e701 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new 3fe25ff863bb 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new 494eb3f3bc01 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new 1eb02cf18cbf 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new d967baefaf23 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 093fb50da2d4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new d5eb504c07fb 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new fe22079ab332 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new e47134bfd9cf 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new 92ac5e076430 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 8109eb6736de 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new 14f8186f87a0 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new ab45ed164786 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 98a50a55528e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 286e5911f999 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new b527a52831bd 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new ed22123e9c65 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new a17aba3f64f0 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new abc6bdc934ae 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 634d97b62bfd 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 82203f512417 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 14372617cd79 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new d6938a4e757c 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new 14b6206f42e0 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new 7f53dab842e6 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new cc4ef1bb1f6e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 7a6747dc3efd 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 45f91304b136 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new ae5a92249a7f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 77aa80c762d6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new f37e721c599c 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 76d262284891 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new f0c08b5e5e87 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 95c58f762875 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 7097578df87c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new c10fc661816a 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 0bf8f13ea341 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 37fbf82ab436 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 9566d2cb56ae 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new ee9c407a4798 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 62c2ff2ee844 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new fb911319f8c4 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 51934116dc62 121: force: #26: : Failure after baseline build: no new commits new 34313a409c23 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 916382eb9b6c 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new b3f27f0053f1 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 0e9e72627cca 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 2990926a79a2 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 3072ecbe1cd2 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new bc62e789001a 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new ff97e6d34b8d 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 1768200a4d7f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new f3d577d41435 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 8310e7faf58d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 0c344f564ba1 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new e58ff801b3b2 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new ec8372b5e548 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new c50777f21692 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new fd39919f69bb 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 43d4299e3d04 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new e2ed3e053a22 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...] new 482e6280d794 140: onsuccess: #47: 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 (4be8c788ccc4) \ 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 2076 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 49760 -> 49416 bytes 04-build_abe-gcc/console.log.xz | Bin 235172 -> 235304 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8724 -> 9480 bytes 07-build_abe-glibc/console.log.xz | Bin 232148 -> 232504 bytes 08-build_abe-gdb/console.log.xz | Bin 47316 -> 47480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3336 -> 2964 bytes 11-check_regression/console.log.xz | Bin 4596 -> 5052 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 42 ++++++++++++++-------------- 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 | 50 +++++++++++++++++++++------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 34 +++++++++++------------ manifest.sh | 38 +++++++++++++------------- sumfiles/gdb.log.xz | Bin 14444 -> 14432 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 102 insertions(+), 90 deletions(-)