Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-aosp/oriole-master updated (176253005a7 -> d8790a17dad)

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_aosp-code_size-aosp/oriole-master in repository toolchain/ci/base-artifacts. from 176253005a7 2: onsuccess: #24: 2: Success after llvm: 110 commits new d8790a17dad 3: onsuccess: #25: 2: Success after toolchain_superproject: [...] 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 1952 -> 1968 bytes 02-build_aosp_toolchain/console.log.xz | Bin 198492 -> 197492 bytes 03-build_shadow_llvm/console.log.xz | Bin 131620 -> 130728 bytes 04-build_aosp/console.log.xz | Bin 1253240 -> 1254136 bytes 05-process_shadow_data/console.log.xz | Bin 272 -> 272 bytes 06-check_regression/aosp.improvements | 1 - 06-check_regression/console.log.xz | Bin 44264 -> 43776 bytes 06-check_regression/mail-body.txt | 1 - 06-check_regression/results-vs-prev.csv | 1668 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/toolchain_superproject_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 3 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +- size.csv | 1646 +++++++++++++++--------------- 16 files changed, 1670 insertions(+), 1673 deletions(-) delete mode 100644 06-check_regression/aosp.improvements -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[gcc] branch master updated (378ec7b87a5 -> 0d9e52675c0)

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 378ec7b87a5 [testsuite] test for weak_undefined support and add options new 86111e7b302 testsuite: Add testcase for already fixed PR [PR99739] new 0d9e52675c0 testsuite: Fix up gcc.target/i386/pr109137.c testcase [PR109137] 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/testsuite/gcc.dg/tree-ssa/pr99739.c | 40 ++++++++++++++++++++++++++++++++ gcc/testsuite/gcc.target/i386/pr109137.c | 11 +++++---- 2 files changed, 46 insertions(+), 5 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/tree-ssa/pr99739.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/llvm-master-aarch64-lts-allnoconfig updated (d6f7a19f45b -> e0711787522)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from d6f7a19f45b 51: onsuccess: #7: boot: Success after binutils/llvm/linux/ [...] new e0711787522 52: onsuccess: #8: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1992 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27376 -> 27796 bytes 04-build_kernel_llvm/console.log.xz | Bin 65532 -> 65108 bytes 05-build_abe-qemu/console.log.xz | Bin 32072 -> 31000 bytes 06-build_linux/console.log.xz | Bin 2932 -> 2924 bytes 08-check_regression/console.log.xz | Bin 4224 -> 4300 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 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_bmk-code_size-cpu2017fast/gnu-aarch64-master-Os updated (a5b1eb93295 -> cdab670e89c)

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 a5b1eb93295 7: onsuccess: #8: 1: [TCWG CI] No change after binutils/gcc [...] new cdab670e89c 8: onsuccess: #9: 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 1792 -> 2068 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 27088 -> 27584 bytes 04-build_abe-stage1/console.log.xz | Bin 71084 -> 71772 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8316 -> 7504 bytes 07-build_abe-glibc/console.log.xz | Bin 242628 -> 243060 bytes 08-build_abe-stage2/console.log.xz | Bin 175628 -> 176876 bytes 09-benchmark/benchmark-build.log | 107 +- 09-benchmark/benchmark.log | 105 +- 09-benchmark/console.log.xz | Bin 3964 -> 3988 bytes .../compare-results-vs-first-internal.csv | 186 +- .../compare-results-vs-prev-internal.csv | 187 +- 10-check_regression/console.log.xz | Bin 11848 -> 13108 bytes .../csv-results-vs-first-0/md5sum.csv | 1656 +- .../csv-results-vs-first-0/results.csv | 1008276 ++++++++-------- .../csv-results-vs-first-0/size.csv | 1008506 ++++++++-------- 10-check_regression/csv-results-vs-first-0/sve.csv | 28 +- .../csv-results-vs-first-0/vect.csv | 40 +- .../csv-results-vs-first-1/md5sum.csv | 2658 +- .../csv-results-vs-first-1/perf.csv | 2967 +- .../csv-results-vs-first-1/results.csv | 1009875 ++++++++-------- .../csv-results-vs-first-1/size.csv | 1009998 ++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 28 +- .../csv-results-vs-first-1/vect.csv | 40 +- .../csv-results-vs-prev-0/md5sum.csv | 2543 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2935 +- .../csv-results-vs-prev-0/results.csv | 1009706 ++++++++-------- 10-check_regression/csv-results-vs-prev-0/size.csv | 1009854 ++++++++-------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 28 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 40 +- .../csv-results-vs-prev-1/md5sum.csv | 2658 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2967 +- .../csv-results-vs-prev-1/results.csv | 1009875 ++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 1009998 ++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 28 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 40 +- .../output-bmk-results/exe.improvement.diff | 0 .../output-bmk-results/exe.regression.diff | 0 .../output-bmk-results/symbol.improvement.diff | 0 .../output-bmk-results/symbol.regression.diff | 0 10-check_regression/results-vs-first-brief.csv | 52 +- 10-check_regression/results-vs-first-full.csv | 3068 +- 10-check_regression/results-vs-first-internal.csv | 184 +- 10-check_regression/results-vs-first.csv | 184 +- 10-check_regression/results-vs-first.log | 1276 +- 10-check_regression/results-vs-prev-brief.csv | 52 +- 10-check_regression/results-vs-prev-compare.csv | 18 +- 10-check_regression/results-vs-prev-full.csv | 3190 +- 10-check_regression/results-vs-prev-internal.csv | 184 +- 10-check_regression/results-vs-prev.csv | 184 +- 10-check_regression/results-vs-prev.log | 1278 +- dashboard/dashboard-generate.sh | 2 +- .../508.namd_r/results-metadata.json | 16 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../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 | 4 +- .../526.blender_r/results-metadata.json | 16 +- .../526.blender_r/results-metrics.json | 2 +- .../600.perlbench_s/results-metadata.json | 16 +- .../600.perlbench_s/results-metrics.json | 4 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 16 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 16 +- .../603.bwaves_s/results-metrics.json | 2 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 16 +- .../squad-vs-first/605.mcf_s/results-metrics.json | 2 +- .../607.cactuBSSN_s/results-metadata.json | 16 +- .../607.cactuBSSN_s/results-metrics.json | 2 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 16 +- .../squad-vs-first/619.lbm_s/results-metrics.json | 2 +- .../620.omnetpp_s/results-functional.json | 2 +- .../620.omnetpp_s/results-metadata.json | 16 +- .../620.omnetpp_s/results-metrics.json | 3 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 16 +- .../squad-vs-first/621.wrf_s/results-metrics.json | 2 +- .../623.xalancbmk_s/results-metadata.json | 16 +- .../623.xalancbmk_s/results-metrics.json | 2 +- .../625.x264_s/results-metadata.json | 16 +- .../squad-vs-first/625.x264_s/results-metrics.json | 2 +- .../627.cam4_s/results-metadata.json | 16 +- .../628.pop2_s/results-metadata.json | 16 +- .../squad-vs-first/628.pop2_s/results-metrics.json | 2 +- .../631.deepsjeng_s/results-metadata.json | 16 +- .../638.imagick_s/results-metadata.json | 16 +- .../638.imagick_s/results-metrics.json | 2 +- .../641.leela_s/results-metadata.json | 16 +- .../641.leela_s/results-metrics.json | 2 +- .../squad-vs-first/644.nab_s/results-metadata.json | 16 +- .../squad-vs-first/644.nab_s/results-metrics.json | 2 +- .../648.exchange2_s/results-metadata.json | 16 +- .../648.exchange2_s/results-metrics.json | 2 +- .../649.fotonik3d_s/results-metadata.json | 16 +- .../649.fotonik3d_s/results-metrics.json | 2 +- .../654.roms_s/results-metadata.json | 16 +- .../squad-vs-first/654.roms_s/results-metrics.json | 4 +- .../squad-vs-first/657.xz_s/results-metadata.json | 16 +- .../squad-vs-first/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 33 +- mail/mail-body.txt | 33 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 111 files changed, 4053058 insertions(+), 4052612 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff delete mode 100644 10-check_regression/output-bmk-results/exe.regression.diff delete mode 100644 10-check_regression/output-bmk-results/symbol.improvement.diff delete mode 100644 10-check_regression/output-bmk-results/symbol.regression.diff -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (8ee55b880fb -> 1985d8cb704)

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 binutils-gdb. from 8ee55b880fb [gdb/dap] Add logging of ignored lines new 1985d8cb704 [gdb/testsuite] Fix gdb.cp/m-static.exp regression on Ubuntu 20.04 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: gdb/testsuite/gdb.cp/m-static.exp | 3 +-- 1 file changed, 1 insertion(+), 2 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-arm updated (d65ac3746ba -> f6085b956dc)

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 d65ac3746ba 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards 98c231f2b48 219: force: #50: 1: Failure after linux: 2520 commits discards 248c866f12a 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards 69e7bdf0ef0 217: force: #45: 1: Success after linux: 1 commits discards a52bf3f1dcb 216: force: #43: : Failure after baseline build: no new commits discards 3bff435725f 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards d22bd1d264c 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards cd0e1fa6bba 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 9b4dbe33be5 212: force: #27: : Failure after baseline build: no new commits discards fff2de94d9c 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards ec36d653274 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 008ec8983e1 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 24606e4242c 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f89e6af9294 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 19cd8f0a828 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 27707fb16e6 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 81fe2cb5a9f 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 958f57f465a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4cf936f25a8 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards dce2b47e4f3 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 95ef6b6e406 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b5a012092d0 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 2e1f348636c 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards bf5e082b5ba 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c20bc67fb1c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 7a7d276ac2a 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards cfaa3206752 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 10e5107e51a 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards fdcaaa2c296 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards a1b672eb209 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 7f0c4817a1c 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards b1169194820 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards dd1b7d51421 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards 832938f6bb7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 4b266a15c63 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 66d5f76e754 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 67e40b90906 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 5290f14b6c5 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 9aeb825ce88 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 9f9c4a34827 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 5aea7afca7f 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 57f360fe606 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards d695968e0db 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards ca9c64dcb7a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards af61dbc1284 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 9d083fb1685 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards bac73f4e253 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards cba4654102b 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7c146f0212b 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 852a2c3599d 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 11ad97917da 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 31e9d7fd04c 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 5464168b700 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards cc91a49b7d4 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 0e001abaa77 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 6f3e4a833a0 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards d4c8ab7a1b4 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 5e6c362962f 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards bb0d1110351 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards cdcf3757700 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 27dcbb362ac 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 48ccbe52955 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a5c325e4405 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards fe84ef34f91 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7669b4be358 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards cf14f087c0b 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards 48c5290360a 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards 9e594f1c2f6 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 3721fec6038 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 38c2c831ccf 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 38b53e05be3 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 7a4c11dddd9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 31ebda51082 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 8bfd513c9b8 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards b2025bcd162 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards ac1bbbcb13e 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 24d123e64fb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards c4b3ce0a5c8 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 7cf04e78a97 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 5926c8dea8c 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 21932bbb7dc 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 63b8c79355a 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 8383d048cd7 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards da9fe5232d9 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 1ed87dfbddc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 0d8278d64b0 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards e223ee51147 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 7222f721d92 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 246da916bec 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 1db95c6cbf9 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards a5a8bfb62dd 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards f432d2127a8 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 12be377ea71 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards f692fa16148 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 781782c5d66 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 06533b9d4d0 125: onsuccess: #614: 1: Success after linux: 12 commits discards 0d7dff229d9 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 916342237ad 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards a65dbaa51e0 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards fcc577741cf 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards dea1d78e734 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 3ea33422587 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 1f70b42a0cc 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new d38e3f22153 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new c5376006567 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new ae980169a5c 124: onsuccess: #612: 1: Success after binutils: 18 commits new 317b203ded5 125: onsuccess: #614: 1: Success after linux: 12 commits new 1ae32b58e73 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new d53e563a185 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 6d8d35ba520 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 0792db74c61 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new c6328a4bd7b 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 7f2efa4c5cc 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new a45b75253c7 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new c5a20ea3d93 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 8cc079ca0b3 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 9164a912c04 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new b5883597a56 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 27dc1560516 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 82168ab00df 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 341ee9b3fcc 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new a50078ec03d 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new eabb81108ed 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new bd3a1e5384d 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 809e6c6e1ad 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new e2228d91095 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new eca09d8f728 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 58859b294d0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 988055fcbad 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 9284aab7955 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 59f440cac77 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 54e2a3851c1 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 95f5d4184f0 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new a964c11d9b7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 17cdf0acf21 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 243dcbb07fe 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 604ff50f73e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 6f8eec63c19 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 4db4bb22e23 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 87606e34ea9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 4e44936d807 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new e71ab6d40a9 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new eea7dbde5f9 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new a3d2b03f885 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 27c4a76b6c9 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 4449d5e106c 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new a8ec68362d3 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new dc0d3f1f82f 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 2325bbd97f7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new b6bba74a470 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 2e046ed0b65 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9df5fb69aae 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 9531f50b02c 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 4f0f0b5114a 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 49cb0f638be 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 9aa001b7897 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ca55176f72a 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new fa61f2be9f7 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 7609246cb3e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 54df284acab 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new e250fbfbf35 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 86104176ffe 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new fcae719b2e1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new e8c62c7cf8d 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new b54491dbb1a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 91c26c3f62c 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new c4cd163b457 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 8a880a43704 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 8acd5e7a8b7 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new e014e2566c4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new dbece5b43bd 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 1db7da68194 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 95e31df7a88 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 02010650733 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 3b6273d70d2 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 094753995a0 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 7f859764325 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new debdef72440 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 391776064b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new eeaa4478972 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 3c3f36f6d7a 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 84d1d045717 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 64a21722d5a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 1ffc5e43688 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ad18fb34cae 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 7bfa5d7880c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new dac63edf22b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 6c468f168fd 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 560c295a74f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 5fb0dbd97a1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 70d4b6aaa21 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 0a4ed564db3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 3aeb30670d0 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 43dc469b7a9 212: force: #27: : Failure after baseline build: no new commits new 5f73003f61c 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 8976690ef02 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 0deb1dd5e57 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 1d8931c005d 216: force: #43: : Failure after baseline build: no new commits new abbc626556b 217: force: #45: 1: Success after linux: 1 commits new 5ae404e006c 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new b56ef3a8e0b 219: force: #50: 1: Failure after linux: 2520 commits new 23034e963da 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new f6085b956dc 221: force: #53: 1: Success after gdb-13-branchpoint-1472-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 (d65ac3746ba) \ 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 1988 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 49232 -> 48680 bytes 04-build_abe-gcc/console.log.xz | Bin 237820 -> 236424 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8524 -> 8556 bytes 07-build_abe-glibc/console.log.xz | Bin 234856 -> 233076 bytes 08-build_abe-gdb/console.log.xz | Bin 47748 -> 46984 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3788 bytes 10-build_abe-check_gdb/console.log.xz | Bin 4312 -> 4496 bytes 11-check_regression/console.log.xz | Bin 3316 -> 3216 bytes 11-check_regression/mail-body.txt | 18 - 11-check_regression/results.compare | 9 +- 12-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- sumfiles/gdb.log.0.xz | Bin 2927064 -> 2930820 bytes sumfiles/gdb.log.1.xz | Bin 134560 -> 185224 bytes sumfiles/gdb.log.2.xz | Bin 12832 -> 16820 bytes sumfiles/gdb.log.3.xz | Bin 6440 -> 14812 bytes sumfiles/gdb.log.4.xz | Bin 0 -> 14976 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10288 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10312 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10160 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10364 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10116 bytes sumfiles/gdb.sum | 3884 +----------- sumfiles/gdb.sum.0 | 3895 +----------- sumfiles/gdb.sum.1 | 10522 +++++++++++++++++++++++++++++++- sumfiles/gdb.sum.2 | 2452 +++++++- sumfiles/gdb.sum.3 | 2182 ++++++- sumfiles/gdb.sum.4 | 2352 +++++++ sumfiles/gdb.sum.5 | 2161 +++++++ sumfiles/gdb.sum.6 | 2173 +++++++ sumfiles/gdb.sum.7 | 2113 +++++++ sumfiles/gdb.sum.8 | 2188 +++++++ sumfiles/gdb.sum.9 | 2163 +++++++ 41 files changed, 28177 insertions(+), 8017 deletions(-) create mode 100644 sumfiles/gdb.log.4.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.log.6.xz create mode 100644 sumfiles/gdb.log.7.xz create mode 100644 sumfiles/gdb.log.8.xz create mode 100644 sumfiles/gdb.log.9.xz create mode 100644 sumfiles/gdb.sum.4 create mode 100644 sumfiles/gdb.sum.5 create mode 100644 sumfiles/gdb.sum.6 create mode 100644 sumfiles/gdb.sum.7 create mode 100644 sumfiles/gdb.sum.8 create mode 100644 sumfiles/gdb.sum.9 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[binutils-gdb] branch master updated (232c5cec145 -> 8ee55b880fb)

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 binutils-gdb. from 232c5cec145 Automatic date update in version.in new 8ee55b880fb [gdb/dap] Add logging of ignored lines 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: gdb/python/lib/gdb/dap/io.py | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- 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_binutils/master-aarch64 updated (5df62f5376c -> 136c7dd6982)

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 5df62f5376c 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards e3a0c8ccd0d 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 2db25954b79 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 5460f19a960 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 7d430dec64c 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 2085ebd7d23 214: onsuccess: #26: 1: Success after binutils: 12 commits discards ef9fea6fd27 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 132ae37654b 212: force: #24: 1: Success after binutils: 2 commits discards ac6b8530b61 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards de3dd601d22 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 13757c3e7c8 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 4947f0642a3 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards ce2090d6812 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 2a84697dd19 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f8271819884 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 0a8e8f7cd87 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards a6154af024f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards ff1f4f76d8c 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 45b24151c9c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4855c145b3f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9be88d6ffb7 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1393a1d9805 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards d45dce8b138 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards abfdc046896 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards e8d02501f92 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards c7e0a1e0e3e 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 605c8a02d0c 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards ccc05c70147 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 17a8f82dd0b 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 56d3e3b57e9 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 853b82ee65c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards ae8c6c4b125 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards ba19437c4f0 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards c0838f576fc 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards fa35fb1a835 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 5e4c2813eb0 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards d969ce189b0 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 1af260f55e7 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 185dbead15e 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 001b0e86793 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards d29755c4cf0 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 00b8ea72767 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 01189b35cdb 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 7a2ce2ac90f 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards c8ab2761ff6 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards e3729cd46d3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 267769e9344 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 0ea23f9ab2a 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards b13d256f684 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 4d46d14a9fb 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 06226003f49 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 297d6add00f 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 5997abe7e9d 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 10c3d4fb9e4 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 93e25be1955 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards ad74c1ecf1f 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 34b9d155f01 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards 576c80edaf7 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards c8945575f94 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 1ce5b99ff95 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards cf11ec43503 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 780ec62f143 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 65f2b8635ea 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards cb3c5fd47e3 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 8ce911a9a88 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards e2abc45de4b 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 70142f0f05d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 7f56717f448 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 20941b1595b 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 07db6ce4ff8 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards ee3101d0405 149: onsuccess: #684: 1: Success after linux: 10 commits discards 6c54fadff1f 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 0464a1d18fc 147: onsuccess: #681: 1: Success after gcc: 6 commits discards fcc92967bcc 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 16cf5e59e42 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards d4737196a26 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards f9b8e006639 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards ec8be7d27ff 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 221cfbc6871 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards b3a82348a13 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 192d34d1f49 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 57c9d2d9ad9 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 2d460c1b2db 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 733f8b9369f 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 65eecf01e7a 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 9f57336ff3d 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 2aa944ac43a 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a6012f325d6 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards ecf5c986132 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 4c0756d0e3e 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 2aa3307d2cd 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 85620865420 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 114a37e7f95 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards b15472cc84d 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 9320dc6bd46 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 468b1acc271 124: onsuccess: #657: 1: Success after glibc: 2 commits discards fad462aa1e0 123: onsuccess: #655: 1: Success after binutils: 22 commits discards dfc9bf693ce 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards b4e218a5b53 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 5f9bb8890b6 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 7945987ade7 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 7dc6e01ac33 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new da1df870a16 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 343c8f98e4c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e465f6390e0 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 8db7e2522ef 123: onsuccess: #655: 1: Success after binutils: 22 commits new 45781bec4b0 124: onsuccess: #657: 1: Success after glibc: 2 commits new 370d7838bce 125: onsuccess: #658: 1: Success after linux: 3224 commits new 04c9c2634ee 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 46101649cda 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 19ed5d38c60 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 0c1e7a76e93 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new c1398896cab 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new dc7a23eb054 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 6dd496268ae 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 7029374993d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c7bbcd844da 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 46dd34df8be 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 1469de0cd64 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 0652fcb9f0e 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new feb103232aa 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 0bb11c278de 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new a82992a6514 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 9f9156ae9eb 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 295c3a6b330 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new 804bd43236c 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 147d9c130e5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new d992f2a78ab 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ff7fae4ce9e 146: onsuccess: #680: 1: Success after binutils: 20 commits new b59172deab3 147: onsuccess: #681: 1: Success after gcc: 6 commits new 082d5d2ad45 148: onsuccess: #683: 1: Success after glibc: 9 commits new a3da735e6a3 149: onsuccess: #684: 1: Success after linux: 10 commits new c77293462bc 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 279d1419351 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 89445c4da6a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 8f1e7db9b29 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 6885a9a9445 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 9c35c18b718 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 2df0b75e78f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new 2b4aac4625e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new d531bf4e4ca 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new bec6d08f378 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new e56ede8784a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 8141b59f299 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new e5a2192eb41 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 1b3d3583d24 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 64a7a6f903a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new 6fd070bd38d 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 67304e26b51 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 3650b248e9f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 33dcc9fe76c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 65be537bc61 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 7e3f17d8e3f 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 5b3329f6158 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new b4d673c1c53 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 45175a08ac3 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new f30cf98095a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new bb2908a6031 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 8beb508d088 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 9713a002504 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 632dffee693 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new b2b37289e13 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new ba6b23e508c 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 818bfc76862 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 8679c2dd366 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 8026dbc02e9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 0ffc83ece3c 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 39a25b9580c 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 66f737c07b8 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new cf556430ae5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new a450bcd1b2e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new 5036f2b007f 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new e500d5ca858 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 334e4c77980 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new bcf8a160f7a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 73431d4c57e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 716d0056c3f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 91f79335d91 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ce459d5c437 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 8ae6ff50ea5 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 713ca2796af 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e1e7a4703c1 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new c6fa03d8375 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 6964c43f2d6 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 3cbf5bc2d23 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 8877a962fb7 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 9ee2e8ea119 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7f7463f786c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 09100b178a8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new cc41b1a9fcf 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9ce599b4142 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 296bc20efd1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new bb6fd47c0c3 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 95eebc834e9 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new d5083f20a22 212: force: #24: 1: Success after binutils: 2 commits new 385e2337872 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 631b6fd8081 214: onsuccess: #26: 1: Success after binutils: 12 commits new 5a9e674ff64 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a0c24f1790b 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 36d45c2932e 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f0db1ae243b 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 2ce73292955 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 136c7dd6982 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] 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 (5df62f5376c) \ 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 2072 -> 2336 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 35544 -> 35108 bytes 04-build_abe-gcc/console.log.xz | Bin 203708 -> 202960 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8356 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 240956 -> 241332 bytes 08-build_abe-gdb/console.log.xz | Bin 35308 -> 34700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3780 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2704 -> 2100 bytes 11-check_regression/console.log.xz | Bin 4800 -> 5032 bytes 11-check_regression/results.compare | 10 ++++---- 11-check_regression/results.compare2 | 22 ++++++++++++----- 12-update_baseline/console.log | 38 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++------------- sumfiles/binutils.log.xz | Bin 62576 -> 63020 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83960 -> 83932 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122476 -> 122608 bytes sumfiles/ld.sum | 9 ++++--- 29 files changed, 74 insertions(+), 61 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 (0cb771cbae4 -> de6eb36b698)

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 0cb771cbae4 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards c224996ee6f 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 8f814eb840d 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards 569755917e2 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 6e955be3f75 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 3a1cf01b9df 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 3ec385913de 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 03ff23d827e 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 4a931c74b60 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] discards dddd7695af2 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] discards 49d4eaf5ec8 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards f77804f80ed 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 140fd2a4a04 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 7cd44b860a4 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards 56af8d4c307 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards adb63387451 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 88190611e5d 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards b3b36e30ff7 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards ed830e62560 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 7500c36f7c5 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards cdc211df88e 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 2402119f4c9 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards a603d2fb885 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 365c91f5858 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards 18e318761d3 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 98bb5121243 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 2f26348967f 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 1749a965b01 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards de8bc55257a 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 139a3c9945d 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 649c633a708 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards 51585686a4c 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards 67409ff3543 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 764b9583a60 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards 7808f97f3f5 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 391d3bffa88 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards 9110ea0b714 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 2f582c64af4 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards 729b60cca83 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards 3b0c5056625 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 3aed06a9e62 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 51a42d77336 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 70c5aa3120f 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 9c1b3e4a602 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards 2ec5b5def31 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 07e4f660f0c 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards e16e5ab6e75 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 46a690fbcb2 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards 4e1e4c56e1a 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 3ec2bf0189f 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards ed53149cd42 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards 68832e861e4 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards 7440d6383c6 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 14167d2b104 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards 40b7596a310 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards 58971d649bb 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards 7f4dd047dae 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards a0de792a91c 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards 73b3cd3bcdf 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards b706e52ae60 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards 3423f51fd12 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards bbef437a542 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards e1f84267617 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards d082cf5ea52 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards f36f0d190a9 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards d03bf976f8d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards 97889f3c05d 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards 8c070c6bad2 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards ddbd156faac 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards 7b825318a51 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 3feec3a205f 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards 9a7537556af 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards ae564d65bfe 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards 7277d4cafda 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards 6ffd8bcedc7 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 11c852b8483 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards fd8910a920c 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 15845785da3 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards 0beea4e6093 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards 96b24b561b8 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards e6f34412343 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards ddbef14df4f 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 671c090ad5a 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 94dd1011f75 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards ce19c991688 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards 4360a3fce95 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 1327c0a20a6 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards 24df46a43b9 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards cdc41c7f46a 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 5be081bb85e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards 024782531a1 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 223a09bfbdc 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards 3e82c65dfab 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards 03e97ea160f 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 86f64cbd0b6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 4b706aa3b98 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards a703eb85ca0 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards 1fb6dea7613 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards 800672d13a7 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] discards 74d76d809ed 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 63ae4f01e61 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new 44ba5d275bc 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new 069917fc01f 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new fc2f3cb9e2d 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new 52552dae955 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new d4e77e3507f 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new 1b6f0df0e91 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new 06b32b515ee 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new a71620c227e 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new b31d53fef12 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new b665461a1b1 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new 0c15d6d9221 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new cffae558e68 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new f7e029bbd82 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 5229841c934 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new fd3135faa68 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 0f9fc606441 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 4c89e8d3365 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new ad2396be35c 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new cd1391b18de 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new c427ee934a5 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new 77685c4a499 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new dc2c4f2a417 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new 3195c39a1b9 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new 7e4acd885f9 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new ba2c8ffad8b 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new fb14f5e9769 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new 81e2cf2f5d1 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new 882d5efd39d 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new ce6ddfdca8b 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new b10e4d35d74 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new db07b762e4d 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new 226f0c0d5fc 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new 84809e3b3b7 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new 7688094352f 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 09b8bde9d60 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new cfbf10fcb2a 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new 1f30360db83 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 24c0fd55263 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new 2dad1f90dc8 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new 20fcfcb3950 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 655ae9a871c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new 10eb423a2cf 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new e805eaf8605 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new 93a00da76b3 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new 53824521461 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new 5ee5f854076 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new bb89020dfe2 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new bb641dc5910 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new beedc3d236a 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 9abdbb1713b 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new 26cf1395826 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 82bbe0f24b4 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new d4701281de5 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 567e04d8a44 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new 0ba57e8e647 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new e07d3c29593 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 795e16f82dd 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 41a01616d82 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 122565e72a7 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new 9318ac0581d 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new e8dcf235490 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 0ef0bc5dc4e 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new a360cd70e12 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 463e82a1f81 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new 83aefc50414 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 11373e4b123 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new 8b116c32b58 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new e445fdb1385 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new 529260f5b07 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new a5d45dccac9 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new ddd67825c2d 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new f1c39464525 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new d56e8a44fdf 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new eb66c27c663 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new f9272b13b63 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 2c67f42d436 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 3f70a206098 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d12f4dd4ed0 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 6b42ef7a544 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new cff14248250 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new b809245eae5 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 3be338792b6 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new 8b019a32321 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new e9e7a1d31dd 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 19bf479c0db 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 15cd2f29169 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 6ebd425737f 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new ae16ac55689 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new 3008cadf80a 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 62be68fa215 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 49d2584eac0 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new 5aabccb2248 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] new 277e921c385 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] new 1aaef4eddd4 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new c84d92ebf78 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new dd51be64c01 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new a9ac3d84624 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new ad6620b2dc5 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 1df5f53bb15 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 5afcf50819a 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 994a4ecd598 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new de6eb36b698 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] 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 (0cb771cbae4) \ 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 2096 -> 2116 bytes 02-prepare_abe/console.log.xz | Bin 2596 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 26948 -> 26832 bytes 04-build_abe-stage1/console.log.xz | Bin 89420 -> 89260 bytes 06-build_abe-linux/console.log.xz | Bin 8372 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 233760 -> 232980 bytes 08-build_abe-stage2/console.log.xz | Bin 227156 -> 225660 bytes 09-build_abe-gdb/console.log.xz | Bin 34380 -> 34256 bytes 10-build_abe-qemu/console.log.xz | Bin 32004 -> 32148 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3824 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6736 -> 7012 bytes 13-check_regression/console.log.xz | Bin 6048 -> 6132 bytes 13-check_regression/results.compare | 16 +- 13-check_regression/results.compare2 | 243 +- 14-update_baseline/console.log | 44 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- sumfiles/g++.log.sep.xz | Bin 158756 -> 144440 bytes sumfiles/g++.log.xz | Bin 2689328 -> 2656464 bytes sumfiles/g++.sum | 47 +- sumfiles/g++.sum.sep | 7517 ++++++++++++++++++++++----- sumfiles/gcc.log.sep.xz | Bin 118652 -> 80816 bytes sumfiles/gcc.log.xz | Bin 2207412 -> 2235156 bytes sumfiles/gcc.sum | 106 +- sumfiles/gcc.sum.sep | 9086 +++++++++++++-------------------- sumfiles/gfortran.log.sep.xz | Bin 49996 -> 33648 bytes sumfiles/gfortran.log.xz | Bin 906120 -> 907700 bytes sumfiles/gfortran.sum | 9 +- sumfiles/gfortran.sum.sep | 5208 ++++++++----------- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217016 -> 217164 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 14032 -> 13136 bytes sumfiles/libstdc++.log.xz | Bin 442792 -> 446044 bytes sumfiles/libstdc++.sum.sep | 293 +- 45 files changed, 12524 insertions(+), 10107 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_bmk-code_vect-cpu2017fast/llvm-aarch64-master-O3_LTO updated (4f29584f59b -> 4e0675ce990)

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_vect-cpu2017fast/llvm-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. from 4f29584f59b 3: onsuccess: #7: 1: [TCWG CI] No change after llvm: 209 commits new 4e0675ce990 4: onsuccess: #8: 1: [TCWG CI] No change after llvm: 365 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1868 -> 1876 bytes 02-build_bmk_llvm/console.log.xz | Bin 99012 -> 99424 bytes 03-benchmark/benchmark-build.log | 118 +- 03-benchmark/benchmark.log | 116 +- 03-benchmark/console.log.xz | Bin 3864 -> 3852 bytes .../compare-results-vs-first-internal.csv | 58 +- .../compare-results-vs-prev-internal.csv | 65 +- 04-check_regression/console.log.xz | Bin 5788 -> 5800 bytes .../csv-results-vs-first-1/perf.csv | 144 +- .../csv-results-vs-first-1/results.csv | 4460 +------------------- .../csv-results-vs-first-1/size.csv | 4320 +------------------ 04-check_regression/csv-results-vs-first-1/sve.csv | 1 - 04-check_regression/csv-results-vs-prev-0/perf.csv | 140 +- .../csv-results-vs-prev-0/results.csv | 4455 ++++++++++++++++++- 04-check_regression/csv-results-vs-prev-0/size.csv | 4326 ++++++++++++++++++- 04-check_regression/csv-results-vs-prev-0/sve.csv | 1 + 04-check_regression/csv-results-vs-prev-1/perf.csv | 144 +- .../csv-results-vs-prev-1/results.csv | 4460 +------------------- 04-check_regression/csv-results-vs-prev-1/size.csv | 4320 +------------------ 04-check_regression/csv-results-vs-prev-1/sve.csv | 1 - .../output-bmk-results/exe.improvement.diff | 0 .../output-bmk-results/exe.regression.diff | 0 .../output-bmk-results/symbol.improvement.diff | 0 .../output-bmk-results/symbol.regression.diff | 0 04-check_regression/results-vs-first-brief.csv | 48 +- 04-check_regression/results-vs-first-full.csv | 149 +- 04-check_regression/results-vs-first-internal.csv | 60 +- 04-check_regression/results-vs-first.csv | 60 +- 04-check_regression/results-vs-first.log | 939 +++-- 04-check_regression/results-vs-prev-brief.csv | 48 +- 04-check_regression/results-vs-prev-full.csv | 151 +- 04-check_regression/results-vs-prev-internal.csv | 60 +- 04-check_regression/results-vs-prev.csv | 60 +- 04-check_regression/results-vs-prev.log | 1144 +++-- dashboard/dashboard-generate.sh | 2 +- .../508.namd_r/results-metadata.json | 10 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 10 +- .../510.parest_r/results-metrics.json | 2 +- .../511.povray_r/results-metadata.json | 10 +- .../511.povray_r/results-metrics.json | 2 +- .../526.blender_r/results-metadata.json | 10 +- .../526.blender_r/results-metrics.json | 2 +- .../600.perlbench_s/results-metadata.json | 10 +- .../squad-vs-first/602.gcc_s/results-metadata.json | 10 +- .../squad-vs-first/602.gcc_s/results-metrics.json | 2 +- .../603.bwaves_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metrics.json | 2 +- .../607.cactuBSSN_s/results-metadata.json | 10 +- .../607.cactuBSSN_s/results-metrics.json | 2 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 10 +- .../squad-vs-first/619.lbm_s/results-metrics.json | 2 +- .../620.omnetpp_s/results-metadata.json | 10 +- .../620.omnetpp_s/results-metrics.json | 2 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-metrics.json | 2 +- .../625.x264_s/results-metadata.json | 10 +- .../squad-vs-first/625.x264_s/results-metrics.json | 2 +- .../627.cam4_s/results-metadata.json | 10 +- .../628.pop2_s/results-metadata.json | 10 +- .../631.deepsjeng_s/results-metadata.json | 10 +- .../631.deepsjeng_s/results-metrics.json | 2 +- .../638.imagick_s/results-metadata.json | 10 +- .../638.imagick_s/results-metrics.json | 2 +- .../641.leela_s/results-metadata.json | 10 +- .../641.leela_s/results-metrics.json | 2 +- .../squad-vs-first/644.nab_s/results-metadata.json | 10 +- .../squad-vs-first/644.nab_s/results-metrics.json | 2 +- .../648.exchange2_s/results-metadata.json | 10 +- .../648.exchange2_s/results-metrics.json | 2 +- .../649.fotonik3d_s/results-metadata.json | 10 +- .../654.roms_s/results-metadata.json | 10 +- .../squad-vs-first/657.xz_s/results-metadata.json | 10 +- .../squad-vs-first/657.xz_s/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 102 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 84 files changed, 11179 insertions(+), 19101 deletions(-) delete mode 100644 04-check_regression/output-bmk-results/exe.improvement.diff delete mode 100644 04-check_regression/output-bmk-results/exe.regression.diff delete mode 100644 04-check_regression/output-bmk-results/symbol.improvement.diff delete mode 100644 04-check_regression/output-bmk-results/symbol.regression.diff -- 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 March 2023