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 a0aba751884 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 2679fe0ac50 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards f434429d0ee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards f2accf4d3a2 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 15d34b834dc 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f693aacd9bd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b08950a9893 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards b6e41f765e0 121: force: #26: : Failure after baseline build: no new commits discards df1060f7573 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 8a4d3069fe2 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 3d6adacec46 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 441d2f8b9af 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 7d73c6853cd 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards b7b1f7e4518 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 17ef2313aca 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 68de6afa2bf 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 3cf696a69ce 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 912e877b786 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards beae34a16e8 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a51cf465876 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4665f9792fb 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards fc73bdd8f86 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 27285f9e6ac 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards d2b86dd6ce4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 4ff04ad3984 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f1bc72cd77b 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5950c0eb58a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards cf41b2eb722 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards d1df5fe31da 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 26a09dbd192 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 92044746889 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 65bd6542433 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards ef894bf915e 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 59df9662baf 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards e84649db06a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 2957932a16f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards a3bbb82f0ca 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards d7e34e227ce 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards a08851c1dbb 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 7338c9d0361 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 4598c66f654 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards b75fef90834 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 65b89a098ca 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards abe60845245 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 7263dd2da8e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards e7a2e32f986 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 1fc66d1a964 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 1dd02fbbfe3 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 05db0bd38c6 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 508bc654941 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards fea7b0cbf45 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 42d74e7c0f8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 07be1891b49 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 1ea502cdbb0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 5609c5d0508 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 9a8cdf6dd1c 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards bfaf78ce159 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 65a3a4e60ee 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 86466ec1093 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 7d58ef804d8 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards d4cc3b98ffb 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 0363f498861 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 7a3b5f70ca9 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 91f10add322 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 7c230f96cb6 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 931fa6c5e48 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 916b4485d58 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 0200db2209a 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 5cc3b040b43 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards ae86c93d762 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards bb69372bafd 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 52c8506a67b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 47a6f19d668 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 29cac887ef5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 94c12e3a55b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards df2f1fa689b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 8d2eb04f3c1 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 91e3a7aacea 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 97da59688e4 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 53643acfb4d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 9ffe595e80d 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 27c5d9ac966 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards cb3deb38d78 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards add17c65b64 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards e5ee13ce1e8 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 4ae8477ce9c 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards bb82e94b17b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards dac14868292 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 718316e7efa 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards b6d8f584dd6 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards a5d3bc5a987 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 946fe28bd02 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 3fcfcdbb7e5 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 23b0ed60088 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 38a9e663c18 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 636ad4e955f 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 920609e3c0f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards fccc8606ba7 31: onsuccess: #38: 1: Success after linux: 14 commits discards fab2f2609c9 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 167ddfe1708 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards d343c3750a8 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 0c7242dd541 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 83bc2bf650a 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new c872b31e784 30: onsuccess: #36: 1: Success after binutils: 18 commits new 0cd2e4f4372 31: onsuccess: #38: 1: Success after linux: 14 commits new 6fdd9cb2a68 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 80bff201de8 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new b1837702cbc 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new e91ae6a326a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 9d3303d9fab 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new b502168c5e5 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 1a060dd4885 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new bbd2182dbb5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 068807d348d 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 8841c4df4d7 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 796f67194e1 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 0cb2e5db611 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new db0693d050a 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 62891e113dd 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 4a44f230d42 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 66583623cbd 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 6f3e943e995 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 060508a3798 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 79eac3e07b8 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new ac018208eb3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new c18028ee2e2 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 1de56612bf8 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 3ed11cf5afb 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new e928022507a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new df76d0bb720 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new c7d818ca081 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 67630247210 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 2dc83b8b878 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new e0a884065f6 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3c1a2ff7b5e 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 5e0bf5e7e99 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new b044735b594 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 9dba788fe77 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new fcebec6752d 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 2cbc897ef72 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 971d8d0c0a3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 6ca66fcb263 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new c8f58499c42 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new a9b5ab545c7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new a5827e1d75f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 7d51dfc5e7e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 91e065d0986 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new c91dbb8e5fa 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new f7a78ac200a 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new caaec1366a5 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new d813bb1b809 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 759e8a663d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 4c5442aea82 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new ec87ca43542 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 11bf85fb6f2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new b1b7e453ab2 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 2d03af9b4f4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 5311b3f6cf0 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5ed93b6b5a2 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new db63d2ccc34 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new e3041d454eb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 948f34ec191 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 223bcc98e00 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new abdd9a7466f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 9e1e55c45b5 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new c36e20a12f5 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 235603842d2 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new e9f51367d3f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new d9c531247f4 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new e793127ed58 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new ec6dd6402cd 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new d80e55aeba3 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 3eded8240be 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 6e4f14ff090 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 592b40ae6f5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new c848be235f6 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new c8b5391fc17 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7e5245dee44 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 26f094cbf66 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 09c9244cab2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 5996746087c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 1ce478081be 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 53e6f5b2287 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7f755b711bd 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new efd35a73f8e 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 65a80cd26f8 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 305b38d4e26 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new a12d42e5057 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6c351e85381 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 926e2fb8716 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 6cc15afb343 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 1c68a47b501 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bcbc831b479 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new eb1aa109345 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new f7a55088645 121: force: #26: : Failure after baseline build: no new commits new 31d0f742e14 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 858c50116cb 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new ecfcd7d8fb4 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new aecc8000b46 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new b48b813ea36 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new ab5087d96ef 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new c44be7a07cf 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 901fd9a0bdd 129: onsuccess: #35: 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 (a0aba751884) \ 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 2140 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2568 bytes 03-build_abe-binutils/console.log.xz | Bin 49076 -> 49288 bytes 04-build_abe-gcc/console.log.xz | Bin 236716 -> 238024 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 232340 -> 233736 bytes 08-build_abe-gdb/console.log.xz | Bin 47396 -> 47124 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2732 -> 2836 bytes 11-check_regression/console.log.xz | Bin 4816 -> 4708 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14468 -> 14464 bytes sumfiles/gdb.sum | 4 ++-- 27 files changed, 51 insertions(+), 53 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt