Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[toolchain/ci/interesting-commits] branch master updated (3547473 -> 099c2c0)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 3547473 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] new 099c2c0 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../tcwg_kernel/llvm-master-aarch64-lts-allyesconfig}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy {linux/sha1/3dd33a09f5dc12ccb0902923c4c784eb0f8c7554/tcwg_kernel/llvm-master- [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] copy llvm/sha1/e07ead85a368173a56e96a21d6841aa497ad80f8/tcwg_kernel/{llvm-master-a [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (ce911684d0 -> 7756d0d351)

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-allyesconfig in repository toolchain/ci/base-artifacts. from ce911684d0 18: onsuccess: #493: all: Success after v7.1.0-446-g99d6b11b [...] new 7756d0d351 19: force: #494: all: Success after llvm: 81 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 1704 -> 1872 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30596 -> 30572 bytes 04-build_kernel_llvm/console.log.xz | Bin 63736 -> 63604 bytes 05-build_abe-qemu/console.log.xz | Bin 32280 -> 32240 bytes 06-build_linux/console.log.xz | Bin 3480 -> 3408 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 2736 -> 2972 bytes 09-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++++------- 15 files changed, 13 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan updated (0296883dc8 -> 9b5d662a6b)

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_ubsan in repository toolchain/ci/base-artifacts. from 0296883dc8 47: force: #473: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 9b5d662a6b 48: onsuccess: #474: 1: Success after gcc: 10 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 1664 -> 1720 bytes 02-prepare_abe/console.log.xz | Bin 2712 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38236 -> 38004 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 83652 -> 80016 bytes 06-check_regression/console.log.xz | Bin 3424 -> 2668 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 20 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 - 06-check_regression/trigger-bisect | 2 - 06-check_regression/trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1061 --------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 11 - 23 files changed, 33 insertions(+), 1127 deletions(-) delete mode 100644 06-check_regression/results.regressions delete mode 100644 06-check_regression/trigger-bisect delete mode 100644 06-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan updated (11aec122d1 -> 0296883dc8)

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_ubsan in repository toolchain/ci/base-artifacts. from 11aec122d1 46: force: #472: 2: Success after gcc: 18 commits new 0296883dc8 47: force: #473: 1: Failure after basepoints/gcc-13-2887-gb0 [...] 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 1696 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2708 -> 2712 bytes 04-build_abe-binutils/console.log.xz | Bin 37876 -> 38236 bytes 05-build_abe-bootstrap_ubsan/console.log.xz | Bin 323772 -> 83652 bytes 06-check_regression/console.log.xz | Bin 2696 -> 3424 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 15 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 11 + 06-check_regression/trigger-bisect | 2 + .../trigger-notify | 0 dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 1061 ++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 15 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 13 +- 23 files changed, 1133 insertions(+), 17 deletions(-) create mode 100644 06-check_regression/results.regressions create mode 100644 06-check_regression/trigger-bisect copy 07-update_baseline/console.log => 06-check_regression/trigger-notify (100%) create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/interesting-commits] branch master updated (f7d76eb -> 3547473)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from f7d76eb Add entry 1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4 from https [...] new 3547473 Add entry b04208895fed34171eac6bafb60c90048eb1cb0c from https [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: .../tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan}/build_url | 2 +- .../last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/{953e08fde44a596e4ec2491efd15cd645e1ddc48/tcwg_gcc_bootstrap/master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/b04208895fed34171eac6bafb60c90048eb1cb0c/tcwg_gcc_bootstrap/{master- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_ubsan updated (6d87c7f3fb -> 11aec122d1)

by git＠git.linaro.org

2 years, 1 month

[linux] branch master updated (511cce163b75 -> 987a926c1d8a)

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 511cce163b75 Merge tag 'net-6.0-rc8' of git://git.kernel.org/pub/scm/li [...] new 06bbaa6dc53c [coredump] don't use __kernel_write() on kmap_local_page() new 987a926c1d8a Merge tag 'pull-fixes' of git://git.kernel.org/pub/scm/lin [...] 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: fs/coredump.c | 38 +++++++++++++++++++++++++++++++++----- fs/internal.h | 3 +++ fs/read_write.c | 22 ++++++++++++++-------- 3 files changed, 50 insertions(+), 13 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (b92a9cf484 -> ce911684d0)

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-allyesconfig in repository toolchain/ci/base-artifacts. from b92a9cf484 17: onsuccess: #491: all: Success after binutils: 25 commits new ce911684d0 18: onsuccess: #493: all: Success after v7.1.0-446-g99d6b11b [...] 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 1688 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30816 -> 30596 bytes 04-build_kernel_llvm/console.log.xz | Bin 64492 -> 63736 bytes 05-build_abe-qemu/console.log.xz | Bin 32412 -> 32280 bytes 06-build_linux/console.log.xz | Bin 3508 -> 3480 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 2944 -> 2736 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 15 files changed, 19 insertions(+), 19 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap updated (64e7c03f4f -> 293e98471d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts. discards 64e7c03f4f 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards d2cf533bf0 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 19920e5e83 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards c6fe5bf211 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 76a12cf61f 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 0fb0bd77aa 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 581e7db873 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards 721d604608 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 60f06b0e8f 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards fd27b92b87 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 69514fbb35 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards 4c9fee34bc 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 27ef24b409 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards d72d7d6d73 135: force: #1540: 2: Success after gcc: 23 commits discards 4cd4749282 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards c16e14d130 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards f152b7e177 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 11a92e862f 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 3aad789d35 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 99ae287961 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards e3fe061241 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards da72188abc 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 9e061b5fdc 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards b7f16101cb 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 67b1263c98 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards cc3b917bee 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 628ad2dc0f 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 266f5730d3 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 509844f7d5 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 923930256f 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards e377e4505f 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards f5e537233c 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards be54025112 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 516bb41e9e 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 1431de9653 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 8001b877aa 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 770b8004f4 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 036de6b21c 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 1feec6cc60 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards d610e6b756 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards b7b366676c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 0f02b63226 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards ef738518b3 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards f803008d00 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 8fc3f919e5 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards d693278f35 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 46be75444a 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 8d3590d455 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards e540ebd464 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 3725939b70 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 417d96c326 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 363c79ba6f 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards ab3b4a4af3 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 97510d0b5e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 4c85128825 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards fd1a70c574 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 8fd0db3cb1 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards db3e0f1e5c 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards a24d0a1062 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 85755f43f8 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards c420da9580 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 433d3af547 87: onsuccess: 2: Success after gcc: 4 commits discards 76af0d4363 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards b58f63bc83 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 620f153dd9 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 441ecef156 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards f0dc54c48c 82: onsuccess: 1: Successful build after gcc: 3 commits discards 94e2a9ae7b 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 0359fe4aa4 80: force: 2: Successful build after gcc: 14 commits discards 29d7aa6fb4 79: onsuccess: 2: Successful build after binutils: 5 commits discards df45b1c8c4 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 4b78d11405 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 0d46ee85ba 76: onsuccess: 2: Successful build after gcc: 12 commits discards 1d1b97d154 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 080ef6ccd9 74: onsuccess: 2: Successful build after baseline build: no [...] discards 4d088b896c 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 2c815a9bb2 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3070e5995b 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards fa8ac7ada4 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 43f689cbb6 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 26e65e6c39 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards d0d3588055 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 79051ea2c4 66: onsuccess: 2: Successful build after gcc: 9 commits discards 789cff9f8c 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6b37074070 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards ceacb474c5 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 302885dc2a 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards afe17c71d5 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 4d72104474 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 663b15b41f 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 33a8054944 58: force: 2: Successful build after gcc: 6 commits discards 89129adaa4 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards b5d24dd73c 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 67a2226ad5 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 66190f17cc 54: onsuccess: 2: Successful build after gcc: 5 commits discards 325b3cb03e 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 35f8c12785 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 62196d3a16 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 94d6639ecc 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 6330e6a77a 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards c9d77cd951 48: onsuccess: 2: Successful build after gcc: 4 commits new be4c443d72 48: onsuccess: 2: Successful build after gcc: 4 commits new 06e640cede 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new a1b8a9d1a7 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 01ae057eef 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 8efb1d3f14 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b174897b5c 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new f3a7758e76 54: onsuccess: 2: Successful build after gcc: 5 commits new 2f00a6eadd 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4587ee29fe 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a846513350 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 42f0b27ec1 58: force: 2: Successful build after gcc: 6 commits new 5e46cf17af 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new e5c29006ff 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 1a47b1b90d 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 8083ad3b0c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 6440f3cf69 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8f2fa9fc0a 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 219f361c39 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new ec51019957 66: onsuccess: 2: Successful build after gcc: 9 commits new a75a07965f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c85a4260bc 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 361c651ef1 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 9782f6f8dc 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new d0958dceaa 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new c89094b390 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new ef39141967 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 18314016da 74: onsuccess: 2: Successful build after baseline build: no [...] new 7be4bc7fd8 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 0a52c8410a 76: onsuccess: 2: Successful build after gcc: 12 commits new 9a2c6c0768 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 1d4a67b6a9 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 2a67580d4b 79: onsuccess: 2: Successful build after binutils: 5 commits new d65f4b4dce 80: force: 2: Successful build after gcc: 14 commits new 966ca251f4 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 6c3f99d77d 82: onsuccess: 1: Successful build after gcc: 3 commits new 6fe15ef61d 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 0ecc71c823 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 6540a9870d 85: onsuccess: 2: Success after binutils/gcc: 25 commits new c427e26576 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 3da6d7ecc6 87: onsuccess: 2: Success after gcc: 4 commits new 3832982bfd 88: onsuccess: 2: Success after binutils/gcc: 25 commits new a6e33be5aa 89: onsuccess: 2: Success after binutils/gcc: 4 commits new a69de884ee 90: onsuccess: 2: Success after binutils/gcc: 16 commits new bfefa79438 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 96f781fc32 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 83aacfa4d7 93: onsuccess: 2: Success after binutils/gcc: 3 commits new d7dd38af4f 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 4ca9447e03 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 17d6eee51f 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 32b4ec2429 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 00b3f9c70b 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new f675a156cc 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 72c45e8a09 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 198a6ff8cc 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 85ccaf4b2e 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new b375bbf148 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 27b81732a4 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new a5ab771bd0 105: onsuccess: #1506: 2: Success after gcc: 2 commits new f6a1d43feb 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 4697b1cab9 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new dcb62bf474 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 83d6c3b508 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new e0e80e47f9 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new cfb3045d1d 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 9dde6ef66d 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 2bc9a1434c 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 90de2f7c33 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new f42f28236a 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 9cd3f9a662 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new a756d38d2c 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 5b835f2126 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 07ab09a399 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 84b184ab79 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 067cb3bc07 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new f772b85b2b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new f36d6128e6 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 7d22b99d9c 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new adc4289f7f 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 6ec40a9ff0 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 6981e5dc9b 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 3bd37aba78 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 6ef3bc430d 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new d4c6e071cf 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 59959927e0 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 897026ac45 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new f7ab998b34 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 9cbeaece1a 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 6af13c1458 135: force: #1540: 2: Success after gcc: 23 commits new 2217821d77 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new acdd4245ae 137: onsuccess: #1542: 1: Success after gcc: 4 commits new f54c7bc532 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new bbcf959879 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 426d425817 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 26801a9346 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 126e8e0c02 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 02a1d44aaf 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 4bce1da6e5 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 0bf3a905e1 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 2ab4f043da 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new b8dc0faf20 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 34700b9623 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new 293e98471d 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 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 (64e7c03f4f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1840 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2704 bytes 04-build_abe-binutils/console.log.xz | Bin 50788 -> 50528 bytes 05-build_abe-bootstrap/console.log.xz | Bin 466164 -> 463384 bytes 06-check_regression/console.log.xz | Bin 2848 -> 2960 bytes 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 | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 18 ++++++++-------- 14 files changed, 36 insertions(+), 36 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (b3a3eda6d3 -> 7996c53f8c)

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 b3a3eda6d3 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards cd1476d2ff 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 48281eb9fc 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards ef3940e156 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 6c7b32e490 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 604ea28b7d 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 1247ce43f5 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 82e0cf73e0 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 98585fa269 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 274efb7543 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 2027e73ee8 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 4547d0653d 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 4c0a87fef4 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a197939054 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 4ef8f496eb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 79634f672f 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 47f5b4b18a 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 73d756dc16 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 351fbd6001 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 600564e810 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards a56e504664 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards a60d90b19a 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 41e460cbfb 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 9abae44c4e 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards e6e1039018 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 3d6e6fd3e1 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 8c362f4a71 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 478311b062 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 6bfa4391a1 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 12a8623527 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 74cda48d2c 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards a10cbad86f 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards 3c628c7570 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 76bbe6403c 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 91d5299be2 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 24178bf72c 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards e3d833e7ac 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards ddb8cc6711 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards fbe9ae9613 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7a85376ae6 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards d3a210355a 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 8b5b1bfdf8 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards f3d583b9e0 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 30a6d55f2c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards b779edb46e 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards a1d28eb9f7 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 265f9593f9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards c8cec07c41 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards 9cb4f6456e 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 50f5454927 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards c371120b3b 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards c7382f5076 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 6a645fd8af 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards fe4a1797fc 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 67eca9c795 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards e2d0c4c5b1 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 740efe8f33 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 349e2f6b7e 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 0d0de87a90 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 25350e8523 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 413adb07e2 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 551455183a 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards cba390dde4 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 568f9af514 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards a5b9795816 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards c75900cec8 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards d2d515a769 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ffa685b59c 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 23163b8a6e 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c7574b31e6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards b729e6ff33 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 564dd1b825 74: onsuccess: 1: Successful build after linux: 44 commits discards c872ba969c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 480ee871f6 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9e0c672c91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 652bc1f8f0 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 45a8afc39f 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards b498021980 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 7a0f5e6848 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8653184f9d 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 5b980fcdc4 65: onsuccess: 1: Successful build after gcc: 4 commits discards 4c7fca1d0f 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ea8e97acf3 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 550f38123f 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 46a063874e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 9c69f3243d 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 8145fb89ef 59: onsuccess: 1: Successful build after glibc: 2 commits discards 157e52e7e5 58: onsuccess: 1: Successful build after binutils: 2 commits discards 3371a33d13 57: onsuccess: 1: Successful build after gcc: 7 commits discards 10e868562e 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c9d7f03c01 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 42e9663b57 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 59cf0a1927 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 1d58eee885 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards 113e03b9bf 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 4823d07ac3 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 10901925c3 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards ce30b6eb82 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards f9144999a3 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 5610f5c660 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards 91792a0685 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0b02bb6282 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cd7c0358bb 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new dde93d3159 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 362c3425d0 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new a3cde4271c 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 063fb4f889 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9599ed7bec 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 01e61b996c 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 13a2a06b7b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new 839cb53b5d 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new c00abce9ce 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 68d266ba97 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 8f04b89c3e 57: onsuccess: 1: Successful build after gcc: 7 commits new 902919300f 58: onsuccess: 1: Successful build after binutils: 2 commits new b80a79b835 59: onsuccess: 1: Successful build after glibc: 2 commits new 3fc39d8472 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 8c9722a4ad 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 1eae0ffe7c 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 55283022a5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 129adc366a 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3650eddc40 65: onsuccess: 1: Successful build after gcc: 4 commits new ddc33ed6a8 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 428c30c822 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d3cc8d7dcc 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6f93a8d30c 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 8cfac98ff2 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 142516c4d7 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new eef49b0ea7 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new e2a4a23607 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 157b000514 74: onsuccess: 1: Successful build after linux: 44 commits new aea051dd27 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new ae15d47665 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new cbfd730abe 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 9ce174d9f2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 95b18aacee 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new c6298a144f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new 8e8c1d71d4 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 271d055af0 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new fc19e06693 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new fe2d0d83b6 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 036d4d5364 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 3a79cedd21 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new 8a65161d44 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new d655b06a79 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ebf56773e8 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new ab30ed6397 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 0dc4d64e6b 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 808990ea28 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new a2fd076206 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 78f7bf282f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new cc510d185a 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new e2b38ff740 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new ec659cdee8 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new bb282dce99 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 226cec3118 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 23f1aef86f 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new d628d5127a 101: onsuccess: #1693: 1: Success after glibc: 14 commits new f992c6572c 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new db22686902 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 264aa95cd9 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 19bdf680a5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 907732a504 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new ca7fcbdea8 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 8760599bd1 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 30a36b8540 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new fe47d65218 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 8212db00b8 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 7222ddfb0d 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new adeeff7331 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 045e7b7fb8 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f9f31138c8 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 76522a1c0b 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 9e98615099 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 53627e4b34 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 2c5fd9bb5d 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ccfb5700ce 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 80a5db4817 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new 6a3740697b 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new a701706b56 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new d6065a8ff5 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 909245781e 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new c0219e1f1b 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 7c397071aa 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new c2376a2aa0 128: onsuccess: #1723: 1: Success after linux: 12 commits new c64610416e 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 15da311af1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 46e94c8beb 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 6644b68643 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 1f78420c3b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new de1d046ec3 134: onsuccess: #1730: 1: Success after binutils: 2 commits new e7d8b7fd80 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 16009aeeec 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6dc03c21d0 137: onsuccess: #1736: 1: Success after gcc: 5 commits new fede1f1a11 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new b93b64adc8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new a60cdeb593 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 6587909b08 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 6ccdc449c1 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new cbad4cfdf3 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 5e6ce1894f 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 739c705dbb 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 7996c53f8c 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b3a3eda6d3) \ 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 1696 -> 1680 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29976 -> 30516 bytes 04-build_abe-stage1/console.log.xz | Bin 90404 -> 90712 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 9304 bytes 07-build_abe-glibc/console.log.xz | Bin 233500 -> 233952 bytes 08-build_abe-stage2/console.log.xz | Bin 223708 -> 223188 bytes 09-build_abe-gdb/console.log.xz | Bin 37104 -> 37624 bytes 10-build_abe-qemu/console.log.xz | Bin 31188 -> 31424 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2784 -> 2732 bytes 13-check_regression/console.log.xz | Bin 6116 -> 7968 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 14 +- 13-check_regression/mail-body.txt | 65 +- 13-check_regression/results.compare | 38 +- 13-check_regression/results.compare2 | 204 ++- 13-check_regression/results.regressions | 38 +- 14-update_baseline/console.log | 60 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 67 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 38 +- sumfiles/g++.log.xz | Bin 2662716 -> 2686552 bytes sumfiles/g++.sum | 123 +- sumfiles/gcc.log.xz | Bin 2225572 -> 2197536 bytes sumfiles/gcc.sum | 2142 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 883416 -> 892680 bytes sumfiles/gfortran.sum | 7 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201160 -> 201096 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 421504 -> 432276 bytes sumfiles/libstdc++.sum | 8 +- 44 files changed, 1633 insertions(+), 1237 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits September 2022