Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-aarch64-master-O3 updated (36d23f32c5c -> 7e20c265aec)

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-spec2k6/gnu-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 36d23f32c5c 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] new 7e20c265aec 1: onsuccess: #2: 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 2568 -> 1764 bytes 01-reset_artifacts/patch-env.sh | 2 - 02-prepare_abe/console.log.xz | Bin 2784 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 31792 -> 31904 bytes 04-build_abe-stage1/console.log.xz | Bin 72476 -> 73392 bytes 06-build_abe-linux/console.log.xz | Bin 8672 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 246280 -> 246272 bytes 08-build_abe-stage2/console.log.xz | Bin 179660 -> 181568 bytes 09-benchmark/benchmark-build.log | 116 +- 09-benchmark/benchmark.log | 114 +- 09-benchmark/console.log.xz | Bin 4048 -> 3980 bytes .../compare-results-vs-first-internal.csv | 232 +- .../compare-results-vs-prev-internal.csv | 232 +- 10-check_regression/console.log.xz | Bin 11672 -> 13824 bytes .../csv-results-vs-first-0/md5sum.csv | 2124 +- .../csv-results-vs-first-0/results.csv | 967348 ++++++++--------- .../csv-results-vs-first-0/size.csv | 970626 ++++++++--------- 10-check_regression/csv-results-vs-first-0/sve.csv | 30826 +- .../csv-results-vs-first-0/vect.csv | 7440 +- .../csv-results-vs-first-1/md5sum.csv | 2288 +- .../csv-results-vs-first-1/perf.csv | 2592 +- .../csv-results-vs-first-1/results.csv | 967757 +++++++++-------- .../csv-results-vs-first-1/size.csv | 970740 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 30748 +- .../csv-results-vs-first-1/vect.csv | 7438 +- .../csv-results-vs-prev-0/md5sum.csv | 2124 +- .../csv-results-vs-prev-0/results.csv | 967348 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 970626 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 30826 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 7440 +- .../csv-results-vs-prev-1/md5sum.csv | 2288 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2592 +- .../csv-results-vs-prev-1/results.csv | 967757 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/size.csv | 970740 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 30748 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 7438 +- .../output-bmk-results/error_code-1 | 0 .../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 | 66 +- 10-check_regression/results-vs-first-full.csv | 2617 +- 10-check_regression/results-vs-first-internal.csv | 235 +- 10-check_regression/results-vs-first.csv | 235 +- 10-check_regression/results-vs-first.log | 1264 +- 10-check_regression/results-vs-prev-brief.csv | 66 +- 10-check_regression/results-vs-prev-compare.csv | 5 +- 10-check_regression/results-vs-prev-full.csv | 2617 +- 10-check_regression/results-vs-prev-internal.csv | 235 +- 10-check_regression/results-vs-prev.csv | 235 +- 10-check_regression/results-vs-prev.log | 1278 +- 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 16 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 16 +- .../435.gromacs/results-metrics.json | 4 +- .../436.cactusADM/results-metadata.json | 16 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 16 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 4 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../482.sphinx3/results-metrics.json | 4 +- .../483.xalancbmk/results-metadata.json | 16 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 26 +- mail/mail-body.txt | 26 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results_id | 2 +- 119 files changed, 3965022 insertions(+), 3965143 deletions(-) delete mode 100644 01-reset_artifacts/patch-env.sh copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/output [...] copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/output [...] copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/output [...] copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/output [...] copy dashboard/squad-vs-first/summary-annotation.txt => 10-check_regression/output [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (af716e19fd5 -> 5391a592858)

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_gcc/master-arm in repository toolchain/ci/base-artifacts. discards af716e19fd5 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards c026a271f8b 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2ff72004847 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 8cdadcc895d 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a11403548d7 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7ff757ac3a7 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 58a94eadcb5 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 64a9790922c 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards 3af4bf5bc80 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 04c29df9987 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards dc51ee6d8f3 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards a7f727458e8 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 680ae47d940 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 29b66d5f4e4 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e70cde63af0 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards d59cbdf341a 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 84a87449206 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards a7c5a2de321 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 8d38f806b19 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 82d1ab8df3f 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 886b8cd64b4 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 2d6fbadce8d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 01f5d006d81 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 28e52003ab5 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 3461cb4132a 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 0a372e36cca 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards c74bb61c07e 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 84c5d0c50f0 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards a50afe04a17 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 821bf1e85f5 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 9d88bf4c954 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c7b539f0baa 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards c8d19d32d98 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 77ab896dca6 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 65867653194 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards 806a7f6e4ce 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 44dad49bb01 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards f2a54f7d512 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards eae2c091b4e 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 38b5cfa8844 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 7bc4954f3c7 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 08118875317 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 53a610eb98b 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards d65a25635cf 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 9c9d0790af8 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 6d76e340e4e 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 42b0383d27f 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards 30876f336e1 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 12fc8ae6287 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 5ace0be972d 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards f2a0617d2c0 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards dbde0515768 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards c253560fb40 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards a1d754a18be 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 9f4a6171ecd 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards feab433e55b 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards ef056c4d06d 162: onsuccess: #624: 1: Success after linux: 10 commits discards 21c3578cb8e 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 86100fcfe80 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 5d9de2e1fc4 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 732d11b11fa 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards b86c88ad357 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards d75bac08921 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards c0c0d120761 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards 4da3a5c0b64 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards 62dd1088b7f 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards 1fb90cda08a 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards de4571e62bc 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 1acab586009 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 3894348dde7 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e852da2f910 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 99639a5f87e 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 3a20e291639 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards d419ec76184 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards fa8ae4cb8a6 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards f1357cc2625 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 81b009148ac 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 3b42427d76e 141: onsuccess: #601: 1: Success after linux: 794 commits discards 1043f04fba7 140: onsuccess: #600: 1: Success after gcc: 23 commits discards c0cd8e0da97 139: onsuccess: #599: 1: Success after binutils: 10 commits discards d5d9dc55f41 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 6048b166d49 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 670e2011b0e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards 351cdb7a0ea 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards fa847811c18 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 213be7776c3 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 120e7a35e61 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards f020ba99062 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 1e641e0d6d5 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards fcd9feb2d59 129: onsuccess: #588: 1: Success after linux: 4 commits discards 2fbf90150db 128: onsuccess: #586: 1: Success after binutils: 22 commits discards 1b106822e8a 127: onsuccess: #584: 1: Success after linux: 21 commits discards e1d04d8d8fe 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 15944a63e8d 125: onsuccess: #581: 1: Success after binutils: 4 commits discards 190426b7957 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards b0edd102251 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 62983a4c4a0 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards c56a3610f34 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 697a6fbb6c1 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards 8382f8c1486 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards fd239d27ffd 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 0c51c472089 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new cfb655ef490 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new ef6d8f8d0ef 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new 1d5824386cf 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 0aa1ebb9954 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 46fffa6c17c 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 0620abc6c06 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new 8342936b560 125: onsuccess: #581: 1: Success after binutils: 4 commits new b938f39d5ab 126: onsuccess: #582: 1: Success after gcc: 9 commits new 42bd41dbc18 127: onsuccess: #584: 1: Success after linux: 21 commits new a8aa1d07949 128: onsuccess: #586: 1: Success after binutils: 22 commits new c8523aa23b2 129: onsuccess: #588: 1: Success after linux: 4 commits new 69243f9374d 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new e7d6e79f906 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new 7e49b681aeb 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new 6f0ce6810ca 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 640e14a5bd0 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new e4903e2d9c4 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new caf7aa9245b 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new 5ee1cb3d91a 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 7c5e657f4a7 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 3b8bef384fc 139: onsuccess: #599: 1: Success after binutils: 10 commits new 6132b01ff33 140: onsuccess: #600: 1: Success after gcc: 23 commits new 55d90a58878 141: onsuccess: #601: 1: Success after linux: 794 commits new 0c52b0e0f2b 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new c00f888b38e 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 9f38e9196c3 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 04ab3d3fc25 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new a7a3b463fd9 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 38271c1b3b7 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 9418acde8cb 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 8be14e2f977 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 9785175a85e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new 690b21cb6bd 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 1dcf09fdee2 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 9f47d0b0d6d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 5cb8e9c216a 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new 156d6a0244f 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 5ce7773ed4d 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 12ae768cc9d 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 31c4d614f94 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 9cc2ff634a2 159: onsuccess: #620: 1: Success after binutils: 12 commits new d2cb038865a 160: onsuccess: #621: 1: Success after gcc: 11 commits new f4a89ead038 161: onsuccess: #623: 1: Success after glibc: 9 commits new e7723bc76b9 162: onsuccess: #624: 1: Success after linux: 10 commits new 488b770cec2 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 3a4e7765095 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 2c448f93f39 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new 379e26b79d2 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 44647e79ad1 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new c81a62f690e 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 621080c9374 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 126aa838282 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new c034cd59fd5 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new dad92ea003d 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new 447c705182d 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 61d0e62eb2b 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new 2325312203d 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 946ae980893 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9b94350307f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 426b4e769b2 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 54f1fffc059 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new a5698fbc66c 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new a0279c85b57 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 01d6c97dab6 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new 236cd21132f 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new a51dca2bbe5 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new b3eb09d6222 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b315aa5ae0f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 4cfd0c9d6c4 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 7ae91b84b54 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ba0128dc836 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new d4204f9046c 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new e2da92a8ebc 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 37d5a06fbd5 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 5414b02684e 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 51cc3a14c2e 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new f7fa7575b90 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 0c4a78f6368 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 8872bb396ff 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new ffb6157ff86 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 19c67288121 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a8337fa300f 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new da5a49f5ff9 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 1d326d6987d 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new e6a31d6c479 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 28eef3235e1 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new c81664abb0f 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4e5090eef5f 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3cada1a7aa4 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 9012c6bce13 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new acde37f4c64 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 55be940504e 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new eeba28d1707 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new ad3c3b65901 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d67a1aac957 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new acadcb64a22 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 5336a0188a4 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new bdebf1cbbf5 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c5609fbae8f 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 2ecde34ff92 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 5391a592858 219: onsuccess: #16: 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 (af716e19fd5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/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 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 53088 -> 52484 bytes 04-build_abe-gcc/console.log.xz | Bin 237580 -> 237308 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8636 bytes 07-build_abe-glibc/console.log.xz | Bin 235604 -> 235656 bytes 08-build_abe-gdb/console.log.xz | Bin 50168 -> 51332 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3744 -> 3768 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2608 -> 3080 bytes 11-check_regression/console.log.xz | Bin 6944 -> 7120 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 172 ++++++++------- 12-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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++-- sumfiles/g++.log.xz | Bin 2891988 -> 2905124 bytes sumfiles/g++.sum | 146 ++++++++----- sumfiles/gcc.log.xz | Bin 2440428 -> 2468624 bytes sumfiles/gcc.sum | 379 ++++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 950696 -> 957524 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2276 -> 2276 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 233916 -> 234156 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 465420 -> 473876 bytes sumfiles/libstdc++.sum | 14 +- 38 files changed, 497 insertions(+), 410 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (a915c29a7d6 -> 20d790aa3ea)

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 a915c29a7d6 c++: constrained lambda error-recovery [PR108972] new 20d790aa3ea MAINTAINERS: add myself to write after approval 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: MAINTAINERS | 1 + 1 file changed, 1 insertion(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (bbfb5e5ffbb -> eb79b03eb9c)

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_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards bbfb5e5ffbb 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 0c7b931c766 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards a2b22b87f0b 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards b47133f374a 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7d5f0f54f5b 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4c637d34f33 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 73405f30e23 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 4d05407b23e 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 87dda0336f8 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a2609c3246b 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 9a68871d8e3 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 05d760575c6 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 13f281de65d 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards dc0a36c90d5 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards 615d1646c21 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards d5247de1bc4 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards 4878b211b0c 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards f733c8675d5 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 6ed3bbe5668 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards e8d870b9efd 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 00dcde20fe3 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 7ae1b594e10 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards e170e45cc7f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards f39dc09873e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards baeee415240 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards efffbae4bb8 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 1e104227fb4 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards 0e126f14668 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 37912436c55 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards 4fa9561130e 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards 36e79038dcc 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards b4b13139ec4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards f0af92bc5f7 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards b4f534d04ec 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards 014d7767777 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards 328add02f58 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards 6b9fc0a44b4 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards f88b0bf5a76 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards cc7ac157eb2 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards d22c2345d47 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards 3f44f37ea79 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards d9c05e140f7 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards 59a4bc6d2a8 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 7248eb9aa94 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards 5c454347291 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 22b8a4b5ad1 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards f1abd830e4a 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 3753a9f815c 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards 6b8142ce48e 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 0e0c19adae8 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards bbaf5b31fcd 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 097b12d3e2f 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 288b78add61 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 5de7ee9d1b2 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 41be75d37b9 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards 7f49678b303 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 91cbb1a9597 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards 92250d953af 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards 1bc3692a344 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards 8b6554ca699 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards 622e6df47c4 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 8f4d0253350 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 2ea864af6eb 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 92a41246c09 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 41e4c0559a7 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards 4cf55573aee 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards 192918264fd 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards c2c2f0989ad 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards b8a494cc14a 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards 9816dc6709f 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 8ae16cf80e4 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards f1409ccc755 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards a6405d02462 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards ddd4fadfb95 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 605dc31eec6 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards 1cf0bb46505 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 99d0c3f0b5c 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards e10e172ad6d 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 9c028ac0886 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards b4acad57615 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 03087323b62 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 79dbeab3fc9 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards dcbfbf5b5eb 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 2e10bcb4445 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards 58690c11ef7 31: onsuccess: #38: 1: Success after linux: 14 commits discards 1edc35644f1 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 120e22a528f 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 460c6717c91 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards 8c1e4a60b4c 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 46ceb4ddaed 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards f4841d4ac83 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] discards 8f0356d1a8b 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] discards 1dee85b7a84 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] discards a5034e07e18 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 60f14e6b5ce 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 50561595bdd 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] discards f23a0f852ce 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] discards db2befe1e21 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] discards b06c6e78e95 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits discards 5946115bfad 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards b259cea3dc0 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new c877502c368 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 3f3cae9253e 16: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new a75c1fe6e9f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 51 commits new 6d19b0d8522 18: onsuccess: #23: 1: Success after binutils/gcc/linux/gdb [...] new 7240d5e45f1 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb [...] new 3626acfa4f2 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb [...] new 395b26376fb 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new b462d3fdb96 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new bfcdcaf0587 23: onsuccess: #28: 1: Success after binutils/gcc/linux/gli [...] new 7f1d6e0b08e 24: onsuccess: #29: 1: Success after binutils/gcc/linux/gli [...] new e637414db77 25: onsuccess: #30: 1: Success after binutils/gcc/linux/gli [...] new ade765c7057 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new f2cace7e069 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new e2d41a72a3c 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new cdfdb412c72 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new a421d77d814 30: onsuccess: #36: 1: Success after binutils: 18 commits new 9dd8924a8d5 31: onsuccess: #38: 1: Success after linux: 14 commits new 4593c5f4741 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 3c2a3421d71 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 6ee500af229 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 9ea5f69528a 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 617de9ba4db 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new ab8a3bd3e09 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new f00d963936f 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new 0186560dedf 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new af5cb952351 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new 187a988d821 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new 9c9a3c0adec 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new c03c292ebd8 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new 5f8ec10bd62 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 3afa5ef42b9 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new c263e0e9b9d 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new d1b39f77933 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 0560adba9ee 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 623b684bb51 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 1d6d3e3d307 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new cc473396ada 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 19b4170cd1f 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new e92e2fd2ec1 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 3b0b11afb24 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 9b214616cd2 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new e70a5d107a2 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 112a9d56528 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new eb15038b590 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new 6024eebd865 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 505613261a8 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 3b44e48e028 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 8b38b7bb76b 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 4798bcd480d 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 70cf963501e 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 6bcaa40ce1e 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 8be3ae3c06d 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new fe4c3ff80b9 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new ffbad1e7fc0 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 91ffebec284 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 035be1fc8b2 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new dc82a361837 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new 0ba6c83d372 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 705d2616c77 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 356d25f3c6c 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 74b442730e2 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 0b4848dd98c 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new faf528e667b 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new 6a1723727ae 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new c055ecaa6d2 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new fa486cddfb0 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 94b76fb225f 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 7b070d3ac90 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new af153cf973e 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 4b43f43f92e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new 33581d0a76e 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new d51bf617eaa 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new bfd5e0cca64 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 9bc02c5db95 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new c9dfcc77ddc 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new e396d2dd9cd 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new 88d591f8571 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new c3ec9d680d1 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 8984d04ed68 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new 48622fe3755 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new d659d479de6 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new 46e398d14ef 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 7cc2436f4fa 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 1d16b0dbee6 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 20cff9667b8 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new c369a9ed79a 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new 85eafdd5460 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 73a43b35932 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new edfd7a8e32f 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new f599a35f202 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 3ac5823e71f 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5e941a56f6d 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new 342965e05dc 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new dcdaa814c11 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 12740fdc677 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 8b983474151 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new e4265ca6215 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 8fc0478c01d 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e01395aeab9 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 82d4078127d 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6094c2c9bb6 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new eb79b03eb9c 116: onsuccess: #15: 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 (bbfb5e5ffbb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] 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 1752 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 53768 -> 53872 bytes 04-build_abe-gcc/console.log.xz | Bin 240636 -> 237384 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8492 -> 8632 bytes 07-build_abe-glibc/console.log.xz | Bin 235272 -> 235616 bytes 08-build_abe-gdb/console.log.xz | Bin 51308 -> 51388 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3748 -> 3744 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2568 -> 2676 bytes 11-check_regression/console.log.xz | Bin 6136 -> 6216 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 6 +-- 12-update_baseline/console.log | 68 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++--------- sumfiles/gdb.log.xz | Bin 11924 -> 11932 bytes sumfiles/gdb.sum | 30 +++++++-------- 26 files changed, 81 insertions(+), 81 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-surfaceflinger/oriole-master updated (e8c427bf6cb -> 3c0c990bc12)

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-surfaceflinger/oriole-master in repository toolchain/ci/base-artifacts. from e8c427bf6cb 10: onsuccess: #33: 0: Success after aosp_manifest: 41 commits new 3c0c990bc12 11: onsuccess: #34: 0: Success after llvm: 121 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 1960 -> 1768 bytes 02-build_aosp_toolchain/console.log.xz | Bin 10480 -> 10364 bytes 03-build_shadow_llvm/console.log.xz | Bin 129280 -> 129076 bytes 04-build_aosp/console.log.xz | Bin 75200 -> 74840 bytes 05-check_regression/aosp.improvements | 2 +- 05-check_regression/binary.improvements | 73 -------------- 05-check_regression/binary.regressions | 7 -- 05-check_regression/console.log.xz | Bin 7408 -> 6152 bytes 05-check_regression/mail-body.txt | 2 +- 05-check_regression/results-vs-first.csv | 4 +- 05-check_regression/results-vs-prev.csv | 168 +++++++++++++++---------------- 05-check_regression/results.regressions | 1 - dashboard/dashboard-generate.sh | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 +- mail/mail-subject.txt | 2 +- manifest.sh | 12 +-- results | 1 - size.csv | 48 ++++----- 20 files changed, 124 insertions(+), 206 deletions(-) delete mode 100644 05-check_regression/binary.improvements delete mode 100644 05-check_regression/binary.regressions delete mode 100644 05-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (4d0baeae315 -> a915c29a7d6)

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 4d0baeae315 ubsan: missed -fsanitize=bounds for compound ops [PR108060] new a915c29a7d6 c++: constrained lambda error-recovery [PR108972] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/cp/lambda.cc | 4 ++++ gcc/testsuite/g++.dg/cpp2a/concepts-lambda3.C | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (78e1cfb433e -> 7df69e5e5e4)

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-allmodconfig in repository toolchain/ci/base-artifacts. from 78e1cfb433e 63: onsuccess: #3: 23519: Success after binutils/llvm/linux [...] new 7df69e5e5e4 64: onsuccess: #4: 23519: 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 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2784 bytes 03-build_abe-binutils/console.log.xz | Bin 30816 -> 31304 bytes 04-build_kernel_llvm/console.log.xz | Bin 68304 -> 66668 bytes 05-build_abe-qemu/console.log.xz | Bin 32368 -> 32480 bytes 06-build_linux/console.log.xz | Bin 3704 -> 4532 bytes 08-check_regression/console.log.xz | Bin 4272 -> 4312 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (e20e5d9dc11 -> 4d0baeae315)

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 e20e5d9dc11 Fortran: fix ICE with bind(c) in block data [PR104332] new 4d0baeae315 ubsan: missed -fsanitize=bounds for compound ops [PR108060] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/c-family/c-gimplify.cc | 12 ++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-17.c | 17 +++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-18.c | 17 +++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-19.c | 20 ++++++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-20.c | 16 ++++++++++++++++ gcc/testsuite/c-c++-common/ubsan/bounds-21.c | 18 ++++++++++++++++++ 6 files changed, 100 insertions(+) create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-17.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-18.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-19.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-20.c create mode 100644 gcc/testsuite/c-c++-common/ubsan/bounds-21.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[glibc] branch master updated (f7e751affb -> e78c4c4983)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from f7e751affb elf: Add missing dependency between resolvfail and testobj1.so new e78c4c4983 linux: fix ntp_gettime abi break (BZ# 30156) 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: sysdeps/unix/sysv/linux/ntp_gettime.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_aosp-code_size-surfaceflinger/oriole-master updated (cc8fe5e4bca -> e8c427bf6cb)

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-surfaceflinger/oriole-master in repository toolchain/ci/base-artifacts. from cc8fe5e4bca 9: onsuccess: #31: 0: Success after llvm: 143 commits new e8c427bf6cb 10: onsuccess: #33: 0: Success after aosp_manifest: 41 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 1744 -> 1960 bytes 02-build_aosp_toolchain/console.log.xz | Bin 10392 -> 10480 bytes 03-build_shadow_llvm/console.log.xz | Bin 129580 -> 129280 bytes 04-build_aosp/console.log.xz | Bin 77492 -> 75200 bytes 05-check_regression/aosp.improvements | 2 +- 05-check_regression/binary.improvements | 73 ++++++++++++++ 05-check_regression/binary.regressions | 7 ++ 05-check_regression/console.log.xz | Bin 6260 -> 7408 bytes 05-check_regression/mail-body.txt | 1 + 05-check_regression/results-vs-first.csv | 165 ++++++++++++++++--------------- 05-check_regression/results-vs-prev.csv | 165 ++++++++++++++++--------------- 05-check_regression/results.regressions | 1 + 06-update_baseline/console.log | 9 ++ dashboard/dashboard-generate.sh | 2 +- git/aosp_manifest_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 3 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++-- results | 1 + size.csv | 165 ++++++++++++++++--------------- 21 files changed, 360 insertions(+), 260 deletions(-) create mode 100644 05-check_regression/binary.improvements create mode 100644 05-check_regression/binary.regressions create mode 100644 05-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023