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 dbebe066674 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] discards 3598a466feb 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] discards c403e29c6e3 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] discards 25b6ab75496 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] discards ed11aa8a6fc 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards cf7997c7bd8 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 13e9850265f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards fad5c17ffaa 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards 14f34bda315 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 5afac8bcf56 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards e0ffe0861dd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 6a70c77d780 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards a9e2d18d459 121: force: #26: : Failure after baseline build: no new commits discards 41a3545c10f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 0677a298403 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c8b4b322b76 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 73563d7fcb5 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 12fb0e3125a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 529398eea34 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards eb92b5e8115 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7e8af6bcf4b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards c1a0548127b 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards eb20b2f0b69 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 8dff3312e2f 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 690a47b5146 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 9e42b36bd0c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards e3c54df5c19 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards b0f90d66856 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards e04f22d7d26 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards de4df5f4394 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 11e7eb300aa 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 7745935f9c7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 9b4aef5f65c 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 8b290475498 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 930aa1e92f6 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards cc6cd9c652c 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards b93895ec458 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 348c9d3a4e1 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 91b3843d462 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards cd4d3043c5c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 50a774d0666 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 4094d7c20fb 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 10350797161 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 3ccf2b086a0 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 71ba9498329 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 6d0e306a0b3 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 4cc36ed1544 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards ebbe61dd7ac 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 8b9866ee65f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 67c45b33dc4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 6cb82f88f3f 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 7257dad943e 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards b77b4751533 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 7efabeae118 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 62c244c7118 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards cf3a51b0d64 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 3298bea36a4 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 4bd8cef25d4 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 737c1462b03 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 1d5b436088f 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 52bb6d05a96 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 9a907ed995e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 4981007799f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards e75001f84f4 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards b793c23666d 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 4e75ff54415 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards b5fdeba2f51 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 90417197842 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 02e1dbc7bd0 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards f8c319b7160 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 4c85902431b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 0d53a4b937c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards af2a222c454 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards c05b61eb3ba 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 5b829774c28 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 58b1bf4fed5 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards d10fe1c4136 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 8d9f1066c22 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 3fafbd3a054 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards b38de214e11 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 4d3bf01fa4d 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards d034f128e85 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards bfb83afe69c 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 35dfac1442e 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 5bc21117df6 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 253637829ff 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 9fd604e8b0d 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 6b736f18980 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 379e2835fd2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards fc222bfcc43 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 4587ecc0916 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 128d92ef7b3 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards c0edde7c1af 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 475fddffd28 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards a365a62ff05 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 1af7f1a9131 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 65bde5bc9d3 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards cc0c6f7faa2 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 58b57e57a2e 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 7cbe9ee8f5a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 67e2354c1a6 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new c61047bd065 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new c64cb16afb5 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 355989a38d9 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new a6c681d9c27 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new fa8224aa1f2 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 228b0c68d5c 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new fc8450000db 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 4b21fd7313a 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 81f63ca427d 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 51b586a8527 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 57bc5dccd42 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 3fa5ad4a5bc 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 4f7efe6d897 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 40ff1fdce38 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 111493841e4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new a770e42874a 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 4765257052a 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new b019579283b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 0dc774965e3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new fbf53982965 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 5d4f0f97206 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new d8c9dacb006 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 91cdaf15401 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 0976e535ffb 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 88759fe0342 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 481e9637d7f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new c5bab59edbd 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 37bec791a41 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new b748451ff45 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 69793bd60f4 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new b548fba4507 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new c4dbd150c42 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 46faf7ce9af 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 9e63aae1a1b 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 8edb37c7d78 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 97af98b5cd4 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new b2f42d2f7ec 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new c3ae8bae6c3 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new c681b93379c 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 5129c0a7e11 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 9ffbd0cd255 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 6465ccc6b45 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 04816d697b6 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new c6818468565 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 07ad76c6383 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 00822fb3e93 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 4ea796c03ee 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 9965a465fec 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 95e18701034 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new e8c54418763 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new ca0d51f1096 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 4e84cb15ec8 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new f6468ca907b 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 2f1acee0dff 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new b87b0c0213f 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 1fe2bba32a0 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new fab54c118c2 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 44ad35548e1 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 8c9e6a03168 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 67587602287 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 6f344e4aa8c 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 4ffffaf406c 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 57706eda5da 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new d40e3acd169 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new da667ceecc0 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new a0a440b262f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 33f1b7a593f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 9c325b27712 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 80f24429c26 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 46e7ffcf26f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new e42911c42a2 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 2416d58de51 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 74d50ca1088 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d1a871b2d36 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 5e8f6591b5a 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 89844d3060e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 1dba6e56f94 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 0a3553ca996 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 1bda8a0fc98 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f3643e15d14 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9d061c36c6e 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new e83a4528aca 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 707e5295f66 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 817152559b0 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 6e1e414ae5d 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 84324bddbab 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new ca225985c46 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 610f311fb24 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1030d4792cf 121: force: #26: : Failure after baseline build: no new commits new f4d011201c7 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 99b7cf2ae3f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new bfd8de60c33 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 3cca2620e00 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 097e488279f 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new a1c2cd5caf6 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new 3f4f6906e9a 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 8ac56c77108 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 4d9794c4c90 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gd [...] new 1aefa1f665f 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gl [...] new 0c2ae2a6c6f 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gc [...] new 331a2218435 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gc [...] new 390112ff174 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gc [...]

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 (dbebe066674) \ 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 2032 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 48832 -> 49164 bytes 04-build_abe-gcc/console.log.xz | Bin 235708 -> 237720 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 232956 -> 231948 bytes 08-build_abe-gdb/console.log.xz | Bin 47468 -> 47568 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2864 -> 2728 bytes 11-check_regression/console.log.xz | Bin 4600 -> 5068 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 60 +++++++++++++++++----------------- 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 | 56 +++++++++++++++++-------------- mail/changes-list-short.txt | 2 +- manifest.sh => mail/last_good.sh | 0 manifest.sh | 38 ++++++++++----------- sumfiles/gdb.log.xz | Bin 14440 -> 14448 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 94 insertions(+), 88 deletions(-) copy manifest.sh => mail/last_good.sh (100%)