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 5f5f3b6445 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 96b0727947 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 1e206eaad8 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards f5b0700fad 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 093907cec2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards c781328801 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 454de4f22a 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards ed01db94cd 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards e23a17872f 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 16d84faecd 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards e8c7d79711 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 5bbb5b1658 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 3d14e063ff 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 1038edc958 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 1e28f88920 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 11ba1efefb 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 7cded38621 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 534ad43ee3 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 4c470b762b 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 38af5b0f67 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards b3a41ea191 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards ba06f271ce 121: force: #26: : Failure after baseline build: no new commits discards 9b97b47543 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards b5f46a87b7 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 470e7ad9e9 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards ea67d6f5f6 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 79d9b7db0a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 4be49186a3 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 9e70a81ad0 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 9c3655a371 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards af8907e7cf 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7dfac079e5 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards cc8504e29f 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards a1211956f9 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards cde22ebdb8 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 0ea08fbf40 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f579ebb02c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards f787edba4c 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards a89a0779c3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards 2d68960632 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards ce0653b118 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards f00cccc7a1 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards 4f87c60433 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 496f0902b5 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 4d9353f42d 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 9deec5faa2 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards a3777cb181 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards ea18e51fac 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards e472b35260 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 61f96dc256 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 3374ab5da7 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards bab1417f19 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 014f47bac7 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards d4e2502dfd 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 9274190edb 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 3c6a952882 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 54a44ad1c1 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 7edcb8c652 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 4e54c1b4cc 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 7283d94bc8 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards ad3d970b29 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 030b72f6fc 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards e911a7b06d 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 7a0aa4b6e9 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards cf993f46d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards ca00c7ded7 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards feaebdff13 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 3cb906aefe 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 86f6b8a3de 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards bd9fc6351a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 9b625ede91 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 411dccc9dd 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards cd623c62da 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards f108fdd450 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 9303dcd71b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards cdc3f3c707 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 1b763e700c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards b6d9e56528 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards e73bb2f035 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 0e3f28b468 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 2991bd1e2e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 3698a8681f 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards 2fe04640b9 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards a9ff2c3368 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 9b1a6ba705 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards a835a11705 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards b48fdc4bda 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards c579bedef3 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards b495772833 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 09caead614 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 47c07e5667 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards 0f02550c32 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards d62717348d 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 149cd80501 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards e3c0a70a25 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards cdc9e306d4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards a95215c96d 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards f617eb4ccc 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards f67025f853 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards b8fa68c998 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] discards 1af0a608b5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] new be822a5919 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] new 0a51935877 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new d56fc6c19f 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 7693592726 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new d0de3bb164 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new 6ef9fb13c2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new fcd22f4637 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new ab2421b6fc 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 86add57fbb 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 0597615cc6 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new ab4a003e1b 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new aba61857b8 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 99e9db7797 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 50f3d347d5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 43c13f39b8 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 848fe380e4 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 0656f4e7fc 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new aab79de62d 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 17d43d452e 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new c6cb5d4b07 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 22b0c697b9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 9c8d15465a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 9aedcead88 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 3c89c7be33 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new cb18edf92d 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new b60f309c79 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 407c5821e1 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 1a5d8ca2c0 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 4ab26a0881 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 7cb74ca5b0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 02f8317e57 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 30d54433f1 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new eb3e6f08b6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 783c9b4929 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 1d827b82f7 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new 6da7612c18 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 496bc84f1f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 75c5f2a09b 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 759f20a758 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new f05d75b0a4 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 678ddcb50b 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 3cc9660ab3 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 8a0c7bbccc 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new c93e9a5c4f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new ba78adcf58 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 7b1eb678cf 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 4f042de119 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 4060df54da 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new bc68f7f6ec 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new eb7dd5879a 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new ef623ca1b8 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new e8200e595a 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 6d906875a5 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new a020b6eb71 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 9eeac743a2 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 01e32e34d6 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new a0bebea879 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 73ca5e4ad8 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new f046072aed 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 569771f281 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new c8d1f2fb30 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 707b5d3363 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new bb650e5187 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 94f36ca958 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8ab6fc6553 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new b6ba9bf4a8 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 9b247d2848 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new ef57f6858a 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 70b73625dd 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 49a59a4779 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 007deefbc3 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 768016fd45 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 4e0378bfdf 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new ae4e720a41 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new c701639b9c 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 214bb55917 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 3167f30f20 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new a433672abb 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new feccbd54dd 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 457c5cf76e 121: force: #26: : Failure after baseline build: no new commits new 4e66b7f79e 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9e07b90efd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new becc37baa8 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 78ce7648c2 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 6a9e631237 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new baba1a91aa 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new aab5bc6da0 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 85a6e9d328 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 94d5e174cc 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new ef5b5c0e8f 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 84b1916472 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new f9823bca1e 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 4f31aef00a 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 181b8bc404 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 007e842e2e 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a9f100ae03 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new fb4673f2f6 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 6cd883295a 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 7741f7e764 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new cc6da63efd 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new c72c3271c0 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new be7ba35e1e 143: onsuccess: #51: 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 (5f5f3b6445) \ 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 2040 -> 2092 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2544 bytes 03-build_abe-binutils/console.log.xz | Bin 48704 -> 49172 bytes 04-build_abe-gcc/console.log.xz | Bin 235236 -> 235780 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8504 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 232500 -> 232244 bytes 08-build_abe-gdb/console.log.xz | Bin 46524 -> 46548 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3808 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2832 -> 2796 bytes 11-check_regression/console.log.xz | Bin 4644 -> 4628 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 64 +++++++++++++++++----------------- 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 | 39 +++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++--------- manifest.sh | 36 +++++++++---------- sumfiles/gdb.log.xz | Bin 14252 -> 14256 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 96 insertions(+), 103 deletions(-)