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 20aa69ef099 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 45fe97df612 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 1b0cdcd4cff 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 508b9bfb88f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0c2074f1212 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 21a341e931d 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards a2b233654bd 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 3d1552fc000 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 59f1230b805 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards c95620dc150 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards a752abfeb54 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 2dddc281032 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards f738a4aabe7 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards ad0319b72ae 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 2eb18287d56 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards a5f92988cb9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3b7f1a3cdec 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards ebb3e9b6969 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards a71107508ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 97c09ca871f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards c3718a19ad6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 54a8000b745 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 2635b5bde2f 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 2d3070ba814 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 4aca07ffbd9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 309f98952bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards b7474e29dcc 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 7248f3e620a 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 04a2550293f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 8238eccbfeb 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards e88ea63ccda 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 03e2d47bdeb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards f9ccc745e0e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 5e3fa3bbe87 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 62b2f3ebd1d 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards e618c1db353 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards eae2ed91a00 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards b91c08ac394 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 3110e7c5bc5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 3a0a74218e4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards d739f9cb32b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 4c8733da6f5 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards e5f57966195 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards ec963556763 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 98efb89399e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 9bed91787ce 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 23cf339ad0f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 38cb8d67c7d 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards b6ed672f7e7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 35f551e1755 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 0054d9ba97e 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 0677376f0d1 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 7998c4506a0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards c332572c2fb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 3d218c3b0c7 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 7224e341370 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 00721b37397 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 3f00b200768 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards e8b5d92068e 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 88995276154 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards bf3b4959b2e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 895f4334038 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 34c00197a38 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 7e300a2f0a5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards c33554f18b6 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 55ac63d1011 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards e53290b4138 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 6d70b10a11a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards b9b11fc912a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 4b608cbcbce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 836f92aea6f 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards bc6bfa50e23 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 25f579f9fa4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 5ce318569e2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 815067a8ccd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards bd6ac125422 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards e4b0d1a08dc 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 7cf9d55e576 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards e4bda099a20 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards d4d343a7f5b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 31685603e94 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 24337a0d4fe 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 4d49721db59 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 5ce81aaba08 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 3f4df179440 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 01f14ffa845 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 45e8b4e9638 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 3c38605822b 31: onsuccess: #38: 1: Success after linux: 14 commits discards 491339085d4 30: onsuccess: #36: 1: Success after binutils: 18 commits discards ee758f106be 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 3d61a22e1fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 5bfa791e975 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 2ecc62004a4 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards f033a5a929e 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 8f9e623a9a4 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 29a679fdc1b 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards aee2e47a29a 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards ca98fcdaf8a 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards e5d6a98cd22 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 3ee96fe0303 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards ccf1e8131d6 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 5d732194ac0 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new f8d50cd97e7 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 960c388bb23 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 200217fd44b 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new ae1552496cb 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 97d1316642e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new d7f4245ebbc 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new 88fd6d50c9b 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new fd9d2354ecd 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 172b59ec7b4 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 87f7721ab59 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 0f73b74e5c4 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 35abb5d85e0 30: onsuccess: #36: 1: Success after binutils: 18 commits new 4039528a0b9 31: onsuccess: #38: 1: Success after linux: 14 commits new 8852001971e 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new d5dfdeedad2 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 696cf57b510 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 86e87cac14b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 3d5d9bbe9d2 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new e8ca4698a00 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 04a627d57dc 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 6505dc5e47a 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 5d600236e6e 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 4b2cb7ed22e 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new fc71be48e8f 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new b4836a1b3bf 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new d2d05a1500f 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 98c68eb3d6b 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 7d8cf27d4c1 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 62d008ca077 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 54b44e70cc5 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new b1b3526131c 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new e32619fb2a1 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new e3f627ff693 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new a967bfea29a 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new a7c44791afd 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 4053e8c88ab 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 1b06ca78e8a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 46f7f1dc102 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new e6c47a0361b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 3b24a9ba51f 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 19f9e78b643 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 338c337bd4f 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 56385904c10 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new fd8cc37e878 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new fe942c759ad 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 280aa83a77b 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 622db248d8d 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new deb4c5ec230 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new c40bcc24d87 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 1939b60e9ee 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 11b4f4fe667 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new d034afff71a 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 94cc050870a 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 2abba98757b 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 77122be8fc8 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 8bea0d40daa 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new adbe2548b23 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 1f99f0ad03a 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new af492a3f8ca 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new d587000d43f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new ea284dc68e7 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new e1fd64faea5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new d22db1cf0f2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 7e484db4c2b 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 72757c6d3f5 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 3ed80257e47 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 99f61f2924f 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 653fe13e804 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new ff202ff8e13 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 183491ecc00 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 3518323a920 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 506740141f6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 8a339daee9c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 050f3f03787 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 9c7e48d510b 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new ed36a95dcce 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 66d9746ec43 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new b090318addb 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 1ab1b551cad 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new d082c300d9f 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 93c12b0e95d 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 0b74028b4ed 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 26218f3c6ec 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 7f7a86b4f33 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new f2edb3f86c8 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new d29081e3788 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 526dc3adc31 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 14c5081a03d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new ed05188115e 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2e23a531ad3 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 6a96af5c29d 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 2b188667caa 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4b84ae309c6 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 5090c42e513 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 805b8b87f56 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 43c8ca71595 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new dadabdd9797 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new b570a8165be 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 8abfa449c75 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 01265d697b3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bfa8b76453e 119: onsuccess: #18: 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 (20aa69ef099) \ 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 1784 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 53544 -> 53908 bytes 04-build_abe-gcc/console.log.xz | Bin 239860 -> 238688 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 8272 bytes 07-build_abe-glibc/console.log.xz | Bin 235624 -> 235692 bytes 08-build_abe-gdb/console.log.xz | Bin 50164 -> 50516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3748 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2384 -> 2616 bytes 11-check_regression/console.log.xz | Bin 5528 -> 6144 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 44 +++++++++++++++++----------------- 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 11932 -> 11920 bytes sumfiles/gdb.sum | 30 +++++++++++------------ 26 files changed, 70 insertions(+), 70 deletions(-)