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 9247d66d02 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 1741c4c71b 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 8c49a10ca1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 43cea30343 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards d72b9e8ec6 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards ff29af20eb 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 7a0df0ad08 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards d51af78a83 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 2073da5e18 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards aab4ebfc7d 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards cc60b90ee0 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 95237606e7 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 8490f946c3 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 70591bf4e5 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 6d0ad02a3c 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 5e39a70db5 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 03f7f11fd9 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 7c9d40b954 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 6b69bfedad 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 2c4536c986 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 548be149bf 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 4ce9458814 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards 91b879719f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 181a6be2e1 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 43228ebafc 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 104d864467 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 9d466ad6cf 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 5f1064c213 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards f61c82386c 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards d7c08dc6ce 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 65e35c04cd 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards ec7f7f3dd9 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 37e2a0fdc9 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 3a11525b05 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards d8f3353335 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 0273ab270c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards f3137cb5f3 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards edc43f11a3 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards 702c9305b9 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards cb5b33915d 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards c4ef615d06 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards f6b89c01c6 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards ea37f22621 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards 6d5f990f67 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards cdf921b271 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards 3f0c2948f1 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 162d25c159 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 2e12a51bcd 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards ea6aa5c7d3 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards c1364347c9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards e640f09283 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards f1107de49f 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] discards da95f30dad 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards fb806b6bb8 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards bc9fff453c 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] discards 115ce3adb6 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] discards 4076c64933 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards dc83705d2b 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] discards 1b7f5bdb4c 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] discards 270c7d9a62 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] discards 66f21f9e25 40: onsuccess: #47: 1: Success after binutils/gcc/linux/glib [...] discards dda8a99e4d 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb: [...] discards 1117636d7f 38: onsuccess: #45: 1: Success after binutils/gcc/linux/glib [...] discards a5ca0d7a2b 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] discards d721878a12 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] discards 6899f972fb 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] discards a16136761e 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] discards 52068c6ed2 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb: [...] discards cde5de6b60 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] discards 72019e2535 31: onsuccess: #38: 1: Success after linux: 14 commits discards 07933e6560 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 3730e9728c 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] discards 8b9fc9551d 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] discards 6a449c2b60 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] discards 679bc164bc 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] discards 913a340600 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] discards deae49f189 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] discards 7b7aacf707 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] discards 99d019ce63 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] discards 373789301c 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] discards e5ed095028 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] discards 8aa0e5f13b 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] discards a15113e604 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb: [...] discards d1664d79e7 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards e5f05d4382 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] discards 61513063ff 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] discards b0e4f110af 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] discards 3a6449b0d1 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] discards e1685140cc 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] discards 9c660cb199 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] discards 86905ef6c1 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] discards fe75d503d1 9: onsuccess: #13: 1: Success after binutils: 3 commits discards f546d08f21 8: onsuccess: #10: 1: Success after binutils: 4 commits discards a8aa9693c0 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 3 [...] discards 8e7d3d39cf 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] discards e3572e6fad 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] discards c21472c194 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] discards c35c6fd454 3: onsuccess: #4: 1: Success after binutils/gcc/linux/glibc/ [...] discards d7cf5965d5 2: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: 5 [...] discards 4608da41b3 1: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: 1 [...] discards b05642c57e 0: init: #1: 1: Success after baseline build: no new commits new 9a6a3879a8 0: init: #1: 1: Success after baseline build: no new commits new 94222b1fe8 1: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: 1 [...] new 861c307c2e 2: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb: 5 [...] new eb9b7a3f2a 3: onsuccess: #4: 1: Success after binutils/gcc/linux/glibc/ [...] new 6212f450d6 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] new 60b7e18878 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] new 6d0cb08652 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] new 626403aa05 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 3 [...] new 310531d4ac 8: onsuccess: #10: 1: Success after binutils: 4 commits new 39237ce741 9: onsuccess: #13: 1: Success after binutils: 3 commits new 7ba7681deb 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] new 0224553ab1 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] new 6ad96b740f 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] new a3e3ea2126 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] new 9ad48be197 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] new a643361cc6 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] new eaff0138ce 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] new 4d13cfafe9 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new e5ce4c8c70 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb: [...] new e3c53d3793 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] new d3ac3aa70c 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] new 7d9139b92e 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] new c44cbe668d 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] new bf53459533 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] new 56ccc47b37 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] new 5e2fe955fe 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] new bf52f8baf8 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] new 1074ba90af 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] new 4400183acb 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] new 65a34db161 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] new 80898fb069 30: onsuccess: #36: 1: Success after binutils: 18 commits new ee62ab7c36 31: onsuccess: #38: 1: Success after linux: 14 commits new 3e3c34886f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] new 2f2e50543e 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb: [...] new 7110caee41 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] new 7bf6d5321e 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] new 269a5b5e57 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] new 166b48c8ad 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] new 8e52790600 38: onsuccess: #45: 1: Success after binutils/gcc/linux/glib [...] new 191eb6ce54 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb: [...] new 264c381fac 40: onsuccess: #47: 1: Success after binutils/gcc/linux/glib [...] new d2c7f7528e 41: onsuccess: #48: 1: Success after binutils/gcc/linux/glib [...] new cb2ac19506 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb: [...] new 57b0f81d4b 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb: [...] new 3cb70e76f1 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 9db014c3a6 45: onsuccess: #52: 1: Success after binutils/gcc/linux/glib [...] new 843f122df7 46: onsuccess: #53: 1: Success after binutils/gcc/linux/glib [...] new d78ef33d28 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new af6e7c9742 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new 05d699c889 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb: [...] new 5c6d51c396 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 02160765d7 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new df6caa1f6e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new 9df2e390c5 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new cfb9201f01 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 6d8ce3c645 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new 8c933b5b6a 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 80c9e1d0a0 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new a788ed9963 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new e47ef9bde2 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 9314b83d15 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new c798cd2670 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 807a4edf0e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new ac499b09ee 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new c3a4239553 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 8db990da90 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new c02150a669 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 5aa29dabf6 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new ac94bd5f7b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new db95c3c748 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 7a488c8ff3 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 2b21dc10e0 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new f684d1db07 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new f401affeb2 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new b5553e2e88 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 40a3c9b42c 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new dde6e54161 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new e9751734c4 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 7947fb154b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 908407c9d4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 7de9fde324 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new ea1827b95d 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 718de63244 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 32b3926ffd 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 7f07ebcd2b 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 75b7363c3e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 3bccc148a4 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 56e37a3b32 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 8f24c9ad2a 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 3812d397e1 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 08c8750a59 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new 8b6a340872 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 09f1476f2e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 6f2816a486 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 39e1fccb64 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new cefdb3445e 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 5cf9a0015e 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new e289ce3b2a 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new f3c43ce548 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new b0d7e9357a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 032816309d 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new beb1cc5167 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...]
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 (9247d66d02) \ 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 1764 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 53420 -> 52488 bytes 04-build_abe-gcc/console.log.xz | Bin 239284 -> 235732 bytes 06-build_abe-linux/console.log.xz | Bin 8384 -> 9140 bytes 07-build_abe-glibc/console.log.xz | Bin 236140 -> 235120 bytes 08-build_abe-gdb/console.log.xz | Bin 51204 -> 50340 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3756 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2392 -> 2416 bytes 11-check_regression/console.log.xz | Bin 5564 -> 5988 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 40 ++++++++++++++++++++++++++++++++++ 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++++---------------- sumfiles/gdb.log.xz | Bin 11956 -> 11936 bytes sumfiles/gdb.sum | 4 ++-- 24 files changed, 72 insertions(+), 32 deletions(-)