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 482e6280d7 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards e2ed3e053a 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 43d4299e3d 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards fd39919f69 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards c50777f216 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards ec8372b5e5 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards e58ff801b3 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 0c344f564b 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 8310e7faf5 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards f3d577d414 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 1768200a4d 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards ff97e6d34b 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards bc62e78900 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 3072ecbe1c 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 2990926a79 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 0e9e72627c 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards b3f27f0053 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 916382eb9b 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 34313a409c 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 51934116dc 121: force: #26: : Failure after baseline build: no new commits discards fb911319f8 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 62c2ff2ee8 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards ee9c407a47 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 9566d2cb56 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 37fbf82ab4 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 0bf8f13ea3 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards c10fc66181 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 7097578df8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 95c58f7628 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards f0c08b5e5e 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 76d2622848 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards f37e721c59 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 77aa80c762 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards ae5a92249a 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 45f91304b1 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 7a6747dc3e 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards cc4ef1bb1f 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 7f53dab842 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 14b6206f42 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards d6938a4e75 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 14372617cd 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 82203f5124 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 634d97b62b 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards abc6bdc934 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards a17aba3f64 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards ed22123e9c 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards b527a52831 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 286e5911f9 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 98a50a5552 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards ab45ed1647 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 14f8186f87 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 8109eb6736 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 92ac5e0764 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards e47134bfd9 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards fe22079ab3 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards d5eb504c07 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 093fb50da2 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards d967baefaf 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 1eb02cf18c 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 494eb3f3bc 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 3fe25ff863 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 6e632250e7 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards fca10c3319 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards b8b6b307c0 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 482d4e8880 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 0d85d4d652 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards a5d2194944 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards ab8ed3f6b0 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards aeb24f8d4c 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 06f9aa800e 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards c06219f816 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 542477775d 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards deb82cf543 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 39d2e4cf36 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards dba56efbb4 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 82498b4454 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards b63e0e1958 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards bfd3da78c8 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards b083eff5eb 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 9c7e038590 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 4f1f512e24 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards d043d728b9 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 3c54f1a1f0 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards e88e03785d 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 4e86b436ff 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 3f0db2db5e 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 91d6c9af05 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards d55003ed16 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 7188236cbc 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 338de21b19 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 9bf117c1c9 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 83ba67772e 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards 4faec2c57b 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 776c7c0820 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards d5392fef6e 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 1261c0d8b5 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards 808d7fc8e6 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 804ea78032 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] discards 5c4accbc20 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] discards e8f1857d81 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] discards 1a320ba9d4 40: onsuccess: #47: 1: Success after binutils/gcc/linux/glib [...] new f9f873db80 40: onsuccess: #47: 1: Success after binutils/gcc/linux/glib [...] new 9e74685e5b 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] new 58f1b99990 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] new 7dcc9d59ae 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new 0d0b780ba3 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 21e4adc581 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new afbb0c365c 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 7f7e72e34a 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new a437fefd75 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new dd024b8e7a 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new cf02fa59ee 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 7eef4ccd50 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new d3d9938394 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new b38e0cc3a9 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new a9d3ec2920 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 0486f64d7d 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 897ba27127 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 190a677944 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new d0bad4878f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new f13043f7e8 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 7843fd76a3 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 03597e07ae 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 9e73dc8694 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 9265782af7 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new b01b88a62b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 65558abfaf 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new c3e2d31b80 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new e7b755dd43 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new c65f85ae33 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new e4791af332 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 3a75f53fe7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 47092c9298 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new a54fd6b32c 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new dc7465be8e 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new ddfadd5227 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new e24147eaa0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 0255ae474b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new c2e1370662 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 6cf803e0e8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 7340ce1277 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new f5b612c066 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new ac47f8d071 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 0d8fe66301 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 6afdd829cc 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new f58d5045bb 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 9f382aa9b7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 2da7090e98 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new a2c837cb1d 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 6447690537 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new c633e797de 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 58214d8d01 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new a9b9eae3e7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 7a821f7210 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 07a7a3469e 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new f51681f084 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 3df7ee3cae 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new b3c8a13a8d 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new b1342900ab 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 2a0ee1c7c5 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 2077ea3c91 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 05b8a79b92 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new f93842ef7e 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 4b2fd705a4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new eab90fe199 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 6026f0c8bd 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 7739de45be 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 374b959bbb 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 8529650f00 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new fa84470644 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new b7b099cc6b 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 6a12ac6c96 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new ba1dcefca7 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 1b634eb513 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a5adb39700 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 1e565ce61d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new c398b4f9ff 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 247896468b 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new a2f4a4f909 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new f6f3fc5d49 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 113c6c4072 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new ae7d1f46fc 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 1ab0c13217 121: force: #26: : Failure after baseline build: no new commits new 2699703211 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 1071fd9334 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 9b34ea33ef 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 50c326f019 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 20efc7f367 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 51b100a80e 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new b62d3458f0 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 3dfbcdcdde 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new b1e6a82493 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 26cb6a64ab 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new f9ce318002 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new cd16697836 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 8ecb5a67fb 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new fdb87e113d 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 239a873593 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 03f2041c9e 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 54f1226c2a 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new b266f36017 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new fad1eeb50b 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new b6df4e0e09 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...]

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 (482e6280d7) \ 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 2048 -> 2100 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 49416 -> 49336 bytes 04-build_abe-gcc/console.log.xz | Bin 235304 -> 237072 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9480 -> 9412 bytes 07-build_abe-glibc/console.log.xz | Bin 232504 -> 232996 bytes 08-build_abe-gdb/console.log.xz | Bin 47480 -> 46552 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3764 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2964 -> 2924 bytes 11-check_regression/console.log.xz | Bin 5052 -> 5048 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 38 ++++++++++----------- 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 | 60 +++++++++++++++++----------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++----------- manifest.sh | 38 ++++++++++----------- sumfiles/gdb.log.xz | Bin 14432 -> 14252 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 101 insertions(+), 101 deletions(-)