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 e22c0bbe82 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 6e0e7244ac 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 97749eba0a 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 176ca3ae10 103: onsuccess: #555: 1: Success after binutils: 4 commits discards d4c9f8f15e 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 7502bcacc2 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 93dd91c325 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 21999df736 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 730e2189a8 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards f116f1333e 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 080c7ca2a2 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 244da612c9 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards ca7e22c6a6 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 96aa5c4fb0 93: onsuccess: #544: 1: Success after linux: 34 commits discards 2ca3302347 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 6e00493ba8 91: onsuccess: #539: 1: Success after linux: 27 commits discards 5168a7c8bd 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 26db0b30de 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 62d1adebc1 88: onsuccess: #534: 1: Success after linux: 12 commits discards fd15abf0ce 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 37f5adc2e0 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 52942fd92b 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 70f977bcb9 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 34ab854168 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 49d7698bce 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards fc3e166714 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 9c7ab9e0fc 80: onsuccess: #524: 1: Success after linux: 9 commits discards a02e58d58a 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 5335db9900 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 1fa43db508 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 034207c439 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 6515b8bbc0 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 792c6ebe54 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 50cb8d3dbd 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 371b5ab1bb 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards de712e2165 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 4b6da8aaf7 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 3a337e95c5 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards dde6b454d8 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards c7d08a3323 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 558cfd5ca5 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 1e199da362 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 0aa0a85703 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 890d027cba 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 4af5ffff2d 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards dc2ec50ad9 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 09684372c8 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 0e2d244d61 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards dfcddd965c 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 50820ae68c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 8dc8d9fb66 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 18088ae6ba 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards c1fe855dec 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 10b8a88b1b 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards bbb5fa0e89 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 767bbb6424 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 97c3d9019a 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 8ebc2ea959 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 0835efefa2 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 39b3cfb250 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 74037fd372 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards ffec2ed569 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 9f051286f8 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 9a6eae49da 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards ea1c263087 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 1a7000bcbf 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 2985a3b748 40: onsuccess: #476: 1: Success after linux: 69 commits discards 4a8b7493f9 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 19dec0e0b7 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 47583a6b76 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 2e6090316d 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 80a7ef7601 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 13d90a86ed 34: onsuccess: #465: 1: Success after binutils: 11 commits discards eac6c5fa17 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 8b965ec60e 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 8218b0b49b 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards c561df8dd7 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards b1ddee5d71 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards b536d39b20 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 4cb2f211b9 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 41aa17e86f 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards da08783add 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards bc4ef1ff27 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 37af35d748 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 57b96913a0 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 42aa72bb91 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 2ac046c0cd 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3466297e90 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d51cbc0d47 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3132a91c53 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c5767deae 16: onsuccess: 1: Successful build after binutils: 5 commits discards 51043b84c6 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 29b5ff7479 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a30f2c4200 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e39709870a 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 367a3d886b 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 6743b52a65 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 942099bb05 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards e1daee884b 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 758e10bbaf 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 112bf04852 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 0cafdf82ab 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 67f9da07e3 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 50afef2847 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3a6142e8d1 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 390d38a814 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b038d15874 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 592874bb89 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d069b22b63 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ee3a14e7fe 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 894eaaaace 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b6aec84e68 16: onsuccess: 1: Successful build after binutils: 5 commits new c81d447fb1 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 938fd29699 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f644865ddb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 70d082c8fd 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 157970cb46 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 3c146199e5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new a6998a6dd0 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 6dfcc34d3f 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new cbfc490dd1 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 5d76e7e631 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new d058154df1 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 502ac72efd 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 400797dda2 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 25fbf95d90 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new b73db66dfe 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 2b2f8ea820 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new aa3bd849e9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new b1b452e5ad 34: onsuccess: #465: 1: Success after binutils: 11 commits new c8125bda66 35: onsuccess: #467: 1: Success after glibc: 2 commits new ee7b83cfeb 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 0e00aad570 37: onsuccess: #470: 1: Success after binutils: 3 commits new e9b6cdd65a 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new d73ea9a8a7 39: onsuccess: #474: 1: Success after binutils: 8 commits new 56966edf8f 40: onsuccess: #476: 1: Success after linux: 69 commits new ab86af1909 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 8bd72b602f 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 276c0f2cf8 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new cce54e6990 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 7a26919d29 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 16264598de 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 33bb4465d7 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new d0213d0d32 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 8ebd63ca07 49: onsuccess: #487: 1: Success after binutils: 11 commits new c9ed93373e 50: onsuccess: #490: 1: Success after binutils: 6 commits new 6ce7e6d024 51: onsuccess: #493: 1: Success after binutils: 13 commits new 70c34a1621 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 4ffa0f4dff 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new fd467889cc 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 7844a09ccd 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new dcd9a91b2b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 370667a9ed 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 62c043135d 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new d6341becaf 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new f76782e040 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 1fb5b3e89b 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new f442bfb208 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 419baecaf1 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new e77a117600 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 8b06c76ba0 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 0b81eb0d31 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 1a7a8ccac2 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new c533fa9400 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 6774379e9e 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new a3f673895a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new f259f64900 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new e8079898da 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 661679822f 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 9b9bb3943d 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new d87914a28f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new f4c8345285 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 854058b8b6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new 5d3bc35ccd 78: onsuccess: #522: 1: Success after binutils: 10 commits new 9419d21428 79: onsuccess: #523: 1: Success after gcc: 25 commits new ab2c36bde0 80: onsuccess: #524: 1: Success after linux: 9 commits new 0704f62bc8 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 4b5bdf606d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 59b5415536 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 8a09e63813 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 0c452463b3 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 42797d1943 86: onsuccess: #532: 1: Success after gcc: 16 commits new 02b77adcbd 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new ab3c74eb19 88: onsuccess: #534: 1: Success after linux: 12 commits new bc34ec6c1c 89: onsuccess: #536: 1: Success after binutils: 27 commits new 8bff3c7f1a 90: onsuccess: #538: 1: Success after glibc: 10 commits new 6a0ff9d181 91: onsuccess: #539: 1: Success after linux: 27 commits new d1f4cf79a7 92: onsuccess: #543: 1: Success after glibc: 4 commits new f721ca4e23 93: onsuccess: #544: 1: Success after linux: 34 commits new 6686808833 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new fc77bcf0af 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new c56e419a29 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new e3bd7b01c4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 68b1be25ed 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 0b22baccb2 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 1e6156da2a 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 48002f91b3 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 7c685fe47c 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 6cf6283199 103: onsuccess: #555: 1: Success after binutils: 4 commits new 378cf229b9 104: onsuccess: #558: 1: Success after binutils: 3 commits new 991d6b19e1 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new fa87ce643d 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 1bb0c2171f 107: onsuccess: #562: 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 (e22c0bbe82) \ 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 1684 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 53532 -> 52188 bytes 04-build_abe-gcc/console.log.xz | Bin 234244 -> 232448 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8936 -> 8552 bytes 07-build_abe-glibc/console.log.xz | Bin 236088 -> 234444 bytes 08-build_abe-gdb/console.log.xz | Bin 51604 -> 50404 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2468 -> 2560 bytes 11-check_regression/console.log.xz | Bin 6216 -> 7968 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 68 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 385 ++- 11-check_regression/results.regressions | 27 - 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 | 70 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 27 - sumfiles/g++.log.xz | Bin 2880608 -> 2911952 bytes sumfiles/g++.sum | 409 ++- sumfiles/gcc.log.xz | Bin 2525668 -> 2508664 bytes sumfiles/gcc.sum | 4714 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 953676 -> 940024 bytes sumfiles/gfortran.sum | 104 +- sumfiles/libatomic.log.xz | Bin 2256 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229468 -> 228176 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470208 -> 462452 bytes sumfiles/libstdc++.sum | 13 +- 42 files changed, 3143 insertions(+), 2839 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-check_regression/results.regressions