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 1bb0c2171f 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards fa87ce643d 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 991d6b19e1 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 378cf229b9 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 6cf6283199 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 7c685fe47c 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 48002f91b3 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 1e6156da2a 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 0b22baccb2 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 68b1be25ed 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards e3bd7b01c4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards c56e419a29 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards fc77bcf0af 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 6686808833 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards f721ca4e23 93: onsuccess: #544: 1: Success after linux: 34 commits discards d1f4cf79a7 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 6a0ff9d181 91: onsuccess: #539: 1: Success after linux: 27 commits discards 8bff3c7f1a 90: onsuccess: #538: 1: Success after glibc: 10 commits discards bc34ec6c1c 89: onsuccess: #536: 1: Success after binutils: 27 commits discards ab3c74eb19 88: onsuccess: #534: 1: Success after linux: 12 commits discards 02b77adcbd 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 42797d1943 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 0c452463b3 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards 8a09e63813 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 59b5415536 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 4b5bdf606d 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 0704f62bc8 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards ab2c36bde0 80: onsuccess: #524: 1: Success after linux: 9 commits discards 9419d21428 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 5d3bc35ccd 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 854058b8b6 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards f4c8345285 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards d87914a28f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 9b9bb3943d 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards 661679822f 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards e8079898da 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards f259f64900 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards a3f673895a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards 6774379e9e 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards c533fa9400 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 1a7a8ccac2 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards 0b81eb0d31 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 8b06c76ba0 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards e77a117600 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 419baecaf1 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards f442bfb208 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 1fb5b3e89b 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards f76782e040 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards d6341becaf 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards 62c043135d 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards 370667a9ed 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards dcd9a91b2b 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 7844a09ccd 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards fd467889cc 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards 4ffa0f4dff 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 70c34a1621 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 6ce7e6d024 51: onsuccess: #493: 1: Success after binutils: 13 commits discards c9ed93373e 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 8ebd63ca07 49: onsuccess: #487: 1: Success after binutils: 11 commits discards d0213d0d32 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards 33bb4465d7 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 16264598de 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 7a26919d29 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards cce54e6990 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 276c0f2cf8 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 8bd72b602f 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards ab86af1909 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 56966edf8f 40: onsuccess: #476: 1: Success after linux: 69 commits discards d73ea9a8a7 39: onsuccess: #474: 1: Success after binutils: 8 commits discards e9b6cdd65a 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 0e00aad570 37: onsuccess: #470: 1: Success after binutils: 3 commits discards ee7b83cfeb 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards c8125bda66 35: onsuccess: #467: 1: Success after glibc: 2 commits discards b1b452e5ad 34: onsuccess: #465: 1: Success after binutils: 11 commits discards aa3bd849e9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards 2b2f8ea820 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards b73db66dfe 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 25fbf95d90 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards 400797dda2 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 502ac72efd 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards d058154df1 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 5d76e7e631 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards cbfc490dd1 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 6dfcc34d3f 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards a6998a6dd0 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 3c146199e5 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 157970cb46 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 70d082c8fd 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f644865ddb 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 938fd29699 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c81d447fb1 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b6aec84e68 16: onsuccess: 1: Successful build after binutils: 5 commits discards 894eaaaace 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ee3a14e7fe 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d069b22b63 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 592874bb89 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b038d15874 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 390d38a814 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 3a6142e8d1 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 50afef2847 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards 67f9da07e3 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4e57517887 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new c0b8f607f8 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 3dc414f5e9 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new bc56f2f032 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 80f508a9d1 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6546be88c0 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0961b04dfe 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d6fdaa023f 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d7251d304d 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 301ad2b9b0 16: onsuccess: 1: Successful build after binutils: 5 commits new 33bfbf799f 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4622d540f1 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3e7a186d2b 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 267d660f6d 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd7a8d5803 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 0f54afcf1f 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 073d1ed417 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new 128594f2ff 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 630434a62f 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new d0b27d454d 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new b8bacedb2d 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 5f03cbf1ff 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new 17be369073 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 1ef6b4db30 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new 753605753e 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new 493daff18f 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new a09dda7b06 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 97a085230e 34: onsuccess: #465: 1: Success after binutils: 11 commits new 3b75717b30 35: onsuccess: #467: 1: Success after glibc: 2 commits new ecdc9ce7f1 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 7e4ba6c9eb 37: onsuccess: #470: 1: Success after binutils: 3 commits new 61c5a52ff1 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 44fdb44fe6 39: onsuccess: #474: 1: Success after binutils: 8 commits new 0ed2da219c 40: onsuccess: #476: 1: Success after linux: 69 commits new 146597dd1b 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new cec70a9b05 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 5621006608 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 1319b7ddb5 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 63cfc43319 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new e334f9141d 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new f2add3ec9c 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new c6227cfd7f 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 39f89f9147 49: onsuccess: #487: 1: Success after binutils: 11 commits new 32781e0dcf 50: onsuccess: #490: 1: Success after binutils: 6 commits new 3bcdd65be3 51: onsuccess: #493: 1: Success after binutils: 13 commits new ec3dc6db54 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 14c7bb4626 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new acbe15ee22 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 7cac5d2fa3 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 70a0db1733 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new 5e53fded8c 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 73ce7e6a7a 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new ddeaf72a1e 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 14588385a5 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new df938afc3d 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 3fdd47a5fb 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new c68d270450 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new bb8f14534c 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new 56ba8994c4 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 6cd0c2c024 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new e91f06ca01 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new 96e92bfa21 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 54789cf475 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new f64fe2e19a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new 4cdb0d6ae3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new d120b18093 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 82caddc4fe 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 13effcb70c 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new ad8081822f 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 88d8ea21e2 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new 3ba79eb57e 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new e8e8d79f58 78: onsuccess: #522: 1: Success after binutils: 10 commits new 0dcadcb8a9 79: onsuccess: #523: 1: Success after gcc: 25 commits new d54f7d4f81 80: onsuccess: #524: 1: Success after linux: 9 commits new cd8fc9ecf8 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new 67a34d0ab9 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 83de79b8de 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 9882372b79 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 56f72a01fd 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new 8b2ffaa70b 86: onsuccess: #532: 1: Success after gcc: 16 commits new c7210f58da 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 630fff03ca 88: onsuccess: #534: 1: Success after linux: 12 commits new fbef9b4263 89: onsuccess: #536: 1: Success after binutils: 27 commits new f21466b97a 90: onsuccess: #538: 1: Success after glibc: 10 commits new a392ffb17f 91: onsuccess: #539: 1: Success after linux: 27 commits new 1efeb6d255 92: onsuccess: #543: 1: Success after glibc: 4 commits new f557d8f6f8 93: onsuccess: #544: 1: Success after linux: 34 commits new b373be3b4f 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new b6d6045495 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 98f8de94c4 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new c352f2a457 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new bf78130d64 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new bcffc9af70 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new 5c049570cc 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 84c52bdef5 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 7027436040 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new c629a2855c 103: onsuccess: #555: 1: Success after binutils: 4 commits new 941a64d8ca 104: onsuccess: #558: 1: Success after binutils: 3 commits new dbd100d2b4 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new dd57c05e44 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new 12562b824e 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new a6616ffdc2 108: onsuccess: #563: 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 (1bb0c2171f) \ 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 1688 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52188 -> 52460 bytes 04-build_abe-gcc/console.log.xz | Bin 232448 -> 233036 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8552 -> 8688 bytes 07-build_abe-glibc/console.log.xz | Bin 234444 -> 235980 bytes 08-build_abe-gdb/console.log.xz | Bin 50404 -> 50360 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2560 -> 2464 bytes 11-check_regression/console.log.xz | Bin 7968 -> 6568 bytes 11-check_regression/mail-body.txt | 27 - 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 394 +-- 12-update_baseline/console.log | 62 +- 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 | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 2911952 -> 2861624 bytes sumfiles/g++.sum | 140 +- sumfiles/gcc.log.xz | Bin 2508664 -> 2561944 bytes sumfiles/gcc.sum | 4450 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 940024 -> 949884 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 228176 -> 229120 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 462452 -> 466984 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2473 insertions(+), 2792 deletions(-)