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 f7bf24dc61 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 476d999cdb 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards e9c4abe4b1 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 150906f5ca 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 0b63b78362 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 5ec8ca6fb6 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 2e56a9cdba 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards e0340ca06c 93: onsuccess: #544: 1: Success after linux: 34 commits discards 598d91d286 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 7cb99aee27 91: onsuccess: #539: 1: Success after linux: 27 commits discards cd9af6ec60 90: onsuccess: #538: 1: Success after glibc: 10 commits discards deebee4eb3 89: onsuccess: #536: 1: Success after binutils: 27 commits discards c1b19ef146 88: onsuccess: #534: 1: Success after linux: 12 commits discards 1cac35ff22 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 6567aad3b7 86: onsuccess: #532: 1: Success after gcc: 16 commits discards e89db40982 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 4982559212 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 0f91bf7360 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 175eb249d1 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards c3ca7fff1a 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 161aed63de 80: onsuccess: #524: 1: Success after linux: 9 commits discards f8d6c98f95 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 6aa287848d 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 273fa0a971 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards b76f386d91 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 82ef810deb 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 9839663f27 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 2aed428fe1 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 9fc22b2c4a 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 8dfbad3019 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 562138c0fe 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 47d24d9745 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards 5b3b2b315c 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 12816684b4 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards c6b845a691 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards bd1d7b5f9f 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 4bcd489e4e 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 2004cdb8c8 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 2897dd1332 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 7283021fa0 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 22f9ba2cf3 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards dfb7685eba 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards eee4783e9e 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards a04ca0fbf7 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards cf0b7644ce 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards a2fd0d5a31 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards e01db3839c 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 72ef2b43d3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 8ce5d3dbb3 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 5238701a0c 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 6d3ccddeef 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 9854cb4770 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 25d846b11b 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 1910d86a62 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 661788cbc4 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards a17a4f3fb6 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards d8d448087b 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 5e5c37906b 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 1d13f4d3f0 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 6e8e3f6716 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 43632f88f0 40: onsuccess: #476: 1: Success after linux: 69 commits discards bfe49845c0 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 13a0999409 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards c0b942be3a 37: onsuccess: #470: 1: Success after binutils: 3 commits discards e840761f62 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards a4d4915cd6 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 6623331580 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 7520b65480 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 02fbd41db0 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 40a66d930d 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 3b93279f67 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 872e366d8f 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 6521edafa3 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 3807c21b3b 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 85f2fb7578 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards e7797a1dc2 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards c5408ea99b 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 4d67e802e7 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 76ed1c96b6 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards eccfe8cb3a 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards ebda1fc481 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 368d8a24f0 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 991e14ae1b 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ec96f306f2 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c2c21b603b 16: onsuccess: 1: Successful build after binutils: 5 commits discards a0ca39358e 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 0c95fe41f5 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d38a813d3c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e2766d3ca0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e396f401d7 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a7db1b88df 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9c799f9a0a 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6c4986ec60 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards aac8f4992c 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 03210408fc 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3cacfce2e6 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards e62863bec2 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 3ad967deb8 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6ef6b5d871 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 8d4429fbfc 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 47a5e89b97 0: update: binutils-gcc-linux-glibc-gdb: 1 new 5b57617fd1 0: update: binutils-gcc-linux-glibc-gdb: 1 new 7a6d81d84e 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e219c53404 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2e122e17fd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new e8581f5957 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4bf6fb78c3 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b3cb9c188d 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 687ea2be0a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c552196b7a 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new e8f714c0a5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new ea6e26c284 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3bcf254f39 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ac68402b66 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b9ba47442f 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new aaf3be5181 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b5867ddf90 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 04c5a4bf2b 16: onsuccess: 1: Successful build after binutils: 5 commits new c84d0b3ee2 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new af7cd02b71 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new def5435600 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3531340ae2 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 47ce0e4c8a 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 2f971d81e2 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 5960225c02 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new f281767627 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 36c5941278 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new e06ffc1fe8 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 1da51481e0 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 415589e900 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 1a3e04adaf 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new c323625115 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new de707f54a7 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 26d5003c04 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 7c166ce9a5 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 3b3beb7448 34: onsuccess: #465: 1: Success after binutils: 11 commits new d77570cd50 35: onsuccess: #467: 1: Success after glibc: 2 commits new 7da92cbda6 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 1e9845534b 37: onsuccess: #470: 1: Success after binutils: 3 commits new c01351e309 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new e2e4644069 39: onsuccess: #474: 1: Success after binutils: 8 commits new f0f5170d6d 40: onsuccess: #476: 1: Success after linux: 69 commits new 8e22273af5 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 436a9bd48c 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new a561a1981c 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 1a3fe0590c 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 94239e638d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 44e7a66a6b 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 657a29614b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new ca4ff77e2d 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new da74bbcbe5 49: onsuccess: #487: 1: Success after binutils: 11 commits new f1ef03fbfb 50: onsuccess: #490: 1: Success after binutils: 6 commits new 27c90c85ac 51: onsuccess: #493: 1: Success after binutils: 13 commits new 90027164a8 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 577b342336 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 08a392b19a 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new f39144abdc 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 0bbedcc137 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new dde194eb1a 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new ebf5a6a3a3 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new bb64a751b1 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 5852db22f5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 7a8d0316a0 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new ca191f30c0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 317eef2881 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 871c1ab528 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 73f5234470 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new d019696cfa 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 882494775b 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new c02a7caf8e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new e58d8cab6a 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new da9b3668ea 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new f413a9d262 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 6d6222f829 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 05ee6cd53e 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 747d46b0df 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 78ccaed652 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new ba031ee4b5 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 8ee31715f7 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new f3bcc9c90a 78: onsuccess: #522: 1: Success after binutils: 10 commits new 80d968aa47 79: onsuccess: #523: 1: Success after gcc: 25 commits new 933d433f7b 80: onsuccess: #524: 1: Success after linux: 9 commits new f14e9358fe 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new f552e763a2 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 717135c3d1 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new f4a0a266bc 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 169c11e634 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 407199073a 86: onsuccess: #532: 1: Success after gcc: 16 commits new ac72967168 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 46c989dccc 88: onsuccess: #534: 1: Success after linux: 12 commits new 06c63e7909 89: onsuccess: #536: 1: Success after binutils: 27 commits new 6f6dbb3477 90: onsuccess: #538: 1: Success after glibc: 10 commits new 44e1716a82 91: onsuccess: #539: 1: Success after linux: 27 commits new 03c9d8ff02 92: onsuccess: #543: 1: Success after glibc: 4 commits new d7806f58ed 93: onsuccess: #544: 1: Success after linux: 34 commits new d220a767ce 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 0fd0d1f5c8 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7e8efb4631 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new d0e10ee700 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 09a84342f1 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 417f9603c1 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 6a3159bb53 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 7f4d5af984 101: onsuccess: #552: 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 (f7bf24dc61) \ 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 1692 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 52036 -> 50684 bytes 04-build_abe-gcc/console.log.xz | Bin 233656 -> 234864 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8852 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 235232 -> 235356 bytes 08-build_abe-gdb/console.log.xz | Bin 51132 -> 49120 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2524 -> 3904 bytes 11-check_regression/console.log.xz | Bin 8316 -> 7040 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 33 +- 11-check_regression/results.compare2 | 265 +- 11-check_regression/results.regressions | 41 - 12-update_baseline/console.log | 39 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 41 - sumfiles/g++.log.xz | Bin 2908760 -> 2887564 bytes sumfiles/g++.sum | 156 +- sumfiles/gcc.log.xz | Bin 2522656 -> 2552924 bytes sumfiles/gcc.sum | 4693 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 950084 -> 949848 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 227944 -> 228304 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 476788 -> 473748 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 2705 insertions(+), 2771 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