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-aarch64 in repository toolchain/ci/base-artifacts.

discards d488f27e25 165: onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b1f71b7ae4 164: onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 1bc6ecb52f 163: onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 81c19c0000 162: onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6976197078 161: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 20c8bba494 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards f48b275ae7 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fcdb6d3fbf 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a9b301818d 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8b6fe274bd 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 48cac4ff96 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 33a93730bc 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards b56b49d027 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 8cd6291cd2 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards cb726b3187 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 49e408ab18 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6daaef2259 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards d9653ad013 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards 6c8fc68751 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards c5a00ede14 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 423da9ba90 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards a41344a827 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards abe2a7655d 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards f238093334 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards fb63a12fd8 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 5835d3324b 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 3febf8506d 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards f869b4010d 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 4365fe8b55 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 868b34ce2c 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 24b0579f1d 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards 5cc8c7b237 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 42b64e4a0a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 8e764ef412 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards d5ebcf451e 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards caf1470d50 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards b9390dc2e4 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 3ebbcf0ce9 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e81fe53ab1 127: force: #27: : Failure after baseline build: no new commits discards 0b5beacf35 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards bc29c7c181 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 7e87a13d46 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 330180f2d7 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards b3ffce2aa2 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 15288875b3 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 968a959c19 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 4d31d4f585 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 900cd84e60 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 0430937cc8 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 7baeb80e6d 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards e26629787e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 0cdb6fb575 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 686d0cfb50 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 890d381f4d 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards f129e0f762 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 364ca309ca 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 5a2f64ba02 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards bccd2816dc 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards e4390e3483 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 76bd249348 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards 7121640b2c 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 467c9773b5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards 437780bff9 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards e12ea71705 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards fca37b64c9 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 9376e58d02 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards aa13842aca 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 744b799def 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards da07b9cb4e 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards f1bc05d544 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 0894d55f42 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 6c1476fd86 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards e545881ace 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 691fc030ed 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards 076caaae17 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards cbf1214f97 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 4e063f1604 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards e630a8ec51 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards a4bc420cd6 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards b89748e150 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 13251e7db0 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 4506bffd41 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards f72bf29d06 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards cfd1974ef8 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 4bc3f98830 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards f73b1592fe 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards f0626f5bf1 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 355db19959 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 59f027c5c8 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 036fb5744f 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 0c8b9750cd 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 6f2677f590 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 826f2cb835 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards f70ab6cc4f 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 399d619b41 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 3dd01bb967 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards f51c276a13 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 4d0a06197a 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards c92a751924 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 64af84376f 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards 5a65534fe2 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 6a207cfd32 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 4b7ebeda5a 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new addbfe72dc 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 34a87e97b1 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new c3db7894a0 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 9357969c3f 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new aa87058b49 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 716041bd62 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 4a09b2262e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 64f196f676 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new b8874ffa36 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 9f19663fc5 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 11018167c8 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new 8f1d25fc17 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 6ae48fa966 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new c2cac52ab3 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 9790ded120 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 017b54ae5a 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 635d3ba058 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new cb0410f448 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new db99af6c12 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new ca9d8f520d 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8bcbe13940 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new aa5a0bde71 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new b284057b19 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new d9c0d414b2 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new a73900bc97 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 6c68cf42b6 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new dc621ab98e 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 76060b2f4a 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new c21fe5f6be 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 12cd1f51f1 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new afba9801ff 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 151c4ee611 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 4b7856c52f 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new 554d86f7ac 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 610568eafc 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new ea85625e17 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new ae3cd25a32 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 705c128882 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new cc783758f5 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 598d2ab53e 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 4a407e7fcf 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 2ed8c5ae8f 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 09470a5519 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new ce672286ce 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 7d174bce9d 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 3a70fca0a5 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new c9a1ab5c83 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 06f10891f8 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9625ecdf80 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 16a6a7af6d 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 7904494888 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 4ce75be911 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 07ac85bb9d 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new d92b44c68e 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 98b6bed3bb 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 98ed282fac 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 460f594f4c 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 7590ff50c8 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 0aebdd916e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 7971c3768e 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 5023a2be45 127: force: #27: : Failure after baseline build: no new commits new 42069582f7 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 8a847b1b7f 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 41d551a8a8 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new e0ecec4ccf 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new d0e8eace88 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 3a3ad0cd72 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6bc54dcd3b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 5e670cafcb 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 801c357727 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new b4dad8b9f1 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new e4ce5ec145 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new a721b616fe 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 0e4aff8aae 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new f33e7fc0c6 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 8e37483ffa 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new fb99616c27 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 5bcc4e5fd4 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new 646455e547 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 1899bb7c92 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 39d3e8094b 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new 145d8b93e8 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new 6fb26e00c4 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cf1a728adc 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3a8fc644c7 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new aa502d661d 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new 700f4f5a4f 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 40147642a1 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 273f9ccb78 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3236528205 156: onsuccess: #68: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b5c0e71a9f 157: onsuccess: #70: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new b0ef9d5365 158: onsuccess: #71: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e2e40b20d9 159: onsuccess: #72: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 55d280eef9 160: onsuccess: #73: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 362a9ca8e9 161: onsuccess: #74: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 0a5e5367de 162: onsuccess: #75: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9b6bb6cfd5 163: onsuccess: #76: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3c87ac41fb 164: onsuccess: #77: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7e991afa39 165: onsuccess: #78: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e0f439a1f7 166: onsuccess: #79: 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 (d488f27e25) \ 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 14436 -> 14456 bytes 01-reset_artifacts/console.log.xz | Bin 2216 -> 2228 bytes 02-prepare_abe/console.log.xz | Bin 2456 -> 2456 bytes 03-build_abe-binutils/console.log.xz | Bin 36048 -> 35572 bytes 04-build_abe-gcc/console.log.xz | Bin 204276 -> 205548 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 8832 bytes 07-build_abe-glibc/console.log.xz | Bin 241552 -> 241712 bytes 08-build_abe-gdb/console.log.xz | Bin 35644 -> 34888 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3880 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4292 -> 3404 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 1196 -> 1204 bytes 11-check_regression/results.compare | 6 +-- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 70 +++++++++++++++++----------------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 6 +-- manifest.sh | 24 ++++++------ sumfiles/gdb.sum | 4 +- 23 files changed, 63 insertions(+), 63 deletions(-)