Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O3 updated (772364a33ce -> 0f3fe63dbfd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 772364a33ce 11: onsuccess: #13: 1: [TCWG CI] No change after llvm: 356 commits new 0f3fe63dbfd 12: onsuccess: #14: 1: [TCWG CI] No change after llvm: 322 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 1900 -> 1892 bytes 02-build_bmk_llvm/console.log.xz | Bin 101136 -> 100032 bytes 03-benchmark/benchmark-build.log | 150 +- 03-benchmark/benchmark.log | 148 +- 03-benchmark/console.log.xz | Bin 3904 -> 4000 bytes .../compare-results-vs-first-internal.csv | 129 +- .../compare-results-vs-prev-internal.csv | 175 +- 04-check_regression/console.log.xz | Bin 11980 -> 12028 bytes .../csv-results-vs-first-1/md5sum.csv | 2255 +- .../csv-results-vs-first-1/perf.csv | 2559 +- .../csv-results-vs-first-1/results.csv | 2831 +- .../csv-results-vs-first-1/size.csv | 228052 +++++++++--------- 04-check_regression/csv-results-vs-first-1/sve.csv | 26 +- .../csv-results-vs-prev-0/md5sum.csv | 2276 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 2575 +- .../csv-results-vs-prev-0/results.csv | 3071 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 201787 ++++++++-------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 28 +- .../csv-results-vs-prev-1/md5sum.csv | 2255 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 2559 +- .../csv-results-vs-prev-1/results.csv | 2831 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 228052 +++++++++--------- 04-check_regression/csv-results-vs-prev-1/sve.csv | 26 +- 04-check_regression/jira-body.txt | 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 | 2546 +- 04-check_regression/results-vs-first-internal.csv | 175 +- 04-check_regression/results-vs-first.csv | 175 +- 04-check_regression/results-vs-first.log | 1088 +- 04-check_regression/results-vs-prev-brief.csv | 48 +- 04-check_regression/results-vs-prev-compare.csv | 1 + 04-check_regression/results-vs-prev-full.csv | 2664 +- 04-check_regression/results-vs-prev-internal.csv | 175 +- 04-check_regression/results-vs-prev.csv | 175 +- 04-check_regression/results-vs-prev.log | 1462 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 10 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 10 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 10 +- .../508.namd_r/results-metadata.json | 10 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 10 +- .../511.povray_r/results-metadata.json | 10 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 10 +- .../520.omnetpp_r/results-metadata.json | 10 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metadata.json | 10 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 10 +- .../526.blender_r/results-metadata.json | 10 +- .../527.cam4_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metadata.json | 10 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 10 +- .../541.leela_r/results-metadata.json | 10 +- .../squad-vs-first/544.nab_r/results-metadata.json | 10 +- .../548.exchange2_r/results-metadata.json | 10 +- .../549.fotonik3d_r/results-metadata.json | 10 +- .../554.roms_r/results-metadata.json | 10 +- .../squad-vs-first/557.xz_r/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/llvm_rev | 2 +- mail/jira-body.txt | 7 - mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 76 files changed, 345633 insertions(+), 345099 deletions(-) delete mode 100644 04-check_regression/jira-body.txt 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 delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-O3 created (now 91a14899f69)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-O3 in repository toolchain/ci/base-artifacts. at 91a14899f69 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] This branch includes the following new commits: new 91a14899f69 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled updated (524a3c49f32 -> 9e300b8aa3a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled in repository toolchain/ci/base-artifacts. discards 524a3c49f32 196: onsuccess: #33: 2: Success after binutils/gcc: 32 commits discards e86996dbdcf 195: onsuccess: #32: 2: Success after binutils/gcc: 28 commits discards 428899d8885 194: onsuccess: #31: 2: Success after binutils/gcc: 36 commits discards 5946be0e007 193: onsuccess: #30: 2: Success after binutils/gcc: 43 commits discards da9461f12b7 192: onsuccess: #29: 2: Success after binutils/gcc: 32 commits discards 5069b626ab9 191: onsuccess: #28: 2: Success after binutils/gcc: 16 commits discards 79d908d4f73 190: onsuccess: #27: 2: Success after binutils/gcc: 30 commits discards 18037713383 189: onsuccess: #26: 2: Success after binutils/gcc: 41 commits discards 6d71fd5b5a9 188: onsuccess: #25: 2: Success after binutils/gcc: 36 commits discards 6ea2448a5ba 187: onsuccess: #24: 2: Success after binutils/gcc: 40 commits discards 9f4ba6f4809 186: onsuccess: #23: 2: Success after binutils/gcc: 43 commits discards 5c7ecc2f7d3 185: onsuccess: #22: 2: Success after binutils/gcc: 59 commits discards 02d52bfaae4 184: onsuccess: #21: 2: Success after binutils/gcc: 12 commits discards 50dc55cdfb3 183: onsuccess: #20: 2: Success after binutils/gcc: 15 commits discards e29b5195519 182: onsuccess: #19: 2: Success after binutils/gcc: 57 commits discards 4ef6414dc7d 181: onsuccess: #18: 2: Success after binutils/gcc: 36 commits discards c050d556f23 180: onsuccess: #17: 2: Success after binutils/gcc: 39 commits discards d9fe740ff49 179: onsuccess: #16: 0: Success after binutils: 28 commits discards 8bf3175299e 178: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards b005db368bb 177: force: #14: 2: Success after binutils: 8 commits discards 790775fe274 176: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards 77075577a71 175: onsuccess: #11: 2: Success after binutils/gcc: 27 commits discards fdd9af7e6e4 174: onsuccess: #10: 2: Success after binutils/gcc: 11 commits discards 44c09b23904 173: onsuccess: #9: 2: Success after binutils/gcc: 44 commits discards 36bf09be306 172: onsuccess: #8: 2: Success after binutils/gcc: 41 commits discards 4c6f6ef65e3 171: onsuccess: #7: 2: Success after binutils/gcc: 228 commits discards ca586173de5 170: onsuccess: #592: 2: Success after binutils/gcc: 35 commits discards f7579060082 169: onsuccess: #591: 2: Success after binutils/gcc: 144 commits discards 75fa692c57d 168: onsuccess: #590: 2: Success after binutils/gcc: 237 commits discards 0a6d28fd83f 167: onsuccess: #584: 2: Success after binutils/gcc: 33 commits discards 41d86aa5cd6 166: onsuccess: #583: 2: Success after binutils/gcc: 92 commits discards 84a01598167 165: onsuccess: #582: 2: Success after binutils/gcc: 115 commits discards a6dd21d2e06 164: onsuccess: #581: 2: Success after binutils/gcc: 57 commits discards 5a30c9cb38d 163: onsuccess: #580: 2: Success after binutils/gcc: 91 commits discards 683b68e6142 162: onsuccess: #578: 2: Success after binutils/gcc: 56 commits discards 7dd3e9bf715 161: onsuccess: #576: 2: Success after binutils/gcc: 31 commits discards 89ceaf59391 160: onsuccess: #575: 2: Success after binutils/gcc: 6 commits discards be16f8bfa8d 159: onsuccess: #574: 2: Success after binutils/gcc: 30 commits discards 24fd359d520 158: onsuccess: #573: 2: Success after binutils/gcc: 59 commits discards bf7a0e601d8 157: onsuccess: #572: 2: Success after binutils/gcc: 36 commits discards 97348843578 156: onsuccess: #571: 2: Success after binutils/gcc: 107 commits discards 5497436b602 155: onsuccess: #570: 2: Success after binutils/gcc: 55 commits discards 67c9c62ba19 154: onsuccess: #569: 2: Success after binutils/gcc: 13 commits discards 026cb145159 153: onsuccess: #568: 2: Success after binutils/gcc: 160 commits discards d81cf47771d 152: onsuccess: #566: 2: Success after binutils/gcc: 52 commits discards 25465c17cce 151: onsuccess: #565: 2: Success after binutils/gcc: 92 commits discards 3899139cca3 150: onsuccess: #563: 2: Success after binutils/gcc: 16 commits discards d733c645582 149: onsuccess: #562: 2: Success after binutils/gcc: 83 commits discards 7ab400807e0 148: onsuccess: #560: 2: Success after binutils/gcc: 31 commits discards c49d3d80d92 147: onsuccess: #559: 2: Success after binutils/gcc: 74 commits discards bf97848176f 146: onsuccess: #558: 2: Success after binutils/gcc: 34 commits discards f983ce70d14 145: onsuccess: #557: 2: Success after binutils/gcc: 137 commits discards 73e17aaea37 144: onsuccess: #556: 2: Success after binutils/gcc: 36 commits discards 20ffa684262 143: onsuccess: #555: 2: Success after binutils/gcc: 139 commits discards 4f8d9a3ccf5 142: onsuccess: #553: 2: Success after binutils/gcc: 6 commits discards 290d900f1c3 141: onsuccess: #552: 2: Success after binutils/gcc: 9 commits discards fe7e24a6951 140: onsuccess: #551: 2: Success after binutils/gcc: 84 commits discards c06e81ecadb 139: onsuccess: #547: 2: Success after binutils/gcc: 30 commits discards 8f6baa06d34 138: onsuccess: #546: 2: Success after binutils/gcc: 60 commits discards cb75bbb8a34 137: onsuccess: #545: 2: Success after binutils/gcc: 24 commits discards 2b6e5704b39 136: onsuccess: #544: 2: Success after binutils/gcc: 13 commits discards e6d4c7abe78 135: onsuccess: #543: 2: Success after binutils/gcc: 16 commits discards a499eccd562 134: onsuccess: #542: 2: Success after binutils/gcc: 28 commits discards 3dfc5fe8a1e 133: onsuccess: #541: 2: Success after binutils/gcc: 6 commits discards 55bc851fbe6 132: onsuccess: #540: 2: Success after binutils/gcc: 14 commits discards acf6d19e9ea 131: onsuccess: #539: 2: Success after binutils/gcc: 23 commits discards df70f32f4e7 130: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards 7d6df2bb996 129: onsuccess: #537: 2: Success after binutils/gcc: 27 commits discards 1f794709c3b 128: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards 8d634810f46 127: onsuccess: #535: 2: Success after binutils/gcc: 95 commits discards babe08c86e8 126: onsuccess: #534: 2: Success after binutils/gcc: 37 commits discards c41cf7d3580 125: onsuccess: #533: 2: Success after binutils/gcc: 65 commits discards ce7777dca33 124: onsuccess: #532: 2: Success after binutils/gcc: 19 commits discards 6bd64729131 123: onsuccess: #531: 2: Success after binutils/gcc: 48 commits discards bc692c563a6 122: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 6618d59e832 121: onsuccess: #529: 2: Success after binutils/gcc: 26 commits discards 788ef268863 120: onsuccess: #528: 2: Success after binutils/gcc: 42 commits discards c76c8774641 119: onsuccess: #527: 2: Success after binutils/gcc: 25 commits discards 0827b53d48a 118: onsuccess: #526: 2: Success after binutils/gcc: 49 commits discards 176cc412848 117: onsuccess: #525: 2: Success after binutils/gcc: 70 commits discards 96159173b80 116: onsuccess: #524: 2: Success after binutils/gcc: 42 commits discards 86e5c9d3d7d 115: onsuccess: #523: 2: Success after binutils/gcc: 89 commits discards ba1bf6cf2e3 114: onsuccess: #519: 2: Success after binutils/gcc: 31 commits discards fd9585183e4 113: onsuccess: #518: 2: Success after binutils/gcc: 42 commits discards aa32b00134b 112: onsuccess: #517: 2: Success after binutils/gcc: 29 commits discards 90d28b02014 111: onsuccess: #516: 2: Success after binutils/gcc: 10 commits discards 89e48c23fec 110: onsuccess: #515: 2: Success after binutils/gcc: 14 commits discards ece3c8689c1 109: onsuccess: #514: 2: Success after binutils/gcc: 30 commits discards b8b5419e595 108: onsuccess: #513: 2: Success after binutils/gcc: 55 commits discards b726588d1b2 107: onsuccess: #512: 2: Success after binutils/gcc: 39 commits discards 87465e6adea 106: onsuccess: #511: 2: Success after binutils/gcc: 55 commits discards 7395ed4a5a8 105: onsuccess: #510: 1: Success after binutils/gcc: 82 commits discards 2096310fa3c 104: onsuccess: #509: 1: Success after binutils/gcc: 4 commits discards 921abb51769 103: onsuccess: #508: 1: Success after binutils/gcc: 7 commits discards d183bf20aa7 102: onsuccess: #507: 1: Success after binutils/gcc: 120 commits discards 645703fe470 101: onsuccess: #506: 1: Success after gcc: 9 commits discards d281ad2b8fe 100: force: #505: 1: Failure after basepoints/gcc-13-4227-g [...] discards e4d8272f3f7 99: force: #504: 2: Success after gcc: 15 commits discards 7afbda6bfc2 98: onsuccess: #501: 2: Success after binutils: 11 commits discards 6bb17e3eb10 97: onsuccess: #499: 2: Success after binutils/gcc: 43 commits discards a30dcaf4813 96: onsuccess: #498: 2: Success after binutils/gcc: 8 commits new dd385a66959 96: onsuccess: #498: 2: Success after binutils/gcc: 8 commits new 870e4a73a88 97: onsuccess: #499: 2: Success after binutils/gcc: 43 commits new 695b0808d85 98: onsuccess: #501: 2: Success after binutils: 11 commits new 87699ea8a07 99: force: #504: 2: Success after gcc: 15 commits new 1c0258739e0 100: force: #505: 1: Failure after basepoints/gcc-13-4227-g [...] new 0f16e0bacd1 101: onsuccess: #506: 1: Success after gcc: 9 commits new 053faaf095c 102: onsuccess: #507: 1: Success after binutils/gcc: 120 commits new 81802a22601 103: onsuccess: #508: 1: Success after binutils/gcc: 7 commits new e0f6f73094c 104: onsuccess: #509: 1: Success after binutils/gcc: 4 commits new fbbec634713 105: onsuccess: #510: 1: Success after binutils/gcc: 82 commits new 353a4fcb352 106: onsuccess: #511: 2: Success after binutils/gcc: 55 commits new 0bfced668e9 107: onsuccess: #512: 2: Success after binutils/gcc: 39 commits new fa86d8696a2 108: onsuccess: #513: 2: Success after binutils/gcc: 55 commits new 8a74d48e1b7 109: onsuccess: #514: 2: Success after binutils/gcc: 30 commits new 99181b0ec02 110: onsuccess: #515: 2: Success after binutils/gcc: 14 commits new cf5c6220442 111: onsuccess: #516: 2: Success after binutils/gcc: 10 commits new eabd0fbf7a9 112: onsuccess: #517: 2: Success after binutils/gcc: 29 commits new 4596781af61 113: onsuccess: #518: 2: Success after binutils/gcc: 42 commits new d3893234772 114: onsuccess: #519: 2: Success after binutils/gcc: 31 commits new 278db9fdf65 115: onsuccess: #523: 2: Success after binutils/gcc: 89 commits new f63bc8cce30 116: onsuccess: #524: 2: Success after binutils/gcc: 42 commits new dc8a49fdfff 117: onsuccess: #525: 2: Success after binutils/gcc: 70 commits new e2c6456e41e 118: onsuccess: #526: 2: Success after binutils/gcc: 49 commits new ba55e7af4ca 119: onsuccess: #527: 2: Success after binutils/gcc: 25 commits new 1438d8db87d 120: onsuccess: #528: 2: Success after binutils/gcc: 42 commits new b611cbdfe79 121: onsuccess: #529: 2: Success after binutils/gcc: 26 commits new 5d2fd593d2b 122: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new c8a6c57f2a8 123: onsuccess: #531: 2: Success after binutils/gcc: 48 commits new 1998154b568 124: onsuccess: #532: 2: Success after binutils/gcc: 19 commits new 4e7b4a2f9f7 125: onsuccess: #533: 2: Success after binutils/gcc: 65 commits new 4327691ef2a 126: onsuccess: #534: 2: Success after binutils/gcc: 37 commits new b7d7d59851c 127: onsuccess: #535: 2: Success after binutils/gcc: 95 commits new 673624d58ea 128: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new 0c10c0ac09c 129: onsuccess: #537: 2: Success after binutils/gcc: 27 commits new 295a569a0e6 130: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new a3140452d71 131: onsuccess: #539: 2: Success after binutils/gcc: 23 commits new dff7fdb281f 132: onsuccess: #540: 2: Success after binutils/gcc: 14 commits new b31aaeb4cf3 133: onsuccess: #541: 2: Success after binutils/gcc: 6 commits new a337c84a220 134: onsuccess: #542: 2: Success after binutils/gcc: 28 commits new 98b0c177258 135: onsuccess: #543: 2: Success after binutils/gcc: 16 commits new a13fe405f3f 136: onsuccess: #544: 2: Success after binutils/gcc: 13 commits new 994b7175ec1 137: onsuccess: #545: 2: Success after binutils/gcc: 24 commits new 53564325f1e 138: onsuccess: #546: 2: Success after binutils/gcc: 60 commits new eca17746830 139: onsuccess: #547: 2: Success after binutils/gcc: 30 commits new 6d73a035062 140: onsuccess: #551: 2: Success after binutils/gcc: 84 commits new 9dadba2f0ff 141: onsuccess: #552: 2: Success after binutils/gcc: 9 commits new edec8091edd 142: onsuccess: #553: 2: Success after binutils/gcc: 6 commits new 0fb73d65d24 143: onsuccess: #555: 2: Success after binutils/gcc: 139 commits new 8a5aab212f1 144: onsuccess: #556: 2: Success after binutils/gcc: 36 commits new 338c21f811c 145: onsuccess: #557: 2: Success after binutils/gcc: 137 commits new 3f6e627e68e 146: onsuccess: #558: 2: Success after binutils/gcc: 34 commits new 6dba916e99a 147: onsuccess: #559: 2: Success after binutils/gcc: 74 commits new 0ad69dd3702 148: onsuccess: #560: 2: Success after binutils/gcc: 31 commits new 2f075478689 149: onsuccess: #562: 2: Success after binutils/gcc: 83 commits new 8ba382216cb 150: onsuccess: #563: 2: Success after binutils/gcc: 16 commits new 5a4ac108f69 151: onsuccess: #565: 2: Success after binutils/gcc: 92 commits new a9c9a7ed017 152: onsuccess: #566: 2: Success after binutils/gcc: 52 commits new 5205a27f180 153: onsuccess: #568: 2: Success after binutils/gcc: 160 commits new 00f4f7e65cb 154: onsuccess: #569: 2: Success after binutils/gcc: 13 commits new 19e03961e94 155: onsuccess: #570: 2: Success after binutils/gcc: 55 commits new beae2844b28 156: onsuccess: #571: 2: Success after binutils/gcc: 107 commits new 62a45ff7829 157: onsuccess: #572: 2: Success after binutils/gcc: 36 commits new d8d701189ce 158: onsuccess: #573: 2: Success after binutils/gcc: 59 commits new b70da8e0fb4 159: onsuccess: #574: 2: Success after binutils/gcc: 30 commits new 59bd9936ef6 160: onsuccess: #575: 2: Success after binutils/gcc: 6 commits new 0b4be59576e 161: onsuccess: #576: 2: Success after binutils/gcc: 31 commits new ed7e0d4b54b 162: onsuccess: #578: 2: Success after binutils/gcc: 56 commits new 5a2b7b89001 163: onsuccess: #580: 2: Success after binutils/gcc: 91 commits new 5c997904697 164: onsuccess: #581: 2: Success after binutils/gcc: 57 commits new 18b918a20cf 165: onsuccess: #582: 2: Success after binutils/gcc: 115 commits new d090e0ca710 166: onsuccess: #583: 2: Success after binutils/gcc: 92 commits new 59f5d4f84c4 167: onsuccess: #584: 2: Success after binutils/gcc: 33 commits new 6d9998f2713 168: onsuccess: #590: 2: Success after binutils/gcc: 237 commits new abaf5074f66 169: onsuccess: #591: 2: Success after binutils/gcc: 144 commits new 2674581c596 170: onsuccess: #592: 2: Success after binutils/gcc: 35 commits new f44aaec7b00 171: onsuccess: #7: 2: Success after binutils/gcc: 228 commits new d4db5b66694 172: onsuccess: #8: 2: Success after binutils/gcc: 41 commits new b65f57426be 173: onsuccess: #9: 2: Success after binutils/gcc: 44 commits new 383bd4245a7 174: onsuccess: #10: 2: Success after binutils/gcc: 11 commits new 07ef67628ac 175: onsuccess: #11: 2: Success after binutils/gcc: 27 commits new 8e6487bebad 176: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 8c76528b600 177: force: #14: 2: Success after binutils: 8 commits new f6fbc233ef3 178: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new 3357778920b 179: onsuccess: #16: 0: Success after binutils: 28 commits new f7fa782d8e2 180: onsuccess: #17: 2: Success after binutils/gcc: 39 commits new fdef183f6ed 181: onsuccess: #18: 2: Success after binutils/gcc: 36 commits new 285b644f87a 182: onsuccess: #19: 2: Success after binutils/gcc: 57 commits new 072e66f5825 183: onsuccess: #20: 2: Success after binutils/gcc: 15 commits new cdafb61ad44 184: onsuccess: #21: 2: Success after binutils/gcc: 12 commits new 9a577eb58f6 185: onsuccess: #22: 2: Success after binutils/gcc: 59 commits new b399004f912 186: onsuccess: #23: 2: Success after binutils/gcc: 43 commits new f67436d6475 187: onsuccess: #24: 2: Success after binutils/gcc: 40 commits new 61ed8dc1dac 188: onsuccess: #25: 2: Success after binutils/gcc: 36 commits new 80cb8099c61 189: onsuccess: #26: 2: Success after binutils/gcc: 41 commits new b11ecf6a000 190: onsuccess: #27: 2: Success after binutils/gcc: 30 commits new d5ab915cb21 191: onsuccess: #28: 2: Success after binutils/gcc: 16 commits new df84558c51b 192: onsuccess: #29: 2: Success after binutils/gcc: 32 commits new 46f61aa828a 193: onsuccess: #30: 2: Success after binutils/gcc: 43 commits new a8af1aeb004 194: onsuccess: #31: 2: Success after binutils/gcc: 36 commits new 9fa15a24513 195: onsuccess: #32: 2: Success after binutils/gcc: 28 commits new a39cef11f6b 196: onsuccess: #33: 2: Success after binutils/gcc: 32 commits new 9e300b8aa3a 197: onsuccess: #34: 2: Success after binutils/gcc: 3 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (524a3c49f32) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1900 -> 1932 bytes 02-prepare_abe/console.log.xz | Bin 2544 -> 2532 bytes 04-build_abe-binutils/console.log.xz | Bin 48916 -> 48968 bytes 05-build_abe-bootstrap_profiled/console.log.xz | Bin 600188 -> 601816 bytes 06-check_regression/console.log.xz | Bin 3040 -> 2556 bytes 07-update_baseline/console.log | 40 ++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++------- 12 files changed, 35 insertions(+), 35 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_kernel/gnu-master-arm-next-defconfig updated (536f2d1bc1e -> 2e6a424357e)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-defconfig in repository toolchain/ci/base-artifacts. from 536f2d1bc1e 53: onsuccess: #6: boot: Success after binutils/gcc/linux/q [...] new 2e6a424357e 54: onsuccess: #8: boot: Success after binutils/gcc/linux/q [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1776 -> 1984 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 26888 -> 26900 bytes 04-build_abe-stage1/console.log.xz | Bin 90584 -> 88816 bytes 05-build_abe-qemu/console.log.xz | Bin 31728 -> 30420 bytes 06-build_linux/console.log.xz | Bin 4832 -> 4568 bytes 07-boot_linux/console.log.xz | Bin 5676 -> 5676 bytes 08-check_regression/console.log.xz | Bin 4224 -> 4220 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 20 files changed, 29 insertions(+), 31 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (659f3e052b0 -> e5be5c51f01)

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 659f3e052b0 226: force: #70: 1: Success after baseline build: no new commits discards 62405cb0445 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] discards 0c6e5afc82c 224: force: #65: 1: Success after gdb: 50 commits discards 94dfbbd1229 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] discards f5f61d12651 222: force: #60: 1: Success after gdb: 16 commits discards bf344a90df7 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] discards 90516df3c33 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] discards d628904170b 219: force: #50: 1: Failure after linux: 2520 commits discards 2a336b7e2b3 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] discards ab62f56d199 217: force: #45: 1: Success after linux: 1 commits discards 3e28e47b3df 216: force: #43: : Failure after baseline build: no new commits discards ec70c3dac99 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] discards 98752a10c41 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] discards df8b0f0260d 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 37b27b39293 212: force: #27: : Failure after baseline build: no new commits discards 158bc5098ec 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 3be50482997 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards b276c9039a0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 070b3d2d32a 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards e513f41c3f3 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4afc6d25b72 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4a77dea95db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4f84fe56100 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6b5a04eff25 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0443390c621 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0c58658bbc8 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards ec7c584c646 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 02d44776646 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d70f98f39a5 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ecf16f44964 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 23ba788ab5d 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards b272eb0ef3e 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 650c0c5a754 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 0d443980e17 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 26f2140554c 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 7c572064eb0 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards e217e3b86d6 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards e75e0afd0d3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards 698f31bece0 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards bb092aa20ae 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards b5834482b5b 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards d3dd7b1837e 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards 2f7ca58d158 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 0120be4d64a 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 34a0fdc800c 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 190807954f7 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards ff7470818f4 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards d989e54b68d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards 58875dcc0cd 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards eb0977bcbf1 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards dc568408e61 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards e20d54ae5bc 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards ea20919cc3f 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 94e963b618f 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 7a0871a05ec 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 466441485e0 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards b3fc5603240 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards 7f179cb8f0e 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards f30e4cb0ee2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 1fef85a2e4f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 0b3464669e1 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 7845edc2317 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards b3cddb94c3e 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards 5c1b2b713c6 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 85f5a725c48 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards c995f025ebe 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 264f6be5384 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards ce9e13440db 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 88ab4618935 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 39088fcd250 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 13ca79fb2fb 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 8a28a01f1ea 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards d9a579691ec 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards d35b2209de4 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards c21c6b9b946 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 7aa42cf9cef 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 8181a0385a8 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards fb36448b6be 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 6173a79524f 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards bd2d458ca5e 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards e5de2e0fc12 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 73676157b9f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards b4b5a99c578 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards dc5d6395b35 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards d5d4ba71dc5 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards ecb23953ddb 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 4f601f28746 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards dd1f104df68 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards 40c6a35b15c 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards d62b83dea96 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards d48ae12d8ae 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards d6f6a7961df 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards 4f993c7e31a 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 0c91d689103 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards f83afb080e0 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards bf335ceb744 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards fbe5833aaaf 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards db05500338e 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 9f7a3ee8cee 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 6044ea33321 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards efc19995102 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new d891f2cddd9 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 55a845bcaa2 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 74fd315fdd7 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 88946c20e45 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new 770623e34f8 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new 6b754c92dde 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new f24f3f4cec1 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 583c02d619a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new 7113bcd38d6 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 0292cdfcd85 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new a60ab4962fa 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 56cefbef595 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 74e0a7ecbe3 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 2488e45e125 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 2711e72b48b 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new b057e801766 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 322229cbefa 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b5b5ee6cafc 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 1e332e86ffb 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new a25f0dda737 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new ae384554af0 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new 6a0f4ddb8c4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 8626e0c2685 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 8d429357910 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 87c1da0dcfc 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new d8ab2efffa6 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 0e59b151c01 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 2876f527a5d 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new dee39530a2f 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 25b74ccb3ef 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 3d8ee57d42b 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new ed1e575abec 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new b0be52e5a36 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 46f70764367 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new de087933b9c 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new fd3fb2a6370 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 1fd8f3ff105 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 4a64ebd1eb1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new 1f8eaad8e1f 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 35a67ccb722 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 740fd51ca96 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 5415d9f514a 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 2165818a65b 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new f4d38a9d8d9 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 9f32362d5d9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 9fabab7c36f 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new e3f9e63ba73 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 25f1b7075b9 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new b9f24287aec 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new ad6f46cbe11 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new a2df64a7c56 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new 97c698c0a1a 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new ec2e83fdf8a 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new a9164553dd6 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 93c23d56b66 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new 0ebddda3fab 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new bf6c7ff8883 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new d5eb47c3de4 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 222a4cf81b4 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new 6c26a084fe1 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new 73c0385842c 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new c2b86dc0aad 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new 6b7887041d7 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new b4445ba21b9 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 0f85cb17624 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new ac5d3791db9 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 02cd84e7810 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new c9944970189 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ca7b16de4b6 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 459143fdd49 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 97773a24c25 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 1c6d2a21c89 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 5c00c50bc98 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c7b32ac005e 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 6d551de67cb 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new bce651a18cc 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new d6c7787dfba 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 386a87b977e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 9c3643cdf00 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new c944f9208db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 49dbb1e9c7b 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9fbe9f78106 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c0af1626020 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 3ed4663e4c7 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 72af0194629 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new bdd6f8750c6 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 55794639a55 212: force: #27: : Failure after baseline build: no new commits new 8980b401b54 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new d115b49ec20 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g [...] new 7b81c36e834 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g [...] new 5137ab170f4 216: force: #43: : Failure after baseline build: no new commits new 8e6b997d3c7 217: force: #45: 1: Success after linux: 1 commits new 53d2d76faa6 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g [...] new 9dabe67e42d 219: force: #50: 1: Failure after linux: 2520 commits new c6d058c7bc2 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02dd [...] new 210ca956980 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g [...] new 6a27129b0e9 222: force: #60: 1: Success after gdb: 16 commits new c0a3968925b 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g [...] new 30950bb6854 224: force: #65: 1: Success after gdb: 50 commits new 341f6271499 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g [...] new d346d052b22 226: force: #70: 1: Success after baseline build: no new commits new e5be5c51f01 227: onsuccess: #72: 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 (659f3e052b0) \ 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 2092 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2524 bytes 03-build_abe-binutils/console.log.xz | Bin 49328 -> 48696 bytes 04-build_abe-gcc/console.log.xz | Bin 235344 -> 234820 bytes 06-build_abe-linux/console.log.xz | Bin 8580 -> 8356 bytes 07-build_abe-glibc/console.log.xz | Bin 233912 -> 233092 bytes 08-build_abe-gdb/console.log.xz | Bin 49900 -> 50116 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3760 -> 3768 bytes 10-build_abe-check_gdb/console.log.xz | Bin 7908 -> 7876 bytes 11-check_regression/console.log.xz | Bin 2528 -> 5340 bytes 11-check_regression/mail-body.txt | 14 --- 11-check_regression/results.compare2 | 110 +++++++++++++++++- 12-update_baseline/console.log | 46 ++++---- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 16 +-- mail/mail-subject.txt | 2 +- manifest.sh | 32 +++--- sumfiles/gdb.log.0.xz | Bin 2822600 -> 2888000 bytes sumfiles/gdb.log.1.xz | Bin 146940 -> 146580 bytes sumfiles/gdb.log.2.xz | Bin 20104 -> 15220 bytes sumfiles/gdb.log.3.xz | Bin 10072 -> 10328 bytes sumfiles/gdb.log.4.xz | Bin 10276 -> 10276 bytes sumfiles/gdb.log.5.xz | Bin 10332 -> 10332 bytes sumfiles/gdb.log.6.xz | Bin 10148 -> 10344 bytes sumfiles/gdb.log.7.xz | Bin 10168 -> 10224 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 10096 bytes sumfiles/gdb.sum | 43 ++++--- sumfiles/gdb.sum.0 | 53 +++++---- sumfiles/gdb.sum.1 | 76 +++++++++---- sumfiles/gdb.sum.2 | 209 ++++++---------------------------- sumfiles/gdb.sum.3 | 40 +++++-- sumfiles/gdb.sum.4 | 69 +++++++++-- sumfiles/gdb.sum.5 | 81 ++----------- sumfiles/gdb.sum.6 | 23 ++-- sumfiles/gdb.sum.7 | 59 +++++++++- sumfiles/{gdb.sum.4 => gdb.sum.8} | 17 +-- 40 files changed, 482 insertions(+), 418 deletions(-) create mode 100644 sumfiles/gdb.log.8.xz copy sumfiles/{gdb.sum.4 => gdb.sum.8} (99%) -- 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/llvm-aarch64-master-O3_LTO created (now 644fa90e36a)

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/llvm-aarch64-master-O3_LTO in repository toolchain/ci/base-artifacts. at 644fa90e36a 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] This branch includes the following new commits: new 644fa90e36a 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig updated (a29e6fa7e8b -> 587b6a0ed44)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from a29e6fa7e8b 55: onsuccess: #11: 21862: Success after binutils/gcc/linux [...] new 587b6a0ed44 56: onsuccess: #12: 21863: Success after binutils/gcc/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 1772 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27736 -> 27168 bytes 04-build_abe-stage1/console.log.xz | Bin 71640 -> 70808 bytes 05-build_abe-qemu/console.log.xz | Bin 31312 -> 32380 bytes 06-build_linux/console.log.xz | Bin 8632 -> 8628 bytes 08-check_regression/console.log.xz | Bin 4516 -> 4216 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 27 insertions(+), 29 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (ba06f494635 -> 24c36c6e845)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from ba06f494635 57: onsuccess: #7: boot: Success after binutils/gcc/linux/q [...] new 24c36c6e845 58: onsuccess: #8: boot: Success after binutils/gcc/linux/q [...] 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 1756 -> 1988 bytes 02-prepare_abe/console.log.xz | Bin 2548 -> 2592 bytes 03-build_abe-binutils/console.log.xz | Bin 27464 -> 26952 bytes 04-build_abe-stage1/console.log.xz | Bin 89140 -> 88596 bytes 05-build_abe-qemu/console.log.xz | Bin 30772 -> 31988 bytes 06-build_linux/console.log.xz | Bin 4568 -> 4600 bytes 07-boot_linux/console.log.xz | Bin 5676 -> 5680 bytes 08-check_regression/console.log.xz | Bin 4296 -> 4180 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 4 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 19 files changed, 26 insertions(+), 28 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (f3f2f3aa379 -> 3da4adcab52)

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 f3f2f3aa379 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 79767a1a156 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards b8bc2ec1fe6 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 616f3b736dd 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 78bd8f9baea 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards a8eafbe23a8 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards f568e0f77e6 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 403a5256e42 214: onsuccess: #26: 1: Success after binutils: 12 commits discards f731721f66b 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards 20e68eb1065 212: force: #24: 1: Success after binutils: 2 commits discards 333622c042d 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 1174e76d353 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 955fec501ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 51618eff352 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 7fe2a5bd673 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 4927e758c81 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards cc1c48ae204 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4f68489e8a9 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4902316cb77 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 2be42943967 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards aac064cef3f 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards f4c10a4a35b 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 9f43c597711 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards a0533196bc2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 06dc79ae0d0 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d4122b9acde 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards d454169b0c5 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 86f49ac66a9 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ed612d36ead 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards cd255cb9940 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9c47b02b1fc 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 4a0d9388480 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards beeae4dc6a8 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 17df9834517 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 139aa136c56 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards d497cfd35c5 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 1977dd85627 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 9c8c58e5c1a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards d9d46f5ac9d 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 82ae35fc7d0 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 81edb8fa092 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards 6a106e5236a 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 81662f34b02 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards d8af7096426 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 51ff81e9409 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 3d2632b0c96 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 56d5e41abb8 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards faf846c3992 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 8ada91956c6 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards 019da3f76ef 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards c6743c61c1c 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 1c829ae9551 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 966888d63ab 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 11031e54b2b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 12488e8cf7f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 14d1beb814a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards a26e98daee9 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 23f91382922 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards cf498eac1ac 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards c99d0cb7944 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards e3588dcaef9 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards 09e1cc55758 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards ee9aea17bfd 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 7c730c8741a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards e0c48bdafb3 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 92c6133735f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 94051a25f15 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards b7ca4b8236e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards fa91920a935 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 331ed43525b 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards d0798f19a1d 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 409b671a1ea 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards 11727ba1560 149: onsuccess: #684: 1: Success after linux: 10 commits discards 49e993a5945 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 897a35ce4e5 147: onsuccess: #681: 1: Success after gcc: 6 commits discards a1e5af08920 146: onsuccess: #680: 1: Success after binutils: 20 commits discards cae94b84d41 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards b27db1acfd4 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards d69278851b6 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 3cbcd12be02 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 49eda5e29da 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards f4b4212efc1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 2d9d92fc21b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 443cf80686f 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 3ff2bae9933 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 7f58674c332 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 59da88b1803 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 732c2ff61f8 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 74c2de29dcf 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 07b01434c14 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 696e4b9d601 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards ad615d1da46 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 56189f5da52 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 879ec17e65b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards ec3d80e4449 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 4d1e8c5a43a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 537a2817e3b 125: onsuccess: #658: 1: Success after linux: 3224 commits discards cb5b967bc7b 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 70ae864e477 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 5d7e343d90c 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards c60d424776b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 4bcfbc7490b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 749744e782f 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new cd746593ff3 123: onsuccess: #655: 1: Success after binutils: 22 commits new 6a121413d41 124: onsuccess: #657: 1: Success after glibc: 2 commits new 6e6461ae5a3 125: onsuccess: #658: 1: Success after linux: 3224 commits new 142ed6aa719 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new fe33cb079bf 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 380f1edf3c7 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new d9633133adf 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new a16fab2f27c 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 12f7acf0b07 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new d35dd9cf5eb 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 5e057514811 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new a8ed71f32d1 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 1e40cf196d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new eef4406ea24 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 503e4edf1a8 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 498a0890f50 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new ba3c5111e24 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new 1097d04a990 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new e398205ff04 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 9ad2636230d 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ccd9aa5116e 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 408b04c4b14 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 068a9962d53 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new ed9c5787dd3 146: onsuccess: #680: 1: Success after binutils: 20 commits new 14d06284f09 147: onsuccess: #681: 1: Success after gcc: 6 commits new 8ef70b66b87 148: onsuccess: #683: 1: Success after glibc: 9 commits new b0a803452bf 149: onsuccess: #684: 1: Success after linux: 10 commits new 4967a1340e2 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new 953c9cef35f 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 23b40fd7d60 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 5f10df012cd 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 829666b1eab 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 68bfcbd83e2 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new b6ea428944e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new ba80d7ce826 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 4a534108718 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 93e44f75aac 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new b4ff12e437c 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new d2658339427 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new 5a647edfb99 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 2b1a1c5b95f 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 703db0a225c 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new db51176a767 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new fa874254d15 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new b7fbe7ed605 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new eb1afa15712 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 868c5f89558 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 1600b5e132a 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 82354a06b96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 0a9c50af9af 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 8e4552d04cd 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new d77b6a13946 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 413824e18c2 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 65f110ea78a 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new cfde8d602f1 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 01af38a1e0b 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 9069a90e939 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 292f6b54cd5 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 2f6a6a47565 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new f0113369d4b 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 91ef39f2cfd 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 9e9d3e95bf1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 6d8917ee7b9 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 5019fdd3236 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new cdbf2af681c 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 5bffdff4c35 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new cfaa043e637 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 2a9ec992007 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 28011f6e09a 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 1c8189e8d1c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 9fb102550c8 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 5b3f9903fe8 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 8bc8ea72280 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new ce0552ca16d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new c0faf349706 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new df3dcba355a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 1cd2730d504 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 4b2c9e19509 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 67dd291584c 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new ea9dede1e7f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 039c9a078ca 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 192a8d2a0c0 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new c823353a2bc 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new b288ed9ea8f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new a038ffc12f1 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new bb80c5dfd3b 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 713dfe7f517 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new effc8ec0f75 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 2ba09d4a881 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new c40ca0c2b55 212: force: #24: 1: Success after binutils: 2 commits new b62f293f2a0 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 54ab6c39a5e 214: onsuccess: #26: 1: Success after binutils: 12 commits new b523b7d335e 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new faa6293b5d1 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 996c32068ba 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 98bceb5a0e1 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 6dc20ccc631 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new edf6aa9a1e3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 0d94d8e6a2a 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 3da4adcab52 222: onsuccess: #36: 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 (f3f2f3aa379) \ 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 2048 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2572 -> 2528 bytes 03-build_abe-binutils/console.log.xz | Bin 34892 -> 35136 bytes 04-build_abe-gcc/console.log.xz | Bin 203564 -> 203396 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8872 -> 8392 bytes 07-build_abe-glibc/console.log.xz | Bin 241428 -> 241460 bytes 08-build_abe-gdb/console.log.xz | Bin 34396 -> 34636 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3796 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2092 -> 2120 bytes 11-check_regression/console.log.xz | Bin 4908 -> 4196 bytes 11-check_regression/results.compare | 10 ++++---- 11-check_regression/results.compare2 | 6 ++--- 12-update_baseline/console.log | 40 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++++++------------ sumfiles/binutils.log.xz | Bin 62936 -> 62984 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 84000 -> 83964 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122584 -> 122620 bytes sumfiles/ld.sum | 4 +-- 28 files changed, 57 insertions(+), 57 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 (3873f543ebc -> 311367f181b)

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 3873f543ebc 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] discards 6aeee0ee43e 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 5db8b196c01 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards 84e61f25033 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards b64c4036952 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards b4aa3b2ab49 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 7d412dfc7c5 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 51e56074c9a 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards 6a1200aff36 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards dd7f0c4dd8f 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 05adfbdec80 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] discards 222f0ed56b8 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] discards 36fe1625a09 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards c645e4cb1d8 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards 3d55d44a40e 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards f5c73c657aa 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards 5c308808b83 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 534438909c5 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards b13dd24b29c 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards bc6d4e09839 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards c7a25e68c70 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards b5e72718daf 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards 650bfd57423 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards f4d255924d9 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 1eb1ab821f5 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards cf4ce0f5233 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards a7319b55115 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 9cebe0f7331 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 3f7388f9ce6 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards aaa199a9f52 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards b6bb0c63f5f 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e75b6dfb701 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 441028ce8b5 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards 77132393b7d 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards 083a77cf9ee 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 8dafc013f0c 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards a5e90175fff 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards 99ccb4eb5be 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards 16c26e85606 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards aa0f27a49e4 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards 5fe0a6dd958 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards 0d9f7654d5b 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards c0f4444985f 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 4f5a07811d0 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards 9f605913274 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 08ba9f5b010 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards 778669559e5 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards fd90d7709d6 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards 535dc651850 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 86e884f37cf 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards a5fcf0cef93 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 86b49f1f2a3 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 55c06755014 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards 9b666cf598c 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards 15bd37d63c8 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards bab3e4396c8 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards 54edfb4ba56 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards 3d74d8a03cd 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards 4936dec9b44 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards f55938b9196 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards 5d3110a96a6 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards 8b4febb13d9 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards d4cdf270813 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 10f9891220b 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 92ff05d9667 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards a642c346cba 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards ccdaba845ea 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards f6fa5dac981 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards 9cb0e473b37 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards af8b5a3c6a0 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards 722836bd865 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards 00bba7f467d 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 97387e0231a 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards 3ba977e7931 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards 05084a82d76 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards 05e388a6668 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards 9e226fa97f3 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 13da4455dcf 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards 1336b399051 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 6074e31a1dc 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards c1bdc1d9bbd 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards 97b92aa9b42 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards f7f45f624b9 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards ae72e06d908 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards da7447192ca 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards d96a85fbf60 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 606ba6e51c9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards fb07284aa39 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards f65936c8523 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards bf7318eac4b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards 2ef687188c9 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards b768305fd1e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards 89158ac807d 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards 8b7f10a0d80 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards de9ea445166 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards 461ddafc6da 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 13ce8f5a78b 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 032d7c62aab 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards 7577d2a543d 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards 26b4ad04a56 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards eb12821b15c 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new c4a0c1ac33e 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new e68073243bd 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new 11179850ea0 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new a655d22f6de 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new d4e8ae65cb0 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new cf74ff7f0cc 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new 7fba13c9d55 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new 08ff5003c9c 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new 8e4b45a4e6a 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 208e931cd49 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new b96ac76355f 384: onsuccess: #2205: 1: Success after gcc: 2 commits new 90f5e062504 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new b87a9355168 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new b0e8aba8c6c 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 01176a9a0ba 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new c776201e998 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 9a2a307b782 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new a27ffe6d2aa 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new 7cf621adf13 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new 729aeb7a7ca 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new c218070d0f7 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new c6a85bf0271 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new 6adae124a37 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new fa08f3ebab6 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new d8340ddd4ad 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new 58b4e3717ad 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new a386c9bde79 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new 10495ef1844 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new 75adc1cef64 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new a1299d9f884 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new a2795e3f396 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new 6fdd2906f4a 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 866425a1aa4 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new 974974f1afc 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new c0eb7380e67 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 17cd2d0f98c 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new 47c1d758c75 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new 3c7c7e22213 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 79cc905147c 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new 278d69dba8a 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new 06d1d5edd35 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new bde08dd0102 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new a9403033cdc 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new 110307cdecd 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new 52f6d5694cc 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new 248b9de3851 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new a81edf14d01 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new be8fdb020d5 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new 1bb6d185a63 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 915dd6f958a 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new ccf2299c39b 424: onsuccess: #2248: 1: Success after gcc: 6 commits new f2f2187c650 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new 3ff5db123e6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new c67bfb58c1e 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 242dc28312e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new cd569b23ee3 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new 596463298bb 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new d4e1dd07be4 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new c4c946065c0 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 03b6c039dcb 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new ebcb5ca8756 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 30be881fb20 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new 23cc5370e24 436: onsuccess: #2260: 1: Success after gcc: 7 commits new 775a7e79b99 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new 4b1fa1b874a 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new f126f5e261b 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new 778aef157ad 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new 7e63b907e75 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new c68e2034a5c 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new 44578f87071 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 4640105e5e3 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new b64b30c07fd 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 2dd54796528 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 411f32628f4 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new d2a5a8f532e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 99ed9f7a249 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 723464357ca 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 17b01dcca05 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new fd300b4463d 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 8dd092dfeb2 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new 41d449fe87f 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 90e86bdccb5 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 95009fa78a2 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 5a174ec6cbf 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 70b2d5b7f61 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new a04bb9ef7b4 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new 579ff6806c4 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new bd9499dd407 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 536245af7da 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new 94d033d8d7a 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] new ecdb4b4ab1d 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gl [...] new d88b3ba9641 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new 59ab9c83b7b 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new d057245247b 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 331dd41b54a 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new e69f10e8607 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new b5985ba64cb 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 4871b87c499 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new 10bfe75d373 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new f9d9b7540f2 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new 70f7e1e7bd1 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...] new 311367f181b 475: onsuccess: #36: 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 (3873f543ebc) \ 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 2116 -> 2120 bytes 02-prepare_abe/console.log.xz | Bin 2576 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 26816 -> 26900 bytes 04-build_abe-stage1/console.log.xz | Bin 89848 -> 88888 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8896 -> 8384 bytes 07-build_abe-glibc/console.log.xz | Bin 232948 -> 233644 bytes 08-build_abe-stage2/console.log.xz | Bin 224992 -> 225104 bytes 09-build_abe-gdb/console.log.xz | Bin 34288 -> 34512 bytes 10-build_abe-qemu/console.log.xz | Bin 32008 -> 32068 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3856 bytes 12-build_abe-check_gcc/console.log.xz | Bin 7388 -> 6128 bytes 13-check_regression/console.log.xz | Bin 11268 -> 4928 bytes 13-check_regression/results.compare | 24 +- 13-check_regression/results.compare2 | 1885 +---------- 14-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +- sumfiles/g++.log.sep.xz | Bin 112204 -> 188208 bytes sumfiles/g++.log.xz | Bin 2661068 -> 2664340 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 2590 ++++++++++++++- sumfiles/gcc.log.sep.xz | Bin 177468 -> 189152 bytes sumfiles/gcc.log.xz | Bin 2235960 -> 2227788 bytes sumfiles/gcc.sum | 4 +- sumfiles/gcc.sum.sep | 4370 ++++++-------------------- sumfiles/gfortran.log.sep.xz | Bin 53764 -> 39972 bytes sumfiles/gfortran.log.xz | Bin 897736 -> 898136 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 5526 ++++++++++++++------------------- sumfiles/libatomic.log.xz | Bin 2284 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217100 -> 217404 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 12656 -> 17028 bytes sumfiles/libstdc++.log.xz | Bin 446448 -> 438980 bytes sumfiles/libstdc++.sum.sep | 662 ++-- 46 files changed, 6371 insertions(+), 8828 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023