Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[binutils-gdb] branch gdb-13-branch updated (02ccd8cfbc7 -> 5fcfbade4ec)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-13-branch in repository binutils-gdb. from 02ccd8cfbc7 Automatic date update in version.in new 5fcfbade4ec Automatic date update in version.in 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: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-mainline-allmodconfig updated (18643f8d87 -> c6699a46a3)

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-release-aarch64-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 18643f8d87 46: onsuccess: #463: all: Success after binutils/linux/qemu: [...] new c6699a46a3 47: onsuccess: #464: all: Success after llvm/linux/qemu: 527 [...] 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 1772 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30612 -> 30524 bytes 04-build_kernel_llvm/console.log.xz | Bin 65548 -> 65240 bytes 05-build_abe-qemu/console.log.xz | Bin 31664 -> 31464 bytes 06-build_linux/console.log.xz | Bin 3128 -> 3112 bytes 08-check_regression/console.log.xz | Bin 3716 -> 3680 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- results | 2 +- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (bf716a53bd8 -> 8eacd95dd44)

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 bf716a53bd8 Fix crash with C++ qualified names new b1c95bc4dd7 Move bfd_init to bfd.c new 5a671d7a854 Move mips_refhi_list to bfd tdata new 10c386190cb peXXigen.c sanity checks new 8eacd95dd44 Set dwarf2 stash pointer earlier The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/Makefile.am | 6 ++-- bfd/Makefile.in | 20 +++++------ bfd/bfd-in2.h | 20 +++++------ bfd/bfd.c | 37 +++++++++++++++++-- bfd/coff-mips.c | 23 ++++-------- bfd/doc/local.mk | 6 ++-- bfd/dwarf2.c | 3 +- bfd/ecoff.c | 15 ++++++++ bfd/init.c | 26 -------------- bfd/libecoff.h | 11 +++++- bfd/peXXigen.c | 96 +++++++++++++++++++++++++++----------------------- bfd/po/SRC-POTFILES.in | 1 - 12 files changed, 140 insertions(+), 124 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-aarch64-bootstrap updated (e32d0ff629 -> d276e58364)

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/release-aarch64-bootstrap in repository toolchain/ci/base-artifacts. from e32d0ff629 45: onsuccess: #151: 2: Success after binutils/gcc: 9 commits new d276e58364 46: onsuccess: #152: 2: Success after gcc: 4 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 1708 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 38148 -> 38176 bytes 05-build_abe-bootstrap/console.log.xz | Bin 264328 -> 264728 bytes 06-check_regression/console.log.xz | Bin 2760 -> 2524 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 11 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_lto updated (01ac0db090 -> d8214bfa56)

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_lto in repository toolchain/ci/base-artifacts. discards 01ac0db090 163: onsuccess: #572: 2: Success after binutils/gcc: 3 commits discards 1ee07f4556 162: onsuccess: #571: 2: Success after binutils/gcc: 6 commits discards 74e4c45de7 161: onsuccess: #570: 2: Success after binutils/gcc: 27 commits discards a5170aa00b 160: onsuccess: #569: 2: Success after binutils/gcc: 55 commits discards dafff9f218 159: onsuccess: #568: 2: Success after binutils/gcc: 36 commits discards 3f8e8cd9a1 158: onsuccess: #567: 2: Success after binutils/gcc: 59 commits discards c75c53e411 157: onsuccess: #566: 1: Success after gcc: 3 commits discards ed3d678327 156: force: #565: 1: Failure after basepoints/gcc-13-4953-g3 [...] discards 3c0794eadb 155: force: #564: 2: Success after gcc: 7 commits discards 91fb0b1efc 154: onsuccess: #562: 2: Success after binutils: 12 commits discards 95c26384d1 153: onsuccess: #560: 2: Success after binutils/gcc: 16 commits discards c1bdfb6776 152: onsuccess: #559: 2: Success after binutils/gcc: 17 commits discards a39ef8bc59 151: onsuccess: #558: 2: Success after binutils/gcc: 11 commits discards 49420ae8b1 150: onsuccess: #557: 2: Success after binutils/gcc: 20 commits discards 54e326f144 149: onsuccess: #556: 2: Success after binutils/gcc: 11 commits discards 267eeb42de 148: onsuccess: #555: 2: Success after binutils/gcc: 27 commits discards 110d01ed06 147: onsuccess: #554: 2: Success after binutils/gcc: 7 commits discards 424c49875d 146: onsuccess: #553: 2: Success after binutils/gcc: 25 commits discards 6bdb49e8d3 145: onsuccess: #552: 2: Success after binutils/gcc: 9 commits discards 8ce2a4d88f 144: onsuccess: #551: 2: Success after binutils/gcc: 90 commits discards df6ced4e83 143: onsuccess: #550: 2: Success after binutils/gcc: 41 commits discards ab790e5152 142: onsuccess: #549: 2: Success after binutils/gcc: 67 commits discards f041ae9604 141: onsuccess: #548: 2: Success after binutils/gcc: 15 commits discards 51ec9ef69f 140: onsuccess: #547: 2: Success after binutils/gcc: 53 commits discards 47d43ab3d7 139: onsuccess: #546: 2: Success after binutils/gcc: 9 commits discards cbbaaac5df 138: onsuccess: #545: 2: Success after binutils/gcc: 18 commits discards f8e179509a 137: onsuccess: #544: 2: Success after binutils/gcc: 38 commits discards eb830bbb54 136: onsuccess: #543: 1: Success after binutils/gcc: 31 commits discards 17108684fa 135: onsuccess: #542: 1: Success after binutils/gcc: 48 commits discards a6543dd475 134: onsuccess: #541: 1: Success after binutils: 9 commits discards 924ca98690 133: force: #540: 1: Failure after gdb-12-branchpoint-3046-g [...] discards 16ae659f03 132: force: #539: 2: Success after binutils: 5 commits discards d9c6043d41 131: onsuccess: #538: 2: Success after gcc: 58 commits discards a6922d25e0 130: onsuccess: #535: 2: Success after binutils/gcc: 45 commits discards decb999a53 129: onsuccess: #534: 2: Success after binutils/gcc: 13 commits discards 92fbac3e6c 128: onsuccess: #533: 2: Success after binutils/gcc: 12 commits discards f547df55de 127: onsuccess: #532: 2: Success after binutils/gcc: 27 commits discards d99e743782 126: onsuccess: #531: 2: Success after binutils/gcc: 31 commits discards 556b3566ca 125: onsuccess: #530: 2: Success after binutils/gcc: 33 commits discards 33d0676f82 124: onsuccess: #529: 2: Success after binutils/gcc: 47 commits discards 933da101d7 123: onsuccess: #528: 2: Success after binutils/gcc: 27 commits discards 0919e888ef 122: onsuccess: #527: 2: Success after binutils/gcc: 10 commits discards f7b1bd287f 121: onsuccess: #526: 2: Success after binutils/gcc: 11 commits discards c45c7bb88d 120: onsuccess: #525: 2: Success after binutils/gcc: 28 commits discards b7626cd95c 119: onsuccess: #524: 2: Success after binutils/gcc: 57 commits discards 9a24c202af 118: onsuccess: #523: 2: Success after binutils/gcc: 42 commits discards 5f2c357072 117: onsuccess: #522: 2: Success after binutils/gcc: 19 commits discards 4df53164f7 116: onsuccess: #521: 2: Success after binutils/gcc: 118 commits discards 514ec4fcec 115: onsuccess: #520: 2: Success after binutils/gcc: 6 commits discards a0895cf499 114: onsuccess: #519: 2: Success after gcc: 2 commits discards 32be85febc 113: onsuccess: #518: 2: Success after binutils: 5 commits discards 88fc783134 112: onsuccess: #516: 2: Success after binutils/gcc: 21 commits discards 42ed98ac44 111: onsuccess: #515: 2: Success after binutils/gcc: 47 commits discards e3c7cb8b85 110: onsuccess: #514: 2: Success after binutils/gcc: 43 commits discards 84516cb3a9 109: onsuccess: #513: 2: Success after binutils/gcc: 37 commits discards 0ab014b147 108: onsuccess: #512: 2: Success after binutils/gcc: 48 commits discards 3ae90314f3 107: onsuccess: #511: 2: Success after binutils/gcc: 10 commits discards c18c78b3de 106: onsuccess: #510: 2: Success after binutils/gcc: 19 commits discards ad79854058 105: onsuccess: #509: 2: Success after binutils/gcc: 40 commits discards 5a39c87cba 104: onsuccess: #508: 2: Success after binutils/gcc: 43 commits discards 12798f737d 103: onsuccess: #507: 2: Success after binutils/gcc: 238 commits discards eee92d1e58 102: onsuccess: #506: 1: Success after gcc: 14 commits discards fcf6be22e2 101: force: #505: 1: Failure after basepoints/gcc-13-3918-gb [...] discards 9ca48dc1b7 100: force: #504: 2: Success after gcc: 4 commits discards e41c07dece 99: onsuccess: #501: 2: Success after binutils: 4 commits discards 61cfc7ed22 98: onsuccess: #499: 2: Success after binutils/gcc: 56 commits discards 987567c887 97: onsuccess: #498: 2: Success after binutils/gcc: 51 commits discards 367a6a3e4e 96: onsuccess: #497: 2: Success after binutils/gcc: 63 commits discards db4b490114 95: onsuccess: #496: 2: Success after binutils/gcc: 66 commits discards d471fe14f1 94: onsuccess: #495: 2: Success after binutils/gcc: 69 commits discards 70e8077c7d 93: onsuccess: #494: 2: Success after binutils/gcc: 14 commits discards 3deba67fe4 92: onsuccess: #493: 2: Success after binutils/gcc: 22 commits discards ff7c5d37b4 91: onsuccess: #492: 2: Success after binutils/gcc: 71 commits discards 35ae2a2c67 90: onsuccess: #491: 2: Success after binutils/gcc: 42 commits discards 189723a87c 89: onsuccess: #490: 2: Success after binutils/gcc: 34 commits discards e2791ee946 88: onsuccess: #489: 2: Success after binutils/gcc: 26 commits discards cb0e424766 87: onsuccess: #488: 2: Success after binutils/gcc: 38 commits discards 8121fe767e 86: onsuccess: #487: 2: Success after binutils/gcc: 3 commits discards c65c7fb712 85: onsuccess: #486: 2: Success after binutils/gcc: 29 commits discards ed111f0095 84: onsuccess: #485: 2: Success after binutils/gcc: 33 commits discards 3fbf1d870c 83: onsuccess: #484: 2: Success after binutils/gcc: 28 commits discards f1cd2851a3 82: onsuccess: #483: 2: Success after binutils/gcc: 32 commits discards 928af30c02 81: onsuccess: #482: 2: Success after binutils/gcc: 35 commits discards 7d251b5366 80: onsuccess: #481: 2: Success after binutils/gcc: 41 commits discards ed52a3dc95 79: onsuccess: #480: 2: Success after binutils/gcc: 7 commits discards a6d4b3e811 78: onsuccess: #479: 2: Success after binutils/gcc: 44 commits discards 8e840e157b 77: onsuccess: #478: 2: Success after binutils/gcc: 51 commits discards 2ed7da6257 76: onsuccess: #477: 2: Success after binutils/gcc: 44 commits discards 876eae1145 75: onsuccess: #476: 2: Success after binutils/gcc: 48 commits discards 4eac3e2309 74: onsuccess: #475: 2: Success after binutils/gcc: 40 commits discards a71d085956 73: onsuccess: #474: 2: Success after binutils/gcc: 9 commits discards 065326cb66 72: onsuccess: #473: 2: Success after binutils/gcc: 7 commits discards 762a6b1599 71: onsuccess: #472: 2: Success after binutils/gcc: 54 commits discards 1e01c2b771 70: onsuccess: #471: 2: Success after binutils/gcc: 27 commits discards 663ae7fbd3 69: onsuccess: #470: 2: Success after binutils/gcc: 42 commits discards c1e853192f 68: onsuccess: #469: 2: Success after binutils/gcc: 63 commits discards b5c98ab0c5 67: onsuccess: #468: 1: Success after binutils/gcc: 46 commits discards 70b1dfea56 66: onsuccess: #467: 1: Success after binutils/gcc: 5 commits discards 25564b84d5 65: onsuccess: #466: 1: Success after binutils/gcc: 7 commits discards b65697ac59 64: onsuccess: #465: 1: Success after baseline build: no new [...] discards 367c6b7bab 63: force: #464: 1: Failure after basepoints/gcc-13-3172-gf3 [...] new 11f54c426a 63: force: #464: 1: Failure after basepoints/gcc-13-3172-gf3 [...] new 76dde09892 64: onsuccess: #465: 1: Success after baseline build: no new [...] new 159bc12960 65: onsuccess: #466: 1: Success after binutils/gcc: 7 commits new 32d5f139d8 66: onsuccess: #467: 1: Success after binutils/gcc: 5 commits new 44abb25b84 67: onsuccess: #468: 1: Success after binutils/gcc: 46 commits new f299254426 68: onsuccess: #469: 2: Success after binutils/gcc: 63 commits new eae4c24455 69: onsuccess: #470: 2: Success after binutils/gcc: 42 commits new 628e8c75f9 70: onsuccess: #471: 2: Success after binutils/gcc: 27 commits new 722b476bc4 71: onsuccess: #472: 2: Success after binutils/gcc: 54 commits new d6d92d0aa9 72: onsuccess: #473: 2: Success after binutils/gcc: 7 commits new 40af056301 73: onsuccess: #474: 2: Success after binutils/gcc: 9 commits new 71d47aa350 74: onsuccess: #475: 2: Success after binutils/gcc: 40 commits new 327b1d0013 75: onsuccess: #476: 2: Success after binutils/gcc: 48 commits new d98ca89e16 76: onsuccess: #477: 2: Success after binutils/gcc: 44 commits new c32bf0b792 77: onsuccess: #478: 2: Success after binutils/gcc: 51 commits new 0ea582b7b4 78: onsuccess: #479: 2: Success after binutils/gcc: 44 commits new 4f61c95747 79: onsuccess: #480: 2: Success after binutils/gcc: 7 commits new 54ed925c12 80: onsuccess: #481: 2: Success after binutils/gcc: 41 commits new d8ead05712 81: onsuccess: #482: 2: Success after binutils/gcc: 35 commits new 62ceebe0da 82: onsuccess: #483: 2: Success after binutils/gcc: 32 commits new 23ce30079e 83: onsuccess: #484: 2: Success after binutils/gcc: 28 commits new 03b1d999be 84: onsuccess: #485: 2: Success after binutils/gcc: 33 commits new 4a6b3890ec 85: onsuccess: #486: 2: Success after binutils/gcc: 29 commits new 9037e31bda 86: onsuccess: #487: 2: Success after binutils/gcc: 3 commits new 502fa89923 87: onsuccess: #488: 2: Success after binutils/gcc: 38 commits new dc269275f8 88: onsuccess: #489: 2: Success after binutils/gcc: 26 commits new d64f499f44 89: onsuccess: #490: 2: Success after binutils/gcc: 34 commits new f9953e7e33 90: onsuccess: #491: 2: Success after binutils/gcc: 42 commits new 66ae59ee70 91: onsuccess: #492: 2: Success after binutils/gcc: 71 commits new 04abde7f82 92: onsuccess: #493: 2: Success after binutils/gcc: 22 commits new f35b7f7ce8 93: onsuccess: #494: 2: Success after binutils/gcc: 14 commits new 691df68a98 94: onsuccess: #495: 2: Success after binutils/gcc: 69 commits new c941e8e3dc 95: onsuccess: #496: 2: Success after binutils/gcc: 66 commits new f34139e2e7 96: onsuccess: #497: 2: Success after binutils/gcc: 63 commits new e604c6e804 97: onsuccess: #498: 2: Success after binutils/gcc: 51 commits new 537af74e3d 98: onsuccess: #499: 2: Success after binutils/gcc: 56 commits new 247c8c9423 99: onsuccess: #501: 2: Success after binutils: 4 commits new c48e53aed5 100: force: #504: 2: Success after gcc: 4 commits new 48449113ee 101: force: #505: 1: Failure after basepoints/gcc-13-3918-gb [...] new 8e697c41c2 102: onsuccess: #506: 1: Success after gcc: 14 commits new 613a89ca85 103: onsuccess: #507: 2: Success after binutils/gcc: 238 commits new 4801e2779d 104: onsuccess: #508: 2: Success after binutils/gcc: 43 commits new 3ca963ad01 105: onsuccess: #509: 2: Success after binutils/gcc: 40 commits new 916d172940 106: onsuccess: #510: 2: Success after binutils/gcc: 19 commits new 5c4ef4b5c1 107: onsuccess: #511: 2: Success after binutils/gcc: 10 commits new 58f61f59b9 108: onsuccess: #512: 2: Success after binutils/gcc: 48 commits new c1f2cc82b5 109: onsuccess: #513: 2: Success after binutils/gcc: 37 commits new dceedc1637 110: onsuccess: #514: 2: Success after binutils/gcc: 43 commits new 6367c968da 111: onsuccess: #515: 2: Success after binutils/gcc: 47 commits new adecb9e611 112: onsuccess: #516: 2: Success after binutils/gcc: 21 commits new 7b2e9e7af3 113: onsuccess: #518: 2: Success after binutils: 5 commits new 79f22056e4 114: onsuccess: #519: 2: Success after gcc: 2 commits new 2062892ca0 115: onsuccess: #520: 2: Success after binutils/gcc: 6 commits new 054d1b85fc 116: onsuccess: #521: 2: Success after binutils/gcc: 118 commits new e975ada04f 117: onsuccess: #522: 2: Success after binutils/gcc: 19 commits new 44a1bcc035 118: onsuccess: #523: 2: Success after binutils/gcc: 42 commits new 3f127da001 119: onsuccess: #524: 2: Success after binutils/gcc: 57 commits new 4e6076e0da 120: onsuccess: #525: 2: Success after binutils/gcc: 28 commits new d1a1f7e275 121: onsuccess: #526: 2: Success after binutils/gcc: 11 commits new 650c7be073 122: onsuccess: #527: 2: Success after binutils/gcc: 10 commits new 68664142d1 123: onsuccess: #528: 2: Success after binutils/gcc: 27 commits new 9c10451d4d 124: onsuccess: #529: 2: Success after binutils/gcc: 47 commits new c6cff4f6a7 125: onsuccess: #530: 2: Success after binutils/gcc: 33 commits new 0da2386658 126: onsuccess: #531: 2: Success after binutils/gcc: 31 commits new e37596ef8c 127: onsuccess: #532: 2: Success after binutils/gcc: 27 commits new a830951267 128: onsuccess: #533: 2: Success after binutils/gcc: 12 commits new e1629304a6 129: onsuccess: #534: 2: Success after binutils/gcc: 13 commits new 7c113bc1c2 130: onsuccess: #535: 2: Success after binutils/gcc: 45 commits new 1c291a6504 131: onsuccess: #538: 2: Success after gcc: 58 commits new 4600d7143c 132: force: #539: 2: Success after binutils: 5 commits new 3015ea2b9a 133: force: #540: 1: Failure after gdb-12-branchpoint-3046-g [...] new 9b2e8d63c2 134: onsuccess: #541: 1: Success after binutils: 9 commits new 2896c1c059 135: onsuccess: #542: 1: Success after binutils/gcc: 48 commits new cfa2c7612a 136: onsuccess: #543: 1: Success after binutils/gcc: 31 commits new c90fd5f1d4 137: onsuccess: #544: 2: Success after binutils/gcc: 38 commits new 488b2d7e96 138: onsuccess: #545: 2: Success after binutils/gcc: 18 commits new a3ee34ceea 139: onsuccess: #546: 2: Success after binutils/gcc: 9 commits new 3276013598 140: onsuccess: #547: 2: Success after binutils/gcc: 53 commits new 15b7b6f70f 141: onsuccess: #548: 2: Success after binutils/gcc: 15 commits new 28b12b9c8d 142: onsuccess: #549: 2: Success after binutils/gcc: 67 commits new 5a6f735b3f 143: onsuccess: #550: 2: Success after binutils/gcc: 41 commits new e44d58db86 144: onsuccess: #551: 2: Success after binutils/gcc: 90 commits new 5a077a707e 145: onsuccess: #552: 2: Success after binutils/gcc: 9 commits new 8e2b793618 146: onsuccess: #553: 2: Success after binutils/gcc: 25 commits new ea77dc5b39 147: onsuccess: #554: 2: Success after binutils/gcc: 7 commits new c7ab55fbcc 148: onsuccess: #555: 2: Success after binutils/gcc: 27 commits new 2a235916b9 149: onsuccess: #556: 2: Success after binutils/gcc: 11 commits new c503f171b5 150: onsuccess: #557: 2: Success after binutils/gcc: 20 commits new 38b20af429 151: onsuccess: #558: 2: Success after binutils/gcc: 11 commits new 5c45604747 152: onsuccess: #559: 2: Success after binutils/gcc: 17 commits new f22405477b 153: onsuccess: #560: 2: Success after binutils/gcc: 16 commits new f63e7283c4 154: onsuccess: #562: 2: Success after binutils: 12 commits new 8361f7c324 155: force: #564: 2: Success after gcc: 7 commits new 014a072573 156: force: #565: 1: Failure after basepoints/gcc-13-4953-g3 [...] new 27d7917ef4 157: onsuccess: #566: 1: Success after gcc: 3 commits new e768719fd9 158: onsuccess: #567: 2: Success after binutils/gcc: 59 commits new 10727b5199 159: onsuccess: #568: 2: Success after binutils/gcc: 36 commits new 715f1b2909 160: onsuccess: #569: 2: Success after binutils/gcc: 55 commits new 8c519ecd17 161: onsuccess: #570: 2: Success after binutils/gcc: 27 commits new 5b87519f1a 162: onsuccess: #571: 2: Success after binutils/gcc: 6 commits new 7f0c858845 163: onsuccess: #572: 2: Success after binutils/gcc: 3 commits new d8214bfa56 164: onsuccess: #573: 2: Success after binutils/gcc: 23 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 (01ac0db090) \ 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 1740 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 39352 -> 39792 bytes 05-build_abe-bootstrap_lto/console.log.xz | Bin 276032 -> 277772 bytes 06-check_regression/console.log.xz | Bin 2540 -> 3008 bytes 07-update_baseline/console.log | 36 +++++++++++++++--------------- 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, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[linux] branch master updated (1fe4fd6f5cad -> 5a41237ad1d4)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from 1fe4fd6f5cad Merge tag 'xfs-6.2-fixes-2' of git://git.kernel.org/pub/sc [...] new 5a41237ad1d4 gcc: disable -Warray-bounds for gcc-11 too 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: init/Kconfig | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (3a2cbf19e7 -> aa58c11ab5)

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 3a2cbf19e7 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] discards 10bfa98097 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits discards 4d2b882496 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits discards 4af8dfc495 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits discards b8e6b8a83c 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits discards bdb578789f 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] discards 077de1c6f3 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] discards 6ee33ff193 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] discards d41df29521 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards e425e949a7 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] discards d7f8284aeb 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] discards 2dc43ed3e8 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] discards b6247e3a64 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 1ede503e15 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits discards cb21322e7b 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] discards 19df97723d 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 651404fc46 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 93ef2f26bd 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] discards 7bd7ef9d5d 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits discards c5650d15b7 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards 335bd17ca8 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] discards 2cd36cdad5 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] discards 4c048b6884 321: force: #2055: 7: Success after gdb: 2 commits discards b7a0d61118 320: onsuccess: #2050: 7: Success after gcc: 4 commits discards 5a73e3f2d5 319: onsuccess: #2049: 7: Success after binutils: 4 commits discards 11362618b0 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] discards cdad80ccb3 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits discards f497102eaf 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 132f7ce870 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards ca1622c88c 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] discards 3c5bed9228 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits discards 1aa4a590eb 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits discards a3402838b2 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits discards 245a8f5e24 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits discards 5242ba8c58 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits discards 12f557e64c 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards f86c251694 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits discards 59a706925a 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] discards cdaef70f27 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] discards b7f731316b 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits discards 54d980fd43 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits discards 3f0cd79a86 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits discards 4c874d0490 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits discards 59c15d3465 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits discards b183156529 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits discards a953fa2124 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] discards 5e638fe01b 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] discards cb7f1131fe 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits discards 661b545b6c 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] discards bd090ff2db 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits discards 5ee65a0918 293: onsuccess: #2022: 7: Success after gcc: 2 commits discards 600a3fb5de 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] discards bafdceabf2 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits discards e78e99929c 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits discards 431c530ec0 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] discards 97bda02b22 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits discards 51b0f0e866 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits discards 1d474054c6 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] discards 531147dd06 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] discards d22090d53e 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] discards b8db79ae18 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards d25e623aa7 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards 604ea772e5 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards c0bff3a5a1 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards c849d5c027 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 2dc5625dd1 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 5d84585680 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 669cb58698 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards 814e36deb0 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards b4ee86490d 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards 944c6bfcb6 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards 781cb0d052 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 1e781aa1c0 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 8d5dcd4dd5 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards badf93d8dc 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards 0e2c8d880e 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 7aa085f993 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 1e736d066f 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards cb9c8acafa 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 8a651dceb5 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 12183e4465 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards d1017f3632 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards 87cf1db251 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards 09514d5a12 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 511de033a9 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards be042cd164 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards 26c9153068 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards f2009d0fc6 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards 1ce1420b50 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards bdaaea3fa2 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards b9e628cc00 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards 266e260f9d 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards e48f7969b1 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards c56305a0ca 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards 80faf5b270 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards 708e28ea4f 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards 04259dbfa5 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards 68736bc9c6 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards f9d57e23c8 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards eb1cca72ba 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards a9cae9d05d 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new 01ad9ea4a3 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new 4dbce7262f 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 9155f5c196 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new 152cd6721a 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new 3657877eac 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new f2b9b15f60 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 5cf5cf4828 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new 92de7c0631 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new 0716eb5679 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 3d50a185b5 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new 4ef2d2c997 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new c8f0359dd1 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new e33c91c4a3 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new c019bc3214 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new 8955a3591f 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 922fa205cd 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 7ed989e951 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new dde485b21b 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new c6108877a0 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new 460b99526d 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new f08ef2b0a9 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new a5ef77eaeb 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new 52ff819797 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 315754122f 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 24e06cf538 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new a80a256064 268: onsuccess: #1997: 7: Success after glibc: 2 commits new 0319bd40b7 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new a6337f2a44 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 05fbb2b3d2 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new cebd0871a7 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new df50199f98 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 73b62673ea 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 6bb96b1257 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 5893bd4c99 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 0d701ef4ca 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new 22f3da8814 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new fe53280215 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 0da35c4576 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 28b6fe7cc5 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 7ec181b29d 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new e9695c52ae 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 5743973ec9 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] new f349e2a78f 285: onsuccess: #2014: 7: Success after binutils/gcc/gdb: 74 [...] new 7fff9b90f3 286: onsuccess: #2015: 7: Success after binutils/gcc/linux/g [...] new c4811dfb08 287: onsuccess: #2016: 7: Success after binutils/gcc/gdb: 6 commits new 90e79b0602 288: onsuccess: #2017: 7: Success after binutils/gcc/gdb: 9 commits new 7824fc3de8 289: onsuccess: #2018: 7: Success after binutils/gcc/gdb: 17 [...] new 6a886afd6b 290: onsuccess: #2019: 7: Success after binutils/gdb: 20 commits new 4b9620edf2 291: onsuccess: #2020: 7: Success after binutils/gcc/gdb: 3 commits new 8466e1c469 292: onsuccess: #2021: 7: Success after binutils/linux/gdb: [...] new 732e99b5f3 293: onsuccess: #2022: 7: Success after gcc: 2 commits new 08928a7fcc 294: onsuccess: #2023: 7: Success after binutils/gdb: 4 commits new 0297372eaa 295: onsuccess: #2024: 7: Success after basepoints/gcc-13-48 [...] new cb655c4551 296: onsuccess: #2025: 7: Success after binutils/gcc/gdb: 5 commits new ad3d01edbc 297: onsuccess: #2026: 7: Success after binutils/gcc/gdb: 19 [...] new 93aba554a2 298: onsuccess: #2027: 7: Success after binutils/gcc/gdb: 18 [...] new 4a6078141d 299: onsuccess: #2028: 7: Success after binutils/gcc/gdb: 6 commits new b6197df1bd 300: onsuccess: #2029: 7: Success after binutils/gcc/gdb: 4 commits new ba086311af 301: onsuccess: #2030: 7: Success after binutils/gcc/gdb: 4 commits new 0d1911f98b 302: onsuccess: #2031: 7: Success after binutils/gcc/gdb: 3 commits new fa8e232dc9 303: onsuccess: #2032: 7: Success after binutils/gdb: 2 commits new eb1a1ae1a6 304: onsuccess: #2033: 7: Success after gcc/linux: 60 commits new 094aa6547e 305: onsuccess: #2034: 7: Success after binutils/gcc/linux/g [...] new 050147db40 306: onsuccess: #2035: 7: Success after basepoints/gcc-13-49 [...] new ce3c819073 307: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 7 commits new f672bfe793 308: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new f852ab03a0 309: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 3 commits new d71ded0f02 310: onsuccess: #2039: 7: Success after binutils/gdb: 6 commits new 612fc208d9 311: onsuccess: #2040: 7: Success after binutils/gdb: 20 commits new 42834abd96 312: onsuccess: #2041: 7: Success after gcc/linux: 13 commits new 1a151f7fbc 313: onsuccess: #2042: 7: Success after binutils/gcc/gdb: 4 commits new d421ac5404 314: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 15 [...] new 8dcb774749 315: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 8bd437ca17 316: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 1363f7987f 317: onsuccess: #2046: 7: Success after binutils/gdb: 6 commits new 21128cb11a 318: onsuccess: #2047: 7: Success after binutils/gcc/glibc/g [...] new 344e0fb638 319: onsuccess: #2049: 7: Success after binutils: 4 commits new 88c335d05e 320: onsuccess: #2050: 7: Success after gcc: 4 commits new 18505b7f5f 321: force: #2055: 7: Success after gdb: 2 commits new d212aa4ef6 322: force: #2056: 5: Failure after gdb-13-branchpoint-245-g [...] new b23517374d 323: onsuccess: #2057: 5: Success after gdb-13-branchpoint-2 [...] new 7d4e24cfdf 324: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 5263ba6840 325: onsuccess: #2059: 7: Success after binutils/gcc/gdb: 9 commits new f99b1047d1 326: onsuccess: #2060: 7: Success after binutils/gcc/gdb: 28 [...] new cc8a8465a3 327: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 248bec11cd 328: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 6d644bc8cb 329: onsuccess: #2063: 7: Success after binutils/gcc/gdb: 11 [...] new 5fe62dadf2 330: onsuccess: #2064: 7: Success after binutils/gcc/gdb: 8 commits new 926bd43229 331: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 24aecf0cf2 332: onsuccess: #2066: 7: Success after binutils/gcc/linux/g [...] new 7f8aad4e13 333: onsuccess: #2067: 7: Success after basepoints/gcc-13-50 [...] new 6d954536a3 334: onsuccess: #2068: 7: Success after binutils/gcc/gdb/qem [...] new a3fe67d70e 335: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new f7a21f650b 336: onsuccess: #2070: 7: Success after binutils/gcc/linux/g [...] new e4aa066444 337: onsuccess: #2071: 7: Success after basepoints/gcc-13-50 [...] new 3e391f1601 338: onsuccess: #2072: 7: Success after v7.2.0-493-g052e6534 [...] new 746c8d5cb9 339: onsuccess: #2073: 7: Success after gcc/linux/qemu: 38 commits new 9cbe2690b8 340: onsuccess: #2074: 7: Success after binutils/gcc/gdb: 5 commits new f104f6c382 341: onsuccess: #2075: 7: Success after linux/qemu: 44 commits new b84fba129a 342: onsuccess: #2076: 7: Success after binutils/gcc/gdb: 5 commits new 5b2d6c8373 343: onsuccess: #2077: 7: Success after binutils/gcc/gdb/qem [...] new aa58c11ab5 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 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 (3a2cbf19e7) \ 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 1772 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 31756 -> 32064 bytes 05-build_abe-stage1/console.log.xz | Bin 91956 -> 92456 bytes 07-build_abe-linux/console.log.xz | Bin 8840 -> 8896 bytes 08-build_abe-glibc/console.log.xz | Bin 236224 -> 237016 bytes 09-build_abe-stage2/console.log.xz | Bin 228140 -> 228100 bytes 10-build_abe-gdb/console.log.xz | Bin 39084 -> 39532 bytes 11-build_abe-qemu/console.log.xz | Bin 31160 -> 31332 bytes 12-check_regression/console.log.xz | Bin 4416 -> 3704 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++--------- 19 files changed, 56 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-allnoconfig updated (080c56846c -> 4e7f9b4630)

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/gnu-master-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from 080c56846c 35: onsuccess: #393: all: Success after binutils/gcc/linux/q [...] new 4e7f9b4630 36: onsuccess: #394: all: Success after binutils/gcc/linux/q [...] 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 1760 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 32644 -> 32228 bytes 04-build_abe-stage1/console.log.xz | Bin 91696 -> 91740 bytes 05-build_abe-qemu/console.log.xz | Bin 30912 -> 31604 bytes 06-build_linux/console.log.xz | Bin 4348 -> 4360 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4340 -> 4296 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (5ed8c8f84a -> 735ed65148)

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 5ed8c8f84a 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] discards 8f5762ce52 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] discards 212ebfa628 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits discards ba2f0b497d 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] discards 871b2ad895 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits discards 6a44a73866 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] discards 3b7507fe54 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] discards c1242a4b61 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] discards eb57f4aee9 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] discards ef862923ad 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] discards 446b82b996 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] discards 2cfeced858 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] discards c5d6cf1c6f 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits discards acd860c1b5 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] discards fbf79af517 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] discards 8c720b4c10 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] discards 45f524af95 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] discards ffb679607a 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] discards 036a194149 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] discards 47e7d4d732 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] discards 6c053a30f9 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] discards 73c814794d 311: onsuccess: #2130: 1: Success after gcc: 4 commits discards a6e83eb974 310: onsuccess: #2129: 1: Success after binutils: 4 commits discards 94029d8c2a 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] discards 3afcabf502 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] discards ee2cfcf353 307: onsuccess: #2124: 1: Success after gcc: 2 commits discards 75b0be8caf 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] discards 8e537b408a 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits discards 69c4c9f878 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits discards 095d57061c 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits discards 14feda12fd 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits discards ca62db852c 301: onsuccess: #2118: 1: Success after linux: 16 commits discards ecaf6bac24 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] discards e2d9d00b4c 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] discards c24d15a2a8 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits discards 06b426a18e 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits discards f51a3cd06e 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits discards 66b986221e 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] discards 2fb5fec800 294: onsuccess: #2110: 1: Success after gcc: 17 commits discards b06936d167 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits discards 7572a2f539 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits discards 0ea6b83516 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits discards 7a9f4b67b6 290: onsuccess: #2106: 1: Success after gcc: 2 commits discards c653549660 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits discards c41f7ee138 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] discards 28dd981da9 287: onsuccess: #2103: 1: Success after gcc: 9 commits discards d6345e138a 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits discards 7cd03278d9 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits discards 872aec64a0 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] discards 0a216c66e9 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits discards d68773a8bd 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] discards c524e2b940 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] discards 7002e3905b 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] discards dbfb71c569 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits discards 8a073f52ef 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] discards 3cc4849e4a 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] discards 91643b978d 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] discards 017d7f4098 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] discards c1c99aea39 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] discards a31b3b9174 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] discards 3ee1c088e6 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] discards 6932883502 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] discards d0d93375fa 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] discards c84d580c9c 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] discards 66412e399d 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] discards aee4b95b3d 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] discards 756b618f7f 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits discards 5df2426b64 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] discards 1dbe17322f 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits discards af08aa29eb 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits discards 85efb93ee5 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] discards 403f154324 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] discards f3db47d97c 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] discards 18325b2682 259: onsuccess: #2075: 1: Success after glibc: 2 commits discards f9b6af128b 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] discards a1fac288a3 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] discards e4ba875f5b 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits discards 1c92089965 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits discards 1a3419e330 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] discards 70840a5365 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards 04a91d34a5 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards ff9e6a2ada 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] discards 9be7e0f681 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] discards 57e3e21ae0 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] discards ade1df0bb8 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] discards 2c5efab7bd 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] discards ff2a62dcf8 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] discards 89ec3e5e4b 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] discards f83e88dbfa 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] discards eddbaa1917 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] discards 4d71d12552 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] discards 10b5a9ac26 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] discards c5302b9616 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] discards a1c5fae8b7 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] discards b1fb2f203d 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] discards c1a35c2744 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] discards e00e74c5e0 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] discards 695787351f 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] discards 3b997c3087 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] discards 73a93461fa 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] discards cd657d5b67 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 905877e942 232: onsuccess: #2048: 1: Success after glibc: 2 commits new f8285c2808 233: onsuccess: #2049: 1: Success after binutils/gcc/linux/g [...] new 9067c7955b 234: onsuccess: #2050: 1: Success after binutils/gcc/linux/g [...] new edac5765d8 235: onsuccess: #2051: 1: Success after binutils/linux/gdb: [...] new a7f715be50 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: 10 [...] new a38e19056b 237: onsuccess: #2053: 1: Success after binutils/gcc/linux/g [...] new 004eb159aa 238: onsuccess: #2054: 1: Success after binutils/gcc/linux/g [...] new 2a1479e0db 239: onsuccess: #2055: 1: Success after binutils/gcc/linux/g [...] new 0f034136d1 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: 22 [...] new de5a99844b 241: onsuccess: #2057: 1: Success after binutils/gcc/linux/g [...] new 099193d5ad 242: onsuccess: #2058: 1: Success after binutils/gcc/linux/g [...] new fd5357a35f 243: onsuccess: #2059: 1: Success after basepoints/gcc-13-47 [...] new 432552691c 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/qem [...] new 8aab6b6289 245: onsuccess: #2061: 1: Success after binutils/gcc/linux/g [...] new 465cc5919e 246: onsuccess: #2062: 1: Success after binutils/gcc/linux/g [...] new f8704c1f0d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux/g [...] new 3405a19338 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/qem [...] new ff3741e38f 249: onsuccess: #2065: 1: Success after binutils/gcc/linux/g [...] new 68d881ea64 250: onsuccess: #2066: 1: Success after binutils/gcc/linux/g [...] new 4c132d5f77 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: 13 [...] new 68c4d13002 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new cfdf888181 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 0fae75659a 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/qem [...] new 012becb5ca 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: 5 commits new 012265c79d 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: 5 commits new 6d1110d474 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4af3 [...] new 5425da1f0e 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc/g [...] new f2326bf861 259: onsuccess: #2075: 1: Success after glibc: 2 commits new a5220cee5e 260: onsuccess: #2076: 1: Success after binutils/gcc/glibc/g [...] new a0c349b424 261: onsuccess: #2077: 1: Success after binutils/gcc/linux/g [...] new 5f8c0f4128 262: onsuccess: #2078: 1: Success after binutils/gcc/linux/g [...] new e1cdf564fa 263: onsuccess: #2079: 1: Success after binutils/gcc/gdb: 7 commits new e5520413d1 264: onsuccess: #2080: 1: Success after binutils/gcc/gdb: 7 commits new 25f776dbcd 265: onsuccess: #2081: 1: Success after gcc/linux/glibc/qemu [...] new c06e61b0b0 266: onsuccess: #2082: 1: Success after binutils/gcc/gdb: 8 commits new d8f34ff0f0 267: onsuccess: #2083: 1: Success after binutils/gcc/gdb: 64 [...] new a6f9892134 268: onsuccess: #2084: 1: Success after binutils/gcc/gdb/qem [...] new eaf3da2d32 269: onsuccess: #2085: 1: Success after binutils/gcc/linux/g [...] new dc1b764ee1 270: onsuccess: #2086: 1: Success after binutils/gcc/glibc/g [...] new 4101ea38f9 271: onsuccess: #2087: 1: Success after binutils/gcc/linux/g [...] new b45709bc58 272: onsuccess: #2088: 1: Success after binutils/gcc/gdb: 28 [...] new 3cda9abcc5 273: onsuccess: #2089: 1: Success after binutils/gcc/glibc/g [...] new f94f9a1ab2 274: onsuccess: #2090: 1: Success after binutils/gcc/linux/g [...] new 54f143fffb 275: onsuccess: #2091: 1: Success after binutils/gcc/gdb: 42 [...] new e6b6937a0b 276: onsuccess: #2092: 1: Success after binutils/gcc/gdb: 69 [...] new 7a68f66647 277: onsuccess: #2093: 1: Success after binutils/gcc/linux/g [...] new d059746c2b 278: onsuccess: #2094: 1: Success after binutils/gcc/linux/g [...] new d07a0343a6 279: onsuccess: #2095: 1: Success after binutils/gcc/gdb: 5 commits new 58897fa6d9 280: onsuccess: #2096: 1: Success after binutils/gcc/gdb: 21 [...] new 80b5215ded 281: onsuccess: #2097: 1: Success after binutils/gcc/gdb: 23 [...] new 37a57e938c 282: onsuccess: #2098: 1: Success after binutils/gcc/linux/g [...] new 5d5a2ea797 283: onsuccess: #2099: 1: Success after binutils/gdb: 4 commits new 87a096c4a4 284: onsuccess: #2100: 1: Success after basepoints/gcc-13-48 [...] new 84cb40823e 285: onsuccess: #2101: 1: Success after binutils/gcc/gdb: 5 commits new 93ff829810 286: onsuccess: #2102: 1: Success after binutils/gdb: 18 commits new 83385cfd51 287: onsuccess: #2103: 1: Success after gcc: 9 commits new fdf7b2c944 288: onsuccess: #2104: 1: Success after binutils/gcc/gdb: 10 [...] new f9957f9dbd 289: onsuccess: #2105: 1: Success after binutils/gcc/gdb: 6 commits new 853cc30d7d 290: onsuccess: #2106: 1: Success after gcc: 2 commits new 6687cc8d75 291: onsuccess: #2107: 1: Success after binutils/gcc/gdb: 6 commits new 7eac67c17e 292: onsuccess: #2108: 1: Success after binutils/gcc/gdb: 3 commits new bc9a7cd934 293: onsuccess: #2109: 1: Success after binutils/gdb: 2 commits new ea7f0f780c 294: onsuccess: #2110: 1: Success after gcc: 17 commits new 4c5f5f93ec 295: onsuccess: #2111: 1: Success after binutils/gcc/linux/g [...] new 12c4d31657 296: onsuccess: #2112: 1: Success after gcc/linux: 26 commits new e0e776ebc9 297: onsuccess: #2113: 1: Success after binutils/gcc/gdb: 7 commits new e4868502cd 298: onsuccess: #2114: 1: Success after binutils/gcc/gdb: 6 commits new 702d49a0a0 299: onsuccess: #2116: 1: Success after gdb-13-branchpoint-2 [...] new 48f13a2495 300: onsuccess: #2117: 1: Success after basepoints/gcc-13-49 [...] new ad32bd0011 301: onsuccess: #2118: 1: Success after linux: 16 commits new 0d145e2035 302: onsuccess: #2119: 1: Success after binutils/gdb: 7 commits new 4a47c53363 303: onsuccess: #2120: 1: Success after binutils/gdb: 20 commits new fab9ffa6a0 304: onsuccess: #2121: 1: Success after gcc/linux: 13 commits new 1f0a1ca065 305: onsuccess: #2122: 1: Success after binutils/gcc/gdb: 4 commits new a5b96de83a 306: onsuccess: #2123: 1: Success after binutils/gcc/gdb: 15 [...] new c5a41b8c4c 307: onsuccess: #2124: 1: Success after gcc: 2 commits new f41011dd23 308: onsuccess: #2126: 1: Success after binutils/gcc/linux/g [...] new 1c0d678b53 309: onsuccess: #2127: 1: Success after binutils/gcc/glibc/g [...] new d5c7129ffc 310: onsuccess: #2129: 1: Success after binutils: 4 commits new 3831295f99 311: onsuccess: #2130: 1: Success after gcc: 4 commits new abab2a34e4 312: onsuccess: #2132: 1: Success after glibc-2.36.9000-416- [...] new 6ea18c4e11 313: onsuccess: #2133: 1: Success after binutils/gcc/linux/g [...] new 66e6ed057f 314: onsuccess: #2134: 1: Success after binutils/gcc/glibc/g [...] new 43709a6d43 315: onsuccess: #2135: 1: Success after binutils/gcc/gdb: 11 [...] new bdf66e48aa 316: onsuccess: #2136: 1: Success after binutils/gcc/gdb: 26 [...] new 8d73cb6c10 317: onsuccess: #2137: 1: Success after binutils/gcc/linux/g [...] new bdd8e82eff 318: onsuccess: #2138: 1: Success after binutils/gcc/linux/g [...] new f1226b1e0b 319: onsuccess: #2139: 1: Success after binutils/gcc/gdb: 11 [...] new e98433c259 320: onsuccess: #2140: 1: Success after binutils/gcc/gdb: 6 commits new e02cf5b6a5 321: onsuccess: #2141: 1: Success after binutils/gcc/linux/g [...] new db35fee8f6 322: onsuccess: #2142: 1: Success after binutils/gcc/linux/g [...] new 05a8cf86bd 323: onsuccess: #2143: 1: Success after basepoints/gcc-13-50 [...] new db39088e15 324: onsuccess: #2144: 1: Success after binutils/gcc/gdb/qem [...] new 3f346df29e 325: onsuccess: #2145: 1: Success after binutils/gcc/glibc/g [...] new f934e6e439 326: onsuccess: #2146: 1: Success after binutils/gcc/linux/g [...] new 55b134b20a 327: onsuccess: #2147: 1: Success after basepoints/gcc-13-50 [...] new 0fcf68bce0 328: onsuccess: #2148: 1: Success after gcc/linux/qemu: 78 commits new ed504dd967 329: onsuccess: #2149: 1: Success after binutils/gcc/gdb/qem [...] new 67f5f69fed 330: onsuccess: #2150: 1: Success after linux/qemu: 36 commits new 007db34804 331: onsuccess: #2151: 1: Success after binutils/gcc/linux/g [...] new 06acba9d12 332: onsuccess: #2152: 1: Success after binutils/gcc/gdb/qem [...] new 735ed65148 333: onsuccess: #2153: 1: Success after binutils/gcc/gdb/qem [...] 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 (5ed8c8f84a) \ 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 1768 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 32124 -> 31912 bytes 04-build_abe-stage1/console.log.xz | Bin 92512 -> 91488 bytes 06-build_abe-linux/console.log.xz | Bin 8892 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 236600 -> 235652 bytes 08-build_abe-stage2/console.log.xz | Bin 229240 -> 228624 bytes 09-build_abe-gdb/console.log.xz | Bin 39500 -> 39484 bytes 10-build_abe-qemu/console.log.xz | Bin 31312 -> 31196 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3916 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3316 -> 2492 bytes 13-check_regression/console.log.xz | Bin 7084 -> 6192 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 15 - 13-check_regression/mail-body.txt | 42 +- 13-check_regression/results.compare | 34 +- 13-check_regression/results.compare2 | 53 +- 13-check_regression/results.regressions | 35 - 14-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 44 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 35 - sumfiles/g++.log.xz | Bin 2690160 -> 2690552 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2237352 -> 2245440 bytes sumfiles/gcc.sum | 2322 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 894608 -> 900076 bytes sumfiles/gfortran.sum | 8 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2256 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214112 -> 214076 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 435940 -> 444200 bytes sumfiles/libstdc++.sum | 10 +- 43 files changed, 1306 insertions(+), 1417 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/release-arm-bootstrap updated (4fceb79466 -> 9b281a1d64)

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/release-arm-bootstrap in repository toolchain/ci/base-artifacts. from 4fceb79466 45: onsuccess: #152: 2: Success after binutils/gcc: 9 commits new 9b281a1d64 46: onsuccess: #153: 2: Success after gcc: 4 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 1716 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 04-build_abe-binutils/console.log.xz | Bin 51224 -> 51268 bytes 05-build_abe-bootstrap/console.log.xz | Bin 463312 -> 464556 bytes 06-check_regression/console.log.xz | Bin 2784 -> 2536 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 ++++++++-------- 11 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page: