Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-next-allyesconfig updated (05dba627889 -> 178f2bd2cf1)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from 05dba627889 82: onsuccess: #5: all: Success after binutils/llvm/linux/q [...] new 178f2bd2cf1 83: onsuccess: #7: all: Success after binutils/llvm/qemu: 6 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30624 -> 30932 bytes 04-build_kernel_llvm/console.log.xz | Bin 66368 -> 64372 bytes 05-build_abe-qemu/console.log.xz | Bin 30472 -> 31928 bytes 06-build_linux/console.log.xz | Bin 3344 -> 3436 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4364 -> 3784 bytes 08-check_regression/mail-body.txt | 4 +++- 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 6 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 31 +++++++++++++++---------------- 18 files changed, 28 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig updated (136b33bb141 -> f6fc1ae1ec0)

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 136b33bb141 55: onsuccess: #3: boot: Success after binutils/llvm/linux/ [...] new f6fc1ae1ec0 56: onsuccess: #4: boot: Success after binutils/llvm/qemu: [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1748 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30792 -> 30772 bytes 04-build_kernel_llvm/console.log.xz | Bin 65336 -> 67088 bytes 05-build_abe-qemu/console.log.xz | Bin 30760 -> 32752 bytes 06-build_linux/console.log.xz | Bin 3428 -> 3428 bytes 07-boot_linux/console.log.xz | Bin 5664 -> 5660 bytes 08-check_regression/console.log.xz | Bin 4320 -> 3840 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 17 files changed, 21 insertions(+), 30 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017fast/gnu-aarch64-master-Os updated (353e4bfccb4 -> b6926bb4703)

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_size-cpu2017fast/gnu-aarch64-master-Os in repository toolchain/ci/base-artifacts. from 353e4bfccb4 2: onsuccess: #3: 1: [TCWG CI] No change after binutils/gcc [...] new b6926bb4703 3: onsuccess: #4: 1: [TCWG CI] No change after binutils/gcc [...] 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 1788 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 31100 -> 31304 bytes 04-build_abe-stage1/console.log.xz | Bin 71176 -> 71492 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8660 -> 8608 bytes 07-build_abe-glibc/console.log.xz | Bin 244828 -> 244748 bytes 08-build_abe-stage2/console.log.xz | Bin 176080 -> 176108 bytes 09-benchmark/benchmark-build.log | 122 +- 09-benchmark/benchmark.log | 120 +- 09-benchmark/console.log.xz | Bin 3908 -> 4012 bytes .../compare-results-vs-first-internal.csv | 178 +- .../compare-results-vs-prev-internal.csv | 180 +- 10-check_regression/console.log.xz | Bin 12084 -> 11996 bytes .../csv-results-vs-first-1/md5sum.csv | 1759 ++++----- .../csv-results-vs-first-1/perf.csv | 2894 ++++++++------- .../csv-results-vs-first-1/results.csv | 3827 ++++++++++---------- .../csv-results-vs-first-1/size.csv | 528 +-- .../csv-results-vs-prev-0/md5sum.csv | 1718 +++++---- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2883 ++++++++------- .../csv-results-vs-prev-0/results.csv | 3334 +++++++++-------- .../csv-results-vs-prev-1/md5sum.csv | 1759 ++++----- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2894 ++++++++------- .../csv-results-vs-prev-1/results.csv | 3827 ++++++++++---------- 10-check_regression/csv-results-vs-prev-1/size.csv | 528 +-- 10-check_regression/mail-body.txt | 2 +- 10-check_regression/results-vs-first-brief.csv | 50 +- 10-check_regression/results-vs-first-full.csv | 2880 ++++++++------- 10-check_regression/results-vs-first-internal.csv | 177 +- 10-check_regression/results-vs-first.csv | 177 +- 10-check_regression/results-vs-first.log | 1050 +++--- 10-check_regression/results-vs-prev-brief.csv | 50 +- 10-check_regression/results-vs-prev-compare.csv | 31 +- 10-check_regression/results-vs-prev-full.csv | 3138 ++++++++-------- 10-check_regression/results-vs-prev-internal.csv | 177 +- 10-check_regression/results-vs-prev.csv | 177 +- 10-check_regression/results-vs-prev.log | 1034 +++--- dashboard/dashboard-generate.sh | 2 +- .../508.namd_r/results-metadata.json | 14 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 14 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 14 +- .../511.povray_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 14 +- .../526.blender_r/results-metrics.json | 2 +- .../600.perlbench_s/results-metadata.json | 14 +- .../600.perlbench_s/results-metrics.json | 2 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 14 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 14 +- .../603.bwaves_s/results-metrics.json | 2 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 14 +- .../squad-vs-first/605.mcf_s/results-metrics.json | 2 +- .../607.cactuBSSN_s/results-metadata.json | 14 +- .../607.cactuBSSN_s/results-metrics.json | 2 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 14 +- .../squad-vs-first/619.lbm_s/results-metrics.json | 2 +- .../620.omnetpp_s/results-metadata.json | 14 +- .../620.omnetpp_s/results-metrics.json | 2 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 14 +- .../squad-vs-first/621.wrf_s/results-metrics.json | 2 +- .../623.xalancbmk_s/results-metadata.json | 14 +- .../623.xalancbmk_s/results-metrics.json | 2 +- .../625.x264_s/results-metadata.json | 14 +- .../squad-vs-first/625.x264_s/results-metrics.json | 2 +- .../627.cam4_s/results-metadata.json | 14 +- .../628.pop2_s/results-metadata.json | 14 +- .../squad-vs-first/628.pop2_s/results-metrics.json | 2 +- .../631.deepsjeng_s/results-metadata.json | 14 +- .../638.imagick_s/results-metadata.json | 14 +- .../638.imagick_s/results-metrics.json | 2 +- .../641.leela_s/results-metadata.json | 14 +- .../641.leela_s/results-metrics.json | 2 +- .../squad-vs-first/644.nab_s/results-metadata.json | 14 +- .../squad-vs-first/644.nab_s/results-metrics.json | 2 +- .../648.exchange2_s/results-metadata.json | 14 +- .../648.exchange2_s/results-metrics.json | 2 +- .../649.fotonik3d_s/results-metadata.json | 14 +- .../649.fotonik3d_s/results-metrics.json | 2 +- .../654.roms_s/results-metadata.json | 14 +- .../squad-vs-first/654.roms_s/results-metrics.json | 2 +- .../squad-vs-first/657.xz_s/results-metadata.json | 14 +- .../squad-vs-first/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 38 +- mail/mail-body.txt | 40 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 94 files changed, 18330 insertions(+), 17782 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-fujitsu_size-cpu2017fast/llvm-aarch64-master-O3 deleted (was d97fc7d2984)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch linaro-local/ci/tcwg_bmk-fujitsu_size-cpu2017fast/llvm-aarch64-master-O3 in repository toolchain/ci/base-artifacts. was d97fc7d2984 0: init: #2: -3: Success after baseline build: no new commits This change permanently discards the following revisions: discards d97fc7d2984 0: init: #2: -3: Success after baseline build: no new commits -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/llvm-arm-master-O3_VECT deleted (was 898c95105f8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. maxim.kuvyrkov pushed a change to branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/llvm-arm-master-O3_VECT in repository toolchain/ci/base-artifacts. was 898c95105f8 0: init: #1: -10: Success after baseline build: no new commits This change permanently discards the following revisions: discards 898c95105f8 0: init: #1: -10: Success after baseline build: no new commits -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (4b68c1013f8 -> 4727000a9f7)

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 4b68c1013f8 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 1d14b6eb890 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 16d110b9bcb 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 8457325587d 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 58dd246eb24 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards 26f79c7b872 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 9ec7c7a080e 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 607b61eed83 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards ec91e648029 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards a88e85af0ef 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards b7436129eda 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 01ae5a4349f 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 6ff7b35e38a 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 2fa15dc7a0d 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 7752127b861 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 58ffaf1eb5f 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards 6d403832eea 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards d7e3dcb78c0 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 26a128a0139 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards 33f5a985ecf 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 6d4118e51c0 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards 2cdaf214b17 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards d0ca5bc3052 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards cd87f71078f 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards ed0d3d9f45f 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 772dde776d7 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards f1da9ee633e 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 22b6bdc0949 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 8dc90a037bd 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards 21c5a43dc88 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards ee1e01e21d7 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards 77385aa9c68 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 7556eea1302 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards 1f81cbfcdf9 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards fe69aae6367 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards d79a5693aff 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards 602474d93de 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards 8d5adfc781b 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 2eab24fcb70 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards c97b9961779 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards c1ac11f3f85 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards ae7878bdcac 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards e51e3c735bb 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards fd3e0a46a50 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards 28a80fc895b 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards b7404140fbf 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 2ebcbb28b24 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards c0c694d2862 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards bb4aed51fad 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards d085b75137a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards 7fa796ebe5e 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards 384eb76bed5 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards 2bd00c5494c 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards a7f4287b592 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards e1229d4bb6e 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 7203d130344 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards eda07debfa0 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards 4db3d9ce35a 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards 7bd255d416f 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards a55f017929b 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 53aa0eff321 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards e6e9ca5e04d 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards c703ca270ef 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards df044d84a52 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards dac1992a0e3 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards 12a6efa706c 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards 6896245d05e 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 3f1f6d1b22f 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 997c2ee3413 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 0fa8e3ee578 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards d7734951151 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 6b30272e5a5 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 951db9c4dcf 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards 02858340826 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 365cc6f9bb7 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards 496aec20179 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 4b47716315e 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards 8ca0c857ec8 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards d4f8eca5611 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 9aa5fb5af6e 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 5484c10c5b5 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards c98ae5536de 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards 239d5ccf5de 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards 8da95cfcbb5 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] discards 90265cc49c2 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 55273b7d8ac 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] discards 1fe7d5969a7 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] discards 7456122d6ab 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards 578e9194c9e 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] discards c16bde0f9ff 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] discards 9db1968af5c 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] discards fadde167825 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] discards 8d585bb645a 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] discards de547418281 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards fab04af4a76 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/ [...] discards c1cd2a9557c 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/ [...] discards 0baf57c3f9f 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/ [...] discards 77969d2c6e7 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards 714c6630717 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/ [...] discards fb2c82b1489 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/ [...] discards b79ad5aa89a 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/ [...] new acc68dee5e6 357: onsuccess: #2177: 1: Success after binutils/gcc/linux/ [...] new 2bf1b2150de 358: onsuccess: #2178: 1: Success after binutils/gcc/linux/ [...] new c82eae85e5c 359: onsuccess: #2179: 1: Success after binutils/gcc/glibc/ [...] new 1ebb455d07a 360: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new 273d364e962 361: onsuccess: #2181: 1: Success after binutils/gcc/linux/ [...] new 1695aea31b5 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/ [...] new ed9e5ff752e 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/ [...] new 033a4e577ca 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new b47141db715 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] new 56361d736aa 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] new e2662df5edf 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] new 39980c68848 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] new 08efeeed9e0 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] new 4bda8f2f4b4 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new f3eb118b3fd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] new c560bb8ca34 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new e6e771b1741 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 1d694ed3faf 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new 76eb83fda6d 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new cb91eae1338 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new 8970cb6b60b 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new 6d9adc0ef0c 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new acba335ad9c 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new 21cde5c8904 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new 98c7e0e7809 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new 0e74d005562 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 2730da6570e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new 5dca3a8dd81 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 2421df9b922 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new d5b26ae4000 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 3ba3006715d 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 73c65c79ecb 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new 22aa12b5e4b 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new aba4821dcd5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new fd67d4f3dcf 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new 0ccd3a97e93 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new 4c2d0c4c344 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new 8983fbd534d 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new 497f31ee3af 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new 9bded8108ce 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new c919de3ba49 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new dae9207ac81 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new d2d5caf9371 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new 72aed31b6a6 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new dafa9695157 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new 5ffbcfe1d6e 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new ff8ced5fbf8 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new 815911b3c3d 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new d9fe76fa418 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 2dfcfe9b313 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new 00c8b243148 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new a47483811a6 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 065eab54e6b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new 94ddcb4562a 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new 0c41d1f5064 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 7c7b59e1b60 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new d5a03824065 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new ad62af9551d 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new c6024d70af3 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new 186c37e1e0a 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new f6593f781ce 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new a7591a12397 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new 71ccf7b05c1 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new 0914e899b52 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 45be956294e 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new fd146fcddbc 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 4047dcb2c36 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new f85fd5b5d82 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 0ef45ef47bf 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new bc2dfc0f22e 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new ed01b8e2321 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new ef6bebbd740 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 7d30568bc50 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 8b2d1fa606c 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new 73986f29194 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new 1ddd4c8ad74 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 374b1dad876 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new 14ae4bba7da 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 3303224c3ab 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new 7ede21b5596 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 967a3e1c3df 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new e88b01778e3 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new 4efde3b2d00 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new 327f341422c 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new afe26f36621 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new 68d7f57dee5 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new 1560fde2a5e 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new eeee665375b 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new a62d444844e 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 43cf085eed8 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new d1c1f886c6a 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 66d1fe351cd 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new bba7e03179f 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 4d82fed4fe7 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 99bcdad1a3f 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new f76d8c092a6 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 85b3b189842 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new ae706eb7e8c 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 918397c84c3 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 9f3fe4fc65a 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 773c4894180 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 4727000a9f7 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] 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 (4b68c1013f8) \ 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 1776 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2788 bytes 03-build_abe-binutils/console.log.xz | Bin 31032 -> 31124 bytes 04-build_abe-stage1/console.log.xz | Bin 90056 -> 89564 bytes 06-build_abe-linux/console.log.xz | Bin 10152 -> 8540 bytes 07-build_abe-glibc/console.log.xz | Bin 236320 -> 236692 bytes 08-build_abe-stage2/console.log.xz | Bin 225684 -> 226976 bytes 09-build_abe-gdb/console.log.xz | Bin 38652 -> 38492 bytes 10-build_abe-qemu/console.log.xz | Bin 32544 -> 32288 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3788 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3028 -> 2840 bytes 13-check_regression/console.log.xz | Bin 7140 -> 6784 bytes 13-check_regression/mail-body.txt | 26 ---------- 13-check_regression/results.compare | 16 +++--- 13-check_regression/results.compare2 | 90 ++++++++-------------------------- 14-update_baseline/console.log | 62 +++++++++++------------ 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 | 44 ++++++++--------- sumfiles/g++.log.xz | Bin 2649116 -> 2664372 bytes sumfiles/g++.sum | 2 +- sumfiles/gcc.log.xz | Bin 2230136 -> 2206744 bytes sumfiles/gcc.sum | 2 +- sumfiles/gfortran.log.xz | Bin 895732 -> 896420 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2276 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217188 -> 217260 bytes sumfiles/libgomp.sum | 8 ++- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432204 -> 439584 bytes sumfiles/libstdc++.sum | 6 +-- 40 files changed, 105 insertions(+), 201 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017rate/llvm-arm-master-Oz created (now c9eaa9443a3)

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_size-cpu2017rate/llvm-arm-master-Oz in repository toolchain/ci/base-artifacts. at c9eaa9443a3 0: init: #1: -10: Success after baseline build: no new commits This branch includes the following new commits: new c9eaa9443a3 0: init: #1: -10: Success after baseline build: no new 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (d81bd926b1f -> abf948c894f)

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_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards d81bd926b1f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 69871a3e682 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards cde5d949892 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f3e38f02678 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 497f1a09453 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 8ed7deb42b2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 0ee2383a233 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2721361086a 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 98ce86cc754 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 8151361b6df 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards e84feed7f1a 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f7615a7e50e 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards d21d46e1e0d 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 3c0b23a12ae 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 26145d045b1 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards f181c202816 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards f780dca0e19 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 191de828a04 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards e31278a30e9 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 1bf8e549754 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards f0729336169 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 7cd0b437f0b 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards d6841d86e75 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards a743616e2c2 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards ee0e10928b7 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 74924603be9 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 76c107c9417 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards daefafc3a0b 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards cf77694f3fb 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards a7e17aac640 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards a8aee803cb1 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards ce8dac4c3a2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards c55045af2ae 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards a4f46a0d5ca 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards d8671ff19f6 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 33bb24b5839 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 8cc9fb19438 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 17430c7759c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards df97009b742 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 4b17914cab7 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards b70878bae9d 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 97f23db2044 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 456a5f84b24 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 55455201d93 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards de9e1721781 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards b2f7b776b0a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 338b53cc96f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 0733a44a1ba 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards c0d55db20f3 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 15ffbac0c0c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 0fdb22d3686 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 532d0f7131f 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards dee4cdf8298 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards e8933332d88 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards f94f9267803 149: onsuccess: #684: 1: Success after linux: 10 commits discards c983e91cb2a 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 88c8d3403da 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 1272b1bbdc0 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 9315999ec31 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 35e07d35a6a 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 654a4f74286 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 53f9cf886d1 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 36dc98fa382 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards e9f64a5de8e 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards cb69d7b90d7 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards a039ae3734a 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards d4331330762 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 36033114a7a 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 8282830ab91 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 7dd31b55846 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards cd447d55090 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 656653ccc56 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards d39d98c623e 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 156825b5025 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 40772a94fe9 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 4b911917d64 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 52f6274877d 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 5d81fb03e1c 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5d886f64dc9 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 75c4080270e 124: onsuccess: #657: 1: Success after glibc: 2 commits discards d60cdf21645 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 5c3f49cc8c1 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards fa95d1f31e3 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 9684448bed7 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 809f0424e86 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 8cc08696960 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 5576c90ae67 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards db058025cd8 116: onsuccess: #647: 1: Success after linux: 3 commits discards 220a57ad29b 115: onsuccess: #645: 1: Success after binutils: 27 commits discards 133eec74bc8 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 940a9500552 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 2354cd4ec01 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 3782abf0577 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards fef6836a9ce 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 67f6ae9db26 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 9ddbb6894be 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 4b15b8c2ee7 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 9f3eee06d77 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 5a48ad1111a 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 166a5ff4441 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards deb8f652b6b 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 71a03dc57cd 103: onsuccess: #629: 1: Success after binutils/gcc/gdb: 68 [...] new 29203bc4c90 104: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new a0f66d8cdcd 105: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 931226ae88b 106: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 25684c03f0c 107: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 8131e55b794 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new e33974301c3 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 97a6f3fc002 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 53efac6de24 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new f34b4edf06c 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new c60c111b112 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 99925446cba 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 4bac3e86630 115: onsuccess: #645: 1: Success after binutils: 27 commits new 1c86f13d94c 116: onsuccess: #647: 1: Success after linux: 3 commits new ee66f25d453 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new d759a126691 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 9c9135bce95 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new bc2e7ff5ef3 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ae50add537b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 0d75dad3c1e 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 252f297011a 123: onsuccess: #655: 1: Success after binutils: 22 commits new 66b3d573de5 124: onsuccess: #657: 1: Success after glibc: 2 commits new b8a0fdde606 125: onsuccess: #658: 1: Success after linux: 3224 commits new c3f6f9caac2 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 4c083754cdd 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new ac87eac5624 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 5d0bd7a5f01 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new d6bbced1a9b 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 1512b42fd42 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 710f8262706 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 407cfd47b11 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 49f38d21f8b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 06890226e22 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 14b8fba74e9 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 7acca9b5209 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new e57675b8615 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 4bd6a7b6845 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 6751bc02ea6 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 4a53e0580b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 2b510ab92b0 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 6137df244cb 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new cc6d7abdcc3 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9a4928d8e0d 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new 5c16fdad601 146: onsuccess: #680: 1: Success after binutils: 20 commits new 2aa0f2988e8 147: onsuccess: #681: 1: Success after gcc: 6 commits new 5adbd5f7f4d 148: onsuccess: #683: 1: Success after glibc: 9 commits new 50513f54436 149: onsuccess: #684: 1: Success after linux: 10 commits new a03d59b0a42 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new c42e76ebff5 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new d952e8ca9cc 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new dd00cfca9c3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new a664c60465a 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new e7d1642c580 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 178aaa94d0c 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new fb0440baf10 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 0dd4cd363c7 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 36b95c8961e 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new c7e53d80de1 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c0165151958 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new ef526c86dbf 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new dbf4a1be1b6 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 1cf54dadca5 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 81c5dc5d4f0 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 2bf4699ff6c 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 7978d3d93e8 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 4a6d5abafd3 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 5803bf513a7 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 2c2f3b9d6f4 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 7bd5e585a13 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 662568d55d2 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new d8c5dce4795 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new a06f6e25174 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 1c99dddec63 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 5a83640438a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new e7c14f9b49c 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 7e44e49aee5 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 3b7017b2c86 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new a238d839b50 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 93fe62dd914 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 01d747247ea 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 8e0644a077d 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new f0e1e10b0b4 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 0dfdb4d2316 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 97c81f6b05a 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new ac55b21fccf 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new e7dfc4de2d5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new f94bca527cc 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new e2d17f370c5 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 7bf8b9cff59 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 504cb77176e 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2eb7d3041f5 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new d1e68ffc15a 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new a7defef1940 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ed31b49cbfc 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 60309cf0a8e 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a27cc4b206e 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 33d2591dfad 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 87022a1fc48 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 17298b18f40 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 892dccfadcf 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 3c61e67be94 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new abf948c894f 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] 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 (d81bd926b1f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] 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 1920 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 38688 -> 38940 bytes 04-build_abe-gcc/console.log.xz | Bin 204024 -> 203116 bytes 06-build_abe-linux/console.log.xz | Bin 10076 -> 8520 bytes 07-build_abe-glibc/console.log.xz | Bin 245572 -> 243972 bytes 08-build_abe-gdb/console.log.xz | Bin 38456 -> 38704 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3760 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2144 -> 2284 bytes 11-check_regression/console.log.xz | Bin 6060 -> 6076 bytes 11-check_regression/results.compare2 | 33 ++++--------------------- 12-update_baseline/console.log | 36 ++++++++++++++------------- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++++++--------------- sumfiles/binutils.log.xz | Bin 63124 -> 62984 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83972 -> 83972 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 123632 -> 123620 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 57 insertions(+), 78 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-Os_LTO updated (f77f7c8e39d -> 8eb2442bcf5)

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_size-spec2k6/gnu-arm-master-Os_LTO in repository toolchain/ci/base-artifacts. from f77f7c8e39d 52: onsuccess: #8: 1: [TCWG CI] No change after binutils/gc [...] new 8eb2442bcf5 53: onsuccess: #9: 1: [TCWG CI] No change 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 2060 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30732 -> 30868 bytes 04-build_abe-stage1/console.log.xz | Bin 89164 -> 89668 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8644 bytes 07-build_abe-glibc/console.log.xz | Bin 236548 -> 236740 bytes 08-build_abe-stage2/console.log.xz | Bin 210888 -> 211100 bytes 09-benchmark/benchmark-build.log | 139 +- 09-benchmark/benchmark.log | 137 +- 09-benchmark/console.log.xz | Bin 4032 -> 4096 bytes .../compare-results-vs-first-internal.csv | 72 +- .../compare-results-vs-prev-internal.csv | 72 +- 10-check_regression/console.log.xz | Bin 10300 -> 10340 bytes .../csv-results-vs-first-1/perf.csv | 157 +- .../csv-results-vs-first-1/results.csv | 689 +- .../csv-results-vs-first-1/size.csv | 500438 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 26 +- .../csv-results-vs-first-1/vect.csv | 11 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 157 +- .../csv-results-vs-prev-0/results.csv | 173 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 424562 +++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 26 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 15 + 10-check_regression/csv-results-vs-prev-1/perf.csv | 157 +- .../csv-results-vs-prev-1/results.csv | 689 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 500438 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 26 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 11 +- 10-check_regression/mail-body.txt | 2 +- .../output-bmk-results/exe.improvement | 5 +- .../output-bmk-results/exe.regression | 12 +- 10-check_regression/results-vs-first-brief.csv | 70 +- 10-check_regression/results-vs-first-full.csv | 173 +- 10-check_regression/results-vs-first-internal.csv | 78 +- 10-check_regression/results-vs-first.csv | 78 +- 10-check_regression/results-vs-first.log | 1446 +- 10-check_regression/results-vs-prev-brief.csv | 70 +- 10-check_regression/results-vs-prev-compare.csv | 2 - 10-check_regression/results-vs-prev-full.csv | 177 +- 10-check_regression/results-vs-prev-internal.csv | 78 +- 10-check_regression/results-vs-prev.csv | 78 +- 10-check_regression/results-vs-prev.log | 1692 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metadata.json | 14 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 14 +- .../410.bwaves/results-metadata.json | 14 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metadata.json | 14 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 14 +- .../434.zeusmp/results-metadata.json | 14 +- .../435.gromacs/results-metadata.json | 14 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 14 +- .../437.leslie3d/results-metadata.json | 14 +- .../squad-vs-first/444.namd/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metadata.json | 14 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 14 +- .../450.soplex/results-metadata.json | 14 +- .../453.povray/results-metadata.json | 14 +- .../454.calculix/results-metadata.json | 14 +- .../squad-vs-first/456.hmmer/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metadata.json | 14 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 14 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 14 +- .../464.h264ref/results-metadata.json | 14 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 14 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 14 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metadata.json | 14 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 14 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 14 +- .../squad-vs-first/Mean/results-metadata.json | 14 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 354 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 38 +- mail/mail-body.txt | 40 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results_id | 2 +- 94 files changed, 716448 insertions(+), 716414 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allnoconfig updated (d89d6467e2e -> f82616cdee6)

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 d89d6467e2e 46: onsuccess: #3: all: Success after binutils/gcc/linux/qe [...] new f82616cdee6 47: onsuccess: #4: all: Success after binutils/gcc/linux/qe [...] 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 1776 -> 1956 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30664 -> 31064 bytes 04-build_abe-stage1/console.log.xz | Bin 88972 -> 89392 bytes 05-build_abe-qemu/console.log.xz | Bin 30556 -> 32544 bytes 06-build_linux/console.log.xz | Bin 4024 -> 4040 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4268 -> 4312 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023