Tcwg-commits October 2022

tcwg-commits@lists.linaro.org

6 participants
4723 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allyesconfig updated (b39a9e0e32 -> 0de52c4df5)

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-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from b39a9e0e32 27: onsuccess: #495: 36: Success after llvm: 46 commits new 0de52c4df5 28: onsuccess: #496: 20661: Success after binutils/llvm/linu [...] 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 1700 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 29896 -> 29840 bytes 04-build_kernel_llvm/console.log.xz | Bin 62756 -> 64744 bytes 05-build_abe-qemu/console.log.xz | Bin 31264 -> 31716 bytes 06-build_linux/console.log.xz | Bin 3760 -> 5052 bytes 08-check_regression/console.log.xz | Bin 2964 -> 4496 bytes 08-check_regression/mail-body.txt | 9 +-------- 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 11 ++--------- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++++-------------- results | 2 +- 19 files changed, 37 insertions(+), 39 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-release-aarch64-lts-allyesconfig updated (547ca9bfc7 -> d1fea7471e)

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-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 547ca9bfc7 12: onsuccess: #233: all: Success after binutils/llvm/linux/ [...] new d1fea7471e 13: onsuccess: #234: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1696 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 30144 -> 30056 bytes 04-build_kernel_llvm/console.log.xz | Bin 63532 -> 63796 bytes 05-build_abe-qemu/console.log.xz | Bin 31456 -> 32116 bytes 06-build_linux/console.log.xz | Bin 3408 -> 3444 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3936 -> 4256 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 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.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/release-aarch64 updated (3e32d5d6ac -> ea12142755)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from 3e32d5d6ac 13: onsuccess: #145: 1: Success after binutils/gcc/linux/gli [...] new ea12142755 14: onsuccess: #146: 1: Success after binutils/gcc/linux/gli [...] 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 1748 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30232 -> 30212 bytes 04-build_abe-stage1/console.log.xz | Bin 68416 -> 68260 bytes 06-build_abe-linux/console.log.xz | Bin 8712 -> 8664 bytes 07-build_abe-glibc/console.log.xz | Bin 236976 -> 236228 bytes 08-build_abe-stage2/console.log.xz | Bin 197976 -> 198652 bytes 09-build_abe-gdb/console.log.xz | Bin 36768 -> 36724 bytes 10-build_abe-qemu/console.log.xz | Bin 31252 -> 32392 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3928 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2448 -> 2456 bytes 13-check_regression/console.log.xz | Bin 10764 -> 10432 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 65 - 13-check_regression/mail-body.txt | 111 +- 13-check_regression/results.compare | 71 +- 13-check_regression/results.compare2 | 440 +-- 13-check_regression/results.regressions | 101 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 113 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +- results | 101 - sumfiles/g++.log.xz | Bin 3362232 -> 3352116 bytes sumfiles/g++.sum | 108 +- sumfiles/gcc.log.xz | Bin 2943508 -> 2945008 bytes sumfiles/gcc.sum | 5780 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1022168 -> 1023944 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2292 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 196856 -> 196712 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2656 -> 2656 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 414848 -> 404848 bytes sumfiles/libstdc++.sum | 18 +- 44 files changed, 3348 insertions(+), 3673 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.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allnoconfig updated (144ae12bc6 -> 9090a20a24)

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-lts-allnoconfig in repository toolchain/ci/base-artifacts. from 144ae12bc6 12: onsuccess: #258: boot: Success after binutils/llvm/linux [...] new 9090a20a24 13: onsuccess: #259: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1948 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30632 -> 30216 bytes 04-build_kernel_llvm/console.log.xz | Bin 64848 -> 63496 bytes 05-build_abe-qemu/console.log.xz | Bin 31640 -> 32072 bytes 06-build_linux/console.log.xz | Bin 3344 -> 3332 bytes 08-check_regression/console.log.xz | Bin 3980 -> 4260 bytes 09-update_baseline/console.log | 8 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 28 insertions(+), 28 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_check_bootstrap/master-arm-check_bootstrap_lto updated (7ece2b7732 -> a3630d279f)

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_check_bootstrap/master-arm-check_bootstrap_lto in repository toolchain/ci/base-artifacts. from 7ece2b7732 51: onsuccess: #477: 1: Success after binutils/gcc: 48 commits new a3630d279f 52: onsuccess: #478: 1: Success after binutils/gcc: 9 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 1740 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 50828 -> 51876 bytes 04-build_abe-bootstrap_lto/console.log.xz | Bin 476244 -> 473684 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3808 bytes 06-build_abe-check_bootstrap_lto/console.log.xz | Bin 2504 -> 2432 bytes 07-check_regression/console.log.xz | Bin 6852 -> 5256 bytes 07-check_regression/mail-body.txt | 80 - 07-check_regression/results.compare | 28 +- 07-check_regression/results.compare2 | 295 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 82 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2864728 -> 2863152 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2479352 -> 2474796 bytes sumfiles/gcc.sum | 4472 +++++++++++------------ sumfiles/gfortran.log.xz | Bin 956004 -> 953048 bytes sumfiles/gfortran.sum | 66 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2304 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 212368 -> 212376 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2724 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 478416 -> 477256 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2442 insertions(+), 2779 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 (0a139ac1ba -> 5ae928d7e8)

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 0a139ac1ba 157: onsuccess: #1562: 2: Success after gcc: 2 commits discards 386c5eb531 156: onsuccess: #1561: 2: Success after gcc: 2 commits discards 4a8fb4caea 155: onsuccess: #1560: 2: Success after gcc: 3 commits discards 233c7d02b6 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits discards b8164c020e 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits discards 912c36536b 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits discards 89f46c2cc6 151: onsuccess: #1556: 2: Success after binutils: 12 commits discards caa6a95bd2 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits discards f70c10e4b6 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits discards 50f1ed90e8 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits discards 4ce333bf58 147: onsuccess: #1552: 1: Success after gcc: 2 commits discards 9117e27556 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits discards 2580815625 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards 46b290b1b7 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards 907b23bf3e 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards e5de707be6 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards decf274e4c 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards 93f7ff0281 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 91e7bdea0c 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 6ec362eb6b 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards ab540777ed 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards a6074c2384 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards c6b37269ec 135: force: #1540: 2: Success after gcc: 23 commits discards a27d304fc7 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 746b8c460d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 429bca8670 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards a6e2a03394 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 582de35e10 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards 6fa5882d47 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 5391240abf 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 5bd51cbe0b 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 867fea8697 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards a9be3ba568 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 9b759f6750 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards c2cdb1f483 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards c85d7e38da 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 17a41dde22 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 51c1ca7ca3 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 1058c9a569 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 3989be41bd 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards d02692ebfb 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards 63dcc1f7d0 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards ea0cd94dad 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 07f70d481c 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 6024302eb0 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards b80495ddcb 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 2eef63bd9d 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 3c7479bdad 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 767113a753 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 278a251be8 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 05dc4ca895 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 24179d08fa 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards e5f30701f6 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards cfb4e93865 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards e8e329f4a3 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 4dc444104d 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 43341fddac 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 3a16ed9c61 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards f996ece922 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 00caf6e150 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards dca8e394e1 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 3b49412232 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 5e27d66552 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 05157103ce 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards ed3428c61a 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards c84e7df8e4 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 8bc317b045 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 49883b166d 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards dd3e4627ae 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 2fe2fdf9df 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards bb22296f6d 87: onsuccess: 2: Success after gcc: 4 commits discards 54f4eda1f8 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards fddd7ac82f 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards ee808a0d98 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 9ae1072882 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards b0aaa946b4 82: onsuccess: 1: Successful build after gcc: 3 commits discards 5e4646f9f7 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 5ff5aafa4e 80: force: 2: Successful build after gcc: 14 commits discards 8ce0757943 79: onsuccess: 2: Successful build after binutils: 5 commits discards c06b115f99 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 02ba8340ca 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 005446f577 76: onsuccess: 2: Successful build after gcc: 12 commits discards 0ff3d0db73 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 3f2147f856 74: onsuccess: 2: Successful build after baseline build: no [...] discards 24fe3ba09f 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards b1f3040f09 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9133658634 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 00e7000613 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f409c3b438 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9a0e5b033f 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards fac23a4ae9 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8ee5a61686 66: onsuccess: 2: Successful build after gcc: 9 commits discards 0c903cd1ef 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards e90d3f850c 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 6d750cde7f 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards aee9463c85 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards e730583974 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 9981f63a2a 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards f5c07b5e8d 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards a77cfe19d7 58: force: 2: Successful build after gcc: 6 commits discards 679d291cfe 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new cb0b996434 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new ed03baa057 58: force: 2: Successful build after gcc: 6 commits new 8b083989f3 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 55edbf950b 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 88df68db70 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 9a21e676f4 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 084e7a55d7 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 2f2b6153f1 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new a1a58657a0 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e2a6962afb 66: onsuccess: 2: Successful build after gcc: 9 commits new d6a3e0310f 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 5e34f3644b 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 6ffb176786 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new fe9384d82b 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new ce35d37fca 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new c400a96cdb 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 50d5b546b9 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 6c9c291e56 74: onsuccess: 2: Successful build after baseline build: no [...] new 38009496c0 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 27b86d3c11 76: onsuccess: 2: Successful build after gcc: 12 commits new b561ec64d2 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f1a10f8fc4 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new a30d1e5290 79: onsuccess: 2: Successful build after binutils: 5 commits new 77948c77d0 80: force: 2: Successful build after gcc: 14 commits new ca80738103 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 3bc3cc9d92 82: onsuccess: 1: Successful build after gcc: 3 commits new 6a60f85a66 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 02d96cf8fa 84: onsuccess: 2: Success after binutils/gcc: 15 commits new e319e871c7 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 89c5b807d5 86: onsuccess: 2: Success after binutils/gcc: 10 commits new f6a951ea2d 87: onsuccess: 2: Success after gcc: 4 commits new 5947af51af 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 39eb991de3 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 440630ba00 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 434348c56f 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 619bcdf09e 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 970f0a6959 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 46f14d0e26 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new ba72be9a20 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new a8b6700cb0 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 703db77977 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new f782bf07fe 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 260d2405dd 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 6a5f189d0a 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 3ddfbe0c18 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 1ac28dd3f7 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 219da72dd9 103: onsuccess: #1504: 2: Success after gcc: 2 commits new e19923d0a3 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new f67beaeb73 105: onsuccess: #1506: 2: Success after gcc: 2 commits new c996569db5 106: onsuccess: #1507: 2: Success after gcc: 2 commits new a85a68bda4 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 01e95c9bd1 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new b9281207e7 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new c9657f5cf4 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new e43e0a8f29 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 04aea6ea48 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 554b5543ee 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 5e7d9578bc 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 74a22d4696 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new e3b8f558f6 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 92a9cea3f4 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 03b3419170 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 4344c8b88e 119: onsuccess: #1520: 2: Success after binutils: 8 commits new ceed5cdfcf 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 67eaf9ed94 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new ad016f49a5 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new a356baed0e 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 5961cda855 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new be1f63921b 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new bde9f77821 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 1c3a91f8ed 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 93025be92c 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 1d55b707b4 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 00b9af7f0d 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 2bba7f94d2 131: onsuccess: #1534: 2: Success after gcc: 9 commits new 1ad89ec8a7 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 86dc881186 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new df0c1eae86 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 2bffb098ee 135: force: #1540: 2: Success after gcc: 23 commits new a9ea4635b3 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 6c5513dfd8 137: onsuccess: #1542: 1: Success after gcc: 4 commits new 7350d2d852 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new aa9e29205b 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new 688e7f4252 140: onsuccess: #1545: 1: Success after gcc: 7 commits new be9d5fc2db 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new b732245f12 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 4a14ea0283 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 35176fdd78 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 61f4dc7a10 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 5fcbe65dde 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 commits new 3d75ae8346 147: onsuccess: #1552: 1: Success after gcc: 2 commits new 14b5ce7c49 148: onsuccess: #1553: 2: Success after binutils/gcc: 32 commits new 6273915269 149: onsuccess: #1554: 2: Success after binutils/gcc: 15 commits new 93c4cbf520 150: onsuccess: #1555: 2: Success after binutils/gcc: 14 commits new 28e61fecf9 151: onsuccess: #1556: 2: Success after binutils: 12 commits new 001eef3a50 152: onsuccess: #1557: 2: Success after binutils/gcc: 12 commits new ced6b6d078 153: onsuccess: #1558: 2: Success after binutils/gcc: 12 commits new 23614f30d6 154: onsuccess: #1559: 2: Success after binutils/gcc: 12 commits new 3d5cce0f83 155: onsuccess: #1560: 2: Success after gcc: 3 commits new d3eb00b99b 156: onsuccess: #1561: 2: Success after gcc: 2 commits new c5125356ad 157: onsuccess: #1562: 2: Success after gcc: 2 commits new 5ae928d7e8 158: onsuccess: #1563: 2: Success after binutils/gcc: 2 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 (0a139ac1ba) \ 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 1692 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 50088 -> 51324 bytes 05-build_abe-bootstrap/console.log.xz | Bin 462904 -> 465744 bytes 06-check_regression/console.log.xz | Bin 2552 -> 2540 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 47 insertions(+), 47 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-release-aarch64-mainline-defconfig updated (51bc1e4aac -> 1223cf313c)

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-defconfig in repository toolchain/ci/base-artifacts. from 51bc1e4aac 11: onsuccess: #427: boot: Success after binutils/llvm/linux [...] new 1223cf313c 12: onsuccess: #428: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1916 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 30748 -> 30080 bytes 04-build_kernel_llvm/console.log.xz | Bin 63604 -> 65760 bytes 05-build_abe-qemu/console.log.xz | Bin 31080 -> 32128 bytes 06-build_linux/console.log.xz | Bin 3056 -> 3100 bytes 07-boot_linux/console.log.xz | Bin 6312 -> 6256 bytes 08-check_regression/console.log.xz | Bin 4060 -> 4380 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 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.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap updated (1b4e6ed840 -> a13bd97f5f)

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 in repository toolchain/ci/base-artifacts. discards 1b4e6ed840 152: onsuccess: #1579: 2: Success after gcc: 2 commits discards d4ca328ec8 151: onsuccess: #1578: 2: Success after gcc: 2 commits discards 3a0bda6a65 150: onsuccess: #1577: 2: Success after gcc: 3 commits discards fe4265bce4 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits discards a8cd9efd45 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits discards 48eb86ff78 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits discards c19b85d328 146: onsuccess: #1573: 2: Success after binutils: 7 commits discards f18eadb628 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits discards 396a60dea2 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits discards d69b0a234d 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits discards 367e33d46c 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] discards b2d30ca1a2 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits discards 8a8cb4f0a1 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits discards d121c4f65f 139: onsuccess: #1566: 1: Success after gcc: 5 commits discards 6c04a12a82 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] discards d36aede1dd 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] discards cdd86a44f3 136: onsuccess: #1561: 2: Success after binutils: 3 commits discards f96f88b4c6 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits discards 04ab60f274 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits discards aa923b6bfb 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits discards bdab2ccfe8 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits discards f1a902be4e 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits discards 512d7e87d5 130: onsuccess: #1554: 2: Success after gcc: 9 commits discards 13de00ba41 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] discards a8ed03bafa 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits discards c06502a0b1 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] discards 345e082341 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] discards b040ead829 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits discards 3cc9a46b55 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits discards 43f1a3e824 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits discards 0f5163c2cf 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits discards 36e731e3ad 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits discards 1b7acf8616 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits discards 92173dd6a2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits discards 0bacb1b59c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits discards e6c33c1099 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits discards 02177a9410 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits discards 949ca36951 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits discards d18c64c070 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits discards 2539794996 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits discards 12b0a7240d 112: onsuccess: #1533: 2: Success after gcc: 5 commits discards 42799c67b5 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits discards 253f657e5c 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 7b1c661bd0 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits discards a230d6d546 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] discards 9f48440542 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits discards 953f73ddfb 106: onsuccess: #1527: 2: Success after gcc: 2 commits discards 748b5cd3aa 105: onsuccess: #1526: 2: Success after gcc: 2 commits discards d710a78b15 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits discards c3b7ce1e1a 103: onsuccess: #1524: 2: Success after gcc: 2 commits discards b116045e6f 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits discards 9775b9fc0a 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits discards a4efb20664 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits discards 346784d1fa 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits discards 43b2c9088b 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits discards 28ab3d1b26 97: onsuccess: #1481: 2: Success after gcc: 8 commits discards ed9a32d9f6 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits discards f46bcb694e 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits discards 596e4c30d7 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] discards 4ea6a148de 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] discards 2927cfcc76 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits discards 8d32e0dda5 91: onsuccess: #1473: 2: Success after gcc: 2 commits discards 31299c2d99 90: onsuccess: #1472: 2: Success after gcc: 2 commits discards 0ef1872f9f 89: onsuccess: 2: Success after binutils/gcc: 39 commits discards f0a9707708 88: onsuccess: 1: Success after gcc: 20 commits discards 00399ce84a 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] discards d30b8d8f94 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] discards 2643786cad 85: onsuccess: 2: Success after binutils: 4 commits discards 37156a1b1e 84: onsuccess: 2: Success after gcc: 9 commits discards af2cb9ec31 83: onsuccess: 2: Success after binutils/gcc: 7 commits discards 406cae4634 82: onsuccess: 2: Success after binutils/gcc: 26 commits discards 1c7009a04f 81: onsuccess: 2: Success after binutils/gcc: 16 commits discards f5b2ce5250 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits discards 2dcbbc963f 79: onsuccess: 1: Successful build after gcc: 3 commits discards 0de204e0f0 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards e0db0e1980 77: force: 2: Successful build after gcc: 32 commits discards c9bfb520a6 76: onsuccess: 2: Successful build after binutils: 10 commits discards 83eaad3613 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 450922f398 74: onsuccess: 2: Successful build after gcc: 13 commits discards eff9ae4479 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 1655d1ef2d 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 577711f918 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f92e40c843 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 41cfdaab7b 69: onsuccess: 2: Successful build after baseline build: no [...] discards 63b4032f07 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 79e1bf522a 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards a11a75f541 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits discards 5e8b397010 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 354a98e5ea 64: onsuccess: 2: Successful build after gcc: 7 commits discards a51dd92ebc 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 29ac06359e 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 352cf3aec5 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits discards aae0927dff 60: onsuccess: 1: Successful build after gcc: 15 commits discards ee94ebed57 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 37c5361ef8 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] discards 8d290e9885 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] discards 109d8eef0c 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards a59e7af402 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1b45d9e2e0 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 3e1c93716d 53: onsuccess: 2: Successful build after gcc: 5 commits discards 9aa8ce6206 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new b67d17efcf 52: onsuccess: 2: Successful build after binutils/gcc: 10 commits new d21b9b7849 53: onsuccess: 2: Successful build after gcc: 5 commits new 054d2b280b 54: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 63429f7245 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4bc766f239 56: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 5049d33fab 57: onsuccess: 2: Successful build after binutils: gas: arm: [...] new afd490e54b 58: force: 2: Successful build after gcc: tree.cc: Fix optim [...] new 5d3230a730 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 2feeb5e97a 60: onsuccess: 1: Successful build after gcc: 15 commits new 7e56bc7fab 61: onsuccess: 2: Successful build after binutils/gcc: 25 commits new 0d87b50e03 62: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8ca4a9d9fe 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e711baaa1d 64: onsuccess: 2: Successful build after gcc: 7 commits new 0645a70e2b 65: onsuccess: 2: Successful build after binutils/gcc: 6 commits new c80f07dbf6 66: onsuccess: 2: Successful build after binutils/gcc: 13 commits new 6bb811445e 67: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 18c27ece88 68: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 61d68f1a1f 69: onsuccess: 2: Successful build after baseline build: no [...] new 6d79f8e769 70: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 3e46a34edf 71: onsuccess: 2: Successful build after binutils/gcc: 4 commits new e4c9ac3e71 72: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 00c976e30c 73: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 537fbb59e6 74: onsuccess: 2: Successful build after gcc: 13 commits new 1118ee9ed6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new e31335d004 76: onsuccess: 2: Successful build after binutils: 10 commits new 03778c15a1 77: force: 2: Successful build after gcc: 32 commits new cf6ffeec73 78: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 0be8e9bc9a 79: onsuccess: 1: Successful build after gcc: 3 commits new 7ab7059579 80: onsuccess: 1: Successful build after binutils/gcc: 8 commits new 2ef2ab2e79 81: onsuccess: 2: Success after binutils/gcc: 16 commits new 75bcf79d07 82: onsuccess: 2: Success after binutils/gcc: 26 commits new c99921694f 83: onsuccess: 2: Success after binutils/gcc: 7 commits new 22396a4c5d 84: onsuccess: 2: Success after gcc: 9 commits new ce48e1e549 85: onsuccess: 2: Success after binutils: 4 commits new 02680d74cd 86: force: 2: Success after gcc: libcpp: Add -Winvalid-utf8 [...] new 4d491600e1 87: force: 1: Failure after gcc: Fix up dump_printf_loc form [...] new 41a730049a 88: onsuccess: 1: Success after gcc: 20 commits new 2b212e8a38 89: onsuccess: 2: Success after binutils/gcc: 39 commits new 16de2a276a 90: onsuccess: #1472: 2: Success after gcc: 2 commits new 7c8e4c91c4 91: onsuccess: #1473: 2: Success after gcc: 2 commits new cdcb056ce5 92: onsuccess: #1474: 2: Success after binutils/gcc: 2 commits new 7b28e9ae04 93: onsuccess: #1475: 2: Success after basepoints/gcc-13-239 [...] new bc42a5b2cd 94: onsuccess: #1476: 2: Success after baseline build: no ne [...] new d7c04644ef 95: onsuccess: #1479: 2: Success after binutils/gcc: 39 commits new 3002f1b5bd 96: onsuccess: #1480: 2: Success after binutils/gcc: 11 commits new fc3c9f0c8b 97: onsuccess: #1481: 2: Success after gcc: 8 commits new dc689448ab 98: onsuccess: #1482: 2: Success after binutils/gcc: 5 commits new 49bc0dc801 99: onsuccess: #1483: 2: Success after binutils/gcc: 39 commits new e7159edb79 100: onsuccess: #1484: 2: Success after binutils/gcc: 18 commits new 271127888c 101: onsuccess: #1522: 2: Success after binutils/gcc: 278 commits new bfd9015120 102: onsuccess: #1523: 2: Success after binutils/gcc: 2 commits new 86d741a375 103: onsuccess: #1524: 2: Success after gcc: 2 commits new 0c3c0dd485 104: onsuccess: #1525: 2: Success after binutils/gcc: 2 commits new d453054030 105: onsuccess: #1526: 2: Success after gcc: 2 commits new 3bb1d1d877 106: onsuccess: #1527: 2: Success after gcc: 2 commits new 4e44882efa 107: onsuccess: #1528: 2: Success after binutils/gcc: 3 commits new 2f80c4a5f8 108: onsuccess: #1529: 2: Success after basepoints/gcc-13-27 [...] new 0d79064a97 109: onsuccess: #1530: 2: Success after binutils/gcc: 4 commits new 8ae9e14d96 110: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new f56b00613f 111: onsuccess: #1532: 2: Success after binutils/gcc: 3 commits new 94fd6bdcd5 112: onsuccess: #1533: 2: Success after gcc: 5 commits new 4b09664fc0 113: onsuccess: #1534: 2: Success after binutils/gcc: 11 commits new ecfaca2154 114: onsuccess: #1535: 2: Success after binutils/gcc: 13 commits new 4f264d43ab 115: onsuccess: #1536: 2: Success after binutils/gcc: 10 commits new b435bd8cac 116: onsuccess: #1537: 2: Success after binutils/gcc: 13 commits new 20993b73b9 117: onsuccess: #1538: 2: Success after binutils/gcc: 9 commits new ab3990892c 118: onsuccess: #1539: 2: Success after binutils/gcc: 11 commits new 752e8d68b2 119: onsuccess: #1541: 2: Success after binutils/gcc: 11 commits new 2ec7782de2 120: onsuccess: #1542: 2: Success after binutils/gcc: 22 commits new 4bb4983bf5 121: onsuccess: #1543: 2: Success after binutils/gcc: 34 commits new a6fe2e7d69 122: onsuccess: #1546: 2: Success after binutils/gcc: 22 commits new 190e86e7ac 123: onsuccess: #1547: 2: Success after binutils/gcc: 8 commits new 13dfbddad1 124: onsuccess: #1548: 2: Success after binutils/gcc: 8 commits new 676374665d 125: onsuccess: #1549: 2: Success after binutils/gcc: 3 commits new 0ed1ae04fd 126: onsuccess: #1550: 2: Success after gdb-12-branchpoint-2 [...] new 76a3da7fce 127: onsuccess: #1551: 2: Success after basepoints/gcc-13-28 [...] new 35afb0941a 128: onsuccess: #1552: 2: Success after binutils/gcc: 2 commits new 3710219943 129: onsuccess: #1553: 2: Success after basepoints/gcc-13-28 [...] new 97ef9fe406 130: onsuccess: #1554: 2: Success after gcc: 9 commits new a459a316c6 131: onsuccess: #1555: 2: Success after binutils/gcc: 2 commits new fd4f05089d 132: onsuccess: #1556: 2: Success after binutils/gcc: 8 commits new f6d699a1b4 133: onsuccess: #1557: 2: Success after binutils/gcc: 26 commits new b6bbbdcdf0 134: onsuccess: #1558: 2: Success after binutils/gcc: 13 commits new b2e8df1c8b 135: onsuccess: #1559: 2: Success after binutils/gcc: 8 commits new 85be350605 136: onsuccess: #1561: 2: Success after binutils: 3 commits new 30c6244d40 137: force: #1564: 2: Success after basepoints/gcc-13-2886-g [...] new cc2b7db73d 138: force: #1565: 1: Failure after basepoints/gcc-13-2887-g [...] new 97f4d6ead7 139: onsuccess: #1566: 1: Success after gcc: 5 commits new ebb37fa610 140: onsuccess: #1567: 1: Success after binutils/gcc: 41 commits new 758fd385f6 141: onsuccess: #1568: 1: Success after binutils/gcc: 6 commits new 14f0c19ec8 142: onsuccess: #1569: 1: Success after basepoints/gcc-13-29 [...] new 500acf2132 143: onsuccess: #1570: 2: Success after binutils/gcc: 32 commits new d8ffc32a73 144: onsuccess: #1571: 2: Success after binutils/gcc: 14 commits new 5a4c6e4cb9 145: onsuccess: #1572: 2: Success after binutils/gcc: 16 commits new 0b3a9b8f44 146: onsuccess: #1573: 2: Success after binutils: 7 commits new b69bbab7ad 147: onsuccess: #1574: 2: Success after binutils/gcc: 16 commits new 864ba528c5 148: onsuccess: #1575: 2: Success after binutils/gcc: 12 commits new 59d8a39371 149: onsuccess: #1576: 2: Success after binutils/gcc: 13 commits new 2c5e8b0f46 150: onsuccess: #1577: 2: Success after gcc: 3 commits new d61612e6c5 151: onsuccess: #1578: 2: Success after gcc: 2 commits new 948a1d42d4 152: onsuccess: #1579: 2: Success after gcc: 2 commits new a13bd97f5f 153: onsuccess: #1580: 2: Success after binutils/gcc: 2 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 (1b4e6ed840) \ 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 1680 -> 1660 bytes 02-prepare_abe/console.log.xz | Bin 2704 -> 2700 bytes 04-build_abe-binutils/console.log.xz | Bin 37704 -> 37508 bytes 05-build_abe-bootstrap/console.log.xz | Bin 268040 -> 272852 bytes 06-check_regression/console.log.xz | Bin 2556 -> 2544 bytes 07-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++----- 13 files changed, 47 insertions(+), 47 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 (e983bf3e9c -> 782c15e279)

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 e983bf3e9c 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards d9df8af538 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards 20a59418bf 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 7ee5182049 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards d8f0723963 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 9dad1db68e 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards bd764c03b5 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 5dce5766a3 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 4dd8f075bc 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards b8fcb121ff 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards 26b7b9040b 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 2dfbc043e5 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 49c1b608d8 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards ed3c943398 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 07530500c9 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards d982bc4ffc 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 485a62a95d 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards fa886ceab0 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 9cbeb95bc2 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 8c7c1e6a95 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards 3b6b94d805 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 3ba26c6a09 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards a99f3a8bb3 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 790ab8fe09 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards a5ba3cd9d1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d761ce5e29 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 9310bfa850 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 32c5636dc5 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 0235de1faf 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards e3693f1d49 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards f73aec0706 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards bc0d1b5253 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 0b05186668 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 0df8f7472c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 7097a4cae0 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 18aae24cec 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards c0a3db4c85 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards ce3d5ca4ec 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 4a97e580f7 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 0257429e1e 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards ad21ac19a6 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards cd9cfc7051 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards a0ab6a3ad0 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 1b5152c93e 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 62d2a3628a 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 5048094191 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards ae312d931c 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards b078445d22 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards a345543f24 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 731d4d2da1 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 7940fea132 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 78d8007739 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 5b0356bcfe 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 572b4166a4 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards e294f9b8db 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 855e449b99 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards f18d52e2db 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards db9a4126df 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards e5eb880b3a 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 5c6b895a28 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 86cebe779f 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 96bf0c9a77 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 417841b2f0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 9a50fc47c4 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards 20006fb903 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards ae85b4b02f 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards a89e17ebba 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards d7f40d2ffe 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards 698b16abd6 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 22c8849d64 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 7240ad26ad 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards acfcfccd6b 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards ef667b98c9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 7ed49d5088 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards 6bde732342 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 869e43cf97 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards ac4902beca 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d906ec025 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a2b05392fc 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards f8115df2ff 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 152d9d9c66 74: onsuccess: 1: Successful build after linux: 44 commits discards d18e092599 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 21091188d3 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 24ea50fb85 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards b171334fb3 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards 547233f33a 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 992f51b0ba 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a465020cbc 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 877d0960b6 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 553521013b 65: onsuccess: 1: Successful build after gcc: 4 commits discards d789aa4f6b 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 46f21e916f 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 419b3979cb 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 18a606131e 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards ccd590fb0b 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 5120701f95 59: onsuccess: 1: Successful build after glibc: 2 commits discards 0874c56cb1 58: onsuccess: 1: Successful build after binutils: 2 commits discards ad3a9801b1 57: onsuccess: 1: Successful build after gcc: 7 commits discards 37c3ea4edb 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 8fcf491a1c 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a45dedba1c 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new b1c23570c0 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 9ad8167a90 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d704ec40b 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new bff3df3c20 57: onsuccess: 1: Successful build after gcc: 7 commits new 1414b5a3c0 58: onsuccess: 1: Successful build after binutils: 2 commits new b2df515570 59: onsuccess: 1: Successful build after glibc: 2 commits new dca794fe44 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 74d589a6bd 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new b1d8f12ace 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 6831f0f2f5 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 012eba71a6 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a6f24dc039 65: onsuccess: 1: Successful build after gcc: 4 commits new 8130da6213 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 97ed350313 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6c60ef15f4 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4228b0f2ad 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 0ac8b36af8 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new 8b7ec4ded4 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new 6cd38c226a 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 838f3dd98c 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 28d897959c 74: onsuccess: 1: Successful build after linux: 44 commits new bb4fa8c424 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6cabba42c2 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 65103ae17b 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 54a8a93d22 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 7602705a5f 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new e6eb2bad3f 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new cbadbad84c 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new bb05826da9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 10e1a05c19 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new 3f47e8f14f 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 64a1de7507 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new 23eb873116 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new a38245a177 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new c3a3910b30 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new ee46a68547 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8b88393473 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 947a4bac27 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new b92e83bec0 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 21573f47ed 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 8345610ea1 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new bb560e45ee 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 16cceaa7df 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 71f73b2969 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 95cb27af6f 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new a8b01858c0 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 0eb707729d 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 81c8d77316 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0cd5cf68c6 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 14eb40d58d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 8f83c67218 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 8179d129b5 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 8c443b42c5 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new 21451aa70a 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 7bafa89633 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 194297f8f1 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new dfbc9deb0c 110: onsuccess: #1703: 1: Success after gcc: 6 commits new f65076c256 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new a01c16fa57 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 197421cef5 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 6d3e12e92a 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new f798298e80 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 7d86e378b8 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 87af198a63 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new d16de88b59 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new 13c677f027 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ffe21f6a10 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 7fc8b849c7 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new d407d27e55 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 02b0833778 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 6d5b202f22 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 347215527d 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new 4714590f5f 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new b8633c3f9c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 2678572c4e 128: onsuccess: #1723: 1: Success after linux: 12 commits new 7018865cf1 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new a7fb194afd 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new b37149d27c 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 788b158f1d 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 61d96312cc 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new d4fa75bfde 134: onsuccess: #1730: 1: Success after binutils: 2 commits new cc52c1ea0a 135: onsuccess: #1733: 1: Success after binutils: 5 commits new e6c48e643c 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 4034d8c2b8 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 927ec93fa3 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 1539a087b8 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 4145032150 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 459268cc21 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 9b0c62a331 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 7b59f5e7a2 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 277c2578d2 144: onsuccess: #1743: 1: Success after glibc: 2 commits new 0ab8704a96 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 5df45acfa4 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new a58df84cdb 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new a83196d85b 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new d9ce77a6e4 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new b25bc19c66 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 835809e8e2 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new b8e71afc96 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new 439bf6db34 153: onsuccess: #1754: 1: Success after gcc: 2 commits new fc4734cff9 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 782c15e279 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/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 (e983bf3e9c) \ 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 1724 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 30000 -> 30112 bytes 04-build_abe-stage1/console.log.xz | Bin 90828 -> 90876 bytes 06-build_abe-linux/console.log.xz | Bin 8920 -> 8928 bytes 07-build_abe-glibc/console.log.xz | Bin 234904 -> 234276 bytes 08-build_abe-stage2/console.log.xz | Bin 224020 -> 223936 bytes 09-build_abe-gdb/console.log.xz | Bin 37184 -> 37120 bytes 10-build_abe-qemu/console.log.xz | Bin 31400 -> 31540 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2736 -> 2432 bytes 13-check_regression/console.log.xz | Bin 5916 -> 5700 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 25 +- 13-check_regression/results.compare2 | 64 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 46 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 26 + sumfiles/g++.log.xz | Bin 2650704 -> 2664664 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 2201416 -> 2232560 bytes sumfiles/gcc.sum | 2014 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 893568 -> 886828 bytes sumfiles/gfortran.sum | 10 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201520 -> 201752 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 427764 -> 423444 bytes sumfiles/libstdc++.sum | 8 +- 43 files changed, 1225 insertions(+), 1151 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allyesconfig updated (91a150d6d8 -> 098a603932)

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-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 91a150d6d8 16: onsuccess: #249: 19905: Success after binutils/llvm/linu [...] new 098a603932 17: onsuccess: #250: 19909: Success after binutils/llvm/linu [...] 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 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 29976 -> 29780 bytes 04-build_kernel_llvm/console.log.xz | Bin 62904 -> 62728 bytes 05-build_abe-qemu/console.log.xz | Bin 31168 -> 31396 bytes 06-build_linux/console.log.xz | Bin 4612 -> 4608 bytes 08-check_regression/console.log.xz | Bin 4076 -> 4348 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 18 files changed, 27 insertions(+), 27 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 October 2022