Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/gcc-compare-results] branch master updated (c1e99bd -> 26ddded)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/gcc-compare-results. from c1e99bd From https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--mas [...] new 26ddded From https://ci.linaro.org/job/tcwg_gnu_native_check_gdb--mas [...] The 1 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: .../tcwg_gnu_native_check_gdb-master-aarch64.xfail | 336 +++++++++++++++++++++ 1 file changed, 336 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[linux] branch master updated (17214b70a159 -> 2faac9a98f01)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from 17214b70a159 Merge tag 'fsverity-for-linus' of git://git.kernel.org/pub [...] new 47f9e4c92402 keys: Do not cache key in task struct if key is requested [...] new 4fc5c74dde69 verify_pefile: relax wrapper length check new 3584c1dbfffd asymmetric_keys: log on fatal failures in PE/pkcs7 new 2faac9a98f01 Merge tag 'keys-fixes-20230321' of git://git.kernel.org/pu [...] The 4 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: crypto/asymmetric_keys/pkcs7_verify.c | 10 +++++----- crypto/asymmetric_keys/verify_pefile.c | 32 ++++++++++++++++++-------------- security/keys/request_key.c | 9 ++++++--- 3 files changed, 29 insertions(+), 22 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (956d69621a0 -> 541625244f5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 956d69621a0 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards baf057d9859 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards 53a632e5695 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards 1a117324ad6 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards 45056444f5f 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards 52bda51f3de 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards 175b37ab740 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards 9478aedcd16 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards f5e731a92f3 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards f20835e3646 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards 8b66fbcd8c2 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards fdefcce4088 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 6261c9b519d 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards d18dc141e1e 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards e1cb1d922e0 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 6930dae8dc5 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 5f2fba73269 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards cb777db0f9b 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards f4ee3f15ae6 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 25c101335a7 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 1b6ce7b01eb 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards 3b0de48c09e 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 4cd99ade56b 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards af58c439608 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards 13a292e36da 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards a4debc9feef 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards 06af6aa80ef 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 3435633626a 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 2c664141d0d 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards de535f48b63 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards b75bf352aba 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards cb227c1949f 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 5b9ce088bf9 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 88e37e310cc 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 56d8ba24b2f 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 0973bbcb202 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 63b3560c865 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 44ae1a57d44 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards e641dd1c271 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 02d6b5be4c0 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards f34aacc1226 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards 354074e5245 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 35bad2e7e68 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 09873fe7172 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards e9a42264602 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 41f8e29e303 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards f6f5f8858f6 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards a7e635496e4 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 5f105aec332 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 61cca9c441c 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards eb7e97ee026 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards a70a9151278 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 9e4a507d3bc 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 324e5d6c583 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards 25690441418 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards 4f6f28945be 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 901bebb47ea 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 0170853bcc5 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards 6da4c10cb67 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 739eac4b2c5 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 2daed6b2e6e 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards d228c9d94a9 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards 1eca7fb4573 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 7fba19b1414 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards a49104b91ff 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards b6a4e83f089 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards d8e2b363846 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 7ecf2ecd4dd 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 9f722ff2be9 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards 94e97d438e0 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 956d99bbbd2 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards ec499f2a724 139: force: #557: 2: Success after gcc: 6 commits discards f42b6f82a34 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 55c9dda974e 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards f0baf5f87dd 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards bcbc0505747 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards 503d58987b1 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards 619a332cd66 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards a8a6e8e4c3c 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards 46f33ad5563 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 202b652df5d 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 1bfccee47d6 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 9d6d311ae45 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 253d622f802 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 9f41b481652 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards b1e6ace9ade 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 5ea0031705f 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards 173e5ca833d 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards 3298f7b97e9 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 9fb23dbd434 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 93bd79dcc0d 120: onsuccess: #535: 1: Success after binutils: 10 commits discards f974f4eb6d8 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards 4cbe597760a 118: force: #533: 2: Success after binutils: 4 commits discards e6802fc89a5 117: onsuccess: #531: 2: Success after gcc: 65 commits discards f8257f67a1c 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 42fd4d94115 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards fe01282d600 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 213947e0cee 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 9376039f18e 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 5ee20a0ab97 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 679b2e1057e 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 2543c38035c 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 028f75d4fbd 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 4aee934c5f0 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 93e59e99ab8 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 7ae3ba87151 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 8b29633f1bf 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 422753eaeb1 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 5d309364085 117: onsuccess: #531: 2: Success after gcc: 65 commits new da5012c6ee8 118: force: #533: 2: Success after binutils: 4 commits new 9a4396eb79e 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new bfd45d0dc4c 120: onsuccess: #535: 1: Success after binutils: 10 commits new 5b01153178a 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new be13a7307e5 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new 6711b2b52ec 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 1ab48fc5dfe 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new d0a23baf291 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 300ec77b1e5 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new ea64cc81c14 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new 79a68f3fc21 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 37259d36e17 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 63d10918031 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new cdc5bfefa8e 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new e1662f7f641 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new 2b1ff0c1082 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new feb1a52aab2 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new fff72b5d7ed 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new 3094652b9ae 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 10aa1472693 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new fa823c32ba2 138: onsuccess: #554: 2: Success after binutils: 10 commits new 5012317767e 139: force: #557: 2: Success after gcc: 6 commits new ce49033aeb7 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new 0a1f9a21f59 141: onsuccess: #559: 1: Success after gcc: 4 commits new 606fd9ffa53 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 186a55fbf02 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new c3abe10ea7e 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new 176883354bb 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new 54ee2723edd 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new e5c250c8aee 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new aabcecb5833 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new c61940f4743 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 976a660cf44 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new bc65b102a3a 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new b8030595a5a 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 89bfcbd2714 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 7ff3867f3bc 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new d71b3412e6d 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new d5662b957b6 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new cfce5694cc4 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 3cd4ae30e26 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new c517a83a09b 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 04ebf9f72fe 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 31953fa47d5 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 7065264918d 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 14c5be674ed 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 1bcbd476e4b 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 6283cdd4467 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 0aa316a31a7 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new 5d2e52d5c00 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 7707ce61416 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 87b8ae61643 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new dc39443e87e 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new bad41c3f123 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new b3e31b4dd2a 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 137f8b19b22 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 3114378b258 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new 4cd9f896dc1 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 778adebc1c4 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new fb405414d5c 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new eb5d266c19e 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new 02697a51e0c 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 3a79a835153 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new a41f173376d 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new cc29ad8796d 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new ddca2667ff5 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new f78df2f678e 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new b02f5489923 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new e803c4df208 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new ba5c92b0671 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new d1bbba4c230 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new c33fea659f4 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new c5885b1c401 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new 0b76f87fb96 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 50964a1ed2d 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new 1415ef654be 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new d6b237f3ac2 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 83346dad0dc 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new a5ca1ce4a41 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new deb31ed3e65 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 0fa6a723415 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new 90f8ce35de9 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new cff792e1b72 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 86774e34583 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new c6601d911ff 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new f3133228a53 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new c4a859d664b 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new 64cac7d7009 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new a7ed2759bef 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new 0dcd686dd2c 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new 68dd59daefc 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new 2f4781f99a1 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new 0bcf9f4d91b 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new 541625244f5 211: onsuccess: #27: 2: Success after binutils/gcc: 41 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 (956d69621a0) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1744 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2484 bytes 04-build_abe-binutils/console.log.xz | Bin 35588 -> 35204 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 304804 -> 304092 bytes 06-check_regression/console.log.xz | Bin 3124 -> 3096 bytes 07-update_baseline/console.log | 68 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++--- 13 files changed, 50 insertions(+), 50 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (8ff3ca2d947 -> dd282b16bfd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 8ff3ca2d947 libstdc++: Fix simd compilation with Clang new dd282b16bfd Fortran: reject MODULE PROCEDURE outside generic module int [...] The 1 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: gcc/fortran/decl.cc | 7 ++++--- gcc/testsuite/gfortran.dg/pr99036.f90 | 9 +++++++++ 2 files changed, 13 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/pr99036.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (6bfdc0fa035 -> 281d28dfead)

by git＠git.linaro.org

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 6bfdc0fa035 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 37341ebb089 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 3df1342bb95 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards d9921b748dc 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards b3417168928 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 2c4d32f0080 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 0e45b3ec4d7 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards d4dfaa6f873 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 0ea633aa73f 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 29af1ed45de 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 530163b3557 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cd654ffcc8a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 02cbb00be59 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e7f19a32158 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards d49e3342f5d 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 333703f8c0b 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 73e02da8ccd 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 78e7da62be0 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9304ef8f1b9 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards f2d2a436ca0 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards ec5b7fff7c3 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 6b5ae5e5412 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards c302ab32510 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards 1d9c3de02d3 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 89b5dbdecbf 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 8b297dd5117 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards ca9c8189fec 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 73d0ea0ef6e 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards b2170a04721 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards cd6d797450f 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a2bcb97ecee 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0974bb26de4 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 312b07fd08b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 9ed4cf95022 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards bac422cd19b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 772aaa80fe9 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards e7f6a085727 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 6449efa4f6b 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards c2b1f8ae782 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards aca9ba66c8d 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards e9df2dc89c8 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 7e2baf3272c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards e55a0927d46 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 2bca50d9496 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards ca2b96c9323 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 9923b1397a6 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards bdfe519447e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards a1f5bc746e4 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 150712fc26d 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 0dcd16e9ff4 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards ba6a32beb9f 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards b1d838d9285 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 6ce21a733a1 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards d92bb0119d7 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 5645230710a 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards a9cf07f7190 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 11112fb7ad3 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards aa04b13ab33 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 58f7ace8a16 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards dc05141445d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 6d0c9c8cf9e 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 14864bf0caa 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 109a930ea8f 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 27c30c09506 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 570868b731e 162: onsuccess: #624: 1: Success after linux: 10 commits discards 10cc91598e3 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 8821ad61315 160: onsuccess: #621: 1: Success after gcc: 11 commits discards a4f40a1667c 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 1bd9a1ab611 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 9b749aac43f 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 1839f7cff67 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 1967d49f34f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 45b983dca67 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c2f7bdd3bb0 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards fadd77aa849 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 66af74e9256 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 0e802dbf4b3 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 75c4d8ea1e3 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards bcfcd4e2ab1 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 769f7b45797 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 69be4272fb3 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 5d1782d1dc9 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards d87610cd8ee 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 56ff285420d 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 16f96990919 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 0558a587bc4 141: onsuccess: #601: 1: Success after linux: 794 commits discards 0e10215f7b1 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 2c3ddbc72ce 139: onsuccess: #599: 1: Success after binutils: 10 commits discards dd6f0e61661 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards b3fe0d5c638 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards eb47395f83b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards a71233079c6 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards f707e708a92 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 581ba80f179 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 06c880d159a 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 75e9aa1ba1d 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 48b702b676e 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 2d5199f8cba 129: onsuccess: #588: 1: Success after linux: 4 commits discards a1483b686e0 128: onsuccess: #586: 1: Success after binutils: 22 commits discards f66eda167a7 127: onsuccess: #584: 1: Success after linux: 21 commits discards 275815e18a5 126: onsuccess: #582: 1: Success after gcc: 9 commits new e60629f3629 126: onsuccess: #582: 1: Success after gcc: 9 commits new f620e2bd3f2 127: onsuccess: #584: 1: Success after linux: 21 commits new f4b8ead6617 128: onsuccess: #586: 1: Success after binutils: 22 commits new 7b5923cd3f3 129: onsuccess: #588: 1: Success after linux: 4 commits new d89143d8603 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 208bb6ec2a2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 3d4692e0dc7 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 9e1ffb3e1cb 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 1e7eada4def 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e5bc7131a42 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 118f61f8a01 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 0ad05732b38 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new a0488bd0394 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 11aa4c3808a 139: onsuccess: #599: 1: Success after binutils: 10 commits new 8c91d2784b9 140: onsuccess: #600: 1: Success after gcc: 23 commits new 18899583b69 141: onsuccess: #601: 1: Success after linux: 794 commits new 0a0d4d6b36f 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 8f9706f39c7 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 2bdbb55a333 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 76102eb9e36 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new b8065bdf0a6 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 8b0d90f9c91 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3451700a883 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new f83b23e32d1 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 5b40fab9898 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 19bf265f75b 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new dc3f284013d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new f37103dc474 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 8caa5a4009a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 51eb0e81d24 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 66dcb6224f3 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 191512e205e 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 698b9cb8413 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new dfee1d341e4 159: onsuccess: #620: 1: Success after binutils: 12 commits new e2329eb68fe 160: onsuccess: #621: 1: Success after gcc: 11 commits new d8d6261b1dd 161: onsuccess: #623: 1: Success after glibc: 9 commits new 88dcf6bff94 162: onsuccess: #624: 1: Success after linux: 10 commits new 115ccda244a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 19f91029165 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 35ae7b3c6f8 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 68094f837f3 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new ee5ad6b4f67 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 344f5bff566 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 594da3f18e7 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 6cfe6d7f64c 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new df27d2bc6f8 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new c2cf4551ed3 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b041489db42 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new cb777bf8df8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 6cdc3bbbf2f 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 42d35303cfe 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new e38ad16475a 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 0346ee56d52 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new f1494577cca 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 6294557d98d 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new e53f19a8983 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4732786c400 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 8fc6dc5b9fd 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 66b7bf01629 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 3f5337e953c 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 22fcaa34916 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new ce4cb1d6828 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 91fd72cc52e 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ebeb64f31e0 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 05dde24efdd 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 0bde67e4d47 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new d3c3684820b 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new b482ef50b5a 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 9379b574b33 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 6b002a5f2f7 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new a5b339e248d 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 447e4b0c6fe 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 7ab84b6be81 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 21ba5a3399c 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 1704db54c07 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 8dd515691bc 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 208b85c1ff8 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 2a3c931f753 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 73722c18f63 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 6668e05a208 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new e168cc5e31d 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new a3903094b20 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 11f83068384 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 3c7ce95831e 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7c265a61256 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 4a643caa416 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 82224aa9c8c 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5f3949107fc 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 862bf3d55b4 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new affcc0d8c02 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 226931e58cf 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new a6d6e432762 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f89f3a7869a 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 6a4494f16eb 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 33b0cf1bfca 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new a0fab6fa77a 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 7c60e5b21f8 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b921ef0bdef 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 4ea3d22989f 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new fa0c36480c0 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new 02fd1382745 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 281d28dfead 227: onsuccess: #27: 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 (6bfdc0fa035) \ 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 1744 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49060 -> 49216 bytes 04-build_abe-gcc/console.log.xz | Bin 235536 -> 236148 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8204 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 233148 -> 232532 bytes 08-build_abe-gdb/console.log.xz | Bin 46484 -> 46688 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3784 bytes 10-build_abe-check_gcc/console.log.xz | Bin 10732 -> 10936 bytes 11-check_regression/console.log.xz | Bin 5332 -> 5604 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 119 +- 12-update_baseline/console.log | 64 +- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 48292 -> 101148 bytes sumfiles/g++.log.xz | Bin 2881268 -> 2879124 bytes sumfiles/g++.sum | 34 +- sumfiles/g++.sum.sep | 6689 +++++++++++++++---------------- sumfiles/gcc.log.sep.xz | Bin 51504 -> 70056 bytes sumfiles/gcc.log.xz | Bin 2516772 -> 2509840 bytes sumfiles/gcc.sum | 25 +- sumfiles/gcc.sum.sep | 6985 ++++++++++++++++++++------------- sumfiles/gfortran.log.sep.xz | Bin 44964 -> 46512 bytes sumfiles/gfortran.log.xz | Bin 962060 -> 954884 bytes sumfiles/gfortran.sum | 5 +- sumfiles/gfortran.sum.sep | 1435 ++++--- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233792 -> 233812 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 8724 -> 6416 bytes sumfiles/libstdc++.log.xz | Bin 479208 -> 480148 bytes sumfiles/libstdc++.sum.sep | 270 +- 44 files changed, 8696 insertions(+), 7002 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (34494c5fa8a -> 4a374ba3c59)

by git＠git.linaro.org

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 34494c5fa8a 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards fe4d5d1895e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards d300be0db50 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 6e326722585 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 0d9796f729c 121: force: #26: : Failure after baseline build: no new commits discards 6cd41f3952f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 02e026cd146 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 6094fe690c1 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 6eb9ebe43c7 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards e2061584b4d 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 0cfe597a063 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f68a2a34118 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7a0d42dc333 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 73b8054a80e 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards d4deee82a9a 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards df64d77a2ff 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 11bce5d9dd1 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 6df8fec9eb4 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards a86aefef933 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 47eeec2bffa 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 776df77124b 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 722280f5fdb 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 794e56e2715 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 2bb32ee8257 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards fe94755b578 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 32c13cce78b 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 682021da1f5 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 0d0b9fa71aa 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 53dbbe611cd 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards 5254995cf05 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 7081690fa36 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 380090185b8 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 8392e81ba1e 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards e9d1970891a 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards 4dc0f6f70c5 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards e8f260c1a32 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 80864afbea4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 19b66e0fc55 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 572f2024cfb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 24d6337cae1 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 9dfbdccd742 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 0afd054d0da 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards 4f649ce4973 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 1b523957a63 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards f2f17adee33 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 38db57e806a 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards a220f5f2fc0 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards e3153bbd5d8 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards df2b342ff43 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 7eae2aafe29 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 358756681f8 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 9f7cf038f81 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards c798b72675d 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards a0d87eb571a 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 2b1887ee253 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards b9209f88c6c 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 64cc541bb74 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 8e38a1f6560 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards c146e01bf17 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 2bdec59c5b6 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 8da6d937eb2 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 586fdfcb1f3 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards efafbd6a496 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards dac11aca767 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards f1e1f9bdcac 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 3773e28e8da 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards bb7209f0aca 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 15ad6e72f3d 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 6152d4c6b12 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 42aa0f2c797 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards b02111b77a9 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 92e2845cb93 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 7d4be739d81 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards dbe38d06628 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards a5bed1c97ab 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards f1fb0b0fd5c 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards e79fdc70858 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards c79aa02d9ff 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 7cf1f391efe 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards b39c9ea173e 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards a9d87b2e03c 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 52b01b495a4 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 8b83598bfd1 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 9983c45bfa5 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards d2483e7bb5c 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 6243e246b37 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 2d8d463e35a 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 98e72abc1cc 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 0be4158026a 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 9ba267abde0 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 8db3e57d454 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 339eba2e2af 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 18b62f9d2cc 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 050eaa378e2 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards f5bb029f9a1 31: onsuccess: #38: 1: Success after linux: 14 commits discards bb49f941ab6 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 05585bf4868 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 18cc7943f84 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards b147cb1c45b 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards d923da24945 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards 284d39a0f26 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new be01061a8b9 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new dfbfd2bc09b 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new ff1fdc961bb 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new f0b5ba5f155 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new c5f7a147c55 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 2e70113ce38 30: onsuccess: #36: 1: Success after binutils: 18 commits new 85c7fbf8b01 31: onsuccess: #38: 1: Success after linux: 14 commits new 9b1b1ccfdc7 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 7d411e0d92b 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 0d94bb59577 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new a5fd0776c24 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new f1b0efeef2d 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 8909ccb23a1 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 8e151fc684c 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new e8f89c7e4a9 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 376b8376091 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new d40c359869f 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new e6ed15f3183 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new bda4812f4ed 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 83ea3976bd7 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 513483c35f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new b78409c09dd 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 2aa883eceba 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 193b596ce39 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 702c090e7b2 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new e7bc4e03c7b 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new c17ed7c38b3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new fe99a0c8088 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new b6caa2fb3ac 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new fa42c2ffd48 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new a13248c22fd 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 52f152528d3 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 5b65b52afaf 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 9ca0d04b3cb 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 3c2b0f1461c 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new aea0fb3081c 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 6d722f1fcb1 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new fdcd8a88382 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 325630e5bc2 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 526daaa5304 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 772399ee81c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 8f8936bff8e 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new cfcce76c26c 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 51b245e1ad0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new b70c2610d5b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new f1ff92b60ed 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 0ba7ff1477f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 8a6bc21de03 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 5e7676bc950 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 8a5d54b61f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 95219e8f0e3 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 8e38416075b 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 7de90d3ee18 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new fe0ba61e3b3 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 84bced38dba 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new b2ae59eb7b4 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 6bdd989ff53 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new c6a9185ef27 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 69096adc431 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 0cd2e5a9d15 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5c095f5e99e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new befe4a06a45 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new afe0e01e0e3 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 6405a579831 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 499e679d042 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new 098433c78d5 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new cfb20c6745e 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new 3b038ad3567 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new b375cc723d6 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 218076dbd97 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 306d1286de3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 5e0d7aac85c 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new dc42a7daca9 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new a4c2b93ac30 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new f545fc72c59 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 400bdb7c8ba 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 8b4ffc73464 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 33006f21542 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new 9613a3be5ce 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8826822e8e1 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new f4185230599 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 90bc1e2b682 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 431d8bbe77f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 0abb993e7d5 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new c2681bff147 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 015f2554d5d 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new f05afdd0e98 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 5a130adec6a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e5ea0f11563 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 7e9588c6197 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 64128a95bc5 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 049594f70f7 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 7a1a0ca1702 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 9c74ea06f8c 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0115578abca 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new f7199dd487b 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 64954ec0b8d 121: force: #26: : Failure after baseline build: no new commits new ccd3da37df5 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 783ca66f54f 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 4f8959d77e0 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 945188c87ae 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 4a374ba3c59 126: onsuccess: #32: 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 (34494c5fa8a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 1732 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 48944 -> 49020 bytes 04-build_abe-gcc/console.log.xz | Bin 235852 -> 236288 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8192 -> 8404 bytes 07-build_abe-glibc/console.log.xz | Bin 233480 -> 232820 bytes 08-build_abe-gdb/console.log.xz | Bin 47476 -> 47588 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2836 -> 2916 bytes 11-check_regression/console.log.xz | Bin 4900 -> 4772 bytes 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 31 +++------------- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- 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 | 4 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++--------- sumfiles/gdb.log.xz | Bin 14468 -> 14476 bytes sumfiles/gdb.sum | 4 +- 26 files changed, 71 insertions(+), 90 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (bd6f4f9d091 -> 39075c5637f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards bd6f4f9d091 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 12c6d6e12db 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards 35944920629 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards 8c5428e8759 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards 5019a816d1c 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards faaf0c61e34 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards 850e17f96d1 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards 19c857c8c2a 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards 1a2c909a5ae 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards 1e62da8e65f 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards a934925b6bf 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards 52d31712b63 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards 03bb70f44d2 178: onsuccess: #16: 0: Success after binutils: 15 commits discards 80ca665e698 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards 96ce7296e8b 176: force: #14: 2: Success after binutils: 18 commits discards 6a51dac0662 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards 3e8c23ae3d8 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards 592cc6b0aaf 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards c9f79de8336 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards c06d6186657 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards fa3185703cd 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards 9ec439ebd0e 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 06c362482a5 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 279158d0c9f 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards c811059f871 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards 242402332b9 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards f9fda4ee616 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards d5d7a3e0680 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards fbcfe3eda84 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards ba60d12a12a 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards f8e33b34bb9 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards ec5bca22d82 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards e1b2f73ab91 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards 1b914952f2e 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards 461bfbf635b 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards 98d3e3771b1 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards 42d59816485 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards bc4c8baea19 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 0e3c71cc522 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards 8fe129c7b01 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards 3361c4eb606 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards 775b749c5b8 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards 8982b8df853 148: onsuccess: #571: 2: Success after gcc: 4 commits discards bfbf5e30791 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards 05f3e07ef32 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards 62ae5fcc05c 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards aaa17920066 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards 2bae121e994 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards de6e9842210 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards 30abcf8bf8d 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards bc11d9b7c66 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards c6f944f2a3e 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards 21498bfd950 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards 189c64692ea 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 58e6fc25916 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards b5d0400a113 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards ea77a824b4b 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards 7b2b9407e19 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards e1176cb9c45 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards dc9ab4d1065 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards f72adaabbae 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards 38af1c494da 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards 2a3857eca2f 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards 43a45a4504a 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards a645b81e94a 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards 123dbf41b6e 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 5d4939a93de 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards 6ab65681e44 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards 37eb93fdaa9 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards 8253d10bab9 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards 594f3752f45 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards c2003b59bc4 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards 8c7d2b6ccef 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards b4a7713230e 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards 84efcb37b95 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits discards ed11d72307c 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 23ebdabdd62 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits discards c5ece468d3d 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits discards 267813e46ba 112: onsuccess: #527: 1: Success after binutils: 10 commits discards d6b274d484e 111: force: #526: 1: Failure after binutils: 5 commits discards 0e8489282ca 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits discards 7c74d1a4c89 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits discards 8116871b521 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits discards f5a2aed1ab6 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits discards 00ce3796457 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits discards b7b0ccd3aff 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits discards 113cb9c4b59 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards bae6e6e20d5 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits discards a49ab4c3e5a 102: onsuccess: #511: 2: Success after binutils/gcc: 25 commits discards 4ee6c65c736 101: onsuccess: #510: 2: Success after binutils/gcc: 117 commits discards 8bb2138164e 100: onsuccess: #509: 1: Success after binutils/gcc: 7 commits discards c9716a118be 99: onsuccess: #508: 1: Success after binutils/gcc: 7 commits discards 59bc0937441 98: onsuccess: #507: 1: Success after binutils/gcc: 94 commits discards 70e2bd197fe 97: onsuccess: #506: 1: Success after gcc: 27 commits discards e5bfc995150 96: force: #505: 1: Success after basepoints/gcc-13-4227-g0 [...] discards 17f1a5b5354 95: force: #504: 1: Failure after gcc: 4 commits discards 2e231e88e22 94: onsuccess: #501: 2: Success after binutils: 15 commits discards 252f1e153d7 93: onsuccess: #499: 2: Success after binutils/gcc: 54 commits discards c179eb602c2 92: onsuccess: #498: 2: Success after binutils/gcc: 368 commits discards 9616e2df345 91: onsuccess: #492: 2: Success after binutils: 4 commits discards 310326d70ac 90: onsuccess: #490: 2: Success after binutils/gcc: 105 commits new 7a73010cfb9 90: onsuccess: #490: 2: Success after binutils/gcc: 105 commits new 1a60c3e88d9 91: onsuccess: #492: 2: Success after binutils: 4 commits new db56c93db39 92: onsuccess: #498: 2: Success after binutils/gcc: 368 commits new 3297e7f76e0 93: onsuccess: #499: 2: Success after binutils/gcc: 54 commits new d040c4d008b 94: onsuccess: #501: 2: Success after binutils: 15 commits new 8561fcf257d 95: force: #504: 1: Failure after gcc: 4 commits new ef9ea4e2053 96: force: #505: 1: Success after basepoints/gcc-13-4227-g0 [...] new 83df9d9e9a8 97: onsuccess: #506: 1: Success after gcc: 27 commits new b5a692d78a7 98: onsuccess: #507: 1: Success after binutils/gcc: 94 commits new 71d0c3a6a9c 99: onsuccess: #508: 1: Success after binutils/gcc: 7 commits new 1fc7299e494 100: onsuccess: #509: 1: Success after binutils/gcc: 7 commits new de53b303a37 101: onsuccess: #510: 2: Success after binutils/gcc: 117 commits new cbfd292c42b 102: onsuccess: #511: 2: Success after binutils/gcc: 25 commits new 4441306ab62 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits new b391abdae5f 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new 1c2b7345f9e 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits new 44e681a8be6 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits new 5d1156fafb9 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits new 4998102f4f3 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits new 1cf61f24d7a 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits new a4162e57524 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits new 9a76f198928 111: force: #526: 1: Failure after binutils: 5 commits new d73301fd63a 112: onsuccess: #527: 1: Success after binutils: 10 commits new e4022614cc9 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits new 8b1433089a5 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits new 7bf4fbb4834 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new d866ba02487 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new c1884876f73 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new e917a94cb8e 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new 105c26e5b59 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new e480304d2ac 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new 06136cf0a52 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new e926cfd422f 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new 4d2cb009391 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new 6a94291989c 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new 2136a5e2083 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new c8eb76baf58 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new 7b8139c9a96 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new 2ba5706d261 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new 38b66a87d0e 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new e63a6222d7d 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new 56af2fd8279 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 9dcb5676c8e 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new 478e18ebfb6 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 19543c0d4db 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new a1b19ccd52d 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new ffdd845b590 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new 3debc11a25f 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new d268e5a8944 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new b90bd1c5167 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new 9348fb36242 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new a0f98fe392f 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new 55d6e855bb5 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new d8156f1235c 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new c47e146c405 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new f30557afaa7 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new ead1ae54f11 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new e327208010c 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new 1f00ac5eb2a 148: onsuccess: #571: 2: Success after gcc: 4 commits new 60a02a883f7 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new 570dcb7cd84 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new 89250444a9a 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new 7db4b2a04ac 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new c4a53e386c9 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new a70c33fc871 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new b44dc047379 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new 0a140686c0c 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new 21230119888 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new cce5307654d 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new 7531eca2150 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new 6a7da8137da 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new a06ab73b742 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new e9f4ab5c8af 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new d317ada814e 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new c9002954c2c 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new 3e036e06bbb 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new 193fcad07ee 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new 6e141b03e23 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 5fe9dce819b 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new a0c9cec35a5 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new 015abf8d090 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new 57bc6f13334 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new 70800a333b2 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 1c82985e493 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new 52ed902ef90 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new 2aef17dc058 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 1dfb1663418 176: force: #14: 2: Success after binutils: 18 commits new 95af7a8703c 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new 2adac435b66 178: onsuccess: #16: 0: Success after binutils: 15 commits new 33fd27425b8 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new 1d8022cbce5 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new 93369d7157c 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 32ddbf344ec 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new d092e2ccdc0 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new 62009749b1a 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new 13a15dc1dee 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new 4161782ef92 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new cbd605fe633 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new b96ecb82505 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new 10c4184c5b0 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new 44178ab9035 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new 39075c5637f 191: onsuccess: #30: 2: Success after binutils/gcc: 42 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 (bd6f4f9d091) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] 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 1748 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2484 bytes 04-build_abe-binutils/console.log.xz | Bin 49340 -> 49080 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 612304 -> 606348 bytes 06-check_regression/console.log.xz | Bin 3152 -> 3080 bytes 07-update_baseline/console.log | 38 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++------ 13 files changed, 35 insertions(+), 35 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[newlib] branch main updated (592419133 -> fe2545e9f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch main in repository newlib. from 592419133 Cygwin: regex: fix faulty check for valid range expression new 0a962aa2c Cygwin: fs_info::update: fix NTFS filesystem flags new fe2545e9f Cygwin: don't use unlink/rename POSIX semantics on certain NTFS The 2 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: winsup/cygwin/mount.cc | 12 +++++------- winsup/cygwin/syscalls.cc | 14 +++++++++----- 2 files changed, 14 insertions(+), 12 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (041a164ec9b -> 8ff3ca2d947)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 041a164ec9b c++: DMI in template with virtual base [PR106890] new 8ff3ca2d947 libstdc++: Fix simd compilation with Clang The 1 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: .../include/experimental/bits/simd_detail.h | 2 +- libstdc++-v3/include/experimental/bits/simd_x86.h | 58 ++++++++++++++++++++-- 2 files changed, 55 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (4a9e2ef5cbf -> 30296a8f6f7)

by git＠git.linaro.org

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 4a9e2ef5cbf 223: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] discards 14d3cd5142a 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] discards 90eb24c96fc 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] discards e0ac853de60 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gd [...] discards 0f60eb35888 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gl [...] discards 8fbcb5d0d48 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] discards 75dbb90fe26 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gl [...] discards e309ea06335 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] discards 1a984e4eca0 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] discards 24e2d81a648 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] discards a4c44a24e45 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] discards 0a3b6e75485 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] discards afdded6c0bc 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] discards fe734760780 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] discards ab119b5bdb7 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] discards 0a353621b39 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] discards 34c4837f62c 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] discards 3d2cf1398e4 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] discards ed3ced701cc 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] discards 5f09bd415b0 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] discards 8838e5a56d0 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] discards 7b677f06be6 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] discards d41b4e9ec12 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] discards 267ca5a1cc5 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] discards fd513738534 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] discards 2c676a48595 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] discards a3da5d129d6 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] discards 1c19f10258d 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] discards db320885a7a 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] discards 802aa889cf4 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] discards 70b303e858e 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] discards 2c7fc420e9f 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] discards b70f1e450d3 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] discards 7f0c55d7cc4 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] discards 0af7fe503f6 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] discards b976ecfad57 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] discards fda1a844713 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] discards aa071f8847a 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] discards d4c87d78a2b 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] discards dc854677a30 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] discards d29c373aefa 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] discards 83663e2e3ce 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] discards 3159c5fac78 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] discards 6b6fa7b893e 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] discards c1a222a5429 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] discards 16e49533327 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] discards 90af5cc582d 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] discards 64e36616292 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] discards cf56f7ff784 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] discards 915b086d3f9 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] discards 2c89d7b2519 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] discards 38badabda42 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] discards 0f0399069c7 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] discards 6a5098bf20c 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] discards c4656eca830 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] discards c2a39327f07 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] discards d91e1687bb4 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] discards b2f7b37d192 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] discards 54b71411de8 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] discards 0e25e69d6a7 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] discards a1f66fa0c11 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] discards 44af91abc8e 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 5c501f552ab 161: onsuccess: #578: 6: Success after binutils: 15 commits discards c4bb4f6121a 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] discards 6bcef5e4939 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] discards e93e5c8a7ab 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] discards 2558294c899 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits discards e1860b9d288 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] discards f75ba828541 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] discards 7242507f7d9 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] discards 70c92f7ac22 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] discards db71453d442 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] discards 25ed639f90e 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] discards fccff36ef68 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] discards 37f9e854e39 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] discards 47b26376dc8 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] discards 7f0884a8216 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] discards cbbc51adcd8 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] discards 422bda05926 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] discards fb380e9d663 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] discards 71810a218de 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] discards ea48472933a 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] discards 97bd680ba98 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] discards 992395ce667 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] discards 0b9277486fe 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] discards b51b5b93758 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] discards 8744555076f 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] discards 2936a47a076 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] discards 84aaaa048dd 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] discards 568fa810eca 134: onsuccess: #544: 6: Success after binutils: 18 commits discards b1cbfbf4ed8 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] discards b7381ddc561 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] discards b3978648053 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] discards 04216d28981 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] discards 62937c32170 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] discards e9f385f1796 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] discards 8a33c4a4f55 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] discards 5c0e82d9e08 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] discards f8c5421b7eb 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] discards 5255332be6a 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] discards b7efbc0e2d5 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new 35a0a8b380c 123: onsuccess: #532: 6: Success after binutils/gcc/gdb: 64 [...] new 6471d2b91aa 124: onsuccess: #533: 6: Success after binutils/gcc/linux/g [...] new e26866ba29d 125: onsuccess: #534: 6: Success after binutils/gcc/linux/g [...] new 65f38e12eb4 126: onsuccess: #535: 6: Success after binutils/gcc/linux/g [...] new 3f5f6528c50 127: onsuccess: #536: 6: Success after binutils/gcc/linux/g [...] new 89538099872 128: onsuccess: #537: 6: Success after binutils/gcc/linux/g [...] new 143df87a7eb 129: onsuccess: #538: 6: Success after binutils/gcc/linux/g [...] new b679483173a 130: onsuccess: #539: 6: Success after binutils/gcc/linux/g [...] new e268240b918 131: onsuccess: #540: 6: Success after binutils/gcc/linux/g [...] new e36c377ea88 132: onsuccess: #541: 6: Success after binutils/gcc/linux/g [...] new e1d17952476 133: onsuccess: #542: 6: Success after binutils/gcc/linux/g [...] new 59186240981 134: onsuccess: #544: 6: Success after binutils: 18 commits new c0eff306e49 135: onsuccess: #550: 6: Success after binutils/gcc/linux/g [...] new ba67beb31b5 136: onsuccess: #551: 6: Success after binutils/gcc/linux/g [...] new bd9f949c648 137: onsuccess: #553: 6: Success after binutils/gcc/linux/g [...] new 1fff1b5fae5 138: onsuccess: #554: 6: Success after binutils/gcc/linux/g [...] new b762f319720 139: onsuccess: #555: 6: Success after binutils/gcc/linux/g [...] new 3b29de6e11c 140: onsuccess: #556: 6: Success after binutils/gcc/linux/g [...] new 87f4746853a 141: onsuccess: #557: 6: Success after binutils/gcc/linux/g [...] new 2279b471d52 142: onsuccess: #558: 6: Success after binutils/gcc/linux/g [...] new 6234de4fb76 143: onsuccess: #559: 6: Success after binutils/gcc/linux/g [...] new 00417bb0c45 144: onsuccess: #560: 6: Success after binutils/gcc/linux/g [...] new 9caa5a471e7 145: onsuccess: #561: 6: Success after binutils/gcc/linux/g [...] new 5ab84a1f05f 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 14 [...] new 963f83637a6 147: onsuccess: #563: 6: Success after binutils/gcc/linux/g [...] new cdefacd1a77 148: onsuccess: #564: 6: Success after binutils/gcc/linux/g [...] new 9efa632b455 149: onsuccess: #565: 6: Success after binutils/gcc/linux/g [...] new 0e833990f80 150: onsuccess: #566: 6: Success after binutils/gcc/linux/g [...] new 78e828063c2 151: onsuccess: #567: 6: Success after binutils/gcc/linux/g [...] new 5558c3dcc3c 152: onsuccess: #568: 6: Success after binutils/gcc/linux/g [...] new 09a1c09be47 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 47 [...] new 3029a63cb4b 154: onsuccess: #570: 6: Success after binutils/gcc/linux/g [...] new 2435f669810 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 36 [...] new eb9d9e3ef7a 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 18 [...] new 5b2166233be 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 commits new d5568c63c38 158: onsuccess: #574: 6: Success after binutils/gcc/linux/g [...] new 66170bcb33e 159: onsuccess: #575: 6: Success after binutils/gcc/linux/g [...] new deebe82f7d2 160: onsuccess: #576: 6: Success after binutils/gcc/linux/g [...] new c4a24e4e66d 161: onsuccess: #578: 6: Success after binutils: 15 commits new 9d6a90c4fc3 162: onsuccess: #579: 6: Success after gcc: 11 commits new e683d7ce89e 163: onsuccess: #586: 6: Success after binutils/gcc/linux/g [...] new af399a279ed 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/g [...] new b4bd0c8e1ab 165: onsuccess: #588: 6: Success after binutils/gcc/linux/g [...] new c29886da53a 166: onsuccess: #589: 6: Success after binutils/gcc/linux/g [...] new 701e320f4d2 167: onsuccess: #590: 6: Success after binutils/gcc/linux/g [...] new 33ca3578eee 168: onsuccess: #591: 6: Success after binutils/gcc/linux/g [...] new 74a57cc9c03 169: onsuccess: #593: 6: Success after binutils/gcc/linux/g [...] new fbd1d3df624 170: onsuccess: #594: 6: Success after binutils/gcc/linux/g [...] new 387273f69d4 171: onsuccess: #595: 6: Success after binutils/gcc/linux/g [...] new b3d4f569eb8 172: onsuccess: #596: 6: Success after binutils/gcc/linux/g [...] new badc6d359d5 173: onsuccess: #597: 6: Success after binutils/gcc/linux/g [...] new 4b29d97221d 174: onsuccess: #598: 6: Success after binutils/gcc/linux/g [...] new c626b022276 175: onsuccess: #599: 6: Success after binutils/gcc/linux/g [...] new 6d5b5a64d17 176: onsuccess: #600: 6: Success after binutils/gcc/linux/g [...] new 9b85ceaeb9c 177: onsuccess: #601: 6: Success after binutils/gcc/linux/g [...] new bd9bf86d76e 178: onsuccess: #602: 6: Success after binutils/gcc/linux/g [...] new 3dc48790b7d 179: onsuccess: #603: 6: Success after binutils/gcc/linux/g [...] new 3e21deca460 180: onsuccess: #604: 6: Success after binutils/gcc/linux/g [...] new c17680ddb7b 181: onsuccess: #605: 6: Success after binutils/gcc/linux/g [...] new d5527876cd9 182: onsuccess: #606: 6: Success after binutils/gcc/linux/g [...] new 8407d95f334 183: onsuccess: #607: 6: Success after binutils/gcc/linux/g [...] new 4a29900f8c7 184: onsuccess: #608: 6: Success after binutils/gcc/linux/g [...] new 06a03912f81 185: onsuccess: #609: 6: Success after binutils/gcc/linux/g [...] new 2294ae38390 186: onsuccess: #610: 6: Success after binutils/gcc/linux/g [...] new d7a782984dd 187: onsuccess: #611: 6: Success after binutils/gcc/linux/g [...] new ef8ea0ac520 188: onsuccess: #612: 6: Success after binutils/gcc/linux/g [...] new a3f848aed59 189: onsuccess: #613: 6: Success after binutils/gcc/linux/g [...] new 85db2bb74bb 190: onsuccess: #614: 6: Success after binutils/gcc/linux/g [...] new 3610190d20c 191: onsuccess: #615: 6: Success after binutils/gcc/linux/g [...] new e8cd949205b 192: onsuccess: #617: 6: Success after binutils/gcc/linux/g [...] new d0844a864d1 193: onsuccess: #618: 6: Success after binutils/gcc/linux/g [...] new af6941ca05a 194: onsuccess: #619: 6: Success after binutils/gcc/linux/g [...] new 3a243c6dfaa 195: onsuccess: #620: 6: Success after binutils/gcc/linux/g [...] new c761629a013 196: onsuccess: #621: 6: Success after binutils/gcc/linux/g [...] new c971159118d 197: onsuccess: #628: 6: Success after binutils/gcc/linux/g [...] new 9e6a0f28277 198: onsuccess: #629: 6: Success after binutils/gcc/linux/g [...] new 9b4e344996c 199: onsuccess: #630: 6: Success after binutils/gcc/linux/g [...] new 875fdb51f9a 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gli [...] new b0ebe5d2d1a 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gli [...] new d7723070099 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gdb [...] new c904d142d6e 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gli [...] new 3f8a4f65732 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gli [...] new 1dfcf98c8fd 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gli [...] new 97118d133cc 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gdb [...] new d36d6038416 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gli [...] new 533e4abe36f 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gli [...] new 3b55f3d6d17 209: onsuccess: #10: 6: Success after binutils/gcc/linux/gd [...] new 4007ad7ee40 210: onsuccess: #11: 6: Success after binutils/gcc/linux/gd [...] new 5da1cb68899 211: onsuccess: #12: 6: Success after binutils/gcc/linux/gl [...] new 7873f443c37 212: onsuccess: #17: 6: Success after binutils/gcc/linux/gl [...] new a0ce9425aaa 213: onsuccess: #18: 6: Success after binutils/gcc/linux/gl [...] new 4cf4aad0382 214: onsuccess: #19: 6: Success after binutils/gcc/linux/gd [...] new 56644940613 215: onsuccess: #20: 6: Success after binutils/gcc/linux/gl [...] new aa5a515a439 216: onsuccess: #21: 6: Success after binutils/gcc/linux/gd [...] new 7c08c1bc321 217: onsuccess: #22: 6: Success after binutils/gcc/linux/gl [...] new 5c3f68996ee 218: onsuccess: #23: 6: Success after binutils/gcc/linux/gd [...] new 00861e14560 219: onsuccess: #24: 6: Success after binutils/gcc/linux/gl [...] new 24f2e718160 220: onsuccess: #25: 6: Success after binutils/gcc/linux/gd [...] new 6f04186d838 221: onsuccess: #26: 6: Success after binutils/gcc/linux/gd [...] new 49dc65503ba 222: onsuccess: #28: 6: Success after binutils/gcc/linux/gd [...] new f886ebe21d6 223: onsuccess: #29: 6: Success after binutils/gcc/linux/gd [...] new 30296a8f6f7 224: onsuccess: #30: 6: 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 (4a9e2ef5cbf) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] 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 1784 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2560 bytes 04-build_abe-binutils/console.log.xz | Bin 49596 -> 49148 bytes 05-build_abe-gcc/console.log.xz | Bin 235016 -> 235500 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8196 -> 8412 bytes 08-build_abe-glibc/console.log.xz | Bin 233632 -> 233296 bytes 09-build_abe-gdb/console.log.xz | Bin 47728 -> 47008 bytes 10-check_regression/console.log.xz | Bin 4120 -> 4220 bytes 11-update_baseline/console.log | 44 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++-------------- 19 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023