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

discards dfbf7be137 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards d7b9d9f8c5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards e36dfd3463 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 54c8117fa0 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 2132a24530 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 36ef04ed35 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 7d910d584a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 35bff9dcc5 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 214e3c3d16 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 51ae77f1b5 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 11e8ac1862 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 46164bc908 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 753aaa092b 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards e23596a42e 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards aa4f5a6e04 125: onsuccess: #614: 1: Success after linux: 12 commits discards efaccbb787 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 6687fe3169 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 7476edeb6f 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 4e337aa060 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 92f1cc8875 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 4e692740f7 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 8a13167688 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 65309dff44 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 2823851c7d 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 4553efce3f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 992c82bbd6 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 65aab1a39c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards d550a2cb09 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards acd6a89fa7 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards bfbc0bfa75 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 2687a29623 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 7f7efa361b 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards a88516416e 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 9ea941995a 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 24104032e7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards e00d5f8daa 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards a6ed9bc753 103: onsuccess: #589: 1: Success after binutils: 3 commits discards da51d21523 102: onsuccess: #586: 1: Success after binutils: 5 commits discards f6ec28a9fc 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 8337b82aad 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards ad64a03419 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards f106060165 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 928a55a40b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 85985bf71a 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards fd8d9d55df 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 073cefcdc9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 09a6477d04 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 1de75128aa 92: onsuccess: #575: 1: Success after linux: 34 commits discards 033e8fb57e 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 42aff41342 90: onsuccess: #572: 1: Success after binutils: 15 commits discards e0e93e46ec 89: onsuccess: #570: 1: Success after linux: 11 commits discards 4cb308e88a 88: onsuccess: #569: 1: Success after glibc: 10 commits discards da762d7665 87: onsuccess: #567: 1: Success after binutils: 8 commits discards a572e4cd8a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 114eec7324 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards afbac1392e 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 3c9f2dae7f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 0ec5be12cf 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards a28b092120 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards ef052d6ae4 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards edc1884ed3 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 31a4623ded 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 5f19f6d91d 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 74b5eb501c 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 4a15220c8c 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 2f73678867 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 6b2463e220 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards f633870196 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards dc098f8189 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 0fc48c5274 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 6548a2ed5c 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 830a4ba928 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards f2d4aab95e 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 0d8e3105ee 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 01e565adfd 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards f4020a6178 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards c3d4130015 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards ebcec72911 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards bc489d4897 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 29d1ce91f4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 47ccd1d705 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards d14aee5266 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards e89fadd5e8 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards ff27b8ad07 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 880495ecec 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards cbcf3c90ef 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e4bf311de9 53: onsuccess: #531: 1: Success after binutils: 12 commits discards bc48da4b6e 52: onsuccess: #528: 1: Success after binutils: 8 commits discards c4fbe2b0cc 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 7e5e0a5e89 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 2a7ac1baff 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards d0cbc59bed 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 68ce37e110 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards a66ac10da2 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards 67f771cb61 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 05fa1e7b91 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards dbaf1f1f9b 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 7bd227bc02 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 335100e686 41: onsuccess: #514: 1: Success after linux: 64 commits discards 1d30943c80 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 1ea40eda8c 39: onsuccess: #511: 1: Success after binutils: 8 commits new 07ced14c28 39: onsuccess: #511: 1: Success after binutils: 8 commits new 74460a2bc8 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 5cee24afaa 41: onsuccess: #514: 1: Success after linux: 64 commits new b1118a35af 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new b74e2b4d29 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 914a66e468 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new f96668197e 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new ab05001a2c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new bb0cb3ac97 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new 58179a531e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 6fabf3ff2f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 63d5093d86 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new efc425cb3d 51: onsuccess: #525: 1: Success after binutils: 8 commits new 60e4c1e421 52: onsuccess: #528: 1: Success after binutils: 8 commits new c2f217fe77 53: onsuccess: #531: 1: Success after binutils: 12 commits new 99c3b040dd 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 0700ba89ea 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new b65ab0794d 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new fadde7f745 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new 4dd6ab476a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 8115194ad7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new e1ad8993f7 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new cab55208e7 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new a19f6f4219 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 545fd6fbe4 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 4ccb4f1b85 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new 572f51e24b 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 16947bf0bd 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new a6f0b35c07 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7c54dd3876 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new d8362768b0 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 75b053a0e4 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 66f31eff9f 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new b8dc101b11 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new a1a5ed6442 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 376879dcca 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 13e36a69f8 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new f8713e08b8 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 179c1e29a8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new e5f9b8d99c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new b42a5c1a72 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 9d6ec45abc 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new e84b9985bf 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 240303f589 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 6bba09f2c5 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 2c5d3c16c6 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 0719b78095 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new e7b2747504 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new bd493ce41b 87: onsuccess: #567: 1: Success after binutils: 8 commits new a12caf9b75 88: onsuccess: #569: 1: Success after glibc: 10 commits new 74c30a12f2 89: onsuccess: #570: 1: Success after linux: 11 commits new d85715678f 90: onsuccess: #572: 1: Success after binutils: 15 commits new ca5b11bdc4 91: onsuccess: #574: 1: Success after glibc: 3 commits new 57676e2879 92: onsuccess: #575: 1: Success after linux: 34 commits new 109f82100e 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 9d443a59f3 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 415f76110f 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new d9a7cdfb1d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 12da62cce2 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 180e0a43d2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 7334b6fb74 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 9b62dde9fd 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new ce30dd3afa 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new fd9d62ab55 102: onsuccess: #586: 1: Success after binutils: 5 commits new 3ecdb4ff67 103: onsuccess: #589: 1: Success after binutils: 3 commits new c128f963f4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 6eee4c13a0 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new a9cf92b785 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 82788eb731 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new d52ffff3d5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new df4ba9d74a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 660b4c3bda 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new b55d473bd1 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new e5c16170ad 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new d3f490a261 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new ec96862620 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new c28fe39fdd 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 87c40f6912 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 326d6cc8cd 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 8d6b087070 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new f8dcc5f3b5 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 1aff725078 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 4bc0cb4a70 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new ed0793ad23 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new efae546c00 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new b754f2c3a2 124: onsuccess: #612: 1: Success after binutils: 18 commits new 6db50daede 125: onsuccess: #614: 1: Success after linux: 12 commits new 8683849655 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new c25d0ac5ea 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 7541c1b9b9 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 3ccade06f4 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 8f5fc2a16a 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 34c8ceb5ee 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 174dda1ac6 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new f5090a0990 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new 710ae600a2 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 8c4a0a0ef2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 55823a796f 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new ee8ce1d2b4 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new a3d9c775f8 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new e05c535c74 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 0b42063425 140: onsuccess: #631: 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 (dfbf7be137) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...]

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 1792 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53736 -> 53648 bytes 04-build_abe-gcc/console.log.xz | Bin 238704 -> 234652 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8544 -> 9504 bytes 07-build_abe-glibc/console.log.xz | Bin 238564 -> 238060 bytes 08-build_abe-gdb/console.log.xz | Bin 52160 -> 52480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2368 -> 2256 bytes 11-check_regression/console.log.xz | Bin 13152 -> 11308 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 58 +- 11-check_regression/mail-body.txt | 178 +- 11-check_regression/results.compare | 87 +- 11-check_regression/results.compare2 | 4735 ++++++++++---------- 11-check_regression/results.regressions | 87 +- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 180 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results | 87 +- sumfiles/gdb.log.xz | Bin 1835104 -> 1817952 bytes sumfiles/gdb.sum | 7243 +++++++++++-------------------- 30 files changed, 5191 insertions(+), 7579 deletions(-)