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 0ea50fd036 156: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 21552021d5 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 7d7eea402f 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 9c3fd086aa 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a831aa06a3 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5ae2e84727 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6c7c6454f5 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6fc63d87e9 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards dd0c6a6796 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards f142bc7f45 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1ccd70df6e 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bac93c11d2 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards dffc41ab50 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 4e41bccc3f 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards dfa5ce74f5 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 415f6fe9ea 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards f75b576c36 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards ad337e5456 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards c89e6ce2ab 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards b609c85ef7 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards adfe1a0679 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 2cea3de220 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a59582068b 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 1ae9193d98 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 07dcf3c35d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 1223db0bd1 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 7172f035a6 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 7a0d2331f3 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 92da0d8b3d 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 1fc1ce6fc4 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 23a3fa8902 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 7df4a3f3f4 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 38de1860e0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 1cc7aa3dc5 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards d11fd0b937 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards ea22bf49fc 121: force: #26: : Failure after baseline build: no new commits discards 013e7c0207 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 36a28e266b 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards b12df4e209 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards e1ad0194be 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards 1d8f29e9ad 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 5a27844268 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 5561b650a4 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 0fca38780b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 7a3db07d26 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards c7afe894bc 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 585ef08da4 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 4b708700d7 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards a4dfe4548c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards 54613dc032 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f71641c995 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 34173985cf 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards c78b542b00 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards c7280e2d39 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 0e6d8fc59d 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 61236dc08a 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards c8d8f840df 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 32a7af026e 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards dd7035b7c1 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards a6e4443df8 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards a054b24d01 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 4de5af595d 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards b0aaf94da2 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards 9a9b649a96 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards ff1a53c589 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c0c70a5da6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards dfe3dff274 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards a6ac119d3f 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 0beb91c62b 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards bd24029d46 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 9af1232b16 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards ced8c2a0ad 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 9c35ebda9d 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards c733ea8582 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 810a2ab0d2 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 3c3e6aeb69 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 78b4a52103 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 547f5e1416 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards faae1069c9 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 61920a3f4d 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards bf82c9f3eb 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards 03b6ab06fe 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards eca91f8cb3 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards 00c5d1b0dd 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 10c40b87c4 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 1cf5387280 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards e00f91d627 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards ca37954a48 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards 215581a9bf 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards 3eb89c160f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 2db69d5c01 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 504f4dfbc3 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 8a81df5123 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards ffd027f00a 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards cd81a5981a 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 159ed01ebc 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards fe131e9d10 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards daee8fe0ed 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 67ae76b119 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards e66b99d99a 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards aa308836b4 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 6df8efd538 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 102791b733 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 2a2c98b815 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new 093ca419d4 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new f51e78bba9 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 02aaee65f5 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 9595bf4868 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new f7d4801335 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 29505d9e79 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new b092a1c8c6 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 80f43ef2be 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 7da244b900 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 3b043622fc 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 6d08e1a8e8 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 7e3bcc9c0d 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 7d2eba8377 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new e8e21a67c5 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new 0cba1ec190 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 1e1b178cc2 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 13ca05cd80 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new 9652b3567d 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new aa35282b5c 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 0c0d3eca14 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new a8e9edb54f 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 76e32ca7d3 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 443fedd59a 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new d39f302f0e 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 4a97b7f0d5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 34b20e6615 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 5b1ac70a9b 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 029c977a30 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new 1c2714969c 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new 04e1b9661e 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new e554483365 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new 362b9157c6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new b8d8610451 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new e6bd341757 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 741f4ccd90 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a7917c58bc 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 13f1bb6720 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new e31757c07d 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 1430f97585 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 0f65ef4191 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 60742c7b57 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 30afa8496d 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 761c739e77 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 12890e3a4f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 29a14743db 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 3124120af2 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new fa60737ffc 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new ce5219f07c 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 004f2627e0 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new c8aa7333ef 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 0cc061cce4 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 696a08138c 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b411e4599b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 3ee8038fef 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new fd6367af9a 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 35c37f614a 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new ac6a175901 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new fd3a1f14c0 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 76016df8fb 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new 1c0a74bd4f 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 824996aaed 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 418594819f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 538cad408a 121: force: #26: : Failure after baseline build: no new commits new 47ebaf0ea9 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new e609c0724b 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 3e326f35fb 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 92028a9b25 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 33cbe9d39a 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 01e726114f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 03c1a9ddf7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 89bb05e000 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new efafc82c48 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 51eb308c1d 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new d2d8b33d4e 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new f9179d6ff2 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 142ae78fe7 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 02ab3ce58c 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new abcb144297 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new ca5f4765cd 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new f0ee5ec1e2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new f0e7679526 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new c498b91d59 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 73ecf94375 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 4d0d9d67da 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new fcded71dcb 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new af9dcda5a1 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new da6a92313e 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 1c05955d28 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f19fd11176 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 82d6dca9cd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new dc2a8d00d8 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 2e3698bc68 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new c8ae68ab29 151: onsuccess: #66: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e48685ca4c 152: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 5c32bd31be 153: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7db3829c38 154: onsuccess: #69: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6417b87a1f 155: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new bcdc7083ac 156: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 64378a9c5f 157: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...]
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 (0ea50fd036) \ 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: 00-sumfiles/gdb.log.xz | Bin 14228 -> 14256 bytes 01-reset_artifacts/console.log.xz | Bin 2056 -> 2252 bytes 02-prepare_abe/console.log.xz | Bin 2468 -> 2444 bytes 03-build_abe-binutils/console.log.xz | Bin 49688 -> 49392 bytes 04-build_abe-gcc/console.log.xz | Bin 238536 -> 239464 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 320 bytes 06-build_abe-linux/console.log.xz | Bin 9236 -> 9312 bytes 07-build_abe-glibc/console.log.xz | Bin 233824 -> 235344 bytes 08-build_abe-gdb/console.log.xz | Bin 47436 -> 47356 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3880 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3276 -> 3448 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1196 -> 1208 bytes 11-check_regression/results.compare | 6 ++--- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 44 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 ++--- manifest.sh | 26 ++++++++++---------- sumfiles/gdb.sum | 4 ++-- 23 files changed, 51 insertions(+), 51 deletions(-)