Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (224bb0d80e -> e46fb13490)

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 224bb0d80e 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards c1a11486a1 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards a3c026788b 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards e6d0a31bba 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 0a4858b874 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 3bee08e249 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards 56d7069c5d 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards 93e8a0f550 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards a118c76624 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards 05b75fb421 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 50d7b5f2cc 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards 1431b4d327 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 7d090c248e 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 1df51cbbb6 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 7baa476cca 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards 322847f0e4 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards 8fe6b4ad17 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 8b96c2823c 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 328602c755 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards 02c102d34f 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 5b34dea399 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 58779880e3 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards ab0aaa26d2 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards 080744ad63 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 790cdb8ba5 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards 9331b6e951 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards 694e9ab1e9 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards 193572f3a6 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 35078b7030 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 5c2df2ff58 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards ee7c22980c 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 68f2597650 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards f6314905af 139: force: #557: 2: Success after gcc: 6 commits discards 0f9346e73f 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 8e2363e945 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 99a321b06a 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards fed66b535b 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards 1d7547d574 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards ea4c06bf7a 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 39e749c269 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards 3c9974e7b8 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 6ac15a1f26 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 4b3c2aa748 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards bc7bd022f3 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 9a24862115 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 325bf95ac8 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards 9494f44700 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 311c2e5df0 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards edc05b3d22 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards c52a568983 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 314e210422 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards d4ae748eca 120: onsuccess: #535: 1: Success after binutils: 10 commits discards ed590ade7b 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 583b9bc73a 118: force: #533: 2: Success after binutils: 4 commits discards d894a32106 117: onsuccess: #531: 2: Success after gcc: 65 commits discards d2b81a89e4 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 829e0136f1 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 09fb51c1f8 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards e1492254a8 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards 4176aee57a 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 0182c44325 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 672c1a409f 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards bcbced099d 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards e17359559b 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards eeef4a7029 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards ffccd939bc 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards b40e4a1550 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards 7a9ace2292 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards 73d21f5f50 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits discards e945b3f75d 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits discards cb41c92ac6 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 7dba3e8c2b 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits discards 061e4b495b 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits discards a35b9bc4fe 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits discards 494271ca0a 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits discards ed3f7cd00d 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits discards dc277968e3 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits discards 3d3f9a091a 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits discards 1c0159a3de 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits discards 14bf35df61 92: onsuccess: #499: 2: Success after binutils: 4 commits discards 8c763ab97c 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits discards eb78c21482 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits discards 23ad30a5e3 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits discards acd852c6d4 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits discards a71704d82a 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits discards dd39052844 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits discards 6efae17f26 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits discards c00a1780cf 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits discards f026f13c33 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits discards 2dd69c47bc 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits discards f428f083aa 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits discards b7e1911335 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits discards 70d3b23c0b 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits discards 0f665a1661 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits discards e97a395fea 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits discards 8fdbfc0bdf 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits discards abff2ff712 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits discards 3d2c6b688f 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits discards 24df885b0d 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits discards c4b92fca64 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits discards 4a87f09b4a 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits new 4a2d1bb62b 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits new fdafd59db7 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits new 4bc8e62eb1 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits new 1d2009e190 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits new 09732193e8 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits new d3cd862e86 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits new 17bea38c86 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits new df7fcba49a 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits new 64f095e5e4 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits new 407bd85fbe 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits new a53269c73a 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits new 5896a8ad1d 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits new 19858e8107 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits new 8d40da5f36 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits new c8c86414a6 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits new c98b7ed2c8 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits new 85616705cc 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits new 688317dae3 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits new 94c3d5ae77 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits new 31af5b129d 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits new 6f6b8997b5 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits new 2efa92cb05 92: onsuccess: #499: 2: Success after binutils: 4 commits new 4d66363752 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits new 9745a1cc26 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits new add8c8853e 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits new 410b606d59 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits new 32dc3df96a 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits new f7ce8f9469 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits new e4b906cc69 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits new 47f1b853ef 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits new f0156ce5a2 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new 38f56f5895 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 45fd312a4b 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new 210adbbaec 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new 95b3652700 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new 9de52d16c2 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new 0f1bf468bc 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new bf5a94ff74 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new d10e696a37 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new f35eac0f0f 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 99eb3546db 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 3e8fed3f0a 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 5faacc27fd 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new d8afcc9b4f 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 78d2f9ffe8 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new c8adcb5ea7 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 33da534d30 117: onsuccess: #531: 2: Success after gcc: 65 commits new becb705300 118: force: #533: 2: Success after binutils: 4 commits new 2f233b885c 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] new e8db7eeff4 120: onsuccess: #535: 1: Success after binutils: 10 commits new 9237e1af5d 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new 353af59ab5 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new a6f538b417 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 012d12e2d5 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 5eb8a1a7ca 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 1d4d3592fa 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 435cf9d042 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new b245da9530 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 460b7d9cb1 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 1784fb2d11 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new d2ec0c318d 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new fabba2ef33 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new 0ef3f3b5f7 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new 0bf29aedd5 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 28e8b36773 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new 6c91802449 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 7558b27a26 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new f6f981a9b3 138: onsuccess: #554: 2: Success after binutils: 10 commits new fe88b7372c 139: force: #557: 2: Success after gcc: 6 commits new bcc43d89f2 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g3 [...] new 2e7c2d1d99 141: onsuccess: #559: 1: Success after gcc: 4 commits new 8fce05fd4b 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 06181ce766 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new 437d619d3a 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new cbaf6dfbb6 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new e03ad6800c 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 2913bb468d 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 899e0a015e 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new b097adaded 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 166f4d6e4f 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 6b6b966a09 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new de7530f04b 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new ffc513f73e 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 2cbe0b464d 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new 6788015cdd 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 18e821539d 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new a66ae8bbe2 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new a5be220051 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 9dcc944189 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new e60c057d34 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new fcda540bb0 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 55eeb93108 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new a721d6ed83 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new cf06c9a207 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new f2cde4cd67 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 47c5144c4b 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new 685a358793 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 8221a2a0b9 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new bfeee8bd9d 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new f06fc6abbd 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 0d05e6bb37 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new e46fb13490 172: onsuccess: #592: 2: Success after binutils/gcc: 57 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 (224bb0d80e) \ 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 1752 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 39080 -> 38840 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 528812 -> 525792 bytes 06-check_regression/console.log.xz | Bin 3088 -> 3116 bytes 07-update_baseline/console.log | 64 ++++++++++----------- 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, 48 insertions(+), 48 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (17218a2547 -> d1da188a80)

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_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 17218a2547 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] discards 5f29bed60f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits discards 702d00ada5 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] discards 8c5f744d4d 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] discards e5c6783050 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] discards b58a98fe71 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] discards baae8f7796 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] discards 1e7e6aadd4 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] discards 51a6460513 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards ecf97162fb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] discards 4800a7a51c 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] discards 0f32eabacb 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 200ce4967d 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] discards b244bce66b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards fdf1701ba3 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] discards 66e10da92d 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] discards 0a5f81bb71 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] discards 5512160d9d 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 74110b56e3 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits discards a9cec742a7 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] discards bae288b59c 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] discards 3c9e69fac3 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] discards fe1c350fdf 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] discards ee536b4881 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] discards bf14c7dec4 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] discards 76d2722e40 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] discards 9ca162168b 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] discards 31919ce359 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] discards 2f907ca3fc 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] discards 7536b1a001 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] discards 3604f444fc 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] discards a1eef42ebf 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] discards b433a80d76 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] discards 68199eaaff 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] discards 6d8b808e6e 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] discards ba7d110a54 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] discards d10c6180f2 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] discards 5fafc2e891 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] discards 6453ff180b 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] discards 699351e97b 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] discards ef039a9724 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] discards ec60685ff7 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] discards ba3ac232b0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] discards 12e402e362 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] discards fa0f28a658 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits discards 3add4cc5d0 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] discards 30cb288828 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] discards 052950b40f 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits discards e9727e2345 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] discards 0380ba805e 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] discards 6559c8151c 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] discards ef8951b2bf 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits discards 69c1db87e6 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits discards a7877d56a4 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] discards 7d8800fa46 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] discards 872d9c3328 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] discards bb543638f1 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits discards 5ed96dfda4 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] discards ec5bac885d 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] discards 0489aeafd9 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] discards 16b0da4fa8 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits discards d43bd67e7a 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] discards 07d7784c26 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] discards 05c2e8edfe 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards e3f330478e 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards daa2c5d96f 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards 6db030e5ae 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 037c8cb083 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards c9b11eb56d 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 7441ebef4f 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards f4aae1d48d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards bcfa17dc4c 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards beb534e163 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 3f32bf8eca 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards e1bda16b66 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c3b60e8067 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards 6b60c9c66f 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards 84ba18c0f7 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards d7aca6ea3c 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards ee088b87c6 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards 08a01c5e53 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 9898f5f1fb 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 9ea4d83aa5 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 9d92855324 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 0a2a2544ce 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards d42c502850 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 2b33044219 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 6aa3f0bc3e 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards 0d0a8ae14b 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 51029b4b11 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards b91bc1f0ad 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards ac2320e2f3 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards d8884ee6e5 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 313e571864 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards 35f0559d16 301: onsuccess: #2118: 1: Success after linux: 16 commits discards 61f66db3bc 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards 6c82e5eb8c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards 958f20b886 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards f5ed7cf000 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards 401797e9b7 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards ced15b4786 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 4573c3c0ed 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new ebd53026c1 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new 5f6ede2ff8 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new 8c9f6baa43 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 0fbfa5a634 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new de38d86801 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new 66c152703f 301: onsuccess: #2118: 1: Success after linux: 16 commits new b608db89fd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 3485756c0d 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new 18d92c923e 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new e800728c36 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new eea3093a23 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new 55b165bb90 307: onsuccess: #2124: 1: Success after gcc: 2 commits new bbc71d1571 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new c4cf95d7d7 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new c8769e3b61 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 422375620e 311: onsuccess: #2130: 1: Success after gcc: 4 commits new 94e9aef106 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 9ec3c2a2a7 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new f377976a29 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 902f69c40f 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new 547341ec11 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 611f6d69bb 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new 01dcdc4d2c 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new aab99f3084 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new f69834a310 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new b805ff64b5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new 2966cdfba9 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 7a33b26c63 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new cf32b3739a 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 541340611d 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new c4e4c534f5 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 8ab1059922 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 11629f7a12 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new da5855f53c 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 356f240792 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 853469ec78 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 0743dc022e 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new da40f8bf37 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] new a7e773ebeb 334: onsuccess: #2154: 1: Success after binutils/gcc/linux/g [...] new 39eb23c4fb 335: onsuccess: #2155: 1: Success after binutils/gdb: 146 commits new 5260c4fa2a 336: onsuccess: #2156: 1: Success after binutils/gcc/linux/g [...] new cca2670b69 337: onsuccess: #2157: 1: Success after binutils/gcc/glibc/g [...] new 1fa46a8323 338: onsuccess: #2158: 1: Success after binutils/gcc/linux/g [...] new ac43432cb2 339: onsuccess: #2159: 1: Success after binutils/gcc/gdb: 4 commits new 026834b9b0 340: onsuccess: #2160: 1: Success after binutils/gcc/gdb: 15 [...] new 83dae4a708 341: onsuccess: #2161: 1: Success after binutils/gcc/gdb: 11 [...] new b4fc00d608 342: onsuccess: #2162: 1: Success after binutils/gcc/linux/g [...] new 61644a76a0 343: onsuccess: #2163: 1: Success after binutils/gcc/gdb: 7 commits new 3b132be110 344: onsuccess: #2164: 1: Success after gcc/linux/glibc: 37 commits new d4e1e9ea74 345: onsuccess: #2165: 1: Success after binutils/gcc/glibc/g [...] new ebbcab6fb6 346: onsuccess: #2166: 1: Success after binutils/gcc/linux/g [...] new 990f479d67 347: onsuccess: #2167: 1: Success after basepoints/gcc-13-51 [...] new 30c22fc2a6 348: onsuccess: #2168: 1: Success after binutils/gcc/gdb: 9 commits new 968c6a6abc 349: onsuccess: #2169: 1: Success after binutils/gcc/linux/g [...] new 7ba5b904bf 350: onsuccess: #2170: 1: Success after binutils/gcc/linux/g [...] new 22e5b6d190 351: onsuccess: #2171: 1: Success after gcc/linux: 15 commits new f76a860c35 352: onsuccess: #2172: 1: Success after binutils/gcc/linux/g [...] new 30a59ccef0 353: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 27 [...] new 0d85506880 354: onsuccess: #2174: 1: Success after binutils/gcc/linux/g [...] new cf3cc03dc2 355: onsuccess: #2175: 1: Success after binutils/gcc/linux/g [...] new dd9e8c4862 356: onsuccess: #2176: 1: Success after binutils/gcc/linux/g [...] new 79bd89044e 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/g [...] new c396244e10 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/g [...] new ae458b159a 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/g [...] new 74af86ce04 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/g [...] new 9f7bd9ff57 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/g [...] new ae0fba5b9b 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/g [...] new 191b5901d3 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/g [...] new 15e97fc96a 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/g [...] new 86fd3ccad3 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/g [...] new 6a4bba0402 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/g [...] new 2bdce65cf2 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 14 [...] new ed5e36fa57 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/g [...] new aa95b2d17e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/g [...] new 55f8f09597 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/g [...] new 1c0fb77a52 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 10 [...] new 7c7102eda1 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/g [...] new 81c7a2203a 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/g [...] new df354603ee 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/g [...] new 623153d069 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qem [...] new ee8ee2251f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/g [...] new a489745c37 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 commits new 65e223b683 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new 695a2bf3a5 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/g [...] new 75c3ad7c79 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/g [...] new 089b423d23 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17-g [...] new d80e1f05e5 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 1a8e5cf26a 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/g [...] new 562574e476 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 3ab854d060 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/g [...] new f44d7d71b2 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/g [...] new 9d8f106de1 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 986555f5d9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/g [...] new 52ea0cb736 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/g [...] new 1e663a9042 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/g [...] new e3b9fdbaa4 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qem [...] new 5480015ec1 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/g [...] new 16af9fbb8c 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 12 [...] new 0405b777eb 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 commits new 48db3fff04 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/g [...] new d1da188a80 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (17218a2547) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 1792 -> 1816 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31244 -> 31040 bytes 04-build_abe-stage1/console.log.xz | Bin 91500 -> 91984 bytes 06-build_abe-linux/console.log.xz | Bin 9336 -> 8612 bytes 07-build_abe-glibc/console.log.xz | Bin 235996 -> 236352 bytes 08-build_abe-stage2/console.log.xz | Bin 228236 -> 229732 bytes 09-build_abe-gdb/console.log.xz | Bin 38748 -> 38488 bytes 10-build_abe-qemu/console.log.xz | Bin 30800 -> 30832 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3268 -> 2984 bytes 13-check_regression/console.log.xz | Bin 9284 -> 7400 bytes 13-check_regression/fails.sum | 2 +- 13-check_regression/mail-body.txt | 61 +- 13-check_regression/results.compare | 35 +- 13-check_regression/results.compare2 | 557 ++------ 13-check_regression/results.regressions | 35 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 35 +- sumfiles/g++.log.xz | Bin 2637436 -> 2650780 bytes sumfiles/g++.sum | 39 +- sumfiles/gcc.log.xz | Bin 2205296 -> 2186412 bytes sumfiles/gcc.sum | 2102 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 888848 -> 886596 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2252 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 216860 -> 217064 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 438968 -> 434616 bytes sumfiles/libstdc++.sum | 27 +- 43 files changed, 1457 insertions(+), 1639 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (4a30f201a4 -> 361b2f40e7)

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_cross_build/master-arm in repository toolchain/ci/base-artifacts. discards 4a30f201a4 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards 2115db70ca 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards ec2271db3a 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards 2415f008c8 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards 53e52d0b14 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards dc0af048d6 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards 87bcb12114 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards 8e071838ff 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards defc55c38a 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards b76da9a742 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards 3f62f0e9e1 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards fc35434dc0 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards ffa2875c0f 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards 226e911477 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards e6f2d72fc8 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 0bbc6f9803 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards d28cf2d7cf 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards 0a03350e9f 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards 913f730ed9 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards b29970f401 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards 00fedf856b 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards e5a2a50d65 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards b03031e096 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards 79be547f81 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards 31c8d01454 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 7e5102ecc0 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards abb39334b6 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards 2ff3e18d4b 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards aeeeff8dde 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards ef97f6fceb 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards bb7f77b4e1 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 92d3ff5ba8 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards 8f366d4056 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards c13e80f379 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards 3b47bd6ffa 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 1570b3561e 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards 386716ea95 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 9b185ee164 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards 513c333294 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards fb72a98947 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards 24572f775d 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards fe1ce6d36e 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards df6beff103 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 90ee518813 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards a7b6f797b0 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards fd23b196c8 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards b4747f7e32 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 143cb4e274 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 4d3dd9a675 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards f4dd73c876 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 98bfeead1f 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 06c6b616e0 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards e727368a51 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 6334b0e310 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards d76a8b1a2e 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards f8d458bc18 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards f1974800c0 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards 26f95ba23f 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 2d84faaa08 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 932b51dcec 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 279a66f0dc 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards 654edd3643 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards f9be70042e 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits discards 89083d606b 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards c495a2ba2f 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 83346b5043 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 0324c500d7 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards 3d992f8dc0 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards 1bb533bf36 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards de5ccd9872 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 618a567e13 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards a51aef17d2 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards b57875a86c 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards e0f2bde056 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 3e8ecd7ed0 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards 169764cfa6 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 64afd699e4 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards 4d1f9119fa 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 98eb2a68d3 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 4105150988 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards ddb9468b91 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards d0a79baf82 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards 0895f511f0 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 741b593ffe 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 0140c2f4df 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 341752c0a2 321: force: #2055: 7: Success after gdb: 2 commits discards 75dfd15da9 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards c02d3f8216 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards dda57cff9a 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards a7517a0578 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards 30b775ff9d 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 408b9df929 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 812c1bb316 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 8dd02fcbaa 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 2d7d305091 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards c5d7863ec5 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 8928c6abbf 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards b7303a11c4 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 2ad1d4515c 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards bd65ba81b6 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 63cb999b0e 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 36a187472a 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new 316cabbbe4 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new 0e3ed79ac1 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new b949ab50ac 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new 5eb4416aac 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 73ec19bf6f 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new d4ab5b99d1 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new ebf33b506b 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new 0dc1522b66 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 36bb2f55d7 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new f80fe06f41 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 3a59273c90 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new a003c977b3 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new a844d80323 319: onsuccess: #2049: 7: Success after binutils: 4 commits new dd1ae2b97a 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 128db75c5b 321: force: #2055: 7: Success after gdb: 2 commits new c440d0eafe 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new 23d06c266a 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new aab46e5de7 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new c461e5c7a0 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new 1316299096 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new aa5c56c795 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 613b618caa 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 47bb1498b7 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 82ee728f57 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new c54e0d6947 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 623015f749 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new b5c85230ce 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 517d1f3d9b 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new e80952e7be 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new a1234abe95 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new e5adb52988 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new cb7203cb8a 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 74a6fdcd55 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new e738afc735 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new 9644adc54b 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new 2547712ea3 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new d53a3fae13 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new 15fd3b902f 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new f42f47fd13 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new d1e380a2af 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new 8600e7593d 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 3053548474 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new 39a1365832 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new f6fd46b397 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new e6b2794128 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new f4419c99d4 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new b4a45a170b 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new f0fba28415 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 086b145b2a 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new c989b5ef05 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 4e7bb99c0b 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new dd77297895 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 16d34a4b8d 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new b9895005a7 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new f02f2e6a60 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new 8c6187aeed 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 8081702698 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 253b68c283 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new 7a141854da 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 4f43103ed3 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new 0a29b9dfdc 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 23cedf0705 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new be8e7141a2 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new dff3644ba0 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 332d1f708a 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new 575e1a46cd 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new 7231f520e6 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 6c2f56fcbd 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new 29674cf7ea 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new 09f0d7fef1 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new eb1a532f92 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new 997a97ae7f 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 0dba8cc0aa 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 7e507d4a7d 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 9f375380b8 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new d3c115402f 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 2ead99416e 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 288436e28f 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new 899f71797b 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new d18f139776 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new fb2d62d6a2 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 1fbdb27b95 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new 5932c47d1a 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 25e3b4e1ab 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new e18094dcc0 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 0953258100 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new 0922679cc9 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new 6997c35aab 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new 3e695c5ed5 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new 11455e56d3 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 2d62ed42bb 397: onsuccess: #2132: 7: Success after gcc: 2 commits new be985ff634 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new ed6b52ba6b 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new 617f046972 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new 1cfb8a0df2 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 1703f73cd0 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new 42e4d2c5fb 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new 82bbc53475 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 2fa4ccaf23 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new c0dde4d326 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new 361b2f40e7 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (4a30f201a4) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 30908 -> 31020 bytes 05-build_abe-stage1/console.log.xz | Bin 91432 -> 91860 bytes 07-build_abe-linux/console.log.xz | Bin 8556 -> 9356 bytes 08-build_abe-glibc/console.log.xz | Bin 235896 -> 236412 bytes 09-build_abe-stage2/console.log.xz | Bin 228984 -> 227904 bytes 10-build_abe-gdb/console.log.xz | Bin 38180 -> 38360 bytes 11-build_abe-qemu/console.log.xz | Bin 30628 -> 30808 bytes 12-check_regression/console.log.xz | Bin 3688 -> 4036 bytes 13-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 | 38 ++++++++++----------- 20 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (aa1807419ba -> fe8cdc8ec14)

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 binutils-gdb. from aa1807419ba x86: drop use of VEX3SOURCES new fe8cdc8ec14 Local label checks in integer_constant 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: gas/expr.c | 9 --------- 1 file changed, 9 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (7027a373b24 -> aa1807419ba)

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 binutils-gdb. from 7027a373b24 objcopy of mach-o indirect symbols new 7fc69528652 x86: improve special casing of certain insns new aa4c197de16 x86: simplify a few expressions new ddb62495930 x86: move (and rename) opcodespace attribute new ba3ffa6de05 x86: limit use of XOP2SOURCES new 5dab1799d70 x86: drop use of XOP2SOURCES new aa1807419ba x86: drop use of VEX3SOURCES The 6 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: gas/config/tc-i386.c | 289 +- opcodes/i386-gen.c | 73 +- opcodes/i386-opc.h | 57 +- opcodes/i386-opc.tbl | 72 +- opcodes/i386-tbl.h | 19114 ++++++++++++++++++++----------------------------- 5 files changed, 7857 insertions(+), 11748 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (25ff9ed56f -> 1aeb459c20)

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_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts. discards 25ff9ed56f 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards ddaa5580b9 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 106ed7a7e9 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards aab18c2dac 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards 888a680366 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards bf11c0b373 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards ed42f670fd 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 0271e35d33 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards eed8c11668 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards 896704b707 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards d391c5625a 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 03c1b19061 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 35068e6a9b 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 07aca6b51d 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards ba824afad8 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards 1dfcf0a57f 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards cd9b073e14 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards d35abfc9dc 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 0953d6dd92 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 5fc5955b5c 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards 2a8924dc4d 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 3c6daf5470 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards b2b01d5b90 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 4a5cabade0 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 5d43e4ed41 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards b46775028e 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 5de80437c9 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 5b47f4c07b 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 701e0d9979 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 1e68d3f26a 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards 343cb55415 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards f2994f88fb 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 46860ee444 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards c9e70e5ba7 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards f498993fdf 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 21df7c7232 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards ae7ba100df 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards 40ac43028b 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 706aacac83 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards 2edddc63f6 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards e59a3f5bce 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 536fb1137f 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards eece37a992 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 7a211f527e 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards e9cf24657e 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards a4c4157cbd 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 6c894b07d4 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards 2c9332ae60 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards ac1c49d20c 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 1ad3f006fe 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 39a17b888b 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 76b12573e9 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards c04c183bbb 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 29a1c20dd5 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 47754f0094 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards e2b77edb1d 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 1378991d21 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards e59eaf451d 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards c76fa73f4d 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 3d7df3c8be 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 578853a6fd 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 640f253c25 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards 16ebbe34e3 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards d366696ddb 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards f819048936 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards bdd4d4d020 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards fc2193c203 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 1c0603e5a8 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards a83eb85607 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 38b50f7bae 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 43ac4d56dc 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 1800e1d45f 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 8d7c2155fe 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards af626b2130 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 5433253338 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 803c22f15c 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 809d505aec 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards c138c2b93f 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 110a38a278 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards cfc3bad94b 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 763bdb621c 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 7b6d436c1b 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards a60932e652 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 9c3c8987b0 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 2ceb4241e8 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 7fa22955d0 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards c0014ef1fb 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards dc03e83ddc 305: force: #2006: 7: Success after gdb: 2 commits discards f2ac35f7d2 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards fe022dd046 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 92f30f7e32 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards adecacde23 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 4f8b68c8b9 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 66bea93458 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 9b467876e7 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 655209a7f2 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 9ee45ebf0d 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 43a0304a97 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 4dee3d192a 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 37c84921ac 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards b4c1d94f62 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new a2dc64d5fc 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new a9860609b0 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new 4aa763b26c 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 07e605776c 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new f72bc62bd7 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 440326868e 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new fed2364cc1 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new ebbe52e8e4 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new b277f5f092 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 6ba807676d 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 28668dc616 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new f055afcbd6 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 2edb253452 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 1cf233d505 305: force: #2006: 7: Success after gdb: 2 commits new 9355ed1f91 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 5fa094573f 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new eec96e4e83 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 6d399bd569 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new e273085b90 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 8758421b4a 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 8b7fc78fcc 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 0696267b12 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 80a504d410 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 1011f7808b 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 9f22244cf9 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 64f177ed60 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 7dce946ceb 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new e2da0b05a3 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 576febf411 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 71bed9f20a 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new ea4b8f17e2 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new a79fe45566 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 0dd8604fdf 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new f3e458023d 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 3a84000209 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 1599f99523 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 2e1bbfc8a0 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 81e5be77d6 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new e40478b5f3 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new a38eb86ca4 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 2ca5b5ed6e 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new bacc0a63ed 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 082b771b04 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new b13b903103 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new 44887c182d 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new b64fd1dd20 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 589df65580 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 46b2459546 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 440eed7cd1 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 8e0856f7a2 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new a76787f1fa 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 651a2f1c43 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 65b9a23aba 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 34239a325d 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 7b2054c732 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 6b5a9bed0d 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 425641cf7c 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new d091ad7841 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 1edc96ea73 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new 3d9ad68599 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new ed378fcd47 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new cd8606e015 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 5f9253eff8 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 843e7dfcd0 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 8ee7b975e6 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 5529fc9d0e 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 72a909b73b 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new fa36ddaa65 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new ab28dfcf18 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new f4a45cf274 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new c32ddb406f 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 800f594f24 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new ffbac6fb66 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 84cd097d7a 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new c3017658f9 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 1f48751c3f 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 06d48e39f3 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new 7a4fde49e4 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new dc1f2678dc 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 311eb4880d 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new 8e9b3881c7 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new a65a021969 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new a045a4972c 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new bb99a47357 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 2856dc8866 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 36a216435c 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 70e9e9a791 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new c323c550a1 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new 9e61e9eb28 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new bc1e381d69 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new e9e2c3b1c8 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new d62e8e977d 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 85c18d208d 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 47711cd134 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new b0c71e2bae 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 5bf3188d30 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 741640a442 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 876e2aa180 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new cec0449dbc 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new aa6819b106 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new c151d4aa48 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new 1aeb459c20 393: onsuccess: #2096: 7: Success after gcc/linux: 45 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 (25ff9ed56f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 1720 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 31240 -> 31256 bytes 05-build_abe-stage1/console.log.xz | Bin 72816 -> 73312 bytes 07-build_abe-linux/console.log.xz | Bin 8580 -> 9396 bytes 08-build_abe-glibc/console.log.xz | Bin 244632 -> 244408 bytes 09-build_abe-stage2/console.log.xz | Bin 204324 -> 204720 bytes 10-build_abe-gdb/console.log.xz | Bin 38396 -> 38368 bytes 11-build_abe-qemu/console.log.xz | Bin 31144 -> 31044 bytes 12-check_regression/console.log.xz | Bin 4340 -> 3720 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 ++++++++-------- 18 files changed, 54 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-defconfig deleted (was bb8b291fe3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-defconfig in repository toolchain/ci/base-artifacts. was bb8b291fe3 38: onsuccess: #290: boot: Success after binutils/linux/qemu [...] This change permanently discards the following revisions: discards bb8b291fe3 38: onsuccess: #290: boot: Success after binutils/linux/qemu [...] discards 91a95fda87 37: onsuccess: #289: boot: Success after binutils/llvm/linux [...] discards bd2fea9e5b 36: onsuccess: #288: boot: Success after llvm/linux/qemu: 45 [...] discards fb243b3519 35: onsuccess: #287: boot: Success after binutils/linux/qemu [...] discards ba07f1941b 34: onsuccess: #286: boot: Success after binutils/linux: 107 [...] discards f2df862461 33: onsuccess: #285: boot: Success after binutils/linux/qemu [...] discards f449381a31 32: onsuccess: #284: boot: Success after binutils/linux/qemu [...] discards 85fbf98e85 31: onsuccess: #283: boot: Success after binutils/linux/qemu [...] discards d5e4ab46f6 30: onsuccess: #282: boot: Success after binutils: 4 commits discards 084d402d8a 29: onsuccess: #281: boot: Success after binutils/linux/qemu [...] discards 5938eafbb2 28: onsuccess: #280: boot: Success after binutils/qemu: 25 commits discards 9e4df39543 27: onsuccess: #279: boot: Success after binutils/llvm/linux [...] discards 5d09d2d851 26: onsuccess: #278: boot: Success after binutils/llvm/qemu: [...] discards 0aab8fce61 25: onsuccess: #277: boot: Success after binutils/qemu: 12 commits discards 63ce605c84 24: onsuccess: #276: boot: Success after binutils/llvm/linux [...] discards e37bd82dea 23: onsuccess: #275: boot: Success after binutils/llvm/linux [...] discards 48270dbc47 22: onsuccess: #274: boot: Success after binutils/qemu: 172 commits discards 771fb26a70 21: onsuccess: #273: boot: Success after binutils/llvm/qemu: [...] discards b5dd76c954 20: onsuccess: #272: boot: Success after binutils/llvm/linux [...] discards 614d298a02 19: onsuccess: #271: boot: Success after binutils/llvm/linux [...] discards 570e1b8145 18: onsuccess: #270: boot: Success after binutils/llvm/qemu: [...] discards a7bc481040 17: onsuccess: #269: boot: Success after binutils/llvm/linux [...] discards 9fb80d86bb 16: onsuccess: #268: boot: Success after binutils/llvm/linux [...] discards bbdd40cb4d 15: onsuccess: #267: boot: Success after binutils/qemu: 108 commits discards 129b725ab5 14: onsuccess: #266: boot: Success after binutils/llvm/linux [...] discards 6864156ca7 13: onsuccess: #265: boot: Success after binutils/llvm/linux [...] discards 671c1e2d58 12: onsuccess: #264: boot: Success after binutils/llvm/linux [...] discards 23325d788e 11: onsuccess: #263: boot: Success after binutils/llvm/linux [...] discards 68c167d68c 10: onsuccess: #262: boot: Success after binutils/llvm/linux [...] discards 751e6c40a1 9: onsuccess: #261: boot: Success after binutils/llvm: 9 commits discards 2e785a4233 8: onsuccess: #260: boot: Success after binutils/llvm/linux/ [...] discards f1bc788cb2 7: onsuccess: #259: boot: Success after binutils/llvm/qemu: [...] discards 56939164e2 6: onsuccess: boot: Success after binutils/llvm/linux/qemu: [...] discards d070429a8a 5: onsuccess: boot: Successful build after binutils/llvm/lin [...] discards bca860478a 4: onsuccess: boot: Successful build after binutils/llvm/lin [...] discards 79ad0eec33 3: onsuccess: boot: Successful build after binutils/llvm/qem [...] discards f99d22c0d8 2: onsuccess: binutils-llvm-linux-qemu: boot discards 5c5e5769b7 1: onsuccess: binutils-llvm-linux-qemu: boot discards 825e86dc39 0: update: binutils-llvm-linux-qemu: boot -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allyesconfig deleted (was f53703221f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. was f53703221f 45: onsuccess: #300: all: Success after binutils/linux/qemu: [...] This change permanently discards the following revisions: discards f53703221f 45: onsuccess: #300: all: Success after binutils/linux/qemu: [...] discards 68d412ab8d 44: onsuccess: #299: all: Success after binutils/llvm/linux/ [...] discards 163fe7a42e 43: onsuccess: #298: 20699: Success after llvm/linux/qemu: 3 [...] discards 86ac166218 42: onsuccess: #297: 20699: Success after binutils/linux/qem [...] discards b5bf8618f2 41: onsuccess: #296: 20699: Success after binutils/linux: 10 [...] discards 8034737fcd 40: onsuccess: #295: 20699: Success after binutils/linux/qem [...] discards 4b2f7556ac 39: onsuccess: #294: 20699: Success after binutils/linux/qem [...] discards bef5bbf819 38: onsuccess: #293: 20699: Success after binutils/linux/qem [...] discards 16867d4ceb 37: onsuccess: #292: 20699: Success after binutils: 4 commits discards f9dc393862 36: onsuccess: #291: 20699: Success after linux: 41713 commits discards 968f1efba7 35: force: #290: 20699: Failure after v6.0.11-93-g327d1f01a2 [...] discards d7cf9b899d 34: force: #289: 20879: Success after linux: 373 commits discards cdf296b491 33: onsuccess: #287: 20869: Success after binutils/qemu: 6 commits discards e94b2af43a 32: onsuccess: #285: 20869: Success after binutils/qemu: 25 commits discards 6281e25107 31: onsuccess: #284: 20869: Success after binutils/llvm/linu [...] discards 3f32628977 30: onsuccess: #283: 20869: Success after binutils/llvm/qemu [...] discards d28b7bf592 29: onsuccess: #282: 20869: Success after binutils/qemu: 12 commits discards 1c3044f352 28: onsuccess: #281: 20869: Success after binutils/llvm/linu [...] discards 4d8adc980b 27: onsuccess: #280: 20869: Success after binutils/llvm/linu [...] discards fce39d2284 26: onsuccess: #279: 20868: Success after binutils/qemu: 172 [...] discards 6ff0016bcc 25: onsuccess: #278: 20868: Success after binutils/llvm/qemu [...] discards 7d5e5affb7 24: onsuccess: #277: 20868: Success after binutils/llvm/linu [...] discards 50091c31ff 23: onsuccess: #276: 20868: Success after binutils/llvm/linu [...] discards cb205a61c4 22: onsuccess: #275: 20661: Success after binutils/llvm/qemu [...] discards 0ae04dce73 21: onsuccess: #274: 20661: Success after binutils/llvm/linu [...] discards 8fc7174ece 20: onsuccess: #273: 20661: Success after binutils/llvm/linu [...] discards 7c41c17a91 19: onsuccess: #272: 20661: Success after binutils/linux/qem [...] discards c13fb8cf3b 18: onsuccess: #271: 20661: Success after binutils/llvm/linu [...] discards 41628cd1a5 17: onsuccess: #270: 20661: Success after binutils/llvm/linu [...] discards 9603b025c3 16: onsuccess: #269: 20661: Success after binutils/llvm/linu [...] discards 5fa3ccee42 15: onsuccess: #268: 20661: Success after binutils/llvm/linu [...] discards 3da70c9bde 14: onsuccess: #267: 20661: Success after binutils/llvm/linu [...] discards 1950c80462 13: onsuccess: #266: 20661: Success after binutils/llvm: 9 commits discards b2a749eeb6 12: onsuccess: #265: 20661: Success after binutils/llvm/linu [...] discards 8bde138ddf 11: onsuccess: 20661: Success after binutils/llvm/linux/qemu [...] discards 79ee2fdc22 10: onsuccess: 20384: Successful build after linux: 35563 commits discards 8eaa9a074c 9: force: 20384: Regression after linux: crypto: blake2s - r [...] discards 5c9b888dba 8: force: 20387: Successful build after linux: 979 commits discards 6ad8a44add 7: onsuccess: 20386: Successful build after binutils/llvm/qe [...] discards ef94746a3b 6: onsuccess: 20386: Successful build after binutils/llvm/qe [...] discards fdeba2257f 5: onsuccess: binutils-llvm-linux-qemu: 20386 discards 01251d07ee 4: update: binutils-llvm-linux-qemu: 20386 discards 82079528f5 3: reset: llvm-9e9bda2e8f5b88715bad767a4b7740df32b040d2: 20386 discards 6b7bca5fca 2: update: qemu-09ed077d7fae5f825e18ff9a2004dcdd1b165edb: 20387 discards 08522810ae 1: reset: linux-fad7cd3310db3099f95dd34312c77740fbc455e5: 19715 discards 1185adf04d 0: update: binutils-llvm-qemu: all -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig deleted (was 28105b470f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. laurent.alfonsi pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. was 28105b470f 35: onsuccess: #261: all: Success after binutils/linux/qemu: [...] This change permanently discards the following revisions: discards 28105b470f 35: onsuccess: #261: all: Success after binutils/linux/qemu: [...] discards 6e5ca346db 34: onsuccess: #260: all: Success after binutils/llvm/linux/ [...] discards b419b55ac3 33: onsuccess: #259: all: Success after llvm/linux/qemu: 359 [...] discards c26693878b 32: onsuccess: #258: all: Success after binutils/linux/qemu: [...] discards 95cad30fce 31: onsuccess: #257: all: Success after binutils: 4 commits discards 5965102ebc 30: onsuccess: #256: all: Success after binutils/linux/qemu: [...] discards 82fc5bee04 29: onsuccess: #255: all: Success after binutils/linux/qemu: [...] discards 743283e50a 28: onsuccess: #254: all: Success after binutils/linux/qemu: [...] discards b2389f1963 27: onsuccess: #253: all: Success after binutils/linux/qemu: [...] discards 9346aee732 26: onsuccess: #251: all: Success after binutils/llvm/qemu: [...] discards 3fb8c93ccb 25: onsuccess: #250: all: Success after binutils/linux/qemu: [...] discards a7906d586b 24: onsuccess: #249: all: Success after binutils/llvm/qemu: [...] discards e3bdb12b3a 23: onsuccess: #248: all: Success after binutils/qemu: 12 commits discards 974578ef53 22: onsuccess: #247: all: Success after binutils/llvm/linux/ [...] discards c131410a87 21: onsuccess: #246: all: Success after binutils/llvm/linux/ [...] discards 2e0e005886 20: onsuccess: #245: all: Success after binutils/qemu: 147 commits discards 2058482b38 19: onsuccess: #244: all: Success after binutils/llvm/linux/ [...] discards 2ff7bdf4e5 18: onsuccess: #243: all: Success after binutils/llvm/linux/ [...] discards f06e144fbd 17: onsuccess: #242: all: Success after binutils/llvm/linux/ [...] discards 766f231fd8 16: onsuccess: #241: all: Success after binutils/llvm/qemu: [...] discards 3df371fa1a 15: onsuccess: #240: all: Success after binutils/llvm/linux/ [...] discards b2c07dc1ed 14: onsuccess: #239: all: Success after binutils/llvm/linux/ [...] discards 409693a056 13: onsuccess: #238: all: Success after binutils/linux/qemu: [...] discards a5dffa12b4 12: onsuccess: #237: all: Success after binutils/llvm/linux/ [...] discards 496544f74e 11: onsuccess: #236: all: Success after binutils/llvm/linux/ [...] discards cb5cc94911 10: onsuccess: #235: all: Success after binutils/llvm/linux/ [...] discards bbc2205969 9: onsuccess: #234: all: Success after binutils/llvm/linux/q [...] discards 968d8c876d 8: onsuccess: #233: all: Success after binutils/llvm/linux: [...] discards 66e573a027 7: onsuccess: #232: all: Success after binutils/llvm: 9 commits discards ef0bd30bcf 6: onsuccess: #231: all: Success after binutils/llvm/linux/q [...] discards a535d9514a 5: onsuccess: all: Successful build after binutils/llvm/linu [...] discards bab529b483 4: onsuccess: all: Successful build after binutils/llvm/linu [...] discards 29607ebb55 3: onsuccess: all: Successful build after binutils/llvm/linu [...] discards f81da6ad65 2: onsuccess: all: Successful build after binutils/llvm/qemu [...] discards 0614483c6a 1: onsuccess: binutils-llvm-linux-qemu: all discards aa3a1a5b2e 0: update: binutils-llvm-linux-qemu: all -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (1a61252ddf -> c5d81031a0)

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_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 1a61252ddf 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] discards e836d02257 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] discards 67580158e3 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] discards 2db4f38fb9 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] discards 67d61dd83e 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits discards 3fbcb402c8 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] discards f3e14d0fac 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] discards abee1ead44 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] discards f9eda1bbe8 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] discards 1fef4c1692 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] discards 5ae52eb2c4 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] discards c087123645 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits discards e7d06d633f 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] discards f9b9f0de14 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] discards 2905fcde50 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] discards 361b3829f2 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] discards 2eb9356e44 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits discards 4108dba0e4 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] discards 0d5ee9e976 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] discards 256326448a 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] discards 65751d199f 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] discards 89893c9703 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] discards 4250d933c5 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] discards c13769841d 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] discards 1445bbeede 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] discards 8b4fe6984e 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] discards 197f766ac4 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] discards ee68a9a529 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] discards 189a95630c 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] discards a8e18ece97 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] discards d3b1f18fd3 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] discards e33610f963 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] discards 58d962fc54 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] discards e6fd9010b2 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] discards e460046aad 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] discards ac9607b4bf 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] discards c745de2a74 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] discards 12990eee65 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] discards e8966d0ca4 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] discards 216c1d17d3 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] discards 3054b18efe 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] discards 85b2756ec8 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits discards bbc87a270c 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] discards 99fdde4874 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] discards aca293791f 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits discards 45335cc38f 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] discards 534eb32842 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] discards 1519dd9214 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] discards 57a168e578 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] discards 97c7304619 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] discards c1bfc1655a 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] discards 4e734522b4 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] discards cd839d4601 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits discards 36037d4b06 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] discards b1f68222f0 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] discards 9d00ce00fa 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] discards 8e7e864e70 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits discards 4836cfdf58 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] discards 5bd7a3d2ce 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] discards a9f8fc774f 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] discards fabb8ce0e4 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits discards 10ddf2bdcf 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] discards 35dde61742 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 768b19e316 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 11de4b8713 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 2eab26184a 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards b004b88798 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 4ca4a41817 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 1bc11bd03a 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards bd7bd372c5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 788df3d946 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 09c905425f 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 0d80d9a39e 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 748ca26462 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards c080b66eeb 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards fd03e6e2de 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 6bc4481d82 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 1365d6703a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards 18c8a06004 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards ad3e6cb06c 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards 194ae5da65 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 5665fc0986 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards e7c7c96ae1 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards bd95fef22f 295: onsuccess: #2545: 1: Success after linux: 10 commits discards 9552c492bf 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards db27685c53 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 44852a0a0d 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 5f35da33bf 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 1bf94bd7ee 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 2e219d1d39 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards dbfffd5da6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 3b757f6d12 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards ccfacbbf36 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards d3de0fce29 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards b8b1a55430 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards 020c966194 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards a28351acb1 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 27ff38495b 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 07db0bd9cd 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 4615b3d1b7 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 4a2d125e5f 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 6d83607a54 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 66bf3857fb 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 7da139a378 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new 6fc5bd9bba 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new ef30df4251 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new c6549e849d 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 4651f65d75 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 9fce70bd42 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 41b50d2032 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 3e6e9785d7 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 4296e9b735 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 2b05806f57 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new f5c5a9f40a 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new ed9672dc33 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 7c0ae9d4f7 292: onsuccess: #2541: 1: Success after binutils: 13 commits new d0bf689893 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 9cb82aa629 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 45a13c64a7 295: onsuccess: #2545: 1: Success after linux: 10 commits new 95ebf0c98e 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 950245be25 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new b2ccb93b11 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 179a9a1056 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new 23412d8233 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new f4471e4327 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 6c1d2a8422 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 5f7d3b762c 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new f2b26377af 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 7a79026b41 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new f20b8b8735 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 16da28f9b6 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new befda919be 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 55d3a1711b 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 8e7f0a6233 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 73b37d8c72 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new d1cdcde4ff 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new cc56f30469 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 7b52b01b20 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 771b764745 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 9d8204675c 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new e2af9c6838 317: onsuccess: #2567: 1: Success after binutils/gcc/linux/g [...] new cf27fda2f8 318: onsuccess: #2568: 1: Success after binutils/gdb: 142 commits new b90e8ed774 319: onsuccess: #2569: 1: Success after binutils/gcc/linux/g [...] new ce8884f15c 320: onsuccess: #2570: 1: Success after binutils/gcc/linux/g [...] new 126158ca12 321: onsuccess: #2571: 1: Success after binutils/gcc/gdb: 19 [...] new 1f3cc430ef 322: onsuccess: #2572: 1: Success after binutils/gcc/gdb: 6 commits new 9a17637e9d 323: onsuccess: #2573: 1: Success after binutils/gcc/gdb: 18 [...] new 458ae02b37 324: onsuccess: #2574: 1: Success after binutils/gcc/glibc/g [...] new 9c5c8b8650 325: onsuccess: #2575: 1: Success after binutils/gcc/linux/g [...] new bc9d890149 326: onsuccess: #2576: 1: Success after binutils/gdb: 6 commits new 39ad255817 327: onsuccess: #2577: 1: Success after binutils/gcc/linux/g [...] new 95d7e2f290 328: onsuccess: #2578: 1: Success after binutils/gcc/glibc/g [...] new c0223cf115 329: onsuccess: #2579: 1: Success after binutils/gcc/linux/g [...] new fa48e9e070 330: onsuccess: #2580: 1: Success after basepoints/gcc-13-51 [...] new 189fee0e2b 331: onsuccess: #2581: 1: Success after binutils/gcc/linux/g [...] new ef6a20c04d 332: onsuccess: #2582: 1: Success after binutils/gcc/linux/g [...] new e6e6b7f833 333: onsuccess: #2583: 1: Success after binutils/gcc/linux/g [...] new 689b877827 334: onsuccess: #2584: 1: Success after gcc/linux: 15 commits new a7e47dd526 335: onsuccess: #2585: 1: Success after binutils/gcc/linux/g [...] new 20133d70c6 336: onsuccess: #2586: 1: Success after binutils/gcc/gdb: 22 [...] new 30745a0276 337: onsuccess: #2587: 1: Success after binutils/gdb: 4 commits new eb38550b16 338: onsuccess: #2588: 1: Success after binutils/gcc/linux/g [...] new 5348f008a1 339: onsuccess: #2589: 1: Success after binutils/gcc/glibc/g [...] new 6ddd585bc2 340: onsuccess: #2590: 1: Success after binutils/gcc/gdb/qem [...] new 402749baca 341: onsuccess: #2591: 1: Success after binutils/gcc/linux/g [...] new f4109b9507 342: onsuccess: #2592: 1: Success after binutils/gcc/linux/g [...] new ac62edb17b 343: onsuccess: #2593: 1: Success after binutils/gcc/glibc/g [...] new 5212921009 344: onsuccess: #2594: 1: Success after binutils/gcc/linux/g [...] new 6e9300e2b9 345: onsuccess: #2595: 1: Success after binutils/gcc/linux/g [...] new 168b21aea4 346: onsuccess: #2596: 1: Success after binutils/gcc/linux/g [...] new 295307e4f6 347: onsuccess: #2597: 1: Success after binutils/gcc/linux/g [...] new 5407f29f08 348: onsuccess: #2598: 1: Success after binutils/gcc/linux/g [...] new 7be837a5c9 349: onsuccess: #2599: 1: Success after binutils/gcc/linux/g [...] new 88ff27f397 350: onsuccess: #2600: 1: Success after binutils/gcc/linux/g [...] new 56f043820a 351: onsuccess: #2601: 1: Success after binutils/gcc/gdb: 17 [...] new 9b29b6e92d 352: onsuccess: #2602: 1: Success after binutils/gcc/linux/g [...] new 384c3150e1 353: onsuccess: #2603: 1: Success after binutils/gcc/linux/g [...] new 1bff27b422 354: onsuccess: #2604: 1: Success after binutils/gcc/glibc/g [...] new 676826c8c3 355: onsuccess: #2605: 1: Success after binutils/gcc/linux/g [...] new f23fed92c6 356: onsuccess: #2606: 1: Success after binutils/gcc/linux/g [...] new a222b4a3af 357: onsuccess: #2607: 1: Success after binutils/gcc/linux/g [...] new c757ce6b1b 358: onsuccess: #2608: 1: Success after binutils/gcc/glibc/g [...] new da43dda343 359: onsuccess: #2609: 1: Success after binutils/gcc/linux/g [...] new 6ee0875fc9 360: onsuccess: #2610: 1: Success after binutils/gcc/gdb/qem [...] new 8e7e18f330 361: onsuccess: #2611: 1: Success after binutils/gcc/linux/g [...] new 74c3f8156d 362: onsuccess: #2612: 1: Success after binutils/gcc/gdb: 3 commits new 4e4474919e 363: onsuccess: #2613: 1: Success after binutils/gcc/gdb/qem [...] new cdc36108e6 364: onsuccess: #2614: 1: Success after binutils/gcc/linux/g [...] new e4660a4a47 365: onsuccess: #2615: 1: Success after binutils/gcc/linux/g [...] new b7635702fd 366: onsuccess: #2616: 1: Success after glibc-2.37.9000-17-g [...] new 2cad31049c 367: onsuccess: #2617: 1: Success after gcc/linux/qemu: 107 commits new 3d8d209222 368: onsuccess: #2618: 1: Success after binutils/gcc/linux/g [...] new 9fd8b28b98 369: onsuccess: #2619: 1: Success after binutils/gcc/gdb/qem [...] new 89952f3086 370: onsuccess: #2620: 1: Success after binutils/gcc/glibc/g [...] new 0140d6d5db 371: onsuccess: #2621: 1: Success after binutils/gcc/linux/g [...] new 6ee5423e97 372: onsuccess: #2622: 1: Success after binutils/gcc/glibc/g [...] new 9e04c1dfc6 373: onsuccess: #2623: 1: Success after binutils/gcc/linux/g [...] new afe9446b51 374: onsuccess: #2624: 1: Success after binutils/gcc/gdb: 6 commits new 825a156de5 375: onsuccess: #2625: 1: Success after binutils/gcc/gdb/qem [...] new 6e1403ebd2 376: onsuccess: #2626: 1: Success after binutils/gcc/glibc/g [...] new a3b49d136e 377: onsuccess: #2627: 1: Success after basepoints/gcc-13-57 [...] new 6dc6f1ceb3 378: onsuccess: #2629: 1: Success after binutils/gcc/glibc/g [...] new c5d81031a0 379: onsuccess: #2630: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (1a61252ddf) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] 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 2044 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31764 -> 32172 bytes 04-build_abe-stage1/console.log.xz | Bin 73820 -> 74176 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8576 bytes 07-build_abe-glibc/console.log.xz | Bin 245436 -> 245488 bytes 08-build_abe-stage2/console.log.xz | Bin 205372 -> 208484 bytes 09-build_abe-gdb/console.log.xz | Bin 39064 -> 39408 bytes 10-build_abe-qemu/console.log.xz | Bin 31204 -> 31544 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3148 -> 3120 bytes 13-check_regression/console.log.xz | Bin 9188 -> 8292 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 46 + 13-check_regression/mail-body.txt | 94 +- 13-check_regression/results.compare | 78 +- 13-check_regression/results.compare2 | 684 +--- 13-check_regression/results.regressions | 66 + 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 96 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- results | 66 + sumfiles/g++.log.xz | Bin 3399304 -> 3392096 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 3019400 -> 3023272 bytes sumfiles/gcc.sum | 5289 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1034416 -> 1033676 bytes sumfiles/gfortran.sum | 18 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217648 -> 217688 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427404 -> 432660 bytes sumfiles/libstdc++.sum | 160 +- 44 files changed, 3317 insertions(+), 3449 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page: