Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (e74fa43aaaa -> a5b5ae4fce1)

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_kernel/llvm-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from e74fa43aaaa 49: onsuccess: #7: boot: Success after binutils/llvm/linux/ [...] new a5b5ae4fce1 50: onsuccess: #8: boot: Success after binutils/llvm/linux/ [...] 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: 01-reset_artifacts/console.log.xz | Bin 1776 -> 2012 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2572 bytes 03-build_abe-binutils/console.log.xz | Bin 27132 -> 27448 bytes 04-build_kernel_llvm/console.log.xz | Bin 67412 -> 66644 bytes 05-build_abe-qemu/console.log.xz | Bin 32148 -> 32900 bytes 06-build_linux/console.log.xz | Bin 3116 -> 3120 bytes 07-boot_linux/console.log.xz | Bin 6108 -> 6136 bytes 08-check_regression/console.log.xz | Bin 4348 -> 4228 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 19 files changed, 24 insertions(+), 26 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (6ae6715c8d4 -> 310abf4e3ac)

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 6ae6715c8d4 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits discards fed7ba8abe2 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits discards ebf62d7267b 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits discards 213be6a89b4 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards 80b08c54ef1 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards 30a50e67e7e 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards 80df613363c 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards 4d2befa15b4 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards 97c96a2d5e7 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards 1caeb5f834a 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards 0a9e0c0a1a5 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards 6ec4af8eca7 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards cc4c34c4d12 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards ece833ceb3c 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards 6e9d2e2ec9d 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 10ebd1630ee 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards a54cc4b4444 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 3362c7756a1 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 845ffafb4ee 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards f2bec1aa86b 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards c24b490f85c 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 2eb349110d3 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards d81f914e9ee 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 67549d6b060 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards 31f13a9d937 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards d482a2e172f 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 5cb99c61fc1 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards 39331034593 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards 9d08d2bd1e6 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards 9e46890c605 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards f4c281b02d8 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards a048412d95a 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 09516159225 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards da1308d0bda 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards 5d28dc1b922 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards ad6224238d3 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 56aea7454ea 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 64fbb9301f4 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards cae63a42b66 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards b27ba140ce2 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 17d7d49eec8 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards ccd59d5ef84 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 14b7d231d4f 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 4eeebb358d1 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards 4debc53dd38 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards a06813f4717 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 12a1859b52f 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 84c894ffed2 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards d8d709c3114 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards c25653a4b0d 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 3206f955f3a 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards b17766e84eb 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 15a3c388137 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards 36038402586 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards fd06706f412 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards d33a000cf96 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards c972aad9485 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards d9babcc7c4c 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards ca37a1a8a34 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards c1c71851510 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards ff58689bfa3 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards e4106f7b5db 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 1872ae46882 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards f19cf337f0b 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards f1c1e7c406f 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards 2d9032d6d84 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 9d5d429564f 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards b6e095d51b9 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards 8efc86085cd 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards 6e989de4fde 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 9bf583d3be0 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards c258887e3f8 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards b69001ace08 141: onsuccess: #559: 1: Success after gcc: 4 commits discards 41254c0e357 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards 82186dfd247 139: force: #557: 2: Success after gcc: 6 commits discards e82a0a7a611 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 4409703575c 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards a24f4326c90 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards 7816b7c5c67 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards c945b0b3b1a 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards b8eeb36e4c8 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 8d47ac85bae 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards eb9e48dbdc5 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 3df20d4b47c 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards e31c94db1bd 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 8a7f93104ca 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 08e078e5721 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 0015113d93f 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards ebc32773ed3 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 3439e0b96eb 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards 62b4bc32d59 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards d5e5f9b202d 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 2e35b98e321 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 7e3a7da4e98 120: onsuccess: #535: 1: Success after binutils: 10 commits discards cbe549f0e95 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards 8339afdff81 118: force: #533: 2: Success after binutils: 4 commits discards 85c558828de 117: onsuccess: #531: 2: Success after gcc: 65 commits discards 39e3468ca4b 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 93823de4fd2 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 4506b60621a 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 43978104776 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 97dd0ed4295 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 3f69ef07379 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 581097f34ee 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 0620ced2e73 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 6e95a981fb0 117: onsuccess: #531: 2: Success after gcc: 65 commits new 7fe726b2ed9 118: force: #533: 2: Success after binutils: 4 commits new 5b8286b8322 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new d41bf647eb9 120: onsuccess: #535: 1: Success after binutils: 10 commits new 464877adf9f 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new aa863ae2e5f 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new 07ae615fe1e 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 3d6f9a99c56 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 6a8eb67b311 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new bd4b5273b6b 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 3ffea433df2 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new fad21a4d160 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 16954c8f6f2 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 00bc382d280 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 38fde57b401 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new cc9de18d7ac 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new 8c4c03c881f 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new 94af90f809a 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 704deb30260 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new f95949280e8 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 44f66429e7c 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 6a791bbc92e 138: onsuccess: #554: 2: Success after binutils: 10 commits new 861ccc242f5 139: force: #557: 2: Success after gcc: 6 commits new b235414e772 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new 7f8f09671d6 141: onsuccess: #559: 1: Success after gcc: 4 commits new 76c0c836cd3 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 6de764bf3f4 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new c1979f8d46a 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new eafbc7a5c5b 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new 03a3f70989b 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 7ba2e950e91 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new bf05ccf6b6e 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new a2d9d241a89 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new e0ed593549e 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new c3c386b5976 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new 9ddd5967518 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 6053074f1b1 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 8c8c80e42c9 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new ef95fef81d0 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new 4958a1a7457 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new c83fae40e9f 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new af58207c053 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 051dc0052d2 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 0b5420a3f14 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 34ab7414e5f 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new 0556d8f4819 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 7086c35e62d 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 07e7d61479a 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new a285e69eb4c 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new e20753c8375 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new 99a605d8e78 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 8bd95851136 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 5f2883611fc 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 96c95b15322 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new c78f61640ef 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new aac169e45e2 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 7f9e250be61 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 0292a8f7301 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new 835fd2f4f56 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 1445318513c 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 3e1eb39c06c 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new 0aa9f8c3e7f 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new fe88085b6a3 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 2c84a1af6aa 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 3acb3cd5082 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new 473082ae9e9 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 814d8836d80 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 7a6e8d2c1bd 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new e3f2f838b11 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 3fa1a08e3d7 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new d2fa3fa25ef 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new f2519df512d 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new 7fb8021edbf 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 2c1b08fb163 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new aa8a017aa8b 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 480dfc53b6d 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new 5cf858e5cfa 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new bcb19321803 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 754c2c828ca 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 136e085a258 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new ccfdd40b66c 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new ab5fbb4184d 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new d4306c89934 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new 5be20b32477 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 61af5c817c8 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 97f14f6deb0 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 5618f52057d 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new 78c616921bd 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new aaa9b9dade0 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new 1a5f11f2c22 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new e4ea75b2c43 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new 45faec552e6 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new f9c22468963 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new 0fec51c62c9 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new e50ae23eccb 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits new fc64792ab3b 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits new 6397c6e594e 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits new 310abf4e3ac 214: onsuccess: #30: 2: Success after binutils/gcc: 34 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 (6ae6715c8d4) \ 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 1976 -> 1972 bytes 02-prepare_abe/console.log.xz | Bin 2584 -> 2520 bytes 04-build_abe-binutils/console.log.xz | Bin 35172 -> 35144 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 305432 -> 305616 bytes 06-check_regression/console.log.xz | Bin 3120 -> 3068 bytes 06-check_regression/jira-body.txt | 1 - 06-check_regression/mail-body.txt | 2 +- 07-update_baseline/console.log | 38 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++------ 15 files changed, 35 insertions(+), 37 deletions(-) delete mode 100644 06-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (9c1597d9e6d -> de5703d5064)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 9c1597d9e6d 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards f87ee3c2d75 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards e48a64fe758 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards c348bcd096c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 66d2bbbecac 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards be2ee92923e 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards e79942c5377 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 58876eb0efb 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 1d4fa109769 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 0e04ee8cb78 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 59572290413 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7946d2cb643 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards e93d547af62 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 286d3307987 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 4cca520342a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 45bec1d35fe 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4aaad9a14cb 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 327d5524db8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0380557ee21 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards abacfc6a4ea 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ae85dab48a6 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0caf893d34a 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 6e5823b5c1f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 52c35787263 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f925e27f78b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3463ae5841d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards a6f245a6c25 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards b56b1f1a58b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards b654152b067 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards b1e43f03c47 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards d6ab3232367 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 3373d2d3969 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 14ebbb39908 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards e49652208d0 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 03948748a97 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards f86eb5e8793 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 2cc4d480aeb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards b8115337e1f 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 557d15b826c 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 7f2559ac2a7 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards c9da7953de4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 78807c04eab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards ba65777eae6 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 588c4a8c72b 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards ac85a8974bc 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards fcd9cb51d64 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards aae70307ab0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 71a88cd0bf5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards 2f0168f6ef9 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards f00ff652c04 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards f5b11163316 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 87a5575ee7a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 8ab3484c058 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 48ff78d8478 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards af074126e72 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards be5b8ff271d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards b290977c26c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards c48e50d77c1 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 888d13581f6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 9c57f0729da 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 35a47537397 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 50fd60d03a7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 64a57758b4d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards d0271d6d5f8 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards f65db080f8f 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 7e31d433a88 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 3ae3b0687ae 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 425abda21b2 162: onsuccess: #624: 1: Success after linux: 10 commits discards b832dd99d80 161: onsuccess: #623: 1: Success after glibc: 9 commits discards e173f91de0d 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 50fcf233b0c 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 3c0ad7d2805 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards e223015a672 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 148d840f502 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards dbe625a62ff 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 307b0fcccaa 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 14a77e975a4 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 829b7a75a39 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards eac171ea4f0 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 33c1fb06f7a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards ea1f9215488 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 05ab5f875d7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 401ff94ab05 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 15ecc97e8fc 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 0178a129764 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards afe6f7f0375 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 6ae39aea05f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 4ef0f317cb4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b7961e51cf9 141: onsuccess: #601: 1: Success after linux: 794 commits discards 8a7afc2fc74 140: onsuccess: #600: 1: Success after gcc: 23 commits discards affab5c5011 139: onsuccess: #599: 1: Success after binutils: 10 commits discards 89d16d72651 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards d969226b849 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 7bbfe2d5df7 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 9ba91237d2a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards ff11815c8a6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards cb54ec526d7 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards edea18e5a43 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 730871843a0 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 06186164915 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 0d1c82f4d90 129: onsuccess: #588: 1: Success after linux: 4 commits new ddce5c47990 129: onsuccess: #588: 1: Success after linux: 4 commits new 1e18927a462 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 92a74456dc2 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new ca6cf9c519e 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 84dd60f5109 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new cd6bac438b9 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 9c75560e162 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 82e98e3d340 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new c8ebdf51d19 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 9d429ce7565 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 432c0e4cfe3 139: onsuccess: #599: 1: Success after binutils: 10 commits new 4dafde96d4b 140: onsuccess: #600: 1: Success after gcc: 23 commits new fedefb324c0 141: onsuccess: #601: 1: Success after linux: 794 commits new 9b1a69a881b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 4c144c91dc8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 0dbe369448a 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new a4d12048f6d 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 546386c9793 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new f01866a975d 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 61d06b064e7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 4eea8ac3388 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 7840803ddb9 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 95f9c57e407 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 118d6e89967 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new c3726fd77c7 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 50bd316c51f 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 57378156493 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 8fb7a9ca5d8 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new d8f587af580 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 80fd45b1947 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new c39e319f1c2 159: onsuccess: #620: 1: Success after binutils: 12 commits new 32f185d9c1f 160: onsuccess: #621: 1: Success after gcc: 11 commits new 0dca71117e1 161: onsuccess: #623: 1: Success after glibc: 9 commits new 67a0fff23d7 162: onsuccess: #624: 1: Success after linux: 10 commits new c426fb8df3a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 0b333cfab8e 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1a5bfe5c6d9 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new fb7b44588fe 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new e17efe0d09e 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 98d86ecdc1f 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 8d76214155d 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new ce44355f856 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 018afb09fec 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 337510b50dd 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 5353666c86c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new bb3d63af66d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 9cfca273bfd 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 937c96840e4 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 046406c1630 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 391adfb4a36 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new e240a28d4bd 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 808ad48ad81 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 4375338b943 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 03eeb318693 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 4ccefb689b0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new 04bca5efb38 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new 820c72f3b0b 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 83dec5ec7f2 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 23dc5c75daa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8328fc5b4c8 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new bd58720d63b 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ea6500f738c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new baddeef55e3 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 5eacc0feff2 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 14c62fb0e77 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 0247e36c3a9 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 48f632c64d8 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 658774bb0a3 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 681fa0d4adb 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 04a80b6feb1 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 03db5fc1de9 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new edb497ce2d9 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new a6db7ac5559 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 5ea1b649b1b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 33a363eebf2 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3a195f0439f 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 5efec1478e7 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8e73e722fab 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new f1e3e790c3c 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new dcb1cff0286 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new f8134f8904a 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 24365d5c281 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 777c0bcaab8 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 5f4fb11dd88 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 14a45f6097d 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 4f82be7f064 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new b07ec9c4ef6 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 5a1c5d97400 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 720d2c51885 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 9b12767ce62 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new c73309c9372 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 3cf0dc7582f 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new f36b3751c90 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 13e7058a3a9 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new ae6f3729748 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new cf7f1eb4a02 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new d5834b95a86 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new a525d5d4045 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 56bcb2678dc 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new 9f5c9c3c793 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 9e5b542a1a4 229: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new de5703d5064 230: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (9c1597d9e6d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2028 -> 2236 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2512 bytes 03-build_abe-binutils/console.log.xz | Bin 49012 -> 49052 bytes 04-build_abe-gcc/console.log.xz | Bin 236856 -> 238088 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8424 bytes 07-build_abe-glibc/console.log.xz | Bin 232940 -> 232588 bytes 08-build_abe-gdb/console.log.xz | Bin 47500 -> 47260 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3792 -> 3772 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9116 -> 9644 bytes 11-check_regression/console.log.xz | Bin 5716 -> 9976 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 1699 ++++- 12-update_baseline/console.log | 62 +- 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 81208 -> 76972 bytes sumfiles/g++.log.xz | Bin 2912268 -> 2911672 bytes sumfiles/g++.sum | 1286 ++-- sumfiles/g++.sum.sep | 10725 ++++++++++++-------------------- sumfiles/gcc.log.sep.xz | Bin 67068 -> 63696 bytes sumfiles/gcc.log.xz | Bin 2469108 -> 2484576 bytes sumfiles/gcc.sum | 327 +- sumfiles/gcc.sum.sep | 505 +- sumfiles/gfortran.log.sep.xz | Bin 36364 -> 29272 bytes sumfiles/gfortran.log.xz | Bin 949244 -> 953296 bytes sumfiles/gfortran.sum | 9 +- sumfiles/gfortran.sum.sep | 3723 ++++++----- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233936 -> 233812 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 10152 -> 9900 bytes sumfiles/libstdc++.log.xz | Bin 469128 -> 469836 bytes sumfiles/libstdc++.sum.sep | 493 +- 46 files changed, 8876 insertions(+), 10027 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (1f641d6aba2 -> bbf2424c57c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 1f641d6aba2 libatomic: Fix SEQ_CST 128-bit atomic load [PR108891] new bbf2424c57c c++: outer 'this' leaking into local class [PR106969] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/parser.cc | 13 +++++++++---- gcc/testsuite/g++.dg/lookup/name-clash11.C | 2 +- gcc/testsuite/g++.dg/lookup/this2.C | 22 ++++++++++++++++++++++ 3 files changed, 32 insertions(+), 5 deletions(-) create mode 100644 gcc/testsuite/g++.dg/lookup/this2.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-11 updated (6d3c71225d6 -> 2055702e8d4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 6d3c71225d6 Daily bump. new 0257ba76644 Fortran: procedures with BIND(C) attribute require explicit [...] new 4b722050fe8 Fortran: simplification of NEAREST for large argument [PR109186] new 2055702e8d4 Fortran: reject MODULE PROCEDURE outside generic module int [...] The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/decl.c | 7 ++++--- gcc/fortran/resolve.c | 10 ++++++++++ gcc/fortran/simplify.c | 2 +- gcc/testsuite/gfortran.dg/nearest_6.f90 | 26 ++++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr85877.f90 | 25 +++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr99036.f90 | 9 +++++++++ 6 files changed, 75 insertions(+), 4 deletions(-) create mode 100644 gcc/testsuite/gfortran.dg/nearest_6.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr85877.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr99036.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch releases/gcc-10 updated (84026854950 -> b9f6e7e234b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from 84026854950 Daily bump. new dca8e28c990 Fortran: procedures with BIND(C) attribute require explicit [...] new b9f6e7e234b Fortran: simplification of NEAREST for large argument [PR109186] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/resolve.c | 10 ++++++++++ gcc/fortran/simplify.c | 2 +- gcc/testsuite/gfortran.dg/nearest_6.f90 | 26 ++++++++++++++++++++++++++ gcc/testsuite/gfortran.dg/pr85877.f90 | 25 +++++++++++++++++++++++++ 4 files changed, 62 insertions(+), 1 deletion(-) create mode 100644 gcc/testsuite/gfortran.dg/nearest_6.f90 create mode 100644 gcc/testsuite/gfortran.dg/pr85877.f90 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (a0aba751884 -> 901fd9a0bdd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards a0aba751884 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 2679fe0ac50 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards f434429d0ee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards f2accf4d3a2 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 15d34b834dc 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f693aacd9bd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards b08950a9893 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards b6e41f765e0 121: force: #26: : Failure after baseline build: no new commits discards df1060f7573 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 8a4d3069fe2 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 3d6adacec46 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 441d2f8b9af 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 7d73c6853cd 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards b7b1f7e4518 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 17ef2313aca 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 68de6afa2bf 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 3cf696a69ce 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 912e877b786 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards beae34a16e8 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a51cf465876 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4665f9792fb 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards fc73bdd8f86 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 27285f9e6ac 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards d2b86dd6ce4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 4ff04ad3984 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards f1bc72cd77b 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5950c0eb58a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards cf41b2eb722 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards d1df5fe31da 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 26a09dbd192 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 92044746889 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 65bd6542433 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards ef894bf915e 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 59df9662baf 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards e84649db06a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards 2957932a16f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards a3bbb82f0ca 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards d7e34e227ce 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards a08851c1dbb 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 7338c9d0361 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 4598c66f654 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards b75fef90834 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 65b89a098ca 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards abe60845245 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 7263dd2da8e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards e7a2e32f986 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards 1fc66d1a964 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 1dd02fbbfe3 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 05db0bd38c6 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 508bc654941 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards fea7b0cbf45 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards 42d74e7c0f8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 07be1891b49 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 1ea502cdbb0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards 5609c5d0508 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 9a8cdf6dd1c 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards bfaf78ce159 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 65a3a4e60ee 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 86466ec1093 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 7d58ef804d8 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards d4cc3b98ffb 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 0363f498861 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 7a3b5f70ca9 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 91f10add322 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 7c230f96cb6 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 931fa6c5e48 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 916b4485d58 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 0200db2209a 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 5cc3b040b43 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards ae86c93d762 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards bb69372bafd 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 52c8506a67b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 47a6f19d668 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 29cac887ef5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 94c12e3a55b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards df2f1fa689b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 8d2eb04f3c1 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 91e3a7aacea 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 97da59688e4 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 53643acfb4d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 9ffe595e80d 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards 27c5d9ac966 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards cb3deb38d78 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards add17c65b64 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards e5ee13ce1e8 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 4ae8477ce9c 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards bb82e94b17b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards dac14868292 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 718316e7efa 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards b6d8f584dd6 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards a5d3bc5a987 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 946fe28bd02 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards 3fcfcdbb7e5 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 23b0ed60088 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 38a9e663c18 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 636ad4e955f 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 920609e3c0f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards fccc8606ba7 31: onsuccess: #38: 1: Success after linux: 14 commits discards fab2f2609c9 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 167ddfe1708 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards d343c3750a8 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 0c7242dd541 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 83bc2bf650a 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new c872b31e784 30: onsuccess: #36: 1: Success after binutils: 18 commits new 0cd2e4f4372 31: onsuccess: #38: 1: Success after linux: 14 commits new 6fdd9cb2a68 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 80bff201de8 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new b1837702cbc 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new e91ae6a326a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 9d3303d9fab 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new b502168c5e5 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new 1a060dd4885 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new bbd2182dbb5 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 068807d348d 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 8841c4df4d7 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 796f67194e1 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 0cb2e5db611 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new db0693d050a 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 62891e113dd 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new 4a44f230d42 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 66583623cbd 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 6f3e943e995 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 060508a3798 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 79eac3e07b8 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new ac018208eb3 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new c18028ee2e2 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new 1de56612bf8 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 3ed11cf5afb 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new e928022507a 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new df76d0bb720 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new c7d818ca081 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new 67630247210 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 2dc83b8b878 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new e0a884065f6 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3c1a2ff7b5e 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 5e0bf5e7e99 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new b044735b594 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 9dba788fe77 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new fcebec6752d 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 2cbc897ef72 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 971d8d0c0a3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new 6ca66fcb263 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new c8f58499c42 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new a9b5ab545c7 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new a5827e1d75f 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 7d51dfc5e7e 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 91e065d0986 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new c91dbb8e5fa 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new f7a78ac200a 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new caaec1366a5 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new d813bb1b809 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 759e8a663d2 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 4c5442aea82 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new ec87ca43542 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 11bf85fb6f2 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new b1b7e453ab2 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new 2d03af9b4f4 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 5311b3f6cf0 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 5ed93b6b5a2 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new db63d2ccc34 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new e3041d454eb 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 948f34ec191 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 223bcc98e00 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new abdd9a7466f 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 9e1e55c45b5 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new c36e20a12f5 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 235603842d2 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new e9f51367d3f 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new d9c531247f4 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new e793127ed58 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new ec6dd6402cd 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new d80e55aeba3 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 3eded8240be 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new 6e4f14ff090 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 592b40ae6f5 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new c848be235f6 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new c8b5391fc17 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 7e5245dee44 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 26f094cbf66 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 09c9244cab2 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 5996746087c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 1ce478081be 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 53e6f5b2287 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7f755b711bd 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new efd35a73f8e 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 65a80cd26f8 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 305b38d4e26 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new a12d42e5057 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6c351e85381 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 926e2fb8716 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 6cc15afb343 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 1c68a47b501 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bcbc831b479 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new eb1aa109345 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new f7a55088645 121: force: #26: : Failure after baseline build: no new commits new 31d0f742e14 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 858c50116cb 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new ecfcd7d8fb4 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new aecc8000b46 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new b48b813ea36 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new ab5087d96ef 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new c44be7a07cf 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 901fd9a0bdd 129: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (a0aba751884) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2140 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2568 bytes 03-build_abe-binutils/console.log.xz | Bin 49076 -> 49288 bytes 04-build_abe-gcc/console.log.xz | Bin 236716 -> 238024 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8464 -> 8452 bytes 07-build_abe-glibc/console.log.xz | Bin 232340 -> 233736 bytes 08-build_abe-gdb/console.log.xz | Bin 47396 -> 47124 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3772 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2732 -> 2836 bytes 11-check_regression/console.log.xz | Bin 4816 -> 4708 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14468 -> 14464 bytes sumfiles/gdb.sum | 4 ++-- 27 files changed, 51 insertions(+), 53 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_woa_build/master-woa64 updated (6a96a576ca8 -> e7c30d4071b)

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_woa_build/master-woa64 in repository toolchain/ci/base-artifacts. from 6a96a576ca8 0: init: #2: 1: Success after baseline build: no new commits new e7c30d4071b 1: onsuccess: #3: 1: Success after baseline build: no new commits 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: 01-reset_artifacts/console.log.xz | Bin 2220 -> 1860 bytes 01-reset_artifacts/patch-env.sh | 2 -- 02-prepare_abe/console.log.xz | Bin 2564 -> 2544 bytes 04-build_abe-binutils/console.log.xz | Bin 25016 -> 25528 bytes 05-check_regression/console.log.xz | Bin 1680 -> 1700 bytes 05-check_regression/mail-body.txt | 6 +++++- dashboard/dashboard-generate.sh | 2 +- mail/mail-body.txt | 6 +++++- manifest.sh | 11 +++++------ 9 files changed, 16 insertions(+), 11 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_woa_check_binutils/master-woa64 created (now 548d2dde770)

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_woa_check_binutils/master-woa64 in repository toolchain/ci/base-artifacts. at 548d2dde770 0: init: #2: 1: Success after baseline build: no new commits This branch includes the following new commits: new 548d2dde770 0: init: #2: 1: Success after baseline build: no new commits 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_woa_build/master-woa64 created (now 6a96a576ca8)

by git＠git.linaro.org

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023