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 f1e8eb2bbeb 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 17e466cf831 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5043aff139b 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 9343c13300c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards b63be65c00e 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards e42dc0671a7 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 3d6b16ac598 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 4c1f8eeb5e8 129: onsuccess: #588: 1: Success after linux: 4 commits discards aadbad3c787 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 1a05c2c2c70 127: onsuccess: #584: 1: Success after linux: 21 commits discards ce5ca8aa6f1 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 6807e30df8e 125: onsuccess: #581: 1: Success after binutils: 4 commits discards ae4ed21d0e0 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards ae1e90a9c6b 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 77e689394c3 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards 34c567b6162 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards e197ee199ec 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 5a4364f88e4 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards 3edc84ae39f 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards bb6a56ad2e7 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards f5bac4fcc9f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 66ea9a83a4c 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 55daafc63d3 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 10245a761b6 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards 3b4cb3fd9f1 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards 977e7483d57 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards 4afc7970b80 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards d94956412e2 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards 31ed51e9b41 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards f2543b9d254 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards e89a5fd6445 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards f42cdcecceb 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 46d469c2782 104: onsuccess: #558: 1: Success after binutils: 3 commits discards 96de748769c 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 66dc133f1e1 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 76322173fcc 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 9d910f4d323 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 620df5a3c48 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards f88513c2ff4 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards a9ca1610e6f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 2c186f61fbe 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards b6eb4614b31 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards d29cd032180 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards b578c4418af 93: onsuccess: #544: 1: Success after linux: 34 commits discards 6addebe276d 92: onsuccess: #543: 1: Success after glibc: 4 commits discards 40326205ef7 91: onsuccess: #539: 1: Success after linux: 27 commits discards d644cec02bf 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 65cd957dae5 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 3df1b848d50 88: onsuccess: #534: 1: Success after linux: 12 commits discards 81fd305947a 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards 6f88925e970 86: onsuccess: #532: 1: Success after gcc: 16 commits discards c92cc9b769f 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards e164498984b 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards 625b4bd738d 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards 61cc00a11f2 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards 7bd58c61904 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards 6798e681ab9 80: onsuccess: #524: 1: Success after linux: 9 commits discards 0f1faa8c3e2 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 7a3a39c7d55 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 395519dcac0 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards f29e675b403 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards d4b4c90de9b 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards 79bdacff2ff 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards 8bedfcd2a62 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards cf8a44a0b33 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards 94b42f3b5db 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 5aeb954d4f2 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 2ad913b5ad0 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards 13eee120e96 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards f5d544b6f30 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards b873e4d5321 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards e27152f5534 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards 496adfbd776 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards b331deafb30 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards 74921bcb776 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards cc73da9de56 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards adc3d4f1c5d 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards 5e63cc7bdab 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards 4e5f3ce50fe 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 17e93771f18 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards 984f4f7e2f9 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards b396bd31c79 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards bb39b1bc196 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards 70141552cb9 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards 51bf70ee118 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 21c7de6c143 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 484ee878ddc 50: onsuccess: #490: 1: Success after binutils: 6 commits discards e9cae280cd7 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 86ac5037508 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards 6a29654a2c4 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards 6835e7828d6 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 6e80208b214 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards 04e2bfb9496 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards 2300541e874 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards dcb53448b7d 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 6083d7ca771 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards fe281c0631e 40: onsuccess: #476: 1: Success after linux: 69 commits discards 42ec12af690 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 5b3b46ab269 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] discards e18ee3f41b4 37: onsuccess: #470: 1: Success after binutils: 3 commits discards fe7dfa777bc 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new dde6c8d34bd 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new 5f36defd53f 37: onsuccess: #470: 1: Success after binutils: 3 commits new c10808b8d4d 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] new 4ea3dd1a760 39: onsuccess: #474: 1: Success after binutils: 8 commits new cfe0c439739 40: onsuccess: #476: 1: Success after linux: 69 commits new ab0cffb4d06 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 6b72629aa9e 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new bda72e84ae2 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new b450850a5c1 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 9cfc3666ee6 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new dd7bd5b5c9d 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new 1025d1a6e84 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new ddbdd7a9489 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new 75a4ef3303f 49: onsuccess: #487: 1: Success after binutils: 11 commits new 20aca375b4b 50: onsuccess: #490: 1: Success after binutils: 6 commits new 75bd3e99eeb 51: onsuccess: #493: 1: Success after binutils: 13 commits new 9dbab6ca808 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 852dae7d3c3 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new d9388bdb6a3 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 8af04f8fb54 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new bd1a58e31e1 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new 0b1dd576a17 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 5762ba9d095 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new 6b54d0fdcd0 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new ef2809ffb31 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new 6595488f123 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new e7e903a1edd 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new 4c6ad321769 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new e7be1a07b9f 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new d7fa370b693 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new 8fad2b05b52 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new ea53770ea61 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new 57f3e87cfc5 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new 8db01c1786a 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new b132d9ebce7 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new ac9f324f20f 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new c74462b6d86 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new dbe7df42a71 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new 5e459326d94 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new 2e1aab5e266 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new 643fbf005a0 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new cab0b308aa4 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new 3802dfc2303 78: onsuccess: #522: 1: Success after binutils: 10 commits new 889584ca9e1 79: onsuccess: #523: 1: Success after gcc: 25 commits new f95f651abfb 80: onsuccess: #524: 1: Success after linux: 9 commits new 81cbae8739c 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new 29742fb1598 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new db34d42eb4a 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new f8cd8d6149a 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new 81308e038e7 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new 2bbe3ede6e0 86: onsuccess: #532: 1: Success after gcc: 16 commits new 23e97094b41 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new d7c6347be8b 88: onsuccess: #534: 1: Success after linux: 12 commits new bb9e4a53170 89: onsuccess: #536: 1: Success after binutils: 27 commits new a38f259fab3 90: onsuccess: #538: 1: Success after glibc: 10 commits new 8649c3e39f1 91: onsuccess: #539: 1: Success after linux: 27 commits new 61a2e32befe 92: onsuccess: #543: 1: Success after glibc: 4 commits new f44a3b8eb8b 93: onsuccess: #544: 1: Success after linux: 34 commits new a2e3ef43015 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new d2ffdb6e08f 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new e99d3e9e028 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new aec5b68f30f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new b995d2ef23c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new c5d6edff551 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new 34b0128ff23 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 7b3d3d2bb71 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 0dbc3dda937 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 0d2a1e9c044 103: onsuccess: #555: 1: Success after binutils: 4 commits new 796cdb1e8c2 104: onsuccess: #558: 1: Success after binutils: 3 commits new 6308e734b88 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 207ae839c79 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 39d2136ed93 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new f75f1e8636d 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 77e22345e47 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 31b55ba6647 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new cda9eed4738 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 5b3014d44a2 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new b8705ba8d0c 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 3ada0a75321 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new f5339b35e7b 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new d92376046a1 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new b3ceaf1ba13 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new 13847efd302 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 62e08d6b90e 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new af4c2e3bd56 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 5c4ec0c9ba2 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 9712818552a 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 46ff7f50203 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 5f72fb2d851 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new e228f81dd11 125: onsuccess: #581: 1: Success after binutils: 4 commits new c0a939a20ab 126: onsuccess: #582: 1: Success after gcc: 9 commits new 26225574a38 127: onsuccess: #584: 1: Success after linux: 21 commits new d5a0dd65deb 128: onsuccess: #586: 1: Success after binutils: 22 commits new 6d926f51277 129: onsuccess: #588: 1: Success after linux: 4 commits new 1055325b77f 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 86c506e81f4 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 95f5508aaeb 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 126a61da57c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 1b4875b13f1 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 741257a37f8 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 7a14622097b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new ccabb32a623 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...]
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 (f1e8eb2bbeb) \ 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 1740 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52840 -> 53536 bytes 04-build_abe-gcc/console.log.xz | Bin 235448 -> 235936 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9304 -> 10716 bytes 07-build_abe-glibc/console.log.xz | Bin 235660 -> 235612 bytes 08-build_abe-gdb/console.log.xz | Bin 51116 -> 52940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3872 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2564 -> 3276 bytes 11-check_regression/console.log.xz | Bin 6600 -> 6672 bytes 11-check_regression/mail-body.txt | 81 - 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 80 +- 12-update_baseline/console.log | 40 +- 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 | 83 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- sumfiles/g++.log.xz | Bin 2905352 -> 2938520 bytes sumfiles/g++.sum | 121 +- sumfiles/gcc.log.xz | Bin 2580676 -> 2565376 bytes sumfiles/gcc.sum | 3967 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 954308 -> 954272 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229280 -> 230816 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2676 -> 2672 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 469736 -> 476880 bytes sumfiles/libstdc++.sum | 10 +- 39 files changed, 2215 insertions(+), 2311 deletions(-)