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

discards a6616ffdc2 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 12562b824e 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards dd57c05e44 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards dbd100d2b4 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 941a64d8ca 104: onsuccess: #558: 1: Success after binutils: 3 commits discards c629a2855c 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 7027436040 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 84c52bdef5 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 5c049570cc 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards bcffc9af70 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards bf78130d64 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards c352f2a457 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 98f8de94c4 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards b6d6045495 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards b373be3b4f 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards f557d8f6f8 93: onsuccess: #544: 1: Success after linux: 34 commits discards 1efeb6d255 92: onsuccess: #543: 1: Success after glibc: 4 commits discards a392ffb17f 91: onsuccess: #539: 1: Success after linux: 27 commits discards f21466b97a 90: onsuccess: #538: 1: Success after glibc: 10 commits discards fbef9b4263 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 630fff03ca 88: onsuccess: #534: 1: Success after linux: 12 commits discards c7210f58da 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 8b2ffaa70b 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 56f72a01fd 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 9882372b79 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 83de79b8de 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 67a34d0ab9 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards cd8fc9ecf8 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards d54f7d4f81 80: onsuccess: #524: 1: Success after linux: 9 commits discards 0dcadcb8a9 79: onsuccess: #523: 1: Success after gcc: 25 commits discards e8e8d79f58 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 3ba79eb57e 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 88d8ea21e2 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards ad8081822f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 13effcb70c 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 82caddc4fe 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards d120b18093 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 4cdb0d6ae3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards f64fe2e19a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 54789cf475 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 96e92bfa21 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards e91f06ca01 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 6cd0c2c024 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 56ba8994c4 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards bb8f14534c 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards c68d270450 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 3fdd47a5fb 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards df938afc3d 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 14588385a5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards ddeaf72a1e 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 73ce7e6a7a 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 5e53fded8c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 70a0db1733 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 7cac5d2fa3 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards acbe15ee22 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 14c7bb4626 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards ec3dc6db54 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 3bcdd65be3 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 32781e0dcf 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 39f89f9147 49: onsuccess: #487: 1: Success after binutils: 11 commits discards c6227cfd7f 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards f2add3ec9c 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards e334f9141d 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 63cfc43319 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 1319b7ddb5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 5621006608 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards cec70a9b05 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 146597dd1b 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 0ed2da219c 40: onsuccess: #476: 1: Success after linux: 69 commits discards 44fdb44fe6 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 61c5a52ff1 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 7e4ba6c9eb 37: onsuccess: #470: 1: Success after binutils: 3 commits discards ecdc9ce7f1 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 3b75717b30 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 97a085230e 34: onsuccess: #465: 1: Success after binutils: 11 commits discards a09dda7b06 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 493daff18f 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 753605753e 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 1ef6b4db30 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 17be369073 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 5f03cbf1ff 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards b8bacedb2d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards d0b27d454d 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 630434a62f 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 128594f2ff 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 073d1ed417 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 0f54afcf1f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards cd7a8d5803 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 267d660f6d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3e7a186d2b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4622d540f1 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 33bfbf799f 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 301ad2b9b0 16: onsuccess: 1: Successful build after binutils: 5 commits discards d7251d304d 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d6fdaa023f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0961b04dfe 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6546be88c0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 80f508a9d1 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards bc56f2f032 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3dc414f5e9 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c0b8f607f8 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 1884537dfb 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 74ec205a05 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new aa1e07ad02 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9c66a35998 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b544b7412f 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 408e49243d 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f94fcbc0b6 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 75a1dd981b 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3a9083009b 16: onsuccess: 1: Successful build after binutils: 5 commits new 0d029ec653 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af296a20dc 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 29e96a7549 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1d3a94b13d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9a5d0b8b82 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 81054bad64 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 9b721f83a8 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new bda273d793 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 19bf6bf752 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new fff10839ca 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 7da8bd11f9 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new e2c046aa08 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new ac4f58efd8 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 37bebfcdee 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 82139aeb71 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new f47a05950c 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 93664f5dcf 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new b67e8f821b 34: onsuccess: #465: 1: Success after binutils: 11 commits new f67c65e3c1 35: onsuccess: #467: 1: Success after glibc: 2 commits new b5a616c6d9 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 779ad6a776 37: onsuccess: #470: 1: Success after binutils: 3 commits new 36b0983acd 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 481bba00db 39: onsuccess: #474: 1: Success after binutils: 8 commits new 471341300f 40: onsuccess: #476: 1: Success after linux: 69 commits new 1cc11ac9be 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new a8b56e7e32 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 7f40d71055 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new cb2cc6a5a0 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new a227d0aef4 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new f4ee5c183e 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 8abd0b050f 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 633b4e28bf 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 6a1da501d3 49: onsuccess: #487: 1: Success after binutils: 11 commits new 81ee40229c 50: onsuccess: #490: 1: Success after binutils: 6 commits new d65f5ad4ae 51: onsuccess: #493: 1: Success after binutils: 13 commits new 51206f0110 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 97f7f196e5 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 39116f1ef2 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 6379025f3c 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new d0436df8b0 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new c8ed8dd9d9 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 055a36ee09 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 7f047c6f3a 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 4a9914e550 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 9733842e56 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new ee01549bc9 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new cc5e6535a5 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 46afd83ae1 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new a5a1362429 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new df759d6aa5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 6a431c1ac1 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 980872f183 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 1ade13129c 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 08f99562f4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new e93642214a 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 43441f1b45 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new c927efb591 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new e3597d4b52 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new fa7621b0fd 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new cdd7aafd5a 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 76bc074316 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 90589bece8 78: onsuccess: #522: 1: Success after binutils: 10 commits new 0ab860e3e6 79: onsuccess: #523: 1: Success after gcc: 25 commits new acde30875a 80: onsuccess: #524: 1: Success after linux: 9 commits new afd22b2fd4 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 8de3b0887f 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new b004a3802d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 590e86a1e6 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 9d750797d9 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 96a4a5b63e 86: onsuccess: #532: 1: Success after gcc: 16 commits new 3b0aca9f68 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 9c6b3a6c5b 88: onsuccess: #534: 1: Success after linux: 12 commits new a9aa6b978e 89: onsuccess: #536: 1: Success after binutils: 27 commits new 6af4a48abb 90: onsuccess: #538: 1: Success after glibc: 10 commits new 3911fe1fb6 91: onsuccess: #539: 1: Success after linux: 27 commits new ab3b840a4c 92: onsuccess: #543: 1: Success after glibc: 4 commits new cd3928814c 93: onsuccess: #544: 1: Success after linux: 34 commits new 916ba53cf8 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new d10f9ddced 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new cc6cc0de61 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new fba0c8b09e 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 29612b3f0a 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new a12a73e435 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 5edf5109fb 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 0df0e067a8 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 5f8886f3a5 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new e9aaa438ec 103: onsuccess: #555: 1: Success after binutils: 4 commits new 1d140d9062 104: onsuccess: #558: 1: Success after binutils: 3 commits new f02cf191fc 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new aed19d80e7 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 417d880b4a 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new c60fed6392 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new d3455e5b11 109: onsuccess: #564: 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 (a6616ffdc2) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 1680 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52460 -> 54096 bytes 04-build_abe-gcc/console.log.xz | Bin 233036 -> 235040 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8820 bytes 07-build_abe-glibc/console.log.xz | Bin 235980 -> 236328 bytes 08-build_abe-gdb/console.log.xz | Bin 50360 -> 52256 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3812 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2464 -> 3584 bytes 11-check_regression/console.log.xz | Bin 6568 -> 7264 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 7 + 11-check_regression/mail-body.txt | 27 + 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 192 +- 11-check_regression/results.regressions | 27 + 12-update_baseline/console.log | 40 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 27 + sumfiles/g++.log.xz | Bin 2861624 -> 2863516 bytes sumfiles/g++.sum | 211 +- sumfiles/gcc.log.xz | Bin 2561944 -> 2536520 bytes sumfiles/gcc.sum | 4741 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 949884 -> 951896 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229120 -> 229060 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466984 -> 469432 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2841 insertions(+), 2617 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions