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 5fe18b2a4f9 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 98a1d6ef85d 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 8efffc9eb63 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 435351babe2 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards b3da5eabaf8 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 126490a82e4 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 29ff17fb386 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ac44fd9faa1 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 31d491be9f2 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ff7f6a4d2da 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 0b849aa77cc 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 3f35bcc8f81 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 06be110cb5b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 6196af1ac07 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 1c55bd69508 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1cb815d99a7 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards fb649f316f4 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards cc68fdc43c2 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards ae4a8a90242 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards e23daf6bf8e 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards f7aa9bf1dc5 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards aa970308e19 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards f72b33a0f63 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards ac79bc9f4d4 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards b59b14df462 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards 38b9760c2aa 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 91d7f41479b 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards eb43971b960 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 088fb501687 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 49fe39b7706 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 3c23666f0f8 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards d6b6e56605b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 0650d8d769d 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 6912ff399af 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 7ba3f7c37d4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 01d1dddadb3 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards bf6823a37d2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 333896d3763 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 343cde431ad 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards 1118376323f 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards e6e09b26377 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards a2275e6e0bf 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards d5e1afdb875 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 95b6dd74d1c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 16104aa3686 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 80d7d038190 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 6d08d1222d8 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 774f1059761 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 66a3f94ef3e 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards f28c6de1079 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 1943a053e7f 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 6048baf8b5e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards ea4b981992f 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 5500282febf 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards fb3ab4bbaca 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards fc20a9a949e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards d3380f7aa87 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 74e63721ab4 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards c4d1de2758c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards c38cf1d72c4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 7bd0c00cede 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 48d690570d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 0d6c1ededfb 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 2150a699e77 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 5d02c6fd12f 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 36265db5a5e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 8dd1ee14f87 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards b847389b1b5 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards cb06b46ebce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards fd999fc3a51 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 80a5cf230c2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 3388c13a4f7 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards fe5c38a1b28 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 0d7f92acba0 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 7ddfdd69b0a 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards f598f2e5f17 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards ddfafd94fc1 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 345a8053074 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 77633e87087 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 22f5e751e21 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 8b57098c656 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards a842fad81f8 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards dd543005005 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards fe39fb6260a 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards c7b51602fd4 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 39884a7332b 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 5c94d2b5384 31: onsuccess: #38: 1: Success after linux: 14 commits discards cba7309e4ed 30: onsuccess: #36: 1: Success after binutils: 18 commits discards c2e6b17e211 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 938b5c682fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 95613d0e707 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 310ca396c66 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 8b6542bd882 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards a71152e3d58 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 35e18a4469e 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards 5025bcbe019 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 059da8f4847 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 8903e24926c 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards 51bc5bbfa8c 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards 816ab4051c4 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards ffd6434249f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 03baf6d298c 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new ccf1e8131d6 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 3ee96fe0303 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new e5d6a98cd22 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new ca98fcdaf8a 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new aee2e47a29a 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 29a679fdc1b 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 8f9e623a9a4 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new f033a5a929e 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new 2ecc62004a4 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new 5bfa791e975 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 3d61a22e1fc 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new ee758f106be 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 491339085d4 30: onsuccess: #36: 1: Success after binutils: 18 commits new 3c38605822b 31: onsuccess: #38: 1: Success after linux: 14 commits new 45e8b4e9638 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 01f14ffa845 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 3f4df179440 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 5ce81aaba08 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 4d49721db59 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 24337a0d4fe 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 31685603e94 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new d4d343a7f5b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new e4bda099a20 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 7cf9d55e576 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new e4b0d1a08dc 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new bd6ac125422 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 815067a8ccd 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 5ce318569e2 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 25f579f9fa4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new bc6bfa50e23 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 836f92aea6f 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 4b608cbcbce 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new b9b11fc912a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 6d70b10a11a 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new e53290b4138 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 55ac63d1011 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new c33554f18b6 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 7e300a2f0a5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 34c00197a38 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 895f4334038 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new bf3b4959b2e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 88995276154 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new e8b5d92068e 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3f00b200768 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 00721b37397 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 7224e341370 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 3d218c3b0c7 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new c332572c2fb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 7998c4506a0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 0677376f0d1 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 0054d9ba97e 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 35f551e1755 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new b6ed672f7e7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 38cb8d67c7d 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 23cf339ad0f 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 9bed91787ce 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 98efb89399e 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new ec963556763 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new e5f57966195 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 4c8733da6f5 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new d739f9cb32b 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 3a0a74218e4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 3110e7c5bc5 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new b91c08ac394 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new eae2ed91a00 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new e618c1db353 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 62b2f3ebd1d 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5e3fa3bbe87 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new f9ccc745e0e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new 03e2d47bdeb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new e88ea63ccda 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 8238eccbfeb 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 04a2550293f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 7248f3e620a 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new b7474e29dcc 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 309f98952bb 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 4aca07ffbd9 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 2d3070ba814 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 2635b5bde2f 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 54a8000b745 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new c3718a19ad6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 97c09ca871f 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new a71107508ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new ebb3e9b6969 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 3b7f1a3cdec 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new a5f92988cb9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 2eb18287d56 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new ad0319b72ae 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new f738a4aabe7 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 2dddc281032 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a752abfeb54 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new c95620dc150 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 59f1230b805 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 3d1552fc000 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new a2b233654bd 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 21a341e931d 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 0c2074f1212 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 508b9bfb88f 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 1b0cdcd4cff 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 45fe97df612 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 20aa69ef099 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...]
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 (5fe18b2a4f9) \ 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 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 53404 -> 53544 bytes 04-build_abe-gcc/console.log.xz | Bin 238968 -> 239860 bytes 06-build_abe-linux/console.log.xz | Bin 8772 -> 8544 bytes 07-build_abe-glibc/console.log.xz | Bin 235504 -> 235624 bytes 08-build_abe-gdb/console.log.xz | Bin 51320 -> 50164 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2464 -> 2384 bytes 11-check_regression/console.log.xz | Bin 5748 -> 5528 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 36 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 11932 -> 11932 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 46 insertions(+), 46 deletions(-)