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 b6df4e0e09 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards fad1eeb50b 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards b266f36017 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 54f1226c2a 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 03f2041c9e 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 239a873593 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards fdb87e113d 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 8ecb5a67fb 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards cd16697836 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards f9ce318002 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 26cb6a64ab 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards b1e6a82493 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 3dfbcdcdde 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards b62d3458f0 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 51b100a80e 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 20efc7f367 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 50c326f019 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 9b34ea33ef 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 1071fd9334 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards 2699703211 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 1ab0c13217 121: force: #26: : Failure after baseline build: no new commits discards ae7d1f46fc 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 113c6c4072 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards f6f3fc5d49 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards a2f4a4f909 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 247896468b 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards c398b4f9ff 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 1e565ce61d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards a5adb39700 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 1b634eb513 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards ba1dcefca7 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 6a12ac6c96 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards b7b099cc6b 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards fa84470644 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 8529650f00 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 374b959bbb 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 7739de45be 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 6026f0c8bd 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards eab90fe199 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 4b2fd705a4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards f93842ef7e 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 05b8a79b92 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 2077ea3c91 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 2a0ee1c7c5 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards b1342900ab 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards b3c8a13a8d 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 3df7ee3cae 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards f51681f084 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 07a7a3469e 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 7a821f7210 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards a9b9eae3e7 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 58214d8d01 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards c633e797de 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 6447690537 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards a2c837cb1d 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 2da7090e98 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 9f382aa9b7 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards f58d5045bb 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 6afdd829cc 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 0d8fe66301 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards ac47f8d071 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards f5b612c066 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 7340ce1277 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 6cf803e0e8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards c2e1370662 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 0255ae474b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards e24147eaa0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards ddfadd5227 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards dc7465be8e 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards a54fd6b32c 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 47092c9298 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 3a75f53fe7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards e4791af332 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards c65f85ae33 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards e7b755dd43 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards c3e2d31b80 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 65558abfaf 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards b01b88a62b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 9265782af7 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 9e73dc8694 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 03597e07ae 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 7843fd76a3 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards f13043f7e8 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards d0bad4878f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 190a677944 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 897ba27127 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 0486f64d7d 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards a9d3ec2920 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards b38e0cc3a9 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards d3d9938394 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 7eef4ccd50 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards cf02fa59ee 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards dd024b8e7a 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards a437fefd75 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 7f7e72e34a 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards afbb0c365c 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 21e4adc581 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards 0d0b780ba3 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 7dcc9d59ae 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] discards 58f1b99990 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] discards 9e74685e5b 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] new 493e17c9b7 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] new 1af0a608b5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] new b8fa68c998 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new f67025f853 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new f617eb4ccc 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new a95215c96d 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new cdc9e306d4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new e3c0a70a25 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 149cd80501 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new d62717348d 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 0f02550c32 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 47c07e5667 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 09caead614 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new b495772833 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new c579bedef3 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new b48fdc4bda 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new a835a11705 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 9b1a6ba705 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new a9ff2c3368 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 2fe04640b9 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3698a8681f 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 2991bd1e2e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 0e3f28b468 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new e73bb2f035 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new b6d9e56528 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 1b763e700c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new cdc3f3c707 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 9303dcd71b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new f108fdd450 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new cd623c62da 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 411dccc9dd 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 9b625ede91 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new bd9fc6351a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 86f6b8a3de 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 3cb906aefe 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new feaebdff13 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new ca00c7ded7 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new cf993f46d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 7a0aa4b6e9 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new e911a7b06d 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 030b72f6fc 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new ad3d970b29 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 7283d94bc8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 4e54c1b4cc 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 7edcb8c652 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 54a44ad1c1 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 3c6a952882 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 9274190edb 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new d4e2502dfd 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 014f47bac7 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new bab1417f19 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 3374ab5da7 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 61f96dc256 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new e472b35260 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new ea18e51fac 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new a3777cb181 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 9deec5faa2 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 4d9353f42d 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 496f0902b5 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 4f87c60433 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new f00cccc7a1 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new ce0653b118 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 2d68960632 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new a89a0779c3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new f787edba4c 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new f579ebb02c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 0ea08fbf40 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new cde22ebdb8 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new a1211956f9 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new cc8504e29f 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7dfac079e5 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new af8907e7cf 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 9c3655a371 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 9e70a81ad0 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new 4be49186a3 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 79d9b7db0a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new ea67d6f5f6 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 470e7ad9e9 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new b5f46a87b7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 9b97b47543 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new ba06f271ce 121: force: #26: : Failure after baseline build: no new commits new b3a41ea191 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 38af5b0f67 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 4c470b762b 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 534ad43ee3 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 7cded38621 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 11ba1efefb 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 1e28f88920 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 1038edc958 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3d14e063ff 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 5bbb5b1658 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new e8c7d79711 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 16d84faecd 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new e23a17872f 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new ed01db94cd 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 454de4f22a 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new c781328801 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 093907cec2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new f5b0700fad 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 1e206eaad8 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 96b0727947 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 5f5f3b6445 142: onsuccess: #50: 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 (b6df4e0e09) \ 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 2100 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 49336 -> 48704 bytes 04-build_abe-gcc/console.log.xz | Bin 237072 -> 235236 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9412 -> 8504 bytes 07-build_abe-glibc/console.log.xz | Bin 232996 -> 232500 bytes 08-build_abe-gdb/console.log.xz | Bin 46552 -> 46524 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3820 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2924 -> 2832 bytes 11-check_regression/console.log.xz | Bin 5048 -> 4644 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 46 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 54 +++++++++++++++------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------ manifest.sh | 32 ++++++++++---------- sumfiles/gdb.log.xz | Bin 14252 -> 14252 bytes sumfiles/gdb.sum | 4 +-- 25 files changed, 94 insertions(+), 102 deletions(-)