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 778b7aedcd 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 5f275bbc98 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 2ce38b79bd 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 50e2d19182 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 138fb5e9d2 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 693df2ce28 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards e26f25f12e 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards a5065b3c4f 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 8d25eb89ef 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 370f2eeed9 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards bc7cfa2232 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 23b44720f8 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 3c56396abc 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards e6bf01653d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 0c839ddfc8 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards a9aaa85457 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 44ed05c2da 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 0461e6f671 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards fd439eb5c3 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 86b2437bbb 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards d4bf8de028 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 4b8bfc2408 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 166add88d7 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards a136295ca0 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards feb91fd7c7 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 7428735da7 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 81d245e0f5 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 3986fe1e51 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards c7322210ab 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 4719e24ee6 121: force: #26: : Failure after baseline build: no new commits discards 4b94129d98 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 9399eadbe0 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 6ee4b389b6 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards ae49afec34 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards ba9d925061 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] discards 1d68412565 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 14c597de7c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 93fec16608 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 47a5faef60 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 2bc88fb4bc 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 29293d96b9 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 7f933d27ef 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards b626173e0c 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards e5b803d06e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 30ae1afa57 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] discards 5a5dde367a 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 73d241bbc3 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards fb7f5421ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 1188db75d4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] discards 0ef5521183 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] discards fc0bbc1acb 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] discards 900310c010 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] discards 450700337f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 7dd8601f4b 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] discards e7b5ee3f60 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 87d1b0c41a 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] discards 28cb307f5d 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards e4eca772bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 98c9d372d0 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards d4f7fd31c6 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards 0d5d2ea8be 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] discards 60a787e112 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] discards 300a68de93 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards ffb5840998 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] discards 3eb20685df 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] discards 831996b0a0 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards d4abfb88ee 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 2d14baf6cb 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards b188117220 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 2dab10d1bb 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] discards 0c0aedd9dd 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards c7e57c854e 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] discards f1007ae99c 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 00e9bb0e73 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 2bab72b9f1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] discards ad01f858a7 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] discards 7b4c717312 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] discards cbc3cee3fd 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 1628a7d8fb 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] discards 0791274d02 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 2ec802c142 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] discards 53551111ca 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] discards db3823432b 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] discards a66bb35f3a 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards c7afbeec8c 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 51bd58420c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] discards 8b5f93d6dc 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] discards 8f3b82c946 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] discards dac7ff59a5 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] discards 6f3e3a3784 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] discards d1e7ce9854 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 634b5c478f 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] discards 499871400f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] discards ca368d48e9 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 352a86a6f2 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards c9fa7dd0b7 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] discards 95eeab04ba 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 7592259800 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 84fe0c150a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] discards d69ab42da9 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 4ad276963f 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new e04392aa43 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new 3f57f2c195 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 4742a4c2d3 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb: [...] new d2345f5ec3 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 646905772a 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 3eb099da4d 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb: [...] new c4a4e67f85 56: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 0c171b51c1 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new 10d0035174 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb: [...] new a360683386 59: onsuccess: #67: 1: Success after binutils/gcc/linux/glib [...] new 32bbc74cfc 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new f432875b60 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb: [...] new 1c51b21097 62: onsuccess: #71: 1: Success after binutils/gcc/linux/glib [...] new 37db5e928b 63: onsuccess: #72: 1: Success after binutils/gcc/linux/glib [...] new 0068c9ea52 64: onsuccess: #73: 1: Success after binutils/gcc/linux/glib [...] new 038038b1aa 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new 2f4e7fb4e1 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new a7417c0a7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new bb47a22e68 68: onsuccess: #77: 1: Success after binutils/gcc/linux/glib [...] new 11d111ed98 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb: [...] new 016580871a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/glib [...] new 615cee8f29 71: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 7cd20ae57f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/glib [...] new e419d2bc2f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new eac807e603 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb: [...] new 4b3e71289d 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb: [...] new c99343a679 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb: [...] new d29ca8f73e 77: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 3aa5ea97b0 78: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 07ca128d7d 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb: [...] new 84add8c60e 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 42556f46c9 81: onsuccess: #90: 1: Success after binutils/gcc/linux/glib [...] new 0857433a37 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 4eb21b16a4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new c0e450cc20 84: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new e17089f884 85: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 45a2c5389e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/glib [...] new b50466c1f0 87: onsuccess: #96: 1: Success after binutils/gcc/linux/glib [...] new a6014ee4d9 88: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 99a662366d 89: onsuccess: #98: 1: Success after binutils/gcc/linux/glib [...] new e409838e6f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb: [...] new cd2352536f 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new b8df005a53 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 1e944ca39f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 4e0b6fa15f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 9bcfe4af27 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gdb [...] new 3930667149 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new eb812b6947 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gli [...] new 29ee77aa9e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 613e584013 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gli [...] new 6544135115 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/gd [...] new 2cba4c44d0 101: onsuccess: #122: 1: Success after binutils/gcc/linux/gl [...] new 11300c049f 102: onsuccess: #123: 1: Success after binutils/gcc/linux/gl [...] new 9845c7beea 103: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new a21f1fb22d 104: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 9c62ab051b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 10c97a0053 106: onsuccess: #4: 1: Success after binutils/gcc/linux/glib [...] new 02f7440d8c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0327697aab 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 4acf678b87 109: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 1871a2614f 110: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b3c0a3d06d 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 29c6274c70 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new a8857793d2 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new bd391003ea 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new a5622c7e77 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 2b77b56a3f 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gli [...] new 78f7d80232 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new c05716440c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new ce110b62c4 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 205a137efc 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 5b94e4c1c3 121: force: #26: : Failure after baseline build: no new commits new 3f7229adc6 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new b8dcafa8cb 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new b7b41fabe9 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 419c8ff7c1 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new a3e08bd698 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 0d282af3f9 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 73e69265a9 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 17ac02c96c 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3fb04339c2 130: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new e0b3f751c8 131: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new ee7bef93f0 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new ff525612ce 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 8b07fdf19c 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 78dc09996d 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new f034dca806 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new d2aa6b752d 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 704b3890bf 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 7d618861af 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 5690376e31 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new aba8afb024 141: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 937720316e 142: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 1a2533a1cb 143: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 2cb08392db 144: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 1c8f97cc9b 145: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 64adfd259e 146: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 862c0b4688 147: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b265063fa3 148: force: #63: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 536c06cadf 149: onsuccess: #64: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 363e9ad5a8 150: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new eb2af62a79 151: onsuccess: #66: 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 (778b7aedcd) \ 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 2220 -> 2052 bytes 02-prepare_abe/console.log.xz | Bin 2528 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 48904 -> 49804 bytes 04-build_abe-gcc/console.log.xz | Bin 235504 -> 236752 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8452 -> 8284 bytes 07-build_abe-glibc/console.log.xz | Bin 233108 -> 232736 bytes 08-build_abe-gdb/console.log.xz | Bin 46496 -> 48308 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3852 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1716 -> 4136 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 42 ++-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 34 ++-- results | 2 +- sumfiles/gdb.log.xz | Bin 0 -> 14216 bytes sumfiles/gdb.sum | 353 ++++++++++++++++++++++++++++++++++ sumfiles/xfails.xfail | 0 24 files changed, 399 insertions(+), 46 deletions(-) create mode 100644 sumfiles/gdb.log.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/xfails.xfail