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 b0bfe9b848 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards c461762183 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 20325dd577 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 1569a4f3be 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards bb284e7c98 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 7f0302d4e4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards e05adc9e25 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards d92bceff50 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 9136439222 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 4e2e882d5a 93: onsuccess: #544: 1: Success after linux: 34 commits discards 744dfe3f9f 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 11c4a56553 91: onsuccess: #539: 1: Success after linux: 27 commits discards de6883d557 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 786b664498 89: onsuccess: #536: 1: Success after binutils: 27 commits discards c180590c4d 88: onsuccess: #534: 1: Success after linux: 12 commits discards 13b8f97432 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 34b4c08a5c 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 26da72b53f 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards ec6c9b85ad 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards d73b93a51d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards bf174d995b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards ce4e60e717 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards 97ad357afb 80: onsuccess: #524: 1: Success after linux: 9 commits discards 984ec5c88c 79: onsuccess: #523: 1: Success after gcc: 25 commits discards c7761c3fc3 78: onsuccess: #522: 1: Success after binutils: 10 commits discards ed5f94daec 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards 4f943d60dc 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 120093d684 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 2f4746086c 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 8a7a8ea436 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 3350bf5589 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 035c8c1bfb 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards 8fa3ffcbfc 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 66eec31ba4 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards c21c089db5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards faa9a4123b 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards b46100e9c9 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 8dae571fd5 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 8112e131af 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 92f38dd6e1 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 7134f4e582 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 0c97002d3c 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 9f50e8306c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards 652f36e71e 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 13a2ca28ef 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 51e8981140 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards 5bc4dfa980 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 005aa59092 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards b8ab1c41db 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 9e2e15d946 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 80715687cd 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 8fff68680f 51: onsuccess: #493: 1: Success after binutils: 13 commits discards f577811b99 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 7312970407 49: onsuccess: #487: 1: Success after binutils: 11 commits discards a7cb760950 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards f9b4fdbae2 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards e43e8df6b2 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards e071393423 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards cae0c174e5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 7992d4ef3c 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards fe4357c249 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards 73147c2b23 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards ef303c6ccf 40: onsuccess: #476: 1: Success after linux: 69 commits discards 81aa5007db 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 241a1e2d8d 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 758c6955b1 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 5e91cb2a3e 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 863d1b7fd4 35: onsuccess: #467: 1: Success after glibc: 2 commits discards b6a4efd648 34: onsuccess: #465: 1: Success after binutils: 11 commits discards af14eebdc2 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 3f29923b3b 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 076b1e89c4 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards ab5c14b264 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 3487748ffd 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards e7934cd411 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 07a21d37e5 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards a4a81a3055 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards b71cd04d16 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards a60bf96777 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards 874481a6d2 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 0982340384 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards c97f18db3b 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards f8b24b5528 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1f815c84b9 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 374f37feca 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10ce127a04 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c7294791aa 16: onsuccess: 1: Successful build after binutils: 5 commits discards d2cd1abb12 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e235175a97 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4c57e3fe12 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1933ef326e 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5c8f9d89a7 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 32c54ec79d 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a22684cc17 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 6e34ec12bc 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 06ce20c4ee 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards b61e636714 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards fed3b27bed 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 7fe737b2b0 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards f4bec433ed 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 6e1f909a39 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 47bf2bb3c7 2: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 9a094198bb 3: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 2fd5282033 4: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new ee20f88198 5: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 174d623996 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 1afc964d02 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new df09d40bb5 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 9fdba1ca27 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new dedd904304 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f312467766 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ed577d9c13 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2ac5eb0a25 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c471689c73 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 844a965cf3 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 483c58e246 16: onsuccess: 1: Successful build after binutils: 5 commits new 9dd047d30d 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 46090cb5ed 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new f9b15f5359 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0a11c48874 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5edceeaba6 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 0eb4230afd 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 8dc97fbd7c 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 10fa88f42a 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 763653fd3a 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 267b962014 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new 1abb752f45 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 53e6137957 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new dc3c80ce62 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new c78c5ee6f0 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 1330fb13cd 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new ce00ab3a4e 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new eccf85e4e9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 95382712f4 34: onsuccess: #465: 1: Success after binutils: 11 commits new afd3e6b7ea 35: onsuccess: #467: 1: Success after glibc: 2 commits new c63fb34cd3 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 4cd8f72b6b 37: onsuccess: #470: 1: Success after binutils: 3 commits new 98ee4a58f4 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new fd5e75a450 39: onsuccess: #474: 1: Success after binutils: 8 commits new 9682110c33 40: onsuccess: #476: 1: Success after linux: 69 commits new c710d4686f 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 2860d9147f 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 834b73db9a 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new a470f91ce7 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 8889e16117 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new 9e614b1def 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 35a0819e3b 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new e76cc810fc 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 798dd24f10 49: onsuccess: #487: 1: Success after binutils: 11 commits new 8f3d4bfb56 50: onsuccess: #490: 1: Success after binutils: 6 commits new b770c01f47 51: onsuccess: #493: 1: Success after binutils: 13 commits new bd6d73f188 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new f61472b6a3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 5c435bef93 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 7ef1f04f6d 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new c97d494eac 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new fc3866fac8 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 63e164d472 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new f996607869 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 6eee749f74 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 85c979acfa 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 6b6da1d5ae 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new 24eaeb2e16 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new 76e92905a0 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 9a56b93a85 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 4bac4ba508 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new e29a27cbc1 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 5d33f19037 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new c4b776ae07 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 7b37aa68f4 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new f3940c9788 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 2ebae2dde1 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new e738bac6be 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 4d7c766bac 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new 3aa57de521 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 5b3853ead3 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new aa5986b8a6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new a99c3cfe9b 78: onsuccess: #522: 1: Success after binutils: 10 commits new 5ad94a5bb1 79: onsuccess: #523: 1: Success after gcc: 25 commits new 6bef4de301 80: onsuccess: #524: 1: Success after linux: 9 commits new 18ed867908 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new b249b1827b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new e7d1842a8d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 353277f3a7 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new cf28b35a30 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new e474f66a45 86: onsuccess: #532: 1: Success after gcc: 16 commits new 321ec2af38 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 4164ab25b5 88: onsuccess: #534: 1: Success after linux: 12 commits new 56227a2c8d 89: onsuccess: #536: 1: Success after binutils: 27 commits new b1b4db7e9a 90: onsuccess: #538: 1: Success after glibc: 10 commits new cb1893f49e 91: onsuccess: #539: 1: Success after linux: 27 commits new 8fd9e1573a 92: onsuccess: #543: 1: Success after glibc: 4 commits new 38538dfb7c 93: onsuccess: #544: 1: Success after linux: 34 commits new a703e9eadb 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 0158f81c7e 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 8da300098a 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new 1f8bdae73b 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new 676f0cf703 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new b0476152f7 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 3e43b603ab 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 377ca3b8ec 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new d25e28e78c 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new abac248e6e 103: onsuccess: #555: 1: Success after binutils: 4 commits

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 (b0bfe9b848) \ 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 1700 -> 1652 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 51276 -> 51372 bytes 04-build_abe-gcc/console.log.xz | Bin 233228 -> 234512 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8828 -> 8936 bytes 07-build_abe-glibc/console.log.xz | Bin 235276 -> 237040 bytes 08-build_abe-gdb/console.log.xz | Bin 49732 -> 50432 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2488 -> 2524 bytes 11-check_regression/console.log.xz | Bin 7860 -> 4832 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 6 - 11-check_regression/mail-body.txt | 34 +- 11-check_regression/results.compare | 25 +- 11-check_regression/results.compare2 | 195 +- 11-check_regression/results.regressions | 26 - 12-update_baseline/console.log | 54 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 26 - sumfiles/g++.log.xz | Bin 2910400 -> 2908048 bytes sumfiles/g++.sum | 128 +- sumfiles/gcc.log.xz | Bin 2512744 -> 2512744 bytes sumfiles/gcc.sum | 4522 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 957772 -> 953052 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2252 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 228176 -> 229264 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 471776 -> 473492 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2461 insertions(+), 2704 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