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 b1861fc090 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 53bbc64df5 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards c077794124 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 99bc0112e0 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 27aa36a8ed 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards e5804fe921 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 3ac5ca222c 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards d086e96055 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 3fcb03b091 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards ddc4fae52e 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards aacbd8fb3c 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 32aec39e09 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 560f3fe33f 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 13caf389d6 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards ad33d5fd2e 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards b0a5d22ea1 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 4da5d7f22e 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards a396ffa81e 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards a3b1698c3b 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 6086146385 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 6e15001e88 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 1816adc89d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards c18d259f18 92: onsuccess: #575: 1: Success after linux: 34 commits discards 36cee161f8 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 562ed38490 90: onsuccess: #572: 1: Success after binutils: 15 commits discards b48a8f5d3a 89: onsuccess: #570: 1: Success after linux: 11 commits discards 6acbb309df 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 1a713019f1 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 5dc532145a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 95cf077696 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 06c0808525 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 29b76b4d6f 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 94e7868fb2 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 5af4fca387 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 042d463c12 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards a961ce5263 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards d8401757a6 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 6f83c9a469 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 8c500c4bdf 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards b92a0237ae 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 7a0e83d562 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 5069c682f0 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 374cc8b51a 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 48a851e9f3 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 07b3c67f86 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 1ffa29a1b6 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards ff5e347f92 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards e07423f12a 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 23219ab8a1 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 88a05dc20c 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 62b41388e8 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 44b7825827 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards 2dea08bcc3 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards a79931e200 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 68278180a4 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 60b538ef25 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 68f8df0259 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards c4d354de00 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards 8eca219a5f 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 3e2954af2b 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 40bdb10c0d 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards e56b4398a9 53: onsuccess: #531: 1: Success after binutils: 12 commits discards f7af3aa0fc 52: onsuccess: #528: 1: Success after binutils: 8 commits discards 8b51e2c73f 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 62474d4697 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 11e29c45c6 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 943bbe27be 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards 588ea4a649 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards a33ce666a7 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards d055de2ecd 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards e13543a260 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards 6f8230a7d0 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 0eb09ffec2 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 6160c1abbb 41: onsuccess: #514: 1: Success after linux: 64 commits discards 865fec032d 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] discards 25812f4c73 39: onsuccess: #511: 1: Success after binutils: 8 commits discards 2421b9f968 38: onsuccess: #508: 1: Success after binutils: 3 commits discards 520e3a029f 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 715daa7568 36: onsuccess: #505: 1: Success after glibc: 3 commits discards f496aaa272 35: onsuccess: #503: 1: Success after binutils: 11 commits discards 5907948485 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 1bf24b1946 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] discards 0642abaaa6 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards cd4a46dfb5 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 74535c4aa9 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 5c676de996 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 369df10621 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] discards 0fc0e0cb6c 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 62907c6b66 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] discards 7a69bdf78b 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 561d5045be 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits discards 45390dfe89 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards d0bb34c1dd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 207ca527ed 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5982764234 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8b389c6e3c 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c3ff5c37df 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f34b51930d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4f5a1121a0 16: onsuccess: 1: Successful build after binutils: 4 commits discards 698125396e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 957ad2b95a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new dfdeafe58c 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a89d70a32d 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd8c8297c1 16: onsuccess: 1: Successful build after binutils: 4 commits new 00f2d7dcb7 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bbee4a3804 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8d44e50687 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cec35f597a 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b19d48f151 21: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ad58af811e 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new ee8e1cccae 23: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new d290fd4596 24: onsuccess: 1: Success after binutils/gcc/linux/gdb: 117 commits new a6c14ab83e 25: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new c25dcba72f 26: onsuccess: #493: 1: Success after binutils/gcc/linux/gli [...] new 36f8c769c1 27: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 089aa03531 28: onsuccess: #495: 1: Success after binutils/gcc/linux/gdb [...] new 162694459f 29: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 1571375080 30: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 384111cf60 31: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new eb491b9335 32: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 0a044818ab 33: onsuccess: #500: 1: Success after binutils/gcc/linux/gdb [...] new 18315ad638 34: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 1775258bb8 35: onsuccess: #503: 1: Success after binutils: 11 commits new 411e40b307 36: onsuccess: #505: 1: Success after glibc: 3 commits new 96d31c12c4 37: onsuccess: #506: 1: Success after v6.0-rc5-25-g3245cb65f [...] new f0976a8a28 38: onsuccess: #508: 1: Success after binutils: 3 commits new 198343975c 39: onsuccess: #511: 1: Success after binutils: 8 commits new 5430d7a85a 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 93d3a0922f 41: onsuccess: #514: 1: Success after linux: 64 commits new 930b21d7f6 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new b40a054536 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new fcee6a07b6 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new e1b787d4db 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new d756b17268 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new e764a0ec25 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new df12575693 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 1372767cc3 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 5004b137bc 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 17da14aa5a 51: onsuccess: #525: 1: Success after binutils: 8 commits new f7a5d73e4e 52: onsuccess: #528: 1: Success after binutils: 8 commits new ac80e72a58 53: onsuccess: #531: 1: Success after binutils: 12 commits new 9d6ff294a2 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new 337b1ac3fa 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 0e80f630da 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 83ad54fa51 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new b3a66f89e9 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 71ade5feec 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new 8d732d7307 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new a963962b1b 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 9f166216ce 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new f89e994c2b 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new 1ebc533df3 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new e825400d1f 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 1afdf220b0 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new fb8199c41b 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new ee49dc8d3f 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new 3a1c08481d 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new f89795fe14 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 40c3034922 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 78bef2c111 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new db4794cdb7 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 042c3cf61d 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 982ec95b20 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 5e696895fc 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new ca276cc4bb 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 2abdf20388 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new bdd7709efc 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 66f3a7483a 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 59d91ec1fb 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new 72cf30dc56 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 94316ff0cd 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new ba11d95509 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 7d36752d3e 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new d20f256273 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 14d7645c4e 87: onsuccess: #567: 1: Success after binutils: 8 commits new 579e76c364 88: onsuccess: #569: 1: Success after glibc: 10 commits new c4ed3f5bb5 89: onsuccess: #570: 1: Success after linux: 11 commits new 6011cabb19 90: onsuccess: #572: 1: Success after binutils: 15 commits new c558652c35 91: onsuccess: #574: 1: Success after glibc: 3 commits new 9cf2bdc048 92: onsuccess: #575: 1: Success after linux: 34 commits new 3d2a5e0495 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new d89ce33a31 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 370d3e6585 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new c83ffb8ff7 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new c100990335 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new faeaa7ac41 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 8e19aa1b5d 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new e0e4722d9c 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 8804f6b4ee 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 1a2f24dc3a 102: onsuccess: #586: 1: Success after binutils: 5 commits new 5bc85a4aff 103: onsuccess: #589: 1: Success after binutils: 3 commits new 1885cc1314 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 8fe0d944c7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new b085b1f207 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new c8900294a0 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new f64fa8e898 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 11a41eb6b0 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new bf3ff64231 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 4202149911 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 964622cc30 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new d2ac6d36fa 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new cbb12533b6 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new bb3f45a2e3 115: onsuccess: #602: 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 (b1861fc090) \ 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 1708 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 53152 -> 55540 bytes 04-build_abe-gcc/console.log.xz | Bin 234924 -> 239092 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9520 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 237144 -> 235812 bytes 08-build_abe-gdb/console.log.xz | Bin 51912 -> 52112 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3832 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2200 -> 2496 bytes 11-check_regression/console.log.xz | Bin 10360 -> 16568 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 47 +- 11-check_regression/mail-body.txt | 199 +- 11-check_regression/results.compare | 98 +- 11-check_regression/results.compare2 | 4024 ++++++++++++- 11-check_regression/results.regressions | 98 +- 12-update_baseline/console.log | 62 +- 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 | 201 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 98 +- sumfiles/gdb.log.xz | Bin 1730220 -> 1762500 bytes sumfiles/gdb.sum | 9499 ++++++++++++++++++------------- 30 files changed, 9529 insertions(+), 4845 deletions(-)