Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig updated (3a587822b0c9 -> 74f387896319)

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-lts-defconfig in repository toolchain/ci/base-artifacts. from 3a587822b0c9 60: onsuccess: #8: boot: Success after binutils/llvm/linux [...] new 74f387896319 61: onsuccess: #9: boot: [TCWG CI] Success after binutils/ [...] 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 1996 -> 2004 bytes 02-prepare_abe/console.log.xz | Bin 2576 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 26656 -> 26752 bytes 04-build_kernel_llvm/console.log.xz | Bin 65816 -> 64156 bytes 05-build_abe-qemu/console.log.xz | Bin 31664 -> 31280 bytes 06-build_linux/console.log.xz | Bin 3064 -> 3060 bytes 07-boot_linux/console.log.xz | Bin 5640 -> 5632 bytes 08-check_regression/console.log.xz | Bin 4236 -> 4184 bytes 08-check_regression/mail-body.txt | 31 ------------------------------- 08-check_regression/mail-subject.txt | 1 - 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/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 31 ------------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 23 files changed, 49 insertions(+), 94 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O3_LTO updated (0c47ef8350b1 -> 690730f82854)

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-code_speed-cpu2017rate/gnu-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 0c47ef8350b1 14: onsuccess: #19: 1: [TCWG CI] No change after v6.2.8-48 [...] new 690730f82854 15: onsuccess: #22: 1: [TCWG CI] Success after binutils/gc [...] 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 1984 -> 2076 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 27124 -> 27248 bytes 04-build_abe-stage1/console.log.xz | Bin 90344 -> 90676 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8280 -> 7556 bytes 07-build_abe-glibc/console.log.xz | Bin 233676 -> 233936 bytes 08-build_abe-stage2/console.log.xz | Bin 211224 -> 211428 bytes 09-benchmark/benchmark-build.log | 209 +- 09-benchmark/benchmark.log | 207 +- 09-benchmark/console.log.xz | Bin 4128 -> 4152 bytes 10-check_regression/bmk-specific-variability.csv | 33 - .../compare-results-vs-first-internal.csv | 66 +- .../compare-results-vs-prev-internal.csv | 66 +- 10-check_regression/console.log.xz | Bin 8196 -> 10556 bytes .../csv-results-vs-first-0/results.csv | 693738 ++++++++--------- .../csv-results-vs-first-0/size.csv | 709818 +++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 51572 +- .../csv-results-vs-first-0/vect.csv | 1230 +- .../csv-results-vs-first-1/perf.csv | 171 +- .../csv-results-vs-first-1/results.csv | 660091 ++++++++-------- .../csv-results-vs-first-1/size.csv | 663154 ++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 51470 +- .../csv-results-vs-first-1/vect.csv | 1335 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 168 +- .../csv-results-vs-prev-0/results.csv | 682925 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 686600 +++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 51456 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 1252 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 171 +- .../csv-results-vs-prev-1/results.csv | 660091 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 663154 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 51470 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 1335 +- 10-check_regression/exe.improvement | 2 + 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/mail-body.txt | 4 + 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement | 5 + .../output-bmk-results/exe.improvement.diff | 9 + 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 181 +- 10-check_regression/results-vs-first-internal.csv | 66 +- 10-check_regression/results-vs-first.csv | 66 +- 10-check_regression/results-vs-first.log | 1382 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 4 +- 10-check_regression/results-vs-prev-full.csv | 183 +- 10-check_regression/results-vs-prev-internal.csv | 66 +- 10-check_regression/results-vs-prev.csv | 66 +- 10-check_regression/results-vs-prev.log | 1638 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 16 +- .../510.parest_r/results-metadata.json | 16 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 16 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 4 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 16 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../526.blender_r/results-metadata.json | 16 +- .../527.cam4_r/results-metadata.json | 16 +- .../squad-vs-first/527.cam4_r/results-metrics.json | 2 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metrics.json | 4 +- .../538.imagick_r/results-metadata.json | 16 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 4 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 17 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 35 +- results_id | 2 +- 100 files changed, 2774479 insertions(+), 2861694 deletions(-) create mode 100644 10-check_regression/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (87d3bc53b17 -> 69044e11ac5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 87d3bc53b17 testsuite: Add testcase for already fixed PR [PR109362] new 5fe05ffefd2 range-op-float: Further comparison fixes new 69044e11ac5 range-op-float: Further foperator_{,not_}equal::fold_range fix The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/range-op-float.cc | 168 +++++++++++++++------ gcc/testsuite/gcc.dg/torture/inf-compare-1-float.c | 1 + gcc/testsuite/gcc.dg/torture/inf-compare-1.c | 1 + gcc/testsuite/gcc.dg/torture/inf-compare-2-float.c | 1 + gcc/testsuite/gcc.dg/torture/inf-compare-2.c | 1 + 5 files changed, 126 insertions(+), 46 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (94e529744e7e -> 2757737fcef6)

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 94e529744e7e 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 0779c8bdd5f9 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 83c198b6cf66 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards bdc780fef2ba 476: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 88b28028db39 475: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 9021920f51a1 474: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards d9375d8a33e3 473: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 4c0159863a18 472: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 0603fcaf308c 471: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 8fcac388fed7 470: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards a810a6c1b659 469: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 21ecf7fdc49f 468: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 79d26988e78b 467: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 0c1c1c3df436 466: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 3e26ba0797ca 465: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 34e685123200 464: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards 23d89ddf4d32 463: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] discards 29fd7d7f2bd7 462: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] discards af9a13c8030d 461: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] discards 853410dd966c 460: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards 939229b10ca1 459: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 41e494fed9cf 458: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards d36b040beaa5 457: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards f1dfee5772ab 456: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 2a7e9717e1d3 455: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 585d55832567 454: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards ad884bb0a270 453: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards bd17b1e22a8a 452: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 6a59e8cdef20 451: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards c5062c8d890e 450: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards cdbf314c1038 449: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards d1906c0571b2 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 5e929c17d9f7 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards e509021ee5f9 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 06916b06a18f 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards bff2cac09823 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards dcbf1b15dcb5 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] discards ea38856f3053 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gd [...] discards c946b98534cb 441: onsuccess: #2266: 1: Success after binutils/gcc/linux [...] discards 81f191f8011c 440: onsuccess: #2265: 1: Success after binutils/gcc/linux [...] discards 0815cd1a0d3d 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: [...] discards c74823e174f4 438: onsuccess: #2263: 1: Success after binutils/gcc/linux [...] discards 2a922a348bcc 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc [...] discards e34ee4f7b057 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 67e240acd59e 435: onsuccess: #2259: 1: Success after binutils/gcc/linux [...] discards 181756a47ab4 434: onsuccess: #2258: 1: Success after binutils/gcc/linux [...] discards 736e969b013f 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/q [...] discards c823f1e09366 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards c89a271b2fd5 431: onsuccess: #2255: 1: Success after binutils/gcc/linux [...] discards eb7416882963 430: onsuccess: #2254: 1: Success after binutils/gcc/linux [...] discards d28739e7a6cf 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc [...] discards 2b6c43406267 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards ff532c5284b5 427: onsuccess: #2251: 1: Success after binutils/gcc/linux [...] discards c7007d52699c 426: onsuccess: #2250: 1: Success after binutils/linux/gdb [...] discards 5798cf973938 425: onsuccess: #2249: 1: Success after binutils/gcc/linux [...] discards 28826a1fd539 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards bc5e694fdd52 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 34229cd20f85 422: onsuccess: #2246: 1: Success after binutils/gcc/linux [...] discards eb4fb35ce117 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc [...] discards d31839fed16c 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 998e3db853b7 419: onsuccess: #2243: 1: Success after binutils/gcc/linux [...] discards b399885ceac5 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: [...] discards ba41ef8712c6 417: onsuccess: #2238: 1: Success after binutils/gcc/linux [...] discards 59addd947ce1 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc [...] discards 85bf12c24b7f 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: [...] discards 660ff6fd3ab9 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: [...] discards 8c61a295dd08 413: onsuccess: #2234: 1: Success after binutils/gcc/linux [...] discards c712774e6542 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc [...] discards 55e4f10026ca 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 93f8d593434f 410: onsuccess: #2231: 1: Success after binutils/gcc/linux [...] discards 7b6abc0d3190 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc [...] discards e5c0cd96150b 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: [...] discards 8785d3c1ded2 407: onsuccess: #2228: 1: Success after binutils/gcc/linux [...] discards 446f27d60682 406: onsuccess: #2227: 1: Success after binutils/linux/gli [...] discards 36319a7a8a30 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 6884b69a4543 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: [...] discards 63d8dd71d7ce 403: onsuccess: #2224: 1: Success after binutils/gcc/linux [...] discards f71cd5fc5a23 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: [...] discards aeac2f5ac207 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: [...] discards 4a8bf8d89a03 400: onsuccess: #2221: 1: Success after binutils/gcc/linux [...] discards cf16b5c68527 399: onsuccess: #2220: 1: Success after binutils/gcc/linux [...] discards 0eb5bc717b1d 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/q [...] discards 142fd80955c9 397: onsuccess: #2218: 1: Success after binutils/gcc/linux [...] discards 0a8f50a2eb8b 396: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 4bb7fc89503a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux [...] discards fdca201181ea 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: [...] discards c78c5ad22f19 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: [...] discards f8baffb5c6ed 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc [...] discards 9018603eb5e6 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/q [...] discards 6da003a36bf7 390: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards 962dabfa7d86 389: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 244f06f1d58e 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc [...] discards 6a53eca3aaaf 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 75896889604f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards b292602247c4 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc [...] discards 591a2fe4d0be 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards f511aa59eac4 383: onsuccess: #2204: 1: Success after binutils/gcc/linux [...] discards 26202b26fbe9 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 0955238bd104 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17 [...] discards fd33f305b7ae 380: onsuccess: #2201: 1: Success after binutils/gcc/linux [...] discards 906f051b8849 379: onsuccess: #2200: 1: Success after binutils/gcc/linux [...] new f5bd2a9d98a1 379: onsuccess: #2200: 1: Success after binutils/gcc/linux [...] new eb6cd7ce1655 380: onsuccess: #2201: 1: Success after binutils/gcc/linux [...] new f1baeb385135 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17 [...] new 495aa8c4abed 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 575d32427bb9 383: onsuccess: #2204: 1: Success after binutils/gcc/linux [...] new 4d45e7d5afec 384: onsuccess: #2205: 1: Success after gcc: 2 commits new f3ca1cb99f24 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc [...] new 5c02b7c0872e 386: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new 5db24cb5fe51 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 7b2d4e4097d3 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc [...] new 1737e9b525ae 389: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new bc64c52ed0c0 390: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new c7c61ed4957a 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/q [...] new 64389f18c1b7 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc [...] new ac09befe64e2 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: [...] new f6abc8afc5cf 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: [...] new c0ef7a7fc49a 395: onsuccess: #2216: 1: Success after binutils/gcc/linux [...] new 4756349462dd 396: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new 4b73e6fdf7f2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux [...] new 14a53140e637 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/q [...] new 3ba4c133bee4 399: onsuccess: #2220: 1: Success after binutils/gcc/linux [...] new 41f7d4c722f3 400: onsuccess: #2221: 1: Success after binutils/gcc/linux [...] new d9fc5ff7d5a1 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: [...] new b50241c58c94 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: [...] new 052b62f4ab87 403: onsuccess: #2224: 1: Success after binutils/gcc/linux [...] new 16a7d39848c7 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: [...] new 23310fe0ea35 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new e63b1a7365a4 406: onsuccess: #2227: 1: Success after binutils/linux/gli [...] new ce50fdd894eb 407: onsuccess: #2228: 1: Success after binutils/gcc/linux [...] new be401e0293a1 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: [...] new 47df77a7c87b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc [...] new b761f5fea846 410: onsuccess: #2231: 1: Success after binutils/gcc/linux [...] new 9ae2100c36be 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 290b9304b182 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc [...] new a8653090654e 413: onsuccess: #2234: 1: Success after binutils/gcc/linux [...] new 2faa86eef4bf 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: [...] new 8cc8e604fd2e 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: [...] new 8ee6de7afc04 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc [...] new 21582605feaf 417: onsuccess: #2238: 1: Success after binutils/gcc/linux [...] new d1b7bacdbd90 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: [...] new 7015abdd6e66 419: onsuccess: #2243: 1: Success after binutils/gcc/linux [...] new 41a89b97b2b9 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 9de9f38c97e4 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc [...] new 70d70b4b4794 422: onsuccess: #2246: 1: Success after binutils/gcc/linux [...] new 04eaf65497f3 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new e0fd984e6bef 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 76ef75c6e0c2 425: onsuccess: #2249: 1: Success after binutils/gcc/linux [...] new 9a9b2277645b 426: onsuccess: #2250: 1: Success after binutils/linux/gdb [...] new de5068b058ca 427: onsuccess: #2251: 1: Success after binutils/gcc/linux [...] new ad05bd671706 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 09cb50221099 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc [...] new 112e4e1051f7 430: onsuccess: #2254: 1: Success after binutils/gcc/linux [...] new 68f5757b8bdf 431: onsuccess: #2255: 1: Success after binutils/gcc/linux [...] new 2ee2ccd65064 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new f34a1ef5d807 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/q [...] new a433522081b4 434: onsuccess: #2258: 1: Success after binutils/gcc/linux [...] new 597275ff6204 435: onsuccess: #2259: 1: Success after binutils/gcc/linux [...] new a247f378238e 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 511d60ee0889 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc [...] new 55b4c5e4c8af 438: onsuccess: #2263: 1: Success after binutils/gcc/linux [...] new bf1ca130f2a9 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: [...] new 1ec5f7579df4 440: onsuccess: #2265: 1: Success after binutils/gcc/linux [...] new 1ac6da3265f5 441: onsuccess: #2266: 1: Success after binutils/gcc/linux [...] new 6951010331a8 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gd [...] new 06749ddc93e7 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] new 16b3e8180eaf 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 3d1a2e67ffbf 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new ca3591c36994 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 0f6d44e2e75a 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new fcf31f23b6a4 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 9c7acdffe932 449: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 512fc006c24a 450: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 8a23bb5c5e8a 451: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 7a5d2c246223 452: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 366c9186c286 453: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 27e46a8d5693 454: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new cbd73adaadff 455: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 478485020703 456: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new e83260061b77 457: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new d89eb1d7284f 458: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new c768f56deca7 459: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 07fbb6f26883 460: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new 8e5fd3f43007 461: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] new bd29f86263e4 462: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] new 4b21a1ae8230 463: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] new 6122c7a50af1 464: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new b8f006d6d756 465: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 6e947bffa83d 466: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 3dd8826bedd2 467: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 66dd0c77fe32 468: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new e9750c20df5b 469: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 5315a073d0f7 470: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new c2a243ab417d 471: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new a46ef1b6bd76 472: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 4339c9497b12 473: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 820845e70a4a 474: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 34a1600163c3 475: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new a17a9bc74c3b 476: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 9f601196e531 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 7b4d846d4da9 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new 445c79752825 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 2757737fcef6 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/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 (94e529744e7e) \ 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 2136 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 26772 -> 26976 bytes 04-build_abe-stage1/console.log.xz | Bin 89060 -> 88992 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8436 -> 8904 bytes 07-build_abe-glibc/console.log.xz | Bin 232384 -> 233240 bytes 08-build_abe-stage2/console.log.xz | Bin 224540 -> 225248 bytes 09-build_abe-gdb/console.log.xz | Bin 34248 -> 34116 bytes 10-build_abe-qemu/console.log.xz | Bin 31108 -> 32184 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3868 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6492 -> 6500 bytes 13-check_regression/console.log.xz | Bin 6520 -> 6400 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 6 +- 13-check_regression/results.compare | 33 +- 13-check_regression/results.compare2 | 108 +- 13-check_regression/results.regressions | 33 +- 14-update_baseline/console.log | 68 +- 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/changes-list-long.txt | 57 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 44 +- manifest.sh | 46 +- results | 33 +- sumfiles/g++.log.sep.xz | Bin 144528 -> 157276 bytes sumfiles/g++.log.xz | Bin 2685780 -> 2653820 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 13436 +++++++++++++++++++++++++++++- sumfiles/gcc.log.sep.xz | Bin 166644 -> 135160 bytes sumfiles/gcc.log.xz | Bin 2209880 -> 2210344 bytes sumfiles/gcc.sum | 10 +- sumfiles/gcc.sum.sep | 12243 +++++++-------------------- sumfiles/gfortran.log.sep.xz | Bin 56424 -> 56768 bytes sumfiles/gfortran.log.xz | Bin 901508 -> 915400 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 3777 +-------- sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217224 -> 217180 bytes sumfiles/libgomp.sum | 8 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 13072 -> 16264 bytes sumfiles/libstdc++.log.xz | Bin 446344 -> 440680 bytes sumfiles/libstdc++.sum | 4 +- sumfiles/libstdc++.sum.sep | 491 +- 53 files changed, 16619 insertions(+), 13804 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (b1f6cb2cc3a -> 87d3bc53b17)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from b1f6cb2cc3a aarch64, builtins: Include PR registers in FUNCTION_ARG_REG [...] new 87d3bc53b17 testsuite: Add testcase for already fixed PR [PR109362] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/testsuite/gcc.target/i386/pr109362.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 gcc/testsuite/gcc.target/i386/pr109362.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (fc4cde2e6aa -> b1f6cb2cc3a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from fc4cde2e6aa c++,coroutines: Stabilize names of promoted slot vars [PR101118]. new b1f6cb2cc3a aarch64, builtins: Include PR registers in FUNCTION_ARG_REG [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/builtins.cc | 38 ++++++++++++++----------- gcc/config/aarch64/aarch64.cc | 10 ++++++- gcc/doc/tm.texi | 6 ++-- gcc/target.def | 6 ++-- gcc/testsuite/gcc.target/aarch64/sve/pr109254.c | 27 ++++++++++++++++++ 5 files changed, 65 insertions(+), 22 deletions(-) create mode 100644 gcc/testsuite/gcc.target/aarch64/sve/pr109254.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig updated (54abf00bb7cd -> 129507524c4a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig in repository toolchain/ci/base-artifacts. from 54abf00bb7cd 51: onsuccess: #8: all: Success after binutils/gcc/linux/q [...] new 129507524c4a 52: onsuccess: #9: all: [TCWG CI] Success after binutils/g [...] 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 2016 -> 1992 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2556 bytes 03-build_abe-binutils/console.log.xz | Bin 26888 -> 27056 bytes 04-build_abe-stage1/console.log.xz | Bin 90276 -> 89268 bytes 05-build_abe-qemu/console.log.xz | Bin 32248 -> 32268 bytes 06-build_linux/console.log.xz | Bin 3672 -> 4144 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4252 -> 4256 bytes 08-check_regression/mail-body.txt | 27 --------------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 27 --------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 23 files changed, 50 insertions(+), 78 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig updated (93e9f654cfeb -> 8cd2400b27cd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 93e9f654cfeb 54: onsuccess: #8: boot: Success after binutils/llvm/linux [...] new 8cd2400b27cd 55: onsuccess: #9: boot: [TCWG CI] Success after binutils/ [...] 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 2008 -> 2000 bytes 02-prepare_abe/console.log.xz | Bin 2580 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 27204 -> 27276 bytes 04-build_kernel_llvm/console.log.xz | Bin 66808 -> 67516 bytes 05-build_abe-qemu/console.log.xz | Bin 32632 -> 32748 bytes 06-build_linux/console.log.xz | Bin 2968 -> 2932 bytes 08-check_regression/console.log.xz | Bin 4316 -> 4252 bytes 08-check_regression/mail-body.txt | 31 ------------------------------- 08-check_regression/mail-subject.txt | 1 - dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 31 ------------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 21 files changed, 49 insertions(+), 85 deletions(-) delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (8c5fcdf3d77f -> 830bd4232ddc)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 8c5fcdf3d77f 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] discards a91f42a7caa3 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] discards 6c5155b9aca1 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 295f860a08d4 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] discards 83e33a205d0a 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] discards c22a07fe7a88 234: force: #94: 1: [TCWG CI] Success after baseline build [...] discards 6bb4e1f2bd70 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 511b76ef1022 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards 32135e15af07 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 7afcf500751e 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 41d5826a9bb9 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] discards 43d3544f6801 228: force: #74: 1: Success after gdb: 53 commits discards c84966425239 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] discards 90a9db0cd72a 226: force: #70: 1: Success after baseline build: no new commits discards 25e2073685dc 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] discards 4748967759a1 224: force: #65: 1: Success after gdb: 50 commits discards b7cbf7f89df4 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] discards 5768d3ecf949 222: force: #60: 1: Success after gdb: 16 commits discards 60346fa4dc71 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] discards 172b07407671 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] discards 95ea9bae8af8 219: force: #50: 1: Failure after linux: 2520 commits discards abbac74f23d8 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] discards c2c0a476f2a0 217: force: #45: 1: Success after linux: 1 commits discards 7572bbfccc51 216: force: #43: : Failure after baseline build: no new commits discards be993ca1b4e7 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] discards e66c191253b4 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] discards 3bbca6920423 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 100eea69d371 212: force: #27: : Failure after baseline build: no new commits discards f353086c4313 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 1fc7ddedbe24 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 53ac80926169 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 5c65bc8db320 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 9bfcfd1bb9b5 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards a8912191322d 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards d98b644023e8 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 834f4a0e6153 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 4acb450ffba0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards a8d1cce6d35f 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 93590810eb8d 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 6f6b20470fad 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards d6bf9c275f7f 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards d5d0025aeafd 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards b0bf2fe5f3dc 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 2306fd7da317 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 84e0fd65fa27 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 19f7def1c5c7 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards eb666fd30a77 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 6d051733dc37 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 90db83998bbe 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards dc6d4e1e94f5 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards 82df5fe862ba 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] discards 52fb5c72f033 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] discards e88b8579be09 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] discards 5697dafc3769 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] discards bc826aa4af9f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] discards 8ec0628eea99 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] discards 8b81ddb9e2ed 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards c42a05c581cd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 734d69f16247 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 4555ae3a28f5 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] discards 7c18f866b161 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] discards 6abc623b512a 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards 2bed97b67a88 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 0c388df119ee 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards ab6f3fdf5542 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 482d5ff020f8 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards eade72232b9c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] discards 5242a978e206 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 503fb180f707 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards 0fdff9decae5 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] discards bd964fa63d14 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards dbed5ebd8cf9 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 54d4b227aff7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards cddb37622ae5 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards d34271741081 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 81741fc34f37 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] discards c4d76783baba 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards f3c552250231 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards a670d6b27385 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards 997558a957da 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards cdc72024e826 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards e7746e57d8ab 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 672c36f70305 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards 116b71a1fb5d 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 4b71fe2ba39f 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 4c20c6682195 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] discards 5de30ca361e5 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards 01bc8c4ecc22 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] discards 7a885ffddb13 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards d17cab436e1b 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 0fef25718c14 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 470b9ec999f2 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] discards 94a6521008ae 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] discards 3c09f69953a6 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] discards 8cd20ee15849 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards ceb97f998242 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] discards cbe57da44734 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 340e46a15e20 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards 05e705b0e85e 141: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] discards 991f70c4cae1 140: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 9c102dba47c9 139: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] new c9a5b48e09b1 139: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] new 4c55a30eb2a0 140: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new 48b6c40be3e0 141: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new 967f3d86f25b 142: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new edad504ab634 143: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new ab6c80a0365e 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 4 [...] new 5ab84afe6479 145: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new 4544e3fed7f9 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 3 [...] new fbf30774a7a9 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 1 [...] new 59994cc11108 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 [...] new 58be614ee2d0 149: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new 10dd3067f3fd 150: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new 15a097580b2b 151: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 1ef9612ebaa9 152: onsuccess: #645: 1: Success after binutils/gcc/linux/ [...] new 3e1f291fa7b0 153: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new 1c0ab08f9b5d 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/ [...] new 3c63b6cbf7e5 155: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 6a3e110e8269 156: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new a41033d8e413 157: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new b434f6e76b58 158: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new d742f75b4db6 159: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new 85656c178cb3 160: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new 6b99432bee12 161: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new ffad631c376c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new c77680da417d 163: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 3523b0f7923d 164: onsuccess: #658: 1: Success after binutils/gcc/linux/ [...] new f623a1690deb 165: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 2aacd5b75f82 166: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 6942cbeaf16b 167: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 2685648dab64 168: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new f66daa20d650 169: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new 9b05534e21f6 170: onsuccess: #664: 1: Success after binutils/gcc/linux/ [...] new 0be9ce601a04 171: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new e20a653aaaef 172: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new 66fb50090f4b 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 1 [...] new f89cd2cdced4 174: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new 40860c8b10e2 175: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new faf34ee571a5 176: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new f48eef2d52b8 177: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 684d6a68a041 178: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new 712c3e2c0675 179: onsuccess: #673: 1: Success after binutils/gcc/linux/ [...] new ba18729c6b2e 180: onsuccess: #674: 1: Success after binutils/gcc/linux/ [...] new 7c48f05e4407 181: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 8229140e012d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new 9d720aba4b20 183: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new 40935ecb117b 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/ [...] new 60e962bbee17 185: onsuccess: #679: 1: Success after binutils/gcc/linux/ [...] new 94df4eac9c89 186: onsuccess: #680: 1: Success after binutils/gcc/linux/ [...] new 3e5990f61cc1 187: onsuccess: #681: 1: Success after binutils/gcc/linux/ [...] new 9919819c4bc4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/ [...] new c92d09fba0b7 189: onsuccess: #683: 1: Success after binutils/gcc/linux/ [...] new 81db6cddfb53 190: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new aa2eed0f9234 191: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new ce809ed13256 192: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new d1a1f5230851 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 4eb034886966 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 89e43cafab85 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 7a4c1a730129 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new c7b0a3c65f6a 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 62af980f6c36 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 8e23140c6243 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new eaf31af96e6b 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 760ef24737c4 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 491f268bd92c 202: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new fed0cdc9cbd6 203: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 3bfa4ee71ba7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 00c2064d38f7 205: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 7bcd5c473a13 206: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 8ebd423fe30c 207: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 856be801a26f 208: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 35581d745958 209: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new d768711ed50f 210: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new f220f18cd0f7 211: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 08e6c299ad28 212: force: #27: : Failure after baseline build: no new commits new f52648ae012e 213: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 29f59e394465 214: force: #39: 1: Failure after gdb-13-branchpoint-1470- [...] new 801e6c698ae8 215: force: #41: 1: Failure after gdb-13-branchpoint-1470- [...] new a2f964d80722 216: force: #43: : Failure after baseline build: no new commits new 539268ac3b2b 217: force: #45: 1: Success after linux: 1 commits new 2d25b307b7ad 218: force: #48: 1: Success after gdb-13-branchpoint-1471- [...] new 0f4d2e2d8b8f 219: force: #50: 1: Failure after linux: 2520 commits new f8d02b9a0bfb 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02d [...] new 2410ff2bcf15 221: force: #53: 1: Success after gdb-13-branchpoint-1472- [...] new 90e5130d400d 222: force: #60: 1: Success after gdb: 16 commits new a9701e3431d1 223: force: #63: 1: Failure after gdb-13-branchpoint-1489- [...] new b3c7fd7a24f7 224: force: #65: 1: Success after gdb: 50 commits new f69c7f068f59 225: force: #68: 1: Failure after gdb-13-branchpoint-1540- [...] new 6fbfb3c18ce1 226: force: #70: 1: Success after baseline build: no new commits new 0e3370469341 227: onsuccess: #72: 1: Success after binutils/gcc/linux/g [...] new 94d6c3973ef5 228: force: #74: 1: Success after gdb: 53 commits new 1df70db361d7 229: force: #77: 1: Failure after gdb-13-branchpoint-1594- [...] new 4c361e924857 230: onsuccess: #78: 1: Success after gdb: 2 commits new a211fb4469e4 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new a5626c41d5d3 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchp [...] new cad3d51eed43 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 4dd2dc54d919 234: force: #94: 1: [TCWG CI] Success after baseline build [...] new 7ccf7bef045d 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/g [...] new 12d21cab34e9 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: [...] new ed40e0835daf 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new bb41510f5793 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branch [...] new dfa796455c7c 239: force: #106: 1: [TCWG CI] Success after baseline buil [...] new 830bd4232ddc 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/ [...] 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 (8c5fcdf3d77f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2268 -> 2096 bytes 02-prepare_abe/console.log.xz | Bin 2512 -> 2536 bytes 03-build_abe-binutils/console.log.xz | Bin 48824 -> 48924 bytes 04-build_abe-gcc/console.log.xz | Bin 234820 -> 235412 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8688 -> 8880 bytes 07-build_abe-glibc/console.log.xz | Bin 234652 -> 232296 bytes 08-build_abe-gdb/console.log.xz | Bin 47836 -> 47296 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3788 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4616 -> 4352 bytes 11-check_regression/console.log.xz | Bin 2808 -> 17500 bytes 11-check_regression/results.compare | 15 +- 11-check_regression/results.compare2 | 4675 ++++++++++++++++- 12-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/changes-list-long.txt | 32 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 15 +- manifest.sh | 35 +- sumfiles/gdb.log.0.xz | Bin 2882236 -> 2928340 bytes sumfiles/gdb.log.1.xz | Bin 143620 -> 180604 bytes sumfiles/gdb.log.10.xz | Bin 9928 -> 10292 bytes sumfiles/gdb.log.2.xz | Bin 15536 -> 11800 bytes sumfiles/gdb.log.3.xz | Bin 10336 -> 10184 bytes sumfiles/gdb.log.4.xz | Bin 10284 -> 10156 bytes sumfiles/gdb.log.5.xz | Bin 10348 -> 10252 bytes sumfiles/gdb.log.6.xz | Bin 10152 -> 10264 bytes sumfiles/gdb.log.7.xz | Bin 10392 -> 10260 bytes sumfiles/gdb.log.8.xz | Bin 10072 -> 10088 bytes sumfiles/gdb.log.9.xz | Bin 10300 -> 9968 bytes sumfiles/gdb.sum | 5305 +++---------------- sumfiles/gdb.sum.0 | 5314 +++---------------- sumfiles/gdb.sum.1 | 9053 +++++++++++++++++++++++++++++++-- sumfiles/gdb.sum.10 | 22 +- sumfiles/gdb.sum.2 | 189 +- sumfiles/gdb.sum.3 | 74 +- sumfiles/gdb.sum.4 | 50 +- sumfiles/gdb.sum.5 | 39 +- sumfiles/gdb.sum.6 | 28 +- sumfiles/gdb.sum.7 | 64 +- sumfiles/gdb.sum.8 | 11 +- sumfiles/gdb.sum.9 | 25 +- 47 files changed, 14859 insertions(+), 10171 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (3fb84bee3ce8 -> 7ecc1574e85f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 3fb84bee3ce8 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits discards 6908e44a0244 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] discards 59e59962646b 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits discards 98875f115742 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits discards 3ae4d51ca1b1 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards c2937038e2a4 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits discards 248a2b7e9485 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] discards b0cfa4e19572 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits discards fd0e0b766534 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] discards aeaa8fcb022c 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits discards c88b3b08ac09 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] discards 65a5defdb77a 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] discards a9f102a63588 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] discards dc0a211a75d6 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] discards d91c6d29748a 214: onsuccess: #47: 1: Success after gdb: 21 commits discards 4a2f6406d88f 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] discards 9150b920f1f4 212: force: #45: 1: Success after gdb: 22 commits discards d166dbde0d98 211: onsuccess: #44: 1: Success after linux: 26 commits discards 2093807724ba 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] discards 5ea1c5467bc2 209: force: #37: 1: Success after baseline build: no new commits discards ba7e6759a53d 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards bf3947d52e8b 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 2458a559aa5c 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards a58cc6a9fbe3 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards ebde23a34ebc 204: force: #26: : Failure after baseline build: no new commits discards 5670fdb0a77d 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 85bbe575d6a9 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 2f904b59c708 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 67cc19dc9779 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 84b07eb740ab 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 33c4829406a8 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 30b042824b2d 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 3c2265760214 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards 12ce94584362 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 3e0a01e8ab71 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards f62913402602 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 5d360aa1ca8c 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 8d057f8da6c8 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 87395cf1a29e 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards a12ba7379ad4 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 8af782226d2e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards de6bc5237da0 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 83a849fd965b 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 24b04c7f5a8f 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 66775a029667 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] discards e7e55d04a5bc 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] discards 36ceec0ca1a8 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] discards ecc0631ced26 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] discards bd2223afe89d 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] discards 2c2ec98072ab 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] discards 056e22693dae 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] discards b886cbd04f71 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] discards 706eb7db421b 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] discards 356bf12ae1b0 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] discards 7f6a2041bb0f 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] discards 7bea4149db59 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] discards 91362c145529 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] discards d6d0b7614737 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] discards 1756fdf53499 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] discards 8ffdc900e376 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] discards bce3d5d7ffb6 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] discards 482d075727ae 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] discards 70ab0c6eeb45 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] discards c6c73bb0f214 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] discards b53fcb00bd77 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] discards c97d91b1b8d9 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] discards c12c042474d7 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] discards 941a380a09dc 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] discards 3a8ff0f19473 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] discards 183a76831dd6 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] discards 9a2e39ff7379 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards eb05b2c6bac9 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] discards f778db52357f 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] discards 897c3f99ab92 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] discards 93e529d892a5 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] discards d221bd51c6f8 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] discards ba6da5e5d4f8 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] discards 2ad0b6a99bd5 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] discards c6fef5e0cb60 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] discards e9471910ebcc 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] discards adb164e34f65 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] discards 22870d3027c6 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] discards c53d9c6c285d 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] discards 358fab7d1a5c 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] discards 7f28c98928af 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] discards be9335eb2015 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] discards e24ce74b0302 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] discards 77255adb4423 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] discards 39b13930233c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] discards 6eccaf3f7996 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] discards ed9de0cd33e6 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] discards 731c2b171822 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] discards f73de1225937 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] discards 793a4913cc79 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] discards 913e63d30351 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] discards 6e28b8638d73 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] discards 1020dd4bd54a 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] discards c2bec719f60a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] discards 3f8198b3ed37 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] discards 812b839efe06 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] discards 15c2a445f6f4 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new 4de7a6f29f3b 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/ [...] new 88b47c34dd85 129: onsuccess: #916: 1: Success after binutils/gcc/linux/ [...] new ab1d9fad2462 130: onsuccess: #917: 1: Success after binutils/gcc/linux/ [...] new 4d3a1fac313a 131: onsuccess: #918: 1: Success after binutils/gcc/linux/ [...] new 67199cfd71eb 132: onsuccess: #919: 1: Success after binutils/gcc/linux/ [...] new f8cccfc19e90 133: onsuccess: #920: 1: Success after binutils/gcc/linux/ [...] new 82d020e7845c 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 2 [...] new 98e105ac577c 135: onsuccess: #922: 1: Success after binutils/gcc/linux/ [...] new 07a11cd5a27a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 1 [...] new 753e3aaba1bd 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 4 [...] new cab21e0a1f12 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 1 [...] new 5536e00e3b46 139: onsuccess: #926: 1: Success after binutils/gcc/linux/ [...] new 82fe22aac55c 140: onsuccess: #927: 1: Success after binutils/gcc/linux/ [...] new 8359791166ec 141: onsuccess: #928: 1: Success after binutils/gcc/linux/ [...] new ea1085747924 142: onsuccess: #929: 1: Success after binutils/gcc/linux/ [...] new 0ae7cd229af2 143: onsuccess: #931: 1: Success after binutils/gcc/linux/ [...] new 468f793666d3 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/ [...] new 890484fc79dd 145: onsuccess: #934: 1: Success after binutils/gcc/linux/ [...] new 253cc446fca0 146: onsuccess: #939: 1: Success after binutils/gcc/linux/ [...] new 9200a6fc3076 147: onsuccess: #940: 1: Success after binutils/gcc/linux/ [...] new 89f579dc7189 148: onsuccess: #941: 1: Success after binutils/gcc/linux/ [...] new fc6eee693e2e 149: onsuccess: #942: 1: Success after binutils/gcc/linux/ [...] new d822aa57fbe6 150: onsuccess: #943: 1: Success after binutils/gcc/linux/ [...] new 42bbe56133fa 151: onsuccess: #944: 1: Success after binutils/gcc/linux/ [...] new d72100dc8913 152: onsuccess: #945: 1: Success after binutils/gcc/linux/ [...] new 0f4a3d20c172 153: onsuccess: #946: 1: Success after binutils/gcc/linux/ [...] new 1ed78ffc4996 154: onsuccess: #947: 1: Success after binutils/gcc/linux/ [...] new 8523afc74e1c 155: onsuccess: #948: 1: Success after binutils/gcc/linux/ [...] new 347c10dded7d 156: onsuccess: #949: 1: Success after binutils/gcc/linux/ [...] new e79783c7fa25 157: onsuccess: #950: 1: Success after binutils/gcc/linux/ [...] new 2e29b22a6e58 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 70a6fdf0a6b2 159: onsuccess: #952: 1: Success after binutils/gcc/linux/ [...] new 786c61dbc15f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/ [...] new fff8aa701cfd 161: onsuccess: #954: 1: Success after binutils/gcc/linux/ [...] new 1ace0f123bbc 162: onsuccess: #955: 1: Success after binutils/gcc/linux/ [...] new 4a439ee48ee7 163: onsuccess: #956: 1: Success after binutils/gcc/linux/ [...] new a9f8eaeb1107 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/ [...] new a437e1285dfb 165: onsuccess: #958: 1: Success after binutils/gcc/linux/ [...] new a236efcacde7 166: onsuccess: #959: 1: Success after binutils/gcc/linux/ [...] new 6f3105b22c52 167: onsuccess: #960: 1: Success after binutils/gcc/linux/ [...] new e55518160372 168: onsuccess: #961: 1: Success after binutils/gcc/linux/ [...] new e8f5e4266e53 169: onsuccess: #962: 1: Success after binutils/gcc/linux/ [...] new 5b2b0dd8e4eb 170: onsuccess: #963: 1: Success after binutils/gcc/linux/ [...] new 8645035098a4 171: onsuccess: #964: 1: Success after binutils/gcc/linux/ [...] new 6629081f18e1 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/ [...] new 686be765f250 173: onsuccess: #966: 1: Success after binutils/gcc/linux/ [...] new 18a0a1601a26 174: onsuccess: #967: 1: Success after binutils/gcc/linux/ [...] new bf43b75a04a8 175: onsuccess: #968: 1: Success after binutils/gcc/linux/ [...] new e81959c49923 176: onsuccess: #969: 1: Success after binutils/gcc/linux/ [...] new f891305674ac 177: onsuccess: #970: 1: Success after binutils/gcc/linux/ [...] new c23a0b97d344 178: onsuccess: #971: 1: Success after binutils/gcc/linux/ [...] new 03722e53aa40 179: onsuccess: #972: 1: Success after binutils/gcc/linux/ [...] new dd5b10edb04c 180: onsuccess: #973: 1: Success after binutils/gcc/linux/ [...] new e5c782a23fb3 181: onsuccess: #974: 1: Success after binutils/gcc/linux/ [...] new 8a32f0884133 182: onsuccess: #975: 1: Success after binutils/gcc/linux/ [...] new 34afe9c6e5ab 183: onsuccess: #976: 1: Success after binutils/gcc/linux/ [...] new 543a4fd46cb4 184: onsuccess: #977: 1: Success after binutils/gcc/linux/ [...] new 939068335f2a 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 5af33df8d140 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 0ca5adde29ae 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 7f47352985a0 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 3edd21631015 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 51ff15636cbf 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 7c8032a5156a 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 5ac0aa10f5a4 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new 990a27225eed 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 83ca4de00c5c 194: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new ba04a9a2cdc2 195: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 05e9083f514c 196: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 59f12fb10c0d 197: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new adaff965424b 198: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new f881a021feaf 199: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new a3a55313b5eb 200: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 30c5c636d427 201: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 9f8d538c715f 202: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new c9e6a3537883 203: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 2a8757120581 204: force: #26: : Failure after baseline build: no new commits new 3b8bd7ea5209 205: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 8d530a0421ad 206: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new ada70eb46777 207: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 2b97604b8cda 208: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 7fd204e3b71b 209: force: #37: 1: Success after baseline build: no new commits new 79a26079be0b 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181- [...] new 5af530afb69e 211: onsuccess: #44: 1: Success after linux: 26 commits new 9d106def91ec 212: force: #45: 1: Success after gdb: 22 commits new 42b4c98a2cb4 213: force: #46: 1: Success after gdb-13-branchpoint-1550- [...] new 6053efd77ae3 214: onsuccess: #47: 1: Success after gdb: 21 commits new 1b9836f4da8e 215: onsuccess: #48: 1: Success after binutils/gcc/linux/g [...] new 9685e5391f32 216: onsuccess: #52: 1: Success after binutils/gcc/linux/g [...] new e98c0e8748ad 217: onsuccess: #53: 1: Success after binutils/gcc/linux/g [...] new 8af88ee8df2b 218: onsuccess: #62: 1: [TCWG CI] Success after binutils/g [...] new 2be84e0c7414 219: force: #64: 1: [TCWG CI] Success after gdb: 32 commits new 6ce77e251927 220: force: #65: 1: [TCWG CI] Failure after gdb-13-branchp [...] new ee5e90389884 221: onsuccess: #66: 1: [TCWG CI] Success after gdb: 17 commits new 1a80bc87a160 222: onsuccess: #68: 1: [TCWG CI] Success after binutils/g [...] new 839ffd04f3fd 223: force: #70: 1: [TCWG CI] Success after gdb: 18 commits new 4693983d28e9 224: force: #71: 1: [TCWG CI] Failure after gdb-13-branchp [...] new 5a031576649d 225: onsuccess: #72: 1: [TCWG CI] Success after gdb: 13 commits new 23b4c978eb03 226: onsuccess: #78: 1: [TCWG CI] Success after gcc: 28 commits new d8d8bcbef2d1 227: force: #81: 1: [TCWG CI] Failure after baseline build [...] new 2b3e49de12a1 228: force: #82: 1: [TCWG CI] Success after glibc: 4 commits new 7ecc1574e85f 229: force: #83: 1: [TCWG CI] Success after glibc-2.37.900 [...] 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 (3fb84bee3ce8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2060 -> 1980 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2492 bytes 03-build_abe-binutils/console.log.xz | Bin 35736 -> 35756 bytes 04-build_abe-gcc/console.log.xz | Bin 204072 -> 204128 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 8680 bytes 07-build_abe-glibc/console.log.xz | Bin 241164 -> 240872 bytes 08-build_abe-gdb/console.log.xz | Bin 35476 -> 35292 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3252 -> 3196 bytes 11-check_regression/console.log.xz | Bin 3232 -> 2900 bytes 11-check_regression/results.compare | 14 ------------ 12-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 9 ++++---- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 15 +++++++------ manifest.sh | 14 ++++++------ sumfiles/gdb.log.0.xz | Bin 1941444 -> 1938664 bytes sumfiles/gdb.log.1.xz | Bin 22152 -> 22164 bytes sumfiles/gdb.log.2.xz | Bin 5436 -> 5708 bytes sumfiles/gdb.log.3.xz | Bin 5504 -> 5660 bytes sumfiles/gdb.sum | 7 +++--- sumfiles/gdb.sum.0 | 7 +++--- sumfiles/gdb.sum.1 | 2 +- sumfiles/gdb.sum.2 | 2 +- sumfiles/gdb.sum.3 | 2 +- 27 files changed, 51 insertions(+), 67 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023