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 7f4d5af984 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6a3159bb53 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 417f9603c1 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 09a84342f1 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards d0e10ee700 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards 7e8efb4631 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 0fd0d1f5c8 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards d220a767ce 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards d7806f58ed 93: onsuccess: #544: 1: Success after linux: 34 commits discards 03c9d8ff02 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 44e1716a82 91: onsuccess: #539: 1: Success after linux: 27 commits discards 6f6dbb3477 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 06c63e7909 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 46c989dccc 88: onsuccess: #534: 1: Success after linux: 12 commits discards ac72967168 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 407199073a 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 169c11e634 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards f4a0a266bc 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 717135c3d1 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards f552e763a2 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards f14e9358fe 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 933d433f7b 80: onsuccess: #524: 1: Success after linux: 9 commits discards 80d968aa47 79: onsuccess: #523: 1: Success after gcc: 25 commits discards f3bcc9c90a 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 8ee31715f7 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards ba031ee4b5 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 78ccaed652 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 747d46b0df 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 05ee6cd53e 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 6d6222f829 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards f413a9d262 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards da9b3668ea 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards e58d8cab6a 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards c02a7caf8e 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 882494775b 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards d019696cfa 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 73f5234470 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 871c1ab528 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 317eef2881 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards ca191f30c0 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 7a8d0316a0 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 5852db22f5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards bb64a751b1 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards ebf5a6a3a3 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards dde194eb1a 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 0bbedcc137 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards f39144abdc 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards 08a392b19a 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 577b342336 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 90027164a8 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 27c90c85ac 51: onsuccess: #493: 1: Success after binutils: 13 commits discards f1ef03fbfb 50: onsuccess: #490: 1: Success after binutils: 6 commits discards da74bbcbe5 49: onsuccess: #487: 1: Success after binutils: 11 commits discards ca4ff77e2d 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 657a29614b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 44e7a66a6b 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 94239e638d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 1a3fe0590c 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards a561a1981c 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 436a9bd48c 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 8e22273af5 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards f0f5170d6d 40: onsuccess: #476: 1: Success after linux: 69 commits discards e2e4644069 39: onsuccess: #474: 1: Success after binutils: 8 commits discards c01351e309 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 1e9845534b 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 7da92cbda6 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards d77570cd50 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 3b3beb7448 34: onsuccess: #465: 1: Success after binutils: 11 commits discards 7c166ce9a5 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 26d5003c04 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards de707f54a7 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards c323625115 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 1a3e04adaf 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 415589e900 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 1da51481e0 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards e06ffc1fe8 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 36c5941278 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards f281767627 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 5960225c02 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 2f971d81e2 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 47ce0e4c8a 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 3531340ae2 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards def5435600 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards af7cd02b71 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c84d0b3ee2 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 04c5a4bf2b 16: onsuccess: 1: Successful build after binutils: 5 commits discards b5867ddf90 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards aaf3be5181 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b9ba47442f 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ac68402b66 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3bcf254f39 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea6e26c284 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e8f714c0a5 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards c552196b7a 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 687ea2be0a 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b3cb9c188d 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 4bf6fb78c3 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards e8581f5957 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 2e122e17fd 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards e219c53404 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 7a6d81d84e 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 1342e14ecb 1: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6e1f909a39 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new f4bec433ed 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 7fe737b2b0 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new fed3b27bed 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new b61e636714 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 06ce20c4ee 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 6e34ec12bc 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new a22684cc17 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 32c54ec79d 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5c8f9d89a7 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1933ef326e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4c57e3fe12 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e235175a97 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d2cd1abb12 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c7294791aa 16: onsuccess: 1: Successful build after binutils: 5 commits new 10ce127a04 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 374f37feca 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1f815c84b9 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f8b24b5528 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c97f18db3b 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 0982340384 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 874481a6d2 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new a60bf96777 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new b71cd04d16 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new a4a81a3055 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 07a21d37e5 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new e7934cd411 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 3487748ffd 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new ab5c14b264 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 076b1e89c4 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 3f29923b3b 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new af14eebdc2 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new b6a4efd648 34: onsuccess: #465: 1: Success after binutils: 11 commits new 863d1b7fd4 35: onsuccess: #467: 1: Success after glibc: 2 commits new 5e91cb2a3e 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 758c6955b1 37: onsuccess: #470: 1: Success after binutils: 3 commits new 241a1e2d8d 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 81aa5007db 39: onsuccess: #474: 1: Success after binutils: 8 commits new ef303c6ccf 40: onsuccess: #476: 1: Success after linux: 69 commits new 73147c2b23 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new fe4357c249 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 7992d4ef3c 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new cae0c174e5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new e071393423 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new e43e8df6b2 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new f9b4fdbae2 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new a7cb760950 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 7312970407 49: onsuccess: #487: 1: Success after binutils: 11 commits new f577811b99 50: onsuccess: #490: 1: Success after binutils: 6 commits new 8fff68680f 51: onsuccess: #493: 1: Success after binutils: 13 commits new 80715687cd 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 9e2e15d946 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new b8ab1c41db 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 005aa59092 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 5bc4dfa980 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 51e8981140 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 13a2ca28ef 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 652f36e71e 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 9f50e8306c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 0c97002d3c 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 7134f4e582 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 92f38dd6e1 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 8112e131af 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 8dae571fd5 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new b46100e9c9 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new faa9a4123b 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new c21c089db5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 66eec31ba4 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 8fa3ffcbfc 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 035c8c1bfb 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 3350bf5589 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 8a7a8ea436 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 2f4746086c 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 120093d684 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 4f943d60dc 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new ed5f94daec 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new c7761c3fc3 78: onsuccess: #522: 1: Success after binutils: 10 commits new 984ec5c88c 79: onsuccess: #523: 1: Success after gcc: 25 commits new 97ad357afb 80: onsuccess: #524: 1: Success after linux: 9 commits new ce4e60e717 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new bf174d995b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new d73b93a51d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new ec6c9b85ad 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 26da72b53f 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 34b4c08a5c 86: onsuccess: #532: 1: Success after gcc: 16 commits new 13b8f97432 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new c180590c4d 88: onsuccess: #534: 1: Success after linux: 12 commits new 786b664498 89: onsuccess: #536: 1: Success after binutils: 27 commits new de6883d557 90: onsuccess: #538: 1: Success after glibc: 10 commits new 11c4a56553 91: onsuccess: #539: 1: Success after linux: 27 commits new 744dfe3f9f 92: onsuccess: #543: 1: Success after glibc: 4 commits new 4e2e882d5a 93: onsuccess: #544: 1: Success after linux: 34 commits new 9136439222 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new d92bceff50 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new e05adc9e25 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 7f0302d4e4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new bb284e7c98 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 1569a4f3be 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 20325dd577 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new c461762183 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new b0bfe9b848 102: onsuccess: #553: 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 (7f4d5af984) \ 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 -> 1700 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 50684 -> 51276 bytes 04-build_abe-gcc/console.log.xz | Bin 234864 -> 233228 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8812 -> 8828 bytes 07-build_abe-glibc/console.log.xz | Bin 235356 -> 235276 bytes 08-build_abe-gdb/console.log.xz | Bin 49120 -> 49732 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3808 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3904 -> 2488 bytes 11-check_regression/console.log.xz | Bin 7040 -> 7860 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 6 + 11-check_regression/mail-body.txt | 67 +- 11-check_regression/results.compare | 28 +- 11-check_regression/results.compare2 | 267 +- 11-check_regression/results.regressions | 26 + 12-update_baseline/console.log | 36 +- 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 | 69 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 26 + sumfiles/g++.log.xz | Bin 2887564 -> 2910400 bytes sumfiles/g++.sum | 181 +- sumfiles/gcc.log.xz | Bin 2552924 -> 2512744 bytes sumfiles/gcc.sum | 5130 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 949848 -> 957772 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 228304 -> 228176 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2672 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473748 -> 471776 bytes sumfiles/libstdc++.sum | 28 +- 42 files changed, 3092 insertions(+), 2887 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