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-spec2k6/gnu-arm-master-O2 updated (049d65cbb19 -> 8d1bcf27342)

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-spec2k6/gnu-arm-master-O2 in repository toolchain/ci/base-artifacts. from 049d65cbb19 95: onsuccess: #29: 1: [TCWG CI] No change after gcc: 23 commits new 8d1bcf27342 96: onsuccess: #30: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2084 -> 2040 bytes 02-prepare_abe/console.log.xz | Bin 2488 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 27400 -> 26964 bytes 04-build_abe-stage1/console.log.xz | Bin 89576 -> 90004 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8268 bytes 07-build_abe-glibc/console.log.xz | Bin 234424 -> 233520 bytes 08-build_abe-stage2/console.log.xz | Bin 214884 -> 210968 bytes 09-benchmark/benchmark-build.log | 148 +- 09-benchmark/benchmark.log | 146 +- 09-benchmark/console.log.xz | Bin 4140 -> 4160 bytes .../compare-results-vs-first-internal.csv | 249 +- .../compare-results-vs-prev-internal.csv | 253 +- 10-check_regression/console.log.xz | Bin 15232 -> 17380 bytes .../csv-results-vs-first-1/md5sum.csv | 2488 +- .../csv-results-vs-first-1/perf.csv | 3375 +- .../csv-results-vs-first-1/results.csv | 35815 +- .../csv-results-vs-first-1/size.csv | 298183 ++++---- 10-check_regression/csv-results-vs-first-1/sve.csv | 12516 +- .../csv-results-vs-first-1/vect.csv | 22 +- .../csv-results-vs-prev-0/md5sum.csv | 3094 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 3312 +- .../csv-results-vs-prev-0/results.csv | 29286 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 683231 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 26868 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 48 +- .../csv-results-vs-prev-1/md5sum.csv | 2488 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 3375 +- .../csv-results-vs-prev-1/results.csv | 35815 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 298183 ++++---- 10-check_regression/csv-results-vs-prev-1/sve.csv | 12516 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 22 +- .../output-bmk-results/exe.improvement.diff | 0 .../output-bmk-results/exe.regression.diff | 0 .../output-bmk-results/symbol.improvement.diff | 0 .../output-bmk-results/symbol.regression.diff | 0 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 3318 +- 10-check_regression/results-vs-first-internal.csv | 253 +- 10-check_regression/results-vs-first.csv | 253 +- 10-check_regression/results-vs-first.log | 1490 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 11 +- 10-check_regression/results-vs-prev-full.csv | 3478 +- 10-check_regression/results-vs-prev-internal.csv | 253 +- 10-check_regression/results-vs-prev.csv | 253 +- 10-check_regression/results-vs-prev.log | 1752 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 16 +- .../squad-vs-first/401.bzip2/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metadata.json | 16 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 16 +- .../416.gamess/results-metadata.json | 16 +- .../squad-vs-first/429.mcf/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metadata.json | 16 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 16 +- .../435.gromacs/results-metadata.json | 16 +- .../436.cactusADM/results-metadata.json | 16 +- .../437.leslie3d/results-metadata.json | 16 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metadata.json | 16 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 16 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 16 +- .../453.povray/results-metadata.json | 16 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metadata.json | 16 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 16 +- .../459.GemsFDTD/results-metadata.json | 16 +- .../462.libquantum/results-metadata.json | 16 +- .../464.h264ref/results-metadata.json | 16 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 16 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 16 +- .../471.omnetpp/results-metadata.json | 16 +- .../squad-vs-first/473.astar/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metadata.json | 16 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 16 +- .../483.xalancbmk/results-metadata.json | 16 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 27 +- mail/mail-body.txt | 27 +- mail/mail-subject.txt | 2 +- manifest.sh | 35 +- results_id | 2 +- 98 files changed, 730574 insertions(+), 732781 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff delete mode 100644 10-check_regression/output-bmk-results/exe.regression.diff delete mode 100644 10-check_regression/output-bmk-results/symbol.improvement.diff delete mode 100644 10-check_regression/output-bmk-results/symbol.regression.diff -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (a2f3bd40905 -> 676a2dfa36d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards a2f3bd40905 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] discards a3e8a6f471e 212: force: #45: 1: Success after gdb: 22 commits discards 2759eaded92 211: onsuccess: #44: 1: Success after linux: 26 commits discards 96a39158866 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards 1cb48d12dcc 209: force: #37: 1: Success after baseline build: no new commits discards d17f0713e2f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 2f4a5b6b447 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards a3a817bc542 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards ee8112c6c38 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 7bd7d1b51b6 204: force: #26: : Failure after baseline build: no new commits discards 7475a2e9c58 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 3acff44fd78 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 716eca7f7aa 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 9ac1adbc5e7 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards f03f1b33f3b 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 4410098315a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 1362e518391 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 2b36dd67c1f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 45c578b320c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards ef9698e21ec 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 40fab490442 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 1de2d1ffb42 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 7a467e2bc5b 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 62a432d88f8 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 1a9e72d08cd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 26b57efd98e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 34985f333f4 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 8c8c7ab89e0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 93d6e8bcfc3 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 1fd18f13fd9 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 6c66a848189 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards fc9759600a3 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards cddf244cf16 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards d9c50fd1c8f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 3f37dc8c2ec 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards b3e82d8c852 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards 76a9409d7c4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards 7ec203e7dc4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 0ed3d68d64b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards 00baf16a4dc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 22d49a7da5f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards cb4e3c5a7b8 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards 2ef3b29caac 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards 2bb92bb00e6 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 1d1b5162480 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards ba0af039e1b 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 12ed260f714 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards a5a051e76a3 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards ba00f41df80 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards 09fb6a4cef8 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards d2ed598f347 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards a1e18d53bfe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 1fa7afb8994 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 1e64e7380c6 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards f653051962f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 155c8647dae 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 5037db2e97c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards 31b91904e13 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards dbd05306ff5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 3fc474b2656 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 23d8944bdef 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards ff429a861d0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 11b15f7b847 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 8abd35a9d7d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards bb1123679f5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards 91a01282c78 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 39d3862daea 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 634d717b446 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards f57c6578fab 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards 826e6e2c7a1 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards b822ea73963 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 2b06475c36a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards d758021033e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards 38bf28fd398 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards e3fb1ac0bee 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 522c9b5c6c0 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 0e5d737c878 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards 4507c013a1a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 60e7291aa64 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards f673c4d0653 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards 46d9298ef3e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards e6475d546a8 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 6f9d1482d55 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards c883400d928 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 94d7d2dc0ac 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards bdfdad5db34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 580fda299e7 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 7f03f374dc9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 47c52bc6b91 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 571862398bf 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 256fafec951 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 19bbcb285ca 122: onsuccess: #909: 1: Success after linux: 2753 commits discards a7eefa4fd45 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 7762b129ae7 120: onsuccess: #906: 1: Success after binutils: 29 commits discards 585c6002f06 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 6eae1cedcb2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards d34ae3a039d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 43df5d1cdc7 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 809564829b1 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards b4dc6b81f2e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 748c3e40c82 113: onsuccess: #898: 1: Success after linux: 3 commits new 4792edeed1f 113: onsuccess: #898: 1: Success after linux: 3 commits new 83de2595818 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new d2da3e0b462 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 51a85d3aed1 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new 32e437c5cf3 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 25106cb60fa 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 205a8838338 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 661e772f3ae 120: onsuccess: #906: 1: Success after binutils: 29 commits new 5671b5e5d74 121: onsuccess: #908: 1: Success after glibc: 2 commits new 615701c2141 122: onsuccess: #909: 1: Success after linux: 2753 commits new 8753f8c778a 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 689d47bfbd5 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new a36e6ad46af 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 6cc0d0095b7 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new bb768091813 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 63903513700 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 118459a6189 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 95099a9eb09 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 6f43486b1f3 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new 5e4f3ef0c73 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new d3a603811aa 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 3a44f0161ae 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 56ff421ad70 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new a8c4c13884f 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 11ca4c3b4c7 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new aec2af564ca 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new e23bdc726a3 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new e74be90e5a5 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new 549309d4458 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 896aed9bbda 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new a05f6cf5610 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 60a558aea3d 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new 860fe65dd60 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new e45b83f170f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 444fbf48a89 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 0c805a08450 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new a35b84a61e7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 19cd02866e4 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 54c8ba01985 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 349bd004bdf 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 8ebde80cf0e 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 78caa6228e8 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 8f520848f10 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new b76c8ad9732 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5433fdc61e7 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new bc619a20956 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new d44eb24f557 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 0aa2fb7ad9d 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 6b6fa44af0b 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new 4906ae6a340 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new e07c3bc2bfb 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 2663595e16e 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new 06dc1fcc481 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new 8b2b81cd674 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new ab52fe32c5e 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new a6219a56b74 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new fce3267068d 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 051dd5e3a36 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new ce75b2a183b 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new 22614ee11e7 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new cbb43d36cfa 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 64015d0dc2a 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 5b65896b44e 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new c1d69851206 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 2505dafe883 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new 3d87b2db340 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 5ce72244020 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new 29f71c22964 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new ee67736bb8d 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new 43ee6fcc89e 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 47b1992225a 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new f0da3e7328f 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 30dbb9aee64 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new ad17c45f65c 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 1f68f408ab1 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 262cc6b7eec 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new fcd8a4b2917 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 6e3daaf7b70 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 26902ec3a71 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 0a4a8bc03fd 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 2dbd39bb04f 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 74c053a8bee 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 476188ef4de 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 79ab5101e64 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 84d926d61ec 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new f056c7f47e1 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 694230570eb 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 946278acd1d 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 019b521e02b 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 9e71045f64c 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new f3745e43e27 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e499f7417dd 204: force: #26: : Failure after baseline build: no new commits new 7fff02c3986 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new cbea1943e07 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 22e65d17e09 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 7be32c24106 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 701f90ab597 209: force: #37: 1: Success after baseline build: no new commits new 6962c12b82c 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 539c73cb306 211: onsuccess: #44: 1: Success after linux: 26 commits new 721070651a2 212: force: #45: 1: Success after gdb: 22 commits new 33718ff48c5 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] new 676a2dfa36d 214: onsuccess: #47: 1: Success after gdb: 21 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 (a2f3bd40905) \ 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 2072 -> 2088 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2488 bytes 03-build_abe-binutils/console.log.xz | Bin 35248 -> 35468 bytes 04-build_abe-gcc/console.log.xz | Bin 203300 -> 203728 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8460 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 242420 -> 242400 bytes 08-build_abe-gdb/console.log.xz | Bin 34728 -> 35048 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2720 -> 3088 bytes 11-check_regression/console.log.xz | Bin 3048 -> 5072 bytes 11-check_regression/results.compare | 79 +++++++++++++- 11-check_regression/results.compare2 | 158 +++++++++++++++++++++++++++- 12-update_baseline/console.log | 40 ++++---- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 16 +-- sumfiles/gdb.log.0.xz | Bin 1952768 -> 1949228 bytes sumfiles/gdb.log.1.xz | Bin 25384 -> 21000 bytes sumfiles/gdb.log.2.xz | Bin 5204 -> 5420 bytes sumfiles/gdb.log.3.xz | Bin 5428 -> 5408 bytes sumfiles/gdb.sum | 122 +++++++++++----------- sumfiles/gdb.sum.0 | 116 ++++++++++----------- sumfiles/gdb.sum.1 | 187 ++-------------------------------- sumfiles/gdb.sum.2 | 4 +- sumfiles/gdb.sum.3 | 4 +- 29 files changed, 399 insertions(+), 337 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_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (c8486b659eb -> 6ae6715c8d4)

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-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards c8486b659eb 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits discards bdbec87611b 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits discards c6150c41f99 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards 618e34c249d 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards e3471eba6fc 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards bcc66e57471 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards 3769e3a4a8f 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards a3362048693 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards 19b8b42641c 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards 29b77e77b27 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards 32af0db6bce 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards dff5f0901a7 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards 66ecb21296c 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards 95ad7ee018c 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 1dc8e31ee86 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards e5f841351c9 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 5b2c4d5f4c9 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards 53a9acca04a 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards fdd150159e3 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards ce007b1ce8b 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 543c4c03de3 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards b50b5e15c6f 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards f6d53064f6e 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards b8409f535cd 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 157730607d4 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 51db723150d 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards 2d2fe7aed6f 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards f43c655b074 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards 95907458656 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 9e65ba26375 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards 9cc10067fbb 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 420ce34fd22 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards 9b1c4f4d7dd 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards b2cfd1e8016 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards bb61876c19a 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards e39dcd884e1 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards e5cc5ac99a2 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards ee15bb675f0 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 207416da210 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 3144c7ce602 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards 57865a3141a 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 29d8f722a77 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 8c040421162 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards 836ecdeeb1b 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 046f9f5faa2 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards e24defd2c39 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 2082328dce0 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards fcf1fdf7e0f 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards ed11bf1dda1 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 2afe92e1343 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards fcce7a7db95 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards f21b4fc5efa 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards 47ed976dcbb 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 127dd371606 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 740272b0839 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 45e6d1a89ee 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards 6f83c7cf26d 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards 8e764e2ef9f 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 7402d5984f3 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards ed76086d05b 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards 4bcfb0c12b3 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards 58eacaee8a0 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards a1ed0e279d1 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards 967d61ebc67 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards cf5e12b9b22 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards 87072ea718d 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards d92a72d6861 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards ba6c2e6eaa2 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards e0df6798dbd 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 5f4ef8525d3 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 342207cd3c9 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards dacc3b19c1d 141: onsuccess: #559: 1: Success after gcc: 4 commits discards bfe5f601bf6 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] discards 13dca9f737e 139: force: #557: 2: Success after gcc: 6 commits discards 3b255d0b17f 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 50f368fb8b4 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards f1c08feb313 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards ea3aa102656 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards 453f6588bf1 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards 22570f835df 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards d132beba715 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards 76af2be307b 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 2ddc1403c24 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards a15c589c18c 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards aa066870c9b 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 5a76de66dd9 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 513ad3748ff 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards 535a1ce7bc8 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards 4889dd2921d 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards e4a3f8f336d 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards 01f60b7e047 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards dcefe3e7c22 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 130a19a71aa 120: onsuccess: #535: 1: Success after binutils: 10 commits discards 54295f82a8c 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] discards f0e09be0437 118: force: #533: 2: Success after binutils: 4 commits discards 7f75db353f9 117: onsuccess: #531: 2: Success after gcc: 65 commits discards 89aabae787f 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 9b2a2120a62 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards 6ddfeb4c046 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards a9b51f9ebe6 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards e056abeeff3 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new fb8cba56924 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new 43978104776 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 4506b60621a 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new 93823de4fd2 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 39e3468ca4b 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new 85c558828de 117: onsuccess: #531: 2: Success after gcc: 65 commits new 8339afdff81 118: force: #533: 2: Success after binutils: 4 commits new cbe549f0e95 119: force: #534: 1: Failure after gdb-12-branchpoint-3046- [...] new 7e3a7da4e98 120: onsuccess: #535: 1: Success after binutils: 10 commits new 2e35b98e321 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new d5e5f9b202d 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new 62b4bc32d59 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 3439e0b96eb 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new ebc32773ed3 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 0015113d93f 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 08e078e5721 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new 8a7f93104ca 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new e31c94db1bd 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 3df20d4b47c 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new eb9e48dbdc5 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 8d47ac85bae 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new b8eeb36e4c8 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new c945b0b3b1a 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 7816b7c5c67 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new a24f4326c90 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new 4409703575c 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new e82a0a7a611 138: onsuccess: #554: 2: Success after binutils: 10 commits new 82186dfd247 139: force: #557: 2: Success after gcc: 6 commits new 41254c0e357 140: force: #558: 1: Failure after basepoints/gcc-13-4953-g [...] new b69001ace08 141: onsuccess: #559: 1: Success after gcc: 4 commits new c258887e3f8 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new 9bf583d3be0 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new 6e989de4fde 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new 8efc86085cd 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new b6e095d51b9 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 9d5d429564f 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 2d9032d6d84 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new f1c1e7c406f 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new f19cf337f0b 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new 1872ae46882 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new e4106f7b5db 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new ff58689bfa3 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new c1c71851510 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new ca37a1a8a34 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new d9babcc7c4c 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new c972aad9485 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new d33a000cf96 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new fd06706f412 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new 36038402586 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 15a3c388137 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new b17766e84eb 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 3206f955f3a 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new c25653a4b0d 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new d8d709c3114 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 84c894ffed2 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new 12a1859b52f 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new a06813f4717 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 4debc53dd38 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 4eeebb358d1 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 14b7d231d4f 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new ccd59d5ef84 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 17d7d49eec8 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new b27ba140ce2 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new cae63a42b66 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new 64fbb9301f4 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 56aea7454ea 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new ad6224238d3 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new 5d28dc1b922 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new da1308d0bda 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 09516159225 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new a048412d95a 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new f4c281b02d8 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 9e46890c605 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new 9d08d2bd1e6 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 39331034593 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 5cb99c61fc1 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new d482a2e172f 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new 31f13a9d937 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 67549d6b060 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new d81f914e9ee 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 2eb349110d3 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new c24b490f85c 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new f2bec1aa86b 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 845ffafb4ee 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 3362c7756a1 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new a54cc4b4444 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new 10ebd1630ee 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new 6e9d2e2ec9d 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new ece833ceb3c 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new cc4c34c4d12 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new 6ec4af8eca7 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 0a9e0c0a1a5 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new 1caeb5f834a 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new 97c96a2d5e7 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new 4d2befa15b4 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new 80df613363c 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new 30a50e67e7e 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new 80b08c54ef1 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new 213be6a89b4 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new ebf62d7267b 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits new fed7ba8abe2 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits new 6ae6715c8d4 213: onsuccess: #29: 2: Success after binutils/gcc: 36 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 (c8486b659eb) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] 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 1928 -> 1976 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2584 bytes 04-build_abe-binutils/console.log.xz | Bin 35164 -> 35172 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 305804 -> 305432 bytes 06-check_regression/console.log.xz | Bin 3084 -> 3120 bytes 07-update_baseline/console.log | 38 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++++------ 13 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

[gcc] branch master updated (80ed2a6471a -> f58cbbb7c90)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 80ed2a6471a c: [PR84900] cast of compound literal does not cause the co [...] new f58cbbb7c90 Don't force target of modulo into a distinct register. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/rs6000/rs6000.md | 12 ++++++------ gcc/testsuite/gcc.target/powerpc/mod-no_copy.c | 16 ++++++++++++++++ gcc/testsuite/gcc.target/powerpc/mod-peephole.c | 25 +++++++++++++++++++++++++ 3 files changed, 47 insertions(+), 6 deletions(-) create mode 100644 gcc/testsuite/gcc.target/powerpc/mod-no_copy.c create mode 100644 gcc/testsuite/gcc.target/powerpc/mod-peephole.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (609e86e4415 -> 9c1597d9e6d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 609e86e4415 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] discards df0e1d40ab2 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards dbf636b0283 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] discards 3a04281a868 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] discards 9567119fb60 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards 9621aaeb497 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 2736333baee 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards a812ece8bd9 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] discards 3b78c2e4d6a 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards 43a01c2cf74 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 4cdd9e52362 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 5adcff13a91 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards cb852f68d74 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 4e0d7c2c19f 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards a9fdf817641 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e76413aeed6 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] discards 6e7db891263 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 437765485a0 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] discards a75a4d2182c 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 0f17d57cc72 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 44df691f6df 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards 8dfa428d5d3 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] discards 8a99a8297cd 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards b926b71bc1d 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 0803601c623 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards f6d3ff426dc 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 802005d0013 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 2350927f993 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 8ac784be2cb 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 7f309b9a70a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 37692d29aaa 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 9c82d457f70 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 2e6b96a8c65 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 9ee40c344a3 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards f459c97f759 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards e1431874691 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards dba59e01a9a 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards f688530775f 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 6ab2a981a14 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 4f6c6247203 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f7e907af5ce 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 00bd5ab59e2 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards e562c58c96f 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards a343af4007e 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards 22e3330f06d 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] discards f5281fb95e3 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] discards 8324b5b8577 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] discards bd890ba69ac 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards a5210a8a3fe 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards 9112621b46c 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 8a37e6b9269 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards 6f1bdb16e4f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards a2546e7b2ef 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 5b7faa16483 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 1d972328350 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] discards 52e05a22996 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 8007764c5d7 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards b1d3a168c64 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 798a006ab7e 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] discards 269cc897e9c 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 3953af1c439 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] discards 183ac8b1fe9 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards c239b332ea0 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards 7078c59d2b2 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] discards 59c419d0577 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 7697e2f025a 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] discards 3ddeafa0263 162: onsuccess: #624: 1: Success after linux: 10 commits discards 4d0170a317c 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 9a63000edd8 160: onsuccess: #621: 1: Success after gcc: 11 commits discards bea9c3f85d8 159: onsuccess: #620: 1: Success after binutils: 12 commits discards e58323db238 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 273352ecccf 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] discards 25394ad1f23 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards ea7812cfec7 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards aebc19515d8 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] discards c985d51ee8b 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] discards c965397e54f 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] discards 7f5ca61fa16 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] discards 6c3bae3164e 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards a9ac3e631f8 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards 76f45ae8b0b 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 146bbb83014 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 56cf845a932 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards 54df84ce860 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards 5a5fa2023a7 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] discards 8caa2c689a8 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards b3abb86dcfb 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards 9a12db58243 141: onsuccess: #601: 1: Success after linux: 794 commits discards a5b5483e110 140: onsuccess: #600: 1: Success after gcc: 23 commits discards 5e03bca1c17 139: onsuccess: #599: 1: Success after binutils: 10 commits discards ed03b354ac2 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 4d8d1a0c785 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] discards 2ce87284f4e 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] discards a40b79b0388 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] discards 5f4b6f3ca70 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards ee2db3895ad 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards d338cae2ade 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards d8d4d1944ce 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards 5d27225e2e0 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards 116118980ba 129: onsuccess: #588: 1: Success after linux: 4 commits discards 54e16e8a9ee 128: onsuccess: #586: 1: Success after binutils: 22 commits new 078a4634d98 128: onsuccess: #586: 1: Success after binutils: 22 commits new 0d1c82f4d90 129: onsuccess: #588: 1: Success after linux: 4 commits new 06186164915 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new 730871843a0 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new edea18e5a43 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new cb54ec526d7 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new ff11815c8a6 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 9ba91237d2a 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] new 7bbfe2d5df7 136: onsuccess: #595: 1: Success after binutils/gcc/linux/g [...] new d969226b849 137: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new 89d16d72651 138: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new affab5c5011 139: onsuccess: #599: 1: Success after binutils: 10 commits new 8a7afc2fc74 140: onsuccess: #600: 1: Success after gcc: 23 commits new b7961e51cf9 141: onsuccess: #601: 1: Success after linux: 794 commits new 4ef0f317cb4 142: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 6ae39aea05f 143: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new afe6f7f0375 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 14 [...] new 0178a129764 145: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 15ecc97e8fc 146: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 401ff94ab05 147: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 05ab5f875d7 148: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new ea1f9215488 149: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 33c1fb06f7a 150: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new eac171ea4f0 151: onsuccess: #611: 1: Success after binutils/gcc/linux/g [...] new 829b7a75a39 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 11 [...] new 14a77e975a4 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 40 [...] new 307b0fcccaa 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 14 [...] new dbe625a62ff 155: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 148d840f502 156: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new e223015a672 157: onsuccess: #617: 1: Success after binutils/gcc/linux/g [...] new 3c0ad7d2805 158: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new 50fcf233b0c 159: onsuccess: #620: 1: Success after binutils: 12 commits new e173f91de0d 160: onsuccess: #621: 1: Success after gcc: 11 commits new b832dd99d80 161: onsuccess: #623: 1: Success after glibc: 9 commits new 425abda21b2 162: onsuccess: #624: 1: Success after linux: 10 commits new 3ae3b0687ae 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/g [...] new 7e31d433a88 164: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new f65db080f8f 165: onsuccess: #627: 1: Success after binutils/gcc/linux/g [...] new d0271d6d5f8 166: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new 64a57758b4d 167: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 50fd60d03a7 168: onsuccess: #630: 1: Success after binutils/gcc/linux/g [...] new 35a47537397 169: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 9c57f0729da 170: onsuccess: #632: 1: Success after binutils/gcc/linux/g [...] new 888d13581f6 171: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new c48e50d77c1 172: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new b290977c26c 173: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new be5b8ff271d 174: onsuccess: #636: 1: Success after binutils/gcc/linux/g [...] new af074126e72 175: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 48ff78d8478 176: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 8ab3484c058 177: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new 87a5575ee7a 178: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new f5b11163316 179: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new f00ff652c04 180: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 2f0168f6ef9 181: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 71a88cd0bf5 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 30 [...] new aae70307ab0 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 20 [...] new fcd9cb51d64 184: onsuccess: #646: 1: Success after binutils/gcc/linux/g [...] new ac85a8974bc 185: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new 588c4a8c72b 186: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new ba65777eae6 187: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 78807c04eab 188: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new c9da7953de4 189: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 7f2559ac2a7 190: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 557d15b826c 191: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new b8115337e1f 192: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 2cc4d480aeb 193: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new f86eb5e8793 194: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 03948748a97 195: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new e49652208d0 196: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 14ebbb39908 197: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 3373d2d3969 198: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new d6ab3232367 199: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new b1e43f03c47 200: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new b654152b067 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new b56b1f1a58b 202: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a6f245a6c25 203: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 3463ae5841d 204: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new f925e27f78b 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 52c35787263 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new 6e5823b5c1f 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gdb [...] new 0caf893d34a 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new ae85dab48a6 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new abacfc6a4ea 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 0380557ee21 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb [...] new 327d5524db8 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 4aaad9a14cb 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gli [...] new 45bec1d35fe 214: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 4cca520342a 215: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 286d3307987 216: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new e93d547af62 217: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7946d2cb643 218: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 59572290413 219: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 0e04ee8cb78 220: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 1d4fa109769 221: onsuccess: #18: 1: Success after binutils/gcc/linux/gd [...] new 58876eb0efb 222: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new e79942c5377 223: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new be2ee92923e 224: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 66d2bbbecac 225: onsuccess: #25: 1: Success after binutils/gcc/linux/gd [...] new c348bcd096c 226: onsuccess: #26: 1: Success after binutils/gcc/linux/gd [...] new e48a64fe758 227: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new f87ee3c2d75 228: onsuccess: #28: 1: Success after binutils/gcc/linux/gl [...] new 9c1597d9e6d 229: onsuccess: #29: 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 (609e86e4415) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2040 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2564 bytes 03-build_abe-binutils/console.log.xz | Bin 48968 -> 49012 bytes 04-build_abe-gcc/console.log.xz | Bin 237688 -> 236856 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8388 -> 8396 bytes 07-build_abe-glibc/console.log.xz | Bin 233788 -> 232940 bytes 08-build_abe-gdb/console.log.xz | Bin 47436 -> 47500 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3820 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9304 -> 9116 bytes 11-check_regression/console.log.xz | Bin 5576 -> 5716 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 122 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 63168 -> 81208 bytes sumfiles/g++.log.xz | Bin 2904900 -> 2912268 bytes sumfiles/g++.sum | 57 +- sumfiles/g++.sum.sep | 11625 +++++++++++++++++++------------- sumfiles/gcc.log.sep.xz | Bin 20364 -> 67068 bytes sumfiles/gcc.log.xz | Bin 2472676 -> 2469108 bytes sumfiles/gcc.sum | 6 +- sumfiles/gcc.sum.sep | 905 +-- sumfiles/gfortran.log.sep.xz | Bin 38528 -> 36364 bytes sumfiles/gfortran.log.xz | Bin 950104 -> 949244 bytes sumfiles/gfortran.sum | 6 +- sumfiles/gfortran.sum.sep | 4258 ++++++------ sumfiles/libatomic.log.xz | Bin 2280 -> 2280 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 233884 -> 233936 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 9052 -> 10152 bytes sumfiles/libstdc++.log.xz | Bin 469848 -> 469128 bytes sumfiles/libstdc++.sum.sep | 479 +- 44 files changed, 9356 insertions(+), 8236 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards ca00b6ef22f 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] discards 29b878ea63b 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] discards d4838f45869 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards fbc17d39d7e 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 237f52df399 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards 45415cc7be7 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards e677cf76c81 121: force: #26: : Failure after baseline build: no new commits discards ed52eadcb3f 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 14a473cddb8 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 12c0271cba3 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 08301457f71 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 01d1723e00a 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] discards 906c0e06466 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 51df27ccb4c 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 84f44244578 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards 7f930572e12 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 23ac64a7392 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 99999ffdd9a 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards aa1f39a1e2a 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 053e78ecd74 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 1ff93b2f29f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 2a2a65be538 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] discards b41f36ed7dd 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 79329742227 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] discards 64105ca7db9 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e343a67a8a4 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] discards a5cdbd659db 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] discards 71bf6b08a81 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] discards f8ddfe5f125 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 7ac64261d87 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] discards 0562cfdae37 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] discards e84153f3da3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] discards 1e87fa39656 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] discards 76b904bb0bf 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] discards e499eda7fc4 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] discards d68c968182e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] discards d61469e804c 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] discards 3a81762ee80 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] discards 99a90110c16 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] discards ded065539f7 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] discards 59129e3d537 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] discards d21652521e7 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] discards b1961f30678 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] discards 0afc14c2d68 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] discards c273cce8c2c 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] discards bda3fb54cbd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] discards f50d42494f6 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] discards f9b150aa66b 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits discards dd75ad0f738 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] discards eccd1bb9eb9 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] discards d6695a11ae3 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] discards 604091260a1 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] discards ac7092bab31 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] discards bf91c7267a6 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] discards d221f97ed2a 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] discards 5ef0e0f9035 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] discards c187d811812 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] discards 4a0ed7cae5e 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] discards 19a73dd0fa3 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] discards 6b81bd48477 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] discards b9e12b786b3 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] discards 3b2443b57f0 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 4832c9ad324 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] discards 498c3dd6132 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] discards 9f54d23fcbf 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards b366e701a2c 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] discards 223d641ae70 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] discards d9d30391bd3 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits discards 6f1401f8f30 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] discards f89a9f4f4b4 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] discards da878a73483 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] discards eff73f64b36 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] discards a2b26326f34 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] discards 72c16ac9a6f 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 03278fbacc0 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 1a6e0f9a41c 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] discards 95ee6ed6228 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards d1a732b97cd 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] discards f45c01a0a47 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] discards 43c76c4f3f4 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] discards de55557b214 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] discards d83eba0b4bb 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] discards 62f5e4c105f 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] discards 5d97ff68a98 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards dfb38c31f65 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] discards 5e5230d4833 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] discards 987c44a82f0 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] discards a36fc0e7553 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] discards 281d5aa2829 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] discards 96330b3f189 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] discards 9bf61c3552d 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] discards bc79b138010 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] discards 7a8f8f27bdc 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] discards 529981d3698 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] discards 3a2bd564e14 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] discards 293489ebb5f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] discards a448c8dc51d 31: onsuccess: #38: 1: Success after linux: 14 commits discards 5a83f9231b5 30: onsuccess: #36: 1: Success after binutils: 18 commits discards a31ab09e0d6 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards c184843ab87 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] discards c210536ec47 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 78ab64da314 27: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new d343c3750a8 28: onsuccess: #33: 1: Success after binutils/gcc/linux/gli [...] new 167ddfe1708 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new fab2f2609c9 30: onsuccess: #36: 1: Success after binutils: 18 commits new fccc8606ba7 31: onsuccess: #38: 1: Success after linux: 14 commits new 920609e3c0f 32: onsuccess: #39: 1: Success after binutils/gcc/linux/gli [...] new 636ad4e955f 33: onsuccess: #40: 1: Success after binutils/gcc/glibc/gdb [...] new 38a9e663c18 34: onsuccess: #41: 1: Success after binutils/gcc/linux/gli [...] new 23b0ed60088 35: onsuccess: #42: 1: Success after binutils/gcc/linux/gli [...] new 3fcfcdbb7e5 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb [...] new 946fe28bd02 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb [...] new a5d3bc5a987 38: onsuccess: #45: 1: Success after binutils/gcc/linux/gli [...] new b6d8f584dd6 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gdb [...] new 718316e7efa 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gli [...] new dac14868292 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gli [...] new bb82e94b17b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gdb [...] new 4ae8477ce9c 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gdb [...] new e5ee13ce1e8 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new add17c65b64 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gli [...] new cb3deb38d78 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gli [...] new 27c5d9ac966 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gli [...] new 9ffe595e80d 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gli [...] new 53643acfb4d 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gdb [...] new 97da59688e4 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb [...] new 91e3a7aacea 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 8d2eb04f3c1 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gdb [...] new df2f1fa689b 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 94c12e3a55b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 29cac887ef5 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gdb [...] new 47a6f19d668 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gli [...] new 52c8506a67b 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb [...] new bb69372bafd 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gdb [...] new ae86c93d762 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gli [...] new 5cc3b040b43 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 commits new 0200db2209a 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gdb [...] new 916b4485d58 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gli [...] new 931fa6c5e48 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 7c230f96cb6 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gli [...] new 91f10add322 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb [...] new 7a3b5f70ca9 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 0363f498861 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gli [...] new d4cc3b98ffb 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gli [...] new 7d58ef804d8 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gdb [...] new 86466ec1093 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gli [...] new 65a3a4e60ee 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gli [...] new bfaf78ce159 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gli [...] new 9a8cdf6dd1c 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb [...] new 5609c5d0508 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gdb [...] new 1ea502cdbb0 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gdb [...] new 07be1891b49 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gdb [...] new 42d74e7c0f8 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gli [...] new fea7b0cbf45 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gli [...] new 508bc654941 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gdb [...] new 05db0bd38c6 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 commits new 1dd02fbbfe3 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gli [...] new 1fc66d1a964 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb [...] new e7a2e32f986 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb [...] new 7263dd2da8e 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gli [...] new abe60845245 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gli [...] new 65b89a098ca 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gli [...] new b75fef90834 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gli [...] new 4598c66f654 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gli [...] new 7338c9d0361 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gli [...] new a08851c1dbb 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gdb [...] new d7e34e227ce 91: onsuccess: #100: 1: Success after binutils/gcc/linux/gl [...] new a3bbb82f0ca 92: onsuccess: #101: 1: Success after binutils/gcc/linux/gl [...] new 2957932a16f 93: onsuccess: #103: 1: Success after binutils/gcc/linux/gl [...] new e84649db06a 94: onsuccess: #104: 1: Success after binutils/gcc/linux/gl [...] new 59df9662baf 95: onsuccess: #105: 1: Success after binutils/gcc/linux/gd [...] new ef894bf915e 96: onsuccess: #106: 1: Success after binutils/gcc/linux/gl [...] new 65bd6542433 97: onsuccess: #107: 1: Success after binutils/gcc/linux/gl [...] new 92044746889 98: onsuccess: #108: 1: Success after binutils/gcc/linux/gl [...] new 26a09dbd192 99: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new d1df5fe31da 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/g [...] new cf41b2eb722 101: onsuccess: #122: 1: Success after binutils/gcc/linux/g [...] new 5950c0eb58a 102: onsuccess: #123: 1: Success after binutils/gcc/linux/g [...] new f1bc72cd77b 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 4ff04ad3984 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gli [...] new d2b86dd6ce4 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 27285f9e6ac 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gli [...] new fc73bdd8f86 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 4665f9792fb 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new a51cf465876 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new beae34a16e8 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 912e877b786 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 3cf696a69ce 112: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 68de6afa2bf 113: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 17ef2313aca 114: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new b7b1f7e4518 115: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7d73c6853cd 116: onsuccess: #15: 1: Success after binutils/gcc/linux/gl [...] new 441d2f8b9af 117: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 3d6adacec46 118: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 8a4d3069fe2 119: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new df1060f7573 120: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b6e41f765e0 121: force: #26: : Failure after baseline build: no new commits new b08950a9893 122: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new f693aacd9bd 123: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new 15d34b834dc 124: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new f2accf4d3a2 125: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new f434429d0ee 126: onsuccess: #32: 1: Success after binutils/gcc/linux/gd [...] new 2679fe0ac50 127: onsuccess: #33: 1: Success after binutils/gcc/linux/gl [...] new a0aba751884 128: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (ca00b6ef22f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2064 -> 2140 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 49316 -> 49076 bytes 04-build_abe-gcc/console.log.xz | Bin 238844 -> 236716 bytes 06-build_abe-linux/console.log.xz | Bin 8408 -> 8464 bytes 07-build_abe-glibc/console.log.xz | Bin 232792 -> 232340 bytes 08-build_abe-gdb/console.log.xz | Bin 46776 -> 47396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3784 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2712 -> 2732 bytes 11-check_regression/console.log.xz | Bin 5072 -> 4816 bytes 11-check_regression/results.compare2 | 4 ++-- 12-update_baseline/console.log | 38 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14468 -> 14468 bytes sumfiles/gdb.sum | 4 ++-- 23 files changed, 48 insertions(+), 48 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[linux] branch master updated (fff5a5e7f528 -> 9fd6ba5420ba)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository linux. from fff5a5e7f528 Merge tag 'for-linus' of git://git.armlinux.org.uk/~rmk/linux-arm new d7e673c2a900 zonefs: Prevent uninitialized symbol 'size' warning new 88b170088ad2 zonefs: Fix error message in zonefs_file_dio_append() new 9fd6ba5420ba Merge tag 'zonefs-6.3-rc4' of git://git.kernel.org/pub/scm [...] The 3 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: fs/zonefs/file.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-arm-master-O2 created (now 9b8495ceb38)

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-O2 in repository toolchain/ci/base-artifacts. at 9b8495ceb38 0: init: #1: 1: [TCWG CI] No change after baseline build: n [...] This branch includes the following new commits: new 9b8495ceb38 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_gnu_native_check_gdb/master-aarch64 updated (c10caf608e2 -> a2f3bd40905)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards c10caf608e2 212: force: #45: 1: Success after gdb: 22 commits discards 671c22d495a 211: onsuccess: #44: 1: Success after linux: 26 commits discards 0a621975aa2 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] discards b0aec775768 209: force: #37: 1: Success after baseline build: no new commits discards 20ab9d2d4b1 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards fe522b9234c 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] discards f200421b5ac 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] discards b7c2e59088e 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards e8814458e63 204: force: #26: : Failure after baseline build: no new commits discards 0c09cd15c4c 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 316b13ffd3d 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards c3c48e632da 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards f6578f9cc5f 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 65751224c7f 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 5c2efb669a7 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 4ddb9c0b43b 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 6db724946a2 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ece08b14a78 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 0afa6fca403 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 4455064d982 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards fa3bbabbd35 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards b9f98184707 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ca897c1b2e1 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 2695c6342ad 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards e49aede0325 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 2c277c6b22a 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards b877cd7c2c0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3f782da9147 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards b5a8a6abf59 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] discards 0da40a0e5b5 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] discards ff7bc7d10fe 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] discards f8b3afadda7 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] discards 266e11cf0a7 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] discards 6efaae63a47 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] discards eafdf68a088 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] discards d0651bdc94c 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] discards d6d3d2634f1 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] discards 6cb63bc26c1 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] discards b1d8a059f2e 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] discards 5fff4440790 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] discards 7ab4910364e 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] discards e6945c3e689 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] discards d0adc7c0790 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] discards 57640561d70 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] discards 64c7089c474 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] discards 0149c00c896 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] discards 786d81f1104 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] discards 4f7276baada 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] discards d20ad959ab7 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] discards b2193ebd525 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] discards dc9d5bc6802 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] discards 2e8d1b67bc5 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] discards 31fe5be9052 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] discards 9bea2f16f42 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] discards 2a1af15e1b0 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards 3df6107cc0f 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] discards eb4f1037866 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] discards b45f30fc047 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards 5b5d13017c6 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 13015aca80b 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 57a4381ec6a 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 3b115b5ba23 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 258edd0aea9 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 7455638d24a 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] discards a87b824deb3 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 02624858365 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] discards 0634515cc7f 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 4a08e6f93e9 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] discards e89eb5c62da 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] discards 353a3ccc04e 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards de35b02816f 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards f487e972962 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards c0cca02826d 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 8f0e40f40be 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 7840d3a6984 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] discards 5d73d7726dc 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] discards a1940ca2942 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] discards 4fb767282f0 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 244181822a5 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] discards be3ed7b72a0 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 2715e75e3a4 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards ed3ad75d69b 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 959abb10622 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 4305998d118 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 7fc7ffc19e2 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] discards 66226c13177 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 80b2bc923e6 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 7f90ffde1cb 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards a0c2fddf821 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards e4d426645e0 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 807ed940c3b 122: onsuccess: #909: 1: Success after linux: 2753 commits discards 5d72b98caaa 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 0449b8de305 120: onsuccess: #906: 1: Success after binutils: 29 commits discards f802a507552 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 13ed935b62b 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] discards c9c555f7c4c 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] discards 80ba7ee9b8f 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] discards 60dbf14e8c3 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] discards b39a1bb9dbb 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] discards 75cbc3cb307 113: onsuccess: #898: 1: Success after linux: 3 commits discards 500b5e282c2 112: onsuccess: #896: 1: Success after binutils: 24 commits new f8a531d238f 112: onsuccess: #896: 1: Success after binutils: 24 commits new 748c3e40c82 113: onsuccess: #898: 1: Success after linux: 3 commits new b4dc6b81f2e 114: onsuccess: #899: 1: Success after binutils/gcc/linux/g [...] new 809564829b1 115: onsuccess: #900: 1: Success after binutils/gcc/linux/g [...] new 43df5d1cdc7 116: onsuccess: #901: 1: Success after binutils/gcc/linux/g [...] new d34ae3a039d 117: onsuccess: #902: 1: Success after binutils/gcc/linux/g [...] new 6eae1cedcb2 118: onsuccess: #903: 1: Success after binutils/gcc/linux/g [...] new 585c6002f06 119: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 7762b129ae7 120: onsuccess: #906: 1: Success after binutils: 29 commits new a7eefa4fd45 121: onsuccess: #908: 1: Success after glibc: 2 commits new 19bbcb285ca 122: onsuccess: #909: 1: Success after linux: 2753 commits new 256fafec951 123: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 571862398bf 124: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new 47c52bc6b91 125: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new 7f03f374dc9 126: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 580fda299e7 127: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new bdfdad5db34 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/g [...] new 94d7d2dc0ac 129: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new c883400d928 130: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 6f9d1482d55 131: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new e6475d546a8 132: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 46d9298ef3e 133: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new f673c4d0653 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 [...] new 60e7291aa64 135: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new 4507c013a1a 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 [...] new 0e5d737c878 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 [...] new 522c9b5c6c0 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 [...] new e3fb1ac0bee 139: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 38bf28fd398 140: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new d758021033e 141: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 2b06475c36a 142: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new b822ea73963 143: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 826e6e2c7a1 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/g [...] new f57c6578fab 145: onsuccess: #934: 1: Success after binutils/gcc/linux/g [...] new 634d717b446 146: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 39d3862daea 147: onsuccess: #940: 1: Success after binutils/gcc/linux/g [...] new 91a01282c78 148: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new bb1123679f5 149: onsuccess: #942: 1: Success after binutils/gcc/linux/g [...] new 8abd35a9d7d 150: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 11b15f7b847 151: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new ff429a861d0 152: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 23d8944bdef 153: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new 3fc474b2656 154: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new dbd05306ff5 155: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 31b91904e13 156: onsuccess: #949: 1: Success after binutils/gcc/linux/g [...] new 5037db2e97c 157: onsuccess: #950: 1: Success after binutils/gcc/linux/g [...] new 155c8647dae 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new f653051962f 159: onsuccess: #952: 1: Success after binutils/gcc/linux/g [...] new 1e64e7380c6 160: onsuccess: #953: 1: Success after binutils/gcc/linux/g [...] new 1fa7afb8994 161: onsuccess: #954: 1: Success after binutils/gcc/linux/g [...] new a1e18d53bfe 162: onsuccess: #955: 1: Success after binutils/gcc/linux/g [...] new d2ed598f347 163: onsuccess: #956: 1: Success after binutils/gcc/linux/g [...] new 09fb6a4cef8 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/g [...] new ba00f41df80 165: onsuccess: #958: 1: Success after binutils/gcc/linux/g [...] new a5a051e76a3 166: onsuccess: #959: 1: Success after binutils/gcc/linux/g [...] new 12ed260f714 167: onsuccess: #960: 1: Success after binutils/gcc/linux/g [...] new ba0af039e1b 168: onsuccess: #961: 1: Success after binutils/gcc/linux/g [...] new 1d1b5162480 169: onsuccess: #962: 1: Success after binutils/gcc/linux/g [...] new 2bb92bb00e6 170: onsuccess: #963: 1: Success after binutils/gcc/linux/g [...] new 2ef3b29caac 171: onsuccess: #964: 1: Success after binutils/gcc/linux/g [...] new cb4e3c5a7b8 172: onsuccess: #965: 1: Success after binutils/gcc/glibc/g [...] new 22d49a7da5f 173: onsuccess: #966: 1: Success after binutils/gcc/linux/g [...] new 00baf16a4dc 174: onsuccess: #967: 1: Success after binutils/gcc/linux/g [...] new 0ed3d68d64b 175: onsuccess: #968: 1: Success after binutils/gcc/linux/g [...] new 7ec203e7dc4 176: onsuccess: #969: 1: Success after binutils/gcc/linux/g [...] new 76a9409d7c4 177: onsuccess: #970: 1: Success after binutils/gcc/linux/g [...] new b3e82d8c852 178: onsuccess: #971: 1: Success after binutils/gcc/linux/g [...] new 3f37dc8c2ec 179: onsuccess: #972: 1: Success after binutils/gcc/linux/g [...] new d9c50fd1c8f 180: onsuccess: #973: 1: Success after binutils/gcc/linux/g [...] new cddf244cf16 181: onsuccess: #974: 1: Success after binutils/gcc/linux/g [...] new fc9759600a3 182: onsuccess: #975: 1: Success after binutils/gcc/linux/g [...] new 6c66a848189 183: onsuccess: #976: 1: Success after binutils/gcc/linux/g [...] new 1fd18f13fd9 184: onsuccess: #977: 1: Success after binutils/gcc/linux/g [...] new 93d6e8bcfc3 185: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 8c8c7ab89e0 186: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 34985f333f4 187: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 26b57efd98e 188: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 1a9e72d08cd 189: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 62a432d88f8 190: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 7a467e2bc5b 191: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 1de2d1ffb42 192: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 40fab490442 193: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new ef9698e21ec 194: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 45c578b320c 195: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2b36dd67c1f 196: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 1362e518391 197: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 4410098315a 198: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new f03f1b33f3b 199: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 9ac1adbc5e7 200: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 716eca7f7aa 201: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 3acff44fd78 202: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 7475a2e9c58 203: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 7bd7d1b51b6 204: force: #26: : Failure after baseline build: no new commits new ee8112c6c38 205: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a3a817bc542 206: onsuccess: #28: 1: Success after binutils/gcc/linux/gd [...] new 2f4a5b6b447 207: onsuccess: #29: 1: Success after binutils/gcc/linux/gd [...] new d17f0713e2f 208: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 1cb48d12dcc 209: force: #37: 1: Success after baseline build: no new commits new 96a39158866 210: onsuccess: #43: 1: Success after glibc-2.37.9000-181-g [...] new 2759eaded92 211: onsuccess: #44: 1: Success after linux: 26 commits new a3e8a6f471e 212: force: #45: 1: Success after gdb: 22 commits new a2f3bd40905 213: force: #46: 1: Success after gdb-13-branchpoint-1550-g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (c10caf608e2) \ 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 1964 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2596 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 35288 -> 35248 bytes 04-build_abe-gcc/console.log.xz | Bin 203372 -> 203300 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8456 -> 8460 bytes 07-build_abe-glibc/console.log.xz | Bin 242376 -> 242420 bytes 08-build_abe-gdb/console.log.xz | Bin 34892 -> 34728 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3780 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2716 -> 2720 bytes 11-check_regression/console.log.xz | Bin 3408 -> 3048 bytes 11-check_regression/results.compare | 18 ++---------- 12-update_baseline/console.log | 50 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +++++----- sumfiles/gdb.log.0.xz | Bin 1949676 -> 1952768 bytes sumfiles/gdb.log.1.xz | Bin 25288 -> 25384 bytes sumfiles/gdb.log.2.xz | Bin 5200 -> 5204 bytes sumfiles/gdb.log.3.xz | Bin 5420 -> 5428 bytes sumfiles/gdb.sum | 2 +- sumfiles/gdb.sum.0 | 2 +- sumfiles/gdb.sum.1 | 4 +-- sumfiles/gdb.sum.2 | 4 +-- sumfiles/gdb.sum.3 | 4 +-- 28 files changed, 47 insertions(+), 61 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 8 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (5f0bd77631b -> 7629289d50a)

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_lto in repository toolchain/ci/base-artifacts. discards 5f0bd77631b 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits discards 1d9d998894d 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits discards 9c8f8c579c0 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 0bdfe765b90 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards 0f44d9a567e 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards 3602ab2d1bf 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards 95cf758c189 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards d60bf544e70 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards 91eb61067a0 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards 08093995f77 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards 552d49f2beb 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards 95b98db5719 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards 71f9b920723 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards 95ce1290cb2 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards 3e36790922f 178: onsuccess: #16: 0: Success after binutils: 15 commits discards ad95f4ffae2 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] discards 51b1fce64a0 176: force: #14: 2: Success after binutils: 18 commits discards 79951ff395c 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards bf85b1c6329 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards 9c116776d31 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards 4f8ec1e51b1 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards af6db930ed3 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards 173f61c2d9e 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards c4920235036 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 4e60667e430 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 19145c4b7f1 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 115d516404a 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards cee682cd7fc 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards 914c3132990 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards 9c0cb8a6560 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards b25a974bc22 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards 8aef9486f80 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards fa26e558463 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards e2969e728e1 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards fbaf051420e 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards 6f0b7d32d71 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards c389a70e6b8 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards 71208aa49c3 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards 8b55f1316b5 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards b4368f2f906 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 386e04e1077 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards faef2271db0 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards 879f62ca3db 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards de562570f4d 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards 02ece15be24 148: onsuccess: #571: 2: Success after gcc: 4 commits discards 29da73c0263 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards fa9dafa104f 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards 84a221d0444 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards a8b8b2297b8 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards 05b311cb3fa 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards bc9f7cf05d6 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards eacdc086658 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards 6b9e14e5c90 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards 63f95123cf4 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards 6d0751a22ba 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards 2c74c6e9f69 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 7b14690d7fb 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards 8f6103df46d 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards ccb951d4e36 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards be8f3f3ea4b 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards 56e50d00890 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards 2a4eafe1a19 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards 7abef620540 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards 45aa82e6b98 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards 23c1f3a5ee8 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards 9b362992fbf 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards 63d51c7f887 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards 1c754d9a956 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 61f61e60179 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards b33d2a8cf58 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards 703dfd329b0 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards bd828c5040b 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards 2d12b1e1995 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards e5d4b00bf36 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards 81a53ce549b 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards 96341cd1f8c 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards 198a109f2f9 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits discards 6bd4f1d23a3 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 9a82befbc02 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits discards c6914ac2d29 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits discards c530e6198ab 112: onsuccess: #527: 1: Success after binutils: 10 commits discards 3bb095029a3 111: force: #526: 1: Failure after binutils: 5 commits discards a424074a5f4 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits discards 100c63aac93 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits discards a1b6e4806e2 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits discards ed891fdf1c8 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits discards 507c6372ef6 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits discards 50a4999e078 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits discards 18da79729be 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 5760dddb1ca 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits discards c1245c03c06 102: onsuccess: #511: 2: Success after binutils/gcc: 25 commits discards 0e4b29cad48 101: onsuccess: #510: 2: Success after binutils/gcc: 117 commits discards d7097fe76ea 100: onsuccess: #509: 1: Success after binutils/gcc: 7 commits discards 76df14d6d69 99: onsuccess: #508: 1: Success after binutils/gcc: 7 commits discards 7130c53b6c2 98: onsuccess: #507: 1: Success after binutils/gcc: 94 commits discards 1eff679ccd9 97: onsuccess: #506: 1: Success after gcc: 27 commits discards d24fd03caf7 96: force: #505: 1: Success after basepoints/gcc-13-4227-g0 [...] discards 67719907056 95: force: #504: 1: Failure after gcc: 4 commits discards 324b5083625 94: onsuccess: #501: 2: Success after binutils: 15 commits discards c8b8f29a451 93: onsuccess: #499: 2: Success after binutils/gcc: 54 commits discards f59bc866eac 92: onsuccess: #498: 2: Success after binutils/gcc: 368 commits new 07d681d9fb0 92: onsuccess: #498: 2: Success after binutils/gcc: 368 commits new 86debdf381b 93: onsuccess: #499: 2: Success after binutils/gcc: 54 commits new 3cfa979c1b1 94: onsuccess: #501: 2: Success after binutils: 15 commits new aff29c54735 95: force: #504: 1: Failure after gcc: 4 commits new f2bbf3fade7 96: force: #505: 1: Success after basepoints/gcc-13-4227-g0 [...] new 3ee281bb2a6 97: onsuccess: #506: 1: Success after gcc: 27 commits new 5134f173b78 98: onsuccess: #507: 1: Success after binutils/gcc: 94 commits new 656eed82e8f 99: onsuccess: #508: 1: Success after binutils/gcc: 7 commits new 2a73e99a731 100: onsuccess: #509: 1: Success after binutils/gcc: 7 commits new f0b0366c524 101: onsuccess: #510: 2: Success after binutils/gcc: 117 commits new 68784c7966c 102: onsuccess: #511: 2: Success after binutils/gcc: 25 commits new 37c6e8815fb 103: onsuccess: #512: 2: Success after binutils/gcc: 126 commits new b65a73fe206 104: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new dcc3df24a85 105: onsuccess: #515: 2: Success after binutils/gcc: 94 commits new a4928e7c1b1 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits new 6df571a44c0 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits new 646dbdfa420 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits new 3ae5ea6f608 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits new 35f290a16af 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits new bfaba0ee5c3 111: force: #526: 1: Failure after binutils: 5 commits new 3a056536e1a 112: onsuccess: #527: 1: Success after binutils: 10 commits new 29acc94f6aa 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits new 44a1eb4adba 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits new e7304bec230 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new 3b02be023a7 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new 7b0e5108bd0 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new 1564b382907 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new ccafba5dfa2 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new b15cd2bc4ef 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new cb1096353d4 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new 32da38fec76 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new a1a6d64db76 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new 88fb06cc3cd 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new cffe0e9dcf0 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new 0e4c7d9bf19 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new c067db05e2f 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new 0c4204c570c 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new 4bfee9f4006 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new 63991f60ba9 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new 7ad75f1b5c2 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 3a1d8b842e4 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new c8b8d1bbaab 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 7073e6c49a8 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new 1971f60abae 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new d0761300cde 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new 9b504728664 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new 15bab5a0410 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new b0b602e48b4 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new f464cc7c68f 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new faefb475e83 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new 49df05fe740 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new 9fc383965cb 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new 4acd83283d5 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new 4e76aa92241 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new fa9816a5491 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new 1d8eccfa869 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new 8174bbe6731 148: onsuccess: #571: 2: Success after gcc: 4 commits new a05d4f7de20 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new e9f52f82b1b 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new e924121271f 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new a4e05e00c44 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new 7dc9826f68d 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new 1c6eee7ac20 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new 9049d3404ff 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new 42458536bc1 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new 9b3c4ea2ce3 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new 90cb0cd3952 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new f1df331467c 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new b8c253f9c25 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new ad71183895b 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new 74cd293e178 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new 6238cbca0c9 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new 54c58195794 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new cfab0f4fa22 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new 36a365ffee3 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new 10acf20f408 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new 299c8dfd06d 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new e64612f97a6 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new ed5b331271b 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new aa568855726 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new 6c761812eba 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 839509cb7dd 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new 144d953be4b 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new c875c1be960 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new b9dbf520395 176: force: #14: 2: Success after binutils: 18 commits new 4b5ed7645f9 177: force: #15: 0: Failure after gdb-13-branchpoint-1318-g [...] new 488c3f339d9 178: onsuccess: #16: 0: Success after binutils: 15 commits new 314bf7e0cc5 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new 7449244ddfc 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new 071a4e54223 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 06d0bbd5397 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new 397ff70aea9 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new f6789868c7d 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new 449b0fcd3c8 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new 0fb2eb4c5ea 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new 5c71e2e34e5 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new 2139632c9e7 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new 8d03b4632ef 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new 8c0c2a9832b 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new 9c251dca40a 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits new 304377a5e1b 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits new 7629289d50a 193: onsuccess: #32: 2: Success after binutils/gcc: 42 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 (5f0bd77631b) \ 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 1748 -> 1912 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2568 bytes 04-build_abe-binutils/console.log.xz | Bin 49040 -> 48840 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 611580 -> 607676 bytes 06-check_regression/console.log.xz | Bin 3116 -> 3052 bytes 07-update_baseline/console.log | 36 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++------ 13 files changed, 34 insertions(+), 34 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