Tcwg-commits September 2022

tcwg-commits@lists.linaro.org

7 participants
4685 discussions

[glibc] branch master updated (3e5760fcb4 -> 5eb21c62ce)

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 glibc. from 3e5760fcb4 Update _FloatN header support for C++ in GCC 13 new b0969fa53a x86: Fix wcsnlen-avx2 page cross length comparison [BZ #29591] new 5eb21c62ce Benchtest: Add additional benchmarks for strlen and strnlen 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: benchtests/bench-strlen.c | 33 ++++++++++++++-- benchtests/bench-strnlen.c | 55 ++++++++++++++++++++++++-- string/test-strnlen.c | 70 ++++++++++++++++++++-------------- sysdeps/x86_64/multiarch/strlen-avx2.S | 7 +--- 4 files changed, 124 insertions(+), 41 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch release/2.28/master updated (8b915921fb -> 2b05bbfd35)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.28/master in repository glibc. from 8b915921fb Add test for bug 29530 new 956cda8d9f x86-64: Require BMI2 for strchr-avx2.S [BZ #29611] new 2b05bbfd35 x86-64: Require BMI2 for avx2 functions [BZ #29611] 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: sysdeps/x86_64/multiarch/ifunc-avx2.h | 4 +-- sysdeps/x86_64/multiarch/ifunc-impl-list.c | 50 ++++++++++++++++++++++-------- 2 files changed, 39 insertions(+), 15 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_bmk_llvm_tk1/llvm-master-arm-spec2k6-O3 updated (0088b62c57 -> 08ef17e4fb)

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_bmk_llvm_tk1/llvm-master-arm-spec2k6-O3 in repository toolchain/ci/base-artifacts. from 0088b62c57 7: force: #354: 1: [TCWG CI] 464.h264ref slowed down by 5% a [...] new 08ef17e4fb 8: onsuccess: #355: 1: [TCWG CI] No change after llvm: 31 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 1720 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2732 bytes 03-build_abe-binutils/console.log.xz | Bin 30560 -> 30484 bytes 04-build_abe-stage1/console.log.xz | Bin 92040 -> 91712 bytes 06-build_abe-linux/console.log.xz | Bin 7984 -> 7980 bytes 07-build_abe-glibc/console.log.xz | Bin 234784 -> 234596 bytes 08-build_abe-stage2/console.log.xz | Bin 209956 -> 209104 bytes 09-build_llvm-true/console.log.xz | Bin 60852 -> 61472 bytes 10-benchmark/benchmark-build.log | 112 +- 10-benchmark/benchmark.log | 110 +- 10-benchmark/console.log.xz | Bin 3924 -> 4008 bytes 11-check_regression/console.log.xz | Bin 12628 -> 11428 bytes 11-check_regression/csv-results-0/md5sum.csv | 1567 +- 11-check_regression/csv-results-0/perf.csv | 2018 +- 11-check_regression/csv-results-0/results.csv | 10904 +- 11-check_regression/csv-results-0/size.csv | 282980 +++++++++--------- 11-check_regression/csv-results-0/vect.csv | 20454 +- 11-check_regression/csv-results-1/md5sum.csv | 1688 +- 11-check_regression/csv-results-1/perf.csv | 2026 +- 11-check_regression/csv-results-1/results.csv | 11141 +- 11-check_regression/csv-results-1/size.csv | 227890 +++++++------- 11-check_regression/csv-results-1/vect.csv | 20066 +- 11-check_regression/exe.regression | 1 - 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/jira-body.txt | 7 - 11-check_regression/mail-body.txt | 7 - 11-check_regression/mail-subject.txt | 2 +- 11-check_regression/results-brief.csv | 40 +- 11-check_regression/results-compare.csv | 11 +- 11-check_regression/results-full.csv | 2087 +- 11-check_regression/results-internal.csv | 157 +- 11-check_regression/results.csv | 157 +- 11-check_regression/results.log | 958 +- 11-check_regression/results.regressions | 9 - 11-check_regression/symbol.regression | 1 - 11-check_regression/trigger-bisect | 3 - 11-check_regression/trigger-notify | 0 12-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../squad/400.perlbench/results-metadata.json | 10 +- dashboard/squad/401.bzip2/results-metadata.json | 10 +- dashboard/squad/401.bzip2/results-metrics.json | 2 +- dashboard/squad/403.gcc/results-metadata.json | 10 +- dashboard/squad/403.gcc/results-metrics.json | 2 +- dashboard/squad/429.mcf/results-metadata.json | 10 +- dashboard/squad/429.mcf/results-metrics.json | 2 +- dashboard/squad/433.milc/results-metadata.json | 10 +- dashboard/squad/433.milc/results-metrics.json | 2 +- dashboard/squad/444.namd/results-metadata.json | 10 +- dashboard/squad/444.namd/results-metrics.json | 2 +- dashboard/squad/445.gobmk/results-metadata.json | 10 +- dashboard/squad/445.gobmk/results-metrics.json | 2 +- dashboard/squad/447.dealII/results-metadata.json | 10 +- dashboard/squad/447.dealII/results-metrics.json | 2 +- dashboard/squad/450.soplex/results-metadata.json | 10 +- dashboard/squad/450.soplex/results-metrics.json | 2 +- dashboard/squad/453.povray/results-metadata.json | 10 +- dashboard/squad/453.povray/results-metrics.json | 2 +- dashboard/squad/456.hmmer/results-metadata.json | 10 +- dashboard/squad/456.hmmer/results-metrics.json | 2 +- dashboard/squad/458.sjeng/results-metadata.json | 10 +- dashboard/squad/458.sjeng/results-metrics.json | 2 +- .../squad/462.libquantum/results-metadata.json | 10 +- .../squad/462.libquantum/results-metrics.json | 2 +- dashboard/squad/464.h264ref/results-metadata.json | 10 +- dashboard/squad/464.h264ref/results-metrics.json | 2 +- dashboard/squad/470.lbm/results-metadata.json | 10 +- dashboard/squad/470.lbm/results-metrics.json | 2 +- dashboard/squad/471.omnetpp/results-metadata.json | 10 +- dashboard/squad/471.omnetpp/results-metrics.json | 2 +- dashboard/squad/473.astar/results-metadata.json | 10 +- dashboard/squad/473.astar/results-metrics.json | 2 +- dashboard/squad/482.sphinx3/results-metadata.json | 10 +- dashboard/squad/482.sphinx3/results-metrics.json | 2 +- .../squad/483.xalancbmk/results-metadata.json | 10 +- dashboard/squad/483.xalancbmk/results-metrics.json | 2 +- dashboard/squad/dashboard-push-squad.sh | 84 +- dashboard/squad/summary-annotation.txt | 1 - git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 1023 - jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 18 +- mail/mail-body.txt | 18 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- results | 9 - results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1356524 -> 1359488 bytes save-temps/401.bzip2.tar.xz | Bin 106844 -> 106932 bytes save-temps/403.gcc.tar.xz | Bin 3769768 -> 3765940 bytes save-temps/429.mcf.tar.xz | Bin 35324 -> 34964 bytes save-temps/433.milc.tar.xz | Bin 161604 -> 161292 bytes save-temps/444.namd.tar.xz | Bin 206844 -> 206640 bytes save-temps/445.gobmk.tar.xz | Bin 2117192 -> 2121148 bytes save-temps/447.dealII.tar.xz | Bin 3547620 -> 3498264 bytes save-temps/450.soplex.tar.xz | Bin 534400 -> 537168 bytes save-temps/453.povray.tar.xz | Bin 1250528 -> 1253516 bytes save-temps/456.hmmer.tar.xz | Bin 354376 -> 353896 bytes save-temps/458.sjeng.tar.xz | Bin 169752 -> 170388 bytes save-temps/462.libquantum.tar.xz | Bin 53616 -> 53920 bytes save-temps/464.h264ref.tar.xz | Bin 715136 -> 716312 bytes save-temps/470.lbm.tar.xz | Bin 25632 -> 25660 bytes save-temps/471.omnetpp.tar.xz | Bin 904120 -> 911232 bytes save-temps/473.astar.tar.xz | Bin 76564 -> 76128 bytes save-temps/482.sphinx3.tar.xz | Bin 239624 -> 239592 bytes save-temps/483.xalancbmk.tar.xz | Bin 7217908 -> 7225436 bytes 109 files changed, 293704 insertions(+), 292110 deletions(-) delete mode 100644 11-check_regression/exe.regression delete mode 100644 11-check_regression/results.regressions delete mode 100644 11-check_regression/symbol.regression delete mode 100644 11-check_regression/trigger-bisect delete mode 100644 11-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-arm-bootstrap updated (1008ae9026 -> 18750231c6)

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 1008ae9026 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards b19b85984d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards a432206a91 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 08118e22a5 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards b295598339 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards a51e61b7d6 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 6defc9fec6 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 902a812ee0 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards b3bf804c10 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 4892af99a8 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards b0289eef0e 135: force: #1540: 2: Success after gcc: 23 commits discards 7cf0632137 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 940b326fd2 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 3b21bbc36e 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 311dff2f9d 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 25a3eafc40 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards d50d69df6a 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards d17853eb7a 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 9ae584c84c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 9fafe3d275 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 99198d6b09 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 9869e93cc9 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards d4446a9351 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 51b506434b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 9f41f5c1b2 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 4c638b221a 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards a6b217ad02 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 42f474eb54 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 51ca5f14f9 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards bbc6922d43 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 41165c04de 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 8c5acdb23f 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 0b7e179396 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards ba7bb7c121 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards ee8b70dbb7 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards e591fe8a03 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 826e704351 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 53fe16f06d 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 7fe683f38c 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 63fb2994be 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 5940289390 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards f82e0d5681 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 0a483367d8 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 625a4d54c1 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 929d1d07b7 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 89858fb943 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 67345f00f9 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards bdb82ccd81 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards cac97a60a1 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 47e0ad8f1d 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 5346c23b6e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards aa15ac5978 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards a74bdf2ee0 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards c215daa329 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 606726f2f2 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards ef3566c8f2 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards a56e017864 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards e0406187df 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7baa5547bf 87: onsuccess: 2: Success after gcc: 4 commits discards ba82fc5bfc 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards d7a2858538 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1a13cdd30c 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 7195d91775 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 633cafa317 82: onsuccess: 1: Successful build after gcc: 3 commits discards 53b056092c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 31f2aa500c 80: force: 2: Successful build after gcc: 14 commits discards d4d961c305 79: onsuccess: 2: Successful build after binutils: 5 commits discards 137c0618c0 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards b3eb998a35 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 3962942472 76: onsuccess: 2: Successful build after gcc: 12 commits discards b119b8019e 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 980bd232cd 74: onsuccess: 2: Successful build after baseline build: no [...] discards 338f47b194 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 3688a2a0c0 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 011aa66f8f 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 3af998297d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 2cacaa3123 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 83fcd6595a 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a9561b32fa 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8c94a3bfdc 66: onsuccess: 2: Successful build after gcc: 9 commits discards 88e827ea8d 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 98512795d2 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bf7792f53a 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6ebc0e678c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 50a084f395 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 8a18d0ff57 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards b23567c402 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 60727f43ec 58: force: 2: Successful build after gcc: 6 commits discards e14d5d94d0 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 01352dfdd0 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 060fbe79ce 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9beff6f3e9 54: onsuccess: 2: Successful build after gcc: 5 commits discards 257f8ba30b 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 8be81dddc4 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards db814157a9 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards cd4715d929 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 9149c4bd51 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards b18875c449 48: onsuccess: 2: Successful build after gcc: 4 commits discards 0a8e4ad195 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9f80016f1e 46: onsuccess: 2: Successful build after baseline build: no [...] discards d101dfc6d2 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f5e956d7b0 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f06107854e 46: onsuccess: 2: Successful build after baseline build: no [...] new 239f8c0512 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3da05e9175 48: onsuccess: 2: Successful build after gcc: 4 commits new e2495f68cb 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 83eddf11a3 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new f79c8d70db 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4b760cc8a7 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new d147881e61 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new cc73a78799 54: onsuccess: 2: Successful build after gcc: 5 commits new 19a2efdc05 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3bc42c93e1 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 037288407b 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new fa009c0ef8 58: force: 2: Successful build after gcc: 6 commits new 116a753939 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 6ef718264a 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 8a494e9f20 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 392bf791aa 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new fee6cd200e 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6d8c5e01ba 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f36693b53c 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new cbeab6460c 66: onsuccess: 2: Successful build after gcc: 9 commits new b4d9034503 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c01862b176 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 5735eaa664 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d3c3f50d56 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8684c09049 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new cd263b02a7 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new aae8b94592 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new ae2ffdc240 74: onsuccess: 2: Successful build after baseline build: no [...] new 430a59e0f1 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new fc376564b7 76: onsuccess: 2: Successful build after gcc: 12 commits new a338166289 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3e4ff4899b 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new f19d575de5 79: onsuccess: 2: Successful build after binutils: 5 commits new 4863026dac 80: force: 2: Successful build after gcc: 14 commits new 4db71b7e97 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 40ece67c42 82: onsuccess: 1: Successful build after gcc: 3 commits new 2f40a33273 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 8fb8bfaf6e 84: onsuccess: 2: Success after binutils/gcc: 15 commits new f223322a34 85: onsuccess: 2: Success after binutils/gcc: 25 commits new eef808f40b 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 4fb48c6823 87: onsuccess: 2: Success after gcc: 4 commits new b571f486b2 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 5baaa4cc9f 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 1405440be1 90: onsuccess: 2: Success after binutils/gcc: 16 commits new e562d49a14 91: onsuccess: 2: Success after binutils/gcc: 7 commits new d5191d5d4e 92: onsuccess: 2: Success after binutils/gcc: 9 commits new c59064a16b 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 1cb957ff2b 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 4a36b90045 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 88d1b02848 96: onsuccess: #1452: 2: Success after gcc: 2 commits new d8c28618cd 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 5bd25c4176 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 2db304dedb 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 7ffb66bdad 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new dfd0bb1126 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new dd87795340 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new e563ccee47 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 049f749e2d 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 45522236d3 105: onsuccess: #1506: 2: Success after gcc: 2 commits new bf9432455e 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 54dc6bdb3b 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 3d0a9e7a8e 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 498858025b 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 597c1968c0 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 3429488967 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 86a85e079d 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new f2e2dc612a 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 26a5718443 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 79b81d6bf6 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 38f772af45 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new ae605b17b3 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 05be128bc2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 0bd5eb0a34 119: onsuccess: #1520: 2: Success after binutils: 8 commits new fd27040209 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new f7582a7051 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 5bbce4350a 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new e852636613 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new c778c74646 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new e16470338d 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new b9518c9f59 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new d760991ab4 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new d31ba60f5f 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 72b2875d76 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 25da18b00d 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 4bc4a5484a 131: onsuccess: #1534: 2: Success after gcc: 9 commits new c2596e907a 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 33cf5d36a7 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 60e63550c0 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 2988329f78 135: force: #1540: 2: Success after gcc: 23 commits new 65210d164f 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 21cee9c2f6 137: onsuccess: #1542: 1: Success after gcc: 4 commits new c127f12fe2 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new d4b3aa2950 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new cd33ca8892 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 6e487b535d 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 54776a566b 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 0902c51bb7 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 6723a8524d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 729315b960 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 18750231c6 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 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 (1008ae9026) \ 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 1660 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 51624 -> 51552 bytes 05-build_abe-bootstrap/console.log.xz | Bin 112108 -> 113416 bytes 06-check_regression/console.log.xz | Bin 2948 -> 2748 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- 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, 35 insertions(+), 35 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_profiled updated (a7b7ad78e1 -> 0be16468ae)

by git＠git.linaro.org

2 years, 1 month

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (8bc9f4b2a0 -> 1155375e33)

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 8bc9f4b2a0 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards 8d10f75a4b 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 698d4c14c1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards b7367844d9 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards c3596228bc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards 18448efd20 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards 959755dc19 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 71c6ed8f63 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards c7a59c9144 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 14824d42a9 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 5a04795456 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards 09beba1368 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards d67752466c 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards 3a4cb24a70 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 7230689084 128: onsuccess: #1723: 1: Success after linux: 12 commits discards e748fdc42f 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards 4f70eba9e2 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 3c2254bae8 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 197cbb1036 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards 26509ee736 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards 3ecd6a7d90 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 43e56ed6f4 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards 49b212fa8a 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 0872ae4fe5 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards 1e2992e38d 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards 093869abaa 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 2e7d85f6c0 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards d56767c7ee 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 89113aec95 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards f0851fcc71 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards 36130c6444 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards d380307723 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 810e77831f 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 5e4ab5b436 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards c08fdd475a 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards 7e6518c219 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 187a5753f0 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 0d56c0762b 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards 5270923923 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards e9560cf21c 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards af7cf1074a 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 01f3f38dd8 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards ca46fbd813 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 5de9119f42 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards 75aacdd156 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards a45677a7c4 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 7857103ee2 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards cdd5f384ed 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards 1feb64d7c5 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards 4ea5c0f1f0 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits discards 96240c3b6a 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] discards 00200af208 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits discards fcb32117c2 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards d4259c7aec 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2e2a473757 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits discards 790e37c952 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits discards d03121965c 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits discards 9d9451fed4 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits discards 6a5b8f9cfc 84: onsuccess: 1: Success after gcc/glibc: 9 commits discards ebcefb5e88 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits discards 575e3f96f3 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits discards 04f35fba41 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits discards b60159821a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] discards 00aeef5344 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] discards b3baf148d7 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards 7d81171c45 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 187336acd6 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] discards a7122fb4f4 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 2a5849fd9e 74: onsuccess: 1: Successful build after linux: 44 commits discards a14c2ab260 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits discards 8714afe615 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 9da6ac3a06 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] discards 2b9ef3a981 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] discards baea4d3d82 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] discards 1c3c77ec31 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards c46afbca4c 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards e4c6ccba72 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards e010542225 65: onsuccess: 1: Successful build after gcc: 4 commits discards f9e8508788 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a20d93404a 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards cb61a597cc 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] discards 8160f0fafe 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards b1ca9097af 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] discards 953ca06727 59: onsuccess: 1: Successful build after glibc: 2 commits discards 5535a1356e 58: onsuccess: 1: Successful build after binutils: 2 commits discards 2b0209b138 57: onsuccess: 1: Successful build after gcc: 7 commits discards c74da04346 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards d68343c55a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1604865fde 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits discards 0f25c9255b 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] discards 64afe620f9 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] discards b84b3f987d 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards b456ff6aa9 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 4e2b460e45 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards f9fff1e098 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] discards 6dde03fab9 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ab2d952eb4 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] discards bbd198732e 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 663aef4434 44: onsuccess: 1: Successful build after linux: 34 commits discards 567fb6ff7b 43: onsuccess: 1: Successful build after gcc: 2 commits discards fc50c36ae1 42: onsuccess: 1: Successful build after baseline build: no [...] new 30a09f3ab9 42: onsuccess: 1: Successful build after baseline build: no [...] new 874a1325c1 43: onsuccess: 1: Successful build after gcc: 2 commits new 31b783c80a 44: onsuccess: 1: Successful build after linux: 34 commits new b6e0c900cf 45: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 842a080e62 46: onsuccess: 1: Successful build after binutils/linux/gdb: [...] new dd9f31d122 47: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new a9e88f0e72 48: onsuccess: 1: Successful build after binutils/gcc/gdb: 5 [...] new 59c476ec46 49: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new c4782dc76a 50: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d23c0b0746 51: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 97d780c50e 52: onsuccess: 1: Successful build after binutils/gcc/gdb: 4 [...] new 64b0125917 53: onsuccess: 1: Successful build after binutils/gcc/gdb: 1 [...] new b2d36feb04 54: onsuccess: 1: Successful build after gcc/glibc/qemu: 9 commits new 356ca6c51a 55: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new eefba6ef73 56: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 785f320823 57: onsuccess: 1: Successful build after gcc: 7 commits new f36302c6df 58: onsuccess: 1: Successful build after binutils: 2 commits new 9ec2520582 59: onsuccess: 1: Successful build after glibc: 2 commits new 51bf2c82b6 60: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new c312dc9e78 61: onsuccess: 1: Successful build after binutils/gcc/gdb/qe [...] new 756f49d247 62: onsuccess: 1: Successful build after binutils/gcc/gdb: 2 [...] new 26892c2857 63: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 3a3f0847ad 64: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 433d8537f4 65: onsuccess: 1: Successful build after gcc: 4 commits new 53b58771d9 66: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 3f5d34ea6f 67: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 718023b7fa 68: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2e6ed8f72d 69: onsuccess: 1: Successful build after binutils/gcc/gdb: 3 [...] new 80006d5437 70: onsuccess: 1: Successful build after gcc: Require fgraph [...] new c1e2c17f91 71: onsuccess: 1: Successful build after gcc/linux/glibc: 15 [...] new ad937ef61f 72: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new c69d9d4217 73: onsuccess: 1: Successful build after binutils/gdb: 2 commits new 16966c8eb9 74: onsuccess: 1: Successful build after linux: 44 commits new bcc28740cc 75: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new b08a957d18 76: onsuccess: 1: Successful build after gcc/linux/glibc: 21 [...] new 03d2789538 77: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 54b24ebdd2 78: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 024ca2c347 79: onsuccess: 1: Successful build after binutils/gcc/gdb: 8 [...] new 495d84916a 80: onsuccess: 1: Successful build after gcc: libsanitizer: [...] new e15cfe5826 81: onsuccess: 1: Success after binutils/gcc/glibc/gdb: 19 commits new 947cac56d9 82: onsuccess: 1: Success after binutils/gcc/linux/gdb: 68 commits new 249a195244 83: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 43 commits new a46331671e 84: onsuccess: 1: Success after gcc/glibc: 9 commits new 406e4fbbba 85: onsuccess: 1: Success after binutils/gcc/linux/gdb: 99 commits new d007fadd65 86: onsuccess: 1: Success after binutils/gcc/gdb/qemu: 74 commits new f59d1ca4a9 87: onsuccess: 1: Success after binutils/gcc/gdb: 9 commits new 80fd37c361 88: onsuccess: 1: Success after binutils/gcc/gdb: 15 commits new 837583a321 89: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new 8dd6e783ec 90: onsuccess: 1: Success after binutils/gcc/linux/gdb/qemu: [...] new fdcd3375d6 91: onsuccess: #1611: 1: Success after gcc/linux: 33 commits new 587803dc31 92: onsuccess: #1612: 1: Success after binutils/gcc/linux/gd [...] new 1a0693d7c9 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new d9f51fe9e2 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new e00333a2fa 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 6ffc90b82b 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 808036a27c 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new 0522d50fde 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 9fa73e78d9 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new 1e7abf4226 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new 9446f87e4d 101: onsuccess: #1693: 1: Success after glibc: 14 commits new 0cb3043888 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new a17a27f051 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new bfb0cda74f 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 9c35157fe6 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new b4faf1b0df 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new fa52745e8c 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new b0f610cc28 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new 511613434d 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new 46bff33771 110: onsuccess: #1703: 1: Success after gcc: 6 commits new 115e6368ab 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new b4d07fc103 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new 3f07325dd2 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new 2b3ab2ccac 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new dfbe87c3fe 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 957f067ba5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new b5fd8ce0dd 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new a95961bea2 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new f89ae8bff3 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new ad0d2562dc 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new 72a36a73d5 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new b70e8c90ba 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new 761cce069e 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new a79f42a46e 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new d2d027dfdf 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new d01de6b8ef 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 8ee903730c 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 72ca984f87 128: onsuccess: #1723: 1: Success after linux: 12 commits new cce3957603 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 3f808193c3 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new 5fa1ad7db8 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 4ede5ad5bb 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 735cf761b8 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 55cd045042 134: onsuccess: #1730: 1: Success after binutils: 2 commits new 90326e0df3 135: onsuccess: #1733: 1: Success after binutils: 5 commits new 6384e614e1 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 5e8355e07a 137: onsuccess: #1736: 1: Success after gcc: 5 commits new 86be48dfd6 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new 1fff1edcca 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 0ef74d37f1 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8e9f122d9f 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new d84842ffb2 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new 1155375e33 143: onsuccess: #1742: 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 (8bc9f4b2a0) \ 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 1708 -> 1728 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 30144 -> 29876 bytes 04-build_abe-stage1/console.log.xz | Bin 91152 -> 90612 bytes 06-build_abe-linux/console.log.xz | Bin 9256 -> 8760 bytes 07-build_abe-glibc/console.log.xz | Bin 234364 -> 234572 bytes 08-build_abe-stage2/console.log.xz | Bin 223344 -> 222608 bytes 09-build_abe-gdb/console.log.xz | Bin 37556 -> 37240 bytes 10-build_abe-qemu/console.log.xz | Bin 31096 -> 30776 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3868 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2744 -> 2432 bytes 13-check_regression/console.log.xz | Bin 6036 -> 6944 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 | 66 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 70 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results | 26 + sumfiles/g++.log.xz | Bin 2667716 -> 2651552 bytes sumfiles/g++.sum | 40 +- sumfiles/gcc.log.xz | Bin 2226364 -> 2219996 bytes sumfiles/gcc.sum | 1970 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 881588 -> 882784 bytes sumfiles/gfortran.sum | 6 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 201100 -> 201320 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2672 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 422680 -> 423668 bytes sumfiles/libstdc++.sum | 30 +- 44 files changed, 1288 insertions(+), 1096 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_gcc_bootstrap/master-arm-bootstrap_profiled updated (bb5a95543d -> a7b7ad78e1)

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_profiled in repository toolchain/ci/base-artifacts. from bb5a95543d 45: force: #441: 1: Failure after basepoints/gcc-13-2871-g1b [...] new a7b7ad78e1 46: onsuccess: #442: 1: Success after gcc: 8 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 1668 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51392 -> 50872 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 107860 -> 107832 bytes 06-check_regression/console.log.xz | Bin 3272 -> 2784 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 | 9 -- 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 | 210 ------------------------- 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 | 9 -- 23 files changed, 33 insertions(+), 272 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-arm-bootstrap_profiled updated (b82986dffb -> bb5a95543d)

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_profiled in repository toolchain/ci/base-artifacts. from b82986dffb 44: force: #440: 2: Success after gcc: 29 commits new bb5a95543d 45: force: #441: 1: Failure after basepoints/gcc-13-2871-g1b [...] 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 1712 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2720 bytes 04-build_abe-binutils/console.log.xz | Bin 52268 -> 51392 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 930384 -> 107860 bytes 06-check_regression/console.log.xz | Bin 2704 -> 3272 bytes 06-check_regression/jira-body.txt | 2 +- 06-check_regression/mail-body.txt | 13 +- 06-check_regression/mail-subject.txt | 2 +- 06-check_regression/results.regressions | 9 + 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 | 210 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 13 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +- results | 11 +- 23 files changed, 274 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 (fad7948 -> 2f2ac23)

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 fad7948 Add entry e07ead85a368173a56e96a21d6841aa497ad80f8 from https [...] new 2f2ac23 Add entry 1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4 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: .../{master-arm-bootstrap => master-arm-bootstrap_profiled}/build_url | 2 +- .../{master-arm-bootstrap => master-arm-bootstrap_profiled}/last_good | 0 .../summary.txt | 0 .../tcwg_gcc_bootstrap/status.txt | 3 +++ 4 files changed, 4 insertions(+), 1 deletion(-) copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] copy gcc/sha1/1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4/tcwg_gcc_bootstrap/{master- [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 1 month

[glibc] branch release/2.29/master updated (6da40102c7 -> 114e3349de)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch release/2.29/master in repository glibc. from 6da40102c7 Add test for bug 29530 new 986e7b911f x86-64: Require BMI2 for strchr-avx2.S [BZ #29611] new 114e3349de x86-64: Require BMI2 for avx2 functions [BZ #29611] 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: sysdeps/x86_64/multiarch/ifunc-avx2.h | 4 +-- sysdeps/x86_64/multiarch/ifunc-impl-list.c | 50 ++++++++++++++++++++++-------- 2 files changed, 39 insertions(+), 15 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