April 2023 - Tcwg-commits - lists.linaro.org

[gcc] branch master updated (3bfd0420e4a -> 1bd13193fab)

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 3bfd0420e4a libstdc++: Fix some freestanding test failures new 1bd13193fab PR modula2/109423 cc1gm2 ICE if an INCL or EXCL is performe [...] 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/m2/gm2-compiler/M2Base.def | 1 - gcc/m2/gm2-compiler/M2Error.def | 2 +- gcc/m2/gm2-compiler/M2Quads.mod | 9 +++++---- gcc/m2/gm2-libs-ch/SysExceptions.c | 2 +- gcc/m2/gm2-libs-ch/wrapc.c | 2 +- gcc/m2/gm2-libs/DynamicStrings.mod | 3 --- gcc/m2/gm2-libs/FIO.mod | 2 -- gcc/m2/gm2-libs/FormatStrings.mod | 4 +--- gcc/m2/gm2-libs/Indexing.mod | 6 +++--- gcc/m2/gm2-libs/M2Dependent.mod | 6 +----- gcc/m2/gm2-libs/RTExceptions.mod | 2 +- gcc/m2/gm2-libs/RTint.mod | 4 ---- gcc/m2/gm2-libs/SFIO.mod | 1 - gcc/m2/gm2-libs/StringConvert.mod | 2 -- gcc/testsuite/gm2/pim/fail/setunknown.mod | 8 ++++++++ gcc/testsuite/gm2/pim/fail/setunknown2.mod | 5 +++++ 16 files changed, 27 insertions(+), 32 deletions(-) create mode 100644 gcc/testsuite/gm2/pim/fail/setunknown.mod create mode 100644 gcc/testsuite/gm2/pim/fail/setunknown2.mod -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O2 updated (9d8a57a431 -> de3b35ec95)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/llvm-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from 9d8a57a431 10: onsuccess: #15: 1: [TCWG CI] Success after llvm: 914 commits new de3b35ec95 11: onsuccess: #16: 1: [TCWG CI] Success after llvm: 375 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1960 -> 1884 bytes 02-build_bmk_llvm/console.log.xz | Bin 99820 -> 102364 bytes 03-benchmark/benchmark-build.log | 142 +- 03-benchmark/benchmark.log | 140 +- 03-benchmark/console.log.xz | Bin 3888 -> 3892 bytes 04-check_regression/525.x264_r.symbols-improvement | 1 - .../compare-results-vs-first-internal.csv | 134 +- .../compare-results-vs-prev-internal.csv | 182 +- 04-check_regression/console.log.xz | Bin 13036 -> 12996 bytes .../csv-results-vs-first-1/md5sum.csv | 2217 +- .../csv-results-vs-first-1/perf.csv | 2556 +- .../csv-results-vs-first-1/results.csv | 5192 +- .../csv-results-vs-first-1/size.csv | 128385 +++++----- 04-check_regression/csv-results-vs-first-1/sve.csv | 20 +- .../csv-results-vs-prev-0/md5sum.csv | 2414 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 2605 +- .../csv-results-vs-prev-0/results.csv | 5828 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 229186 +++++++++--------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 26 +- .../csv-results-vs-prev-1/md5sum.csv | 2217 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 2556 +- .../csv-results-vs-prev-1/results.csv | 5192 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 128385 +++++----- 04-check_regression/csv-results-vs-prev-1/sve.csv | 20 +- 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/results-vs-first-brief.csv | 46 +- 04-check_regression/results-vs-first-full.csv | 2592 +- 04-check_regression/results-vs-first-internal.csv | 180 +- 04-check_regression/results-vs-first.csv | 180 +- 04-check_regression/results-vs-first.log | 1134 +- 04-check_regression/results-vs-prev-brief.csv | 48 +- 04-check_regression/results-vs-prev-compare.csv | 8 +- 04-check_regression/results-vs-prev-full.csv | 2686 +- 04-check_regression/results-vs-prev-internal.csv | 182 +- 04-check_regression/results-vs-prev.csv | 182 +- 04-check_regression/results-vs-prev.log | 1476 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 8 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 8 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 8 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 8 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 8 +- .../508.namd_r/results-metadata.json | 8 +- .../510.parest_r/results-metadata.json | 8 +- .../511.povray_r/results-metadata.json | 8 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 8 +- .../520.omnetpp_r/results-metadata.json | 8 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 8 +- .../523.xalancbmk_r/results-metadata.json | 8 +- .../525.x264_r/results-metadata.json | 8 +- .../526.blender_r/results-metadata.json | 8 +- .../527.cam4_r/results-metadata.json | 8 +- .../531.deepsjeng_r/results-metadata.json | 8 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 8 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 8 +- .../541.leela_r/results-metrics.json | 2 +- .../squad-vs-first/544.nab_r/results-metadata.json | 8 +- .../548.exchange2_r/results-metadata.json | 8 +- .../549.fotonik3d_r/results-metadata.json | 8 +- .../554.roms_r/results-metadata.json | 8 +- .../squad-vs-first/557.xz_r/results-metadata.json | 8 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/llvm_rev | 2 +- mail/changes-list-long.txt | 12 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 14 +- manifest.sh | 14 +- results_id | 2 +- 75 files changed, 263225 insertions(+), 263241 deletions(-) delete mode 100644 04-check_regression/525.x264_r.symbols-improvement -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-defconfig updated (35526b42ff -> 07791c6e4b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from 35526b42ff 57: onsuccess: #9: boot: [TCWG CI] Success after binutils/ll [...] new 07791c6e4b 58: onsuccess: #10: boot: [TCWG CI] Success after binutils/l [...] 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 2004 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2516 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27232 -> 27180 bytes 04-build_kernel_llvm/console.log.xz | Bin 63484 -> 65880 bytes 05-build_abe-qemu/console.log.xz | Bin 30676 -> 30888 bytes 06-build_linux/console.log.xz | Bin 2960 -> 2976 bytes 07-boot_linux/console.log.xz | Bin 5644 -> 5656 bytes 08-check_regression/console.log.xz | Bin 4260 -> 3836 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 16 files changed, 54 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (0474816d86 -> e3f8c9676c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 0474816d86 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits discards 88aa6c27d3 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards b404159108 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards 6ec307fdec 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards dee0a2546f 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 7fe63844e7 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards bd2d0879e6 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 0f392bef74 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 388ae1ceba 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards a6f05447eb 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards 2fe853faff 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 28e422f60f 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 1d98d923ba 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards d392f8ec6b 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 8e8c4c3468 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 7e217887ed 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 8170942eb6 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards e32a0d1123 228: force: #74: 1: Success after gdb: 53 commits discards 32f5d6f6cf 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 37273661d1 226: force: #70: 1: Success after baseline build: no new commits discards 44ec99a40a 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 2e54ca8860 224: force: #65: 1: Success after gdb: 50 commits discards 6b76df0daa 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 6d2a2969f4 222: force: #60: 1: Success after gdb: 16 commits discards 16895a550d 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards 680c808bd0 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 5b5e7a4e3a 219: force: #50: 1: Failure after linux: 2520 commits discards 35ffb3b842 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards ea06382dec 217: force: #45: 1: Success after linux: 1 commits discards 4468a30f7a 216: force: #43: : Failure after baseline build: no new commits discards de62228c2d 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 8e3fe46aa2 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 3abec40cff 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 214f7f0435 212: force: #27: : Failure after baseline build: no new commits discards 122de1926e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 2d20eaab18 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 7ace09eb47 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards e6b1d92b64 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 4185c74ab2 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards 24d0f739c4 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 68b828ea44 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 71052f9da7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 64eafdb08e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards ff345a83a3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 7f8cd2eb2b 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9a52d19154 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 9fd709cc73 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards db5ac75a1a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards e8a60ba0b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 4b908ca037 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 9626d02fc1 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards edaee2c6bb 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards c1bd3cc429 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 79d35feccd 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards 45c8750dad 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards 9f82b6cd82 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards 318f610a74 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 27862313b3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 5782a6cf6b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards e180c47c31 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards 4f8be2537c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards fb057406f5 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 05c70d9c12 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 85aaff83c4 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 49d8fab516 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 496c4c3cc2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards 44146dfa4d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 7a22d2edd3 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards d8301da591 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 068c84c4dc 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 82e99f1529 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards bee4faac55 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 73bdfac4d5 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards ba55c6a72f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards ac7bd2cbc1 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 79789fb290 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards b28ea11811 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 2bda50012c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 7caee715a2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 1d95ac46a7 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards c9864dbd84 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards d2fdf0ea95 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 5ee9a56375 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 26af63a239 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 46af2fcbe4 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 8be3cfe064 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards 54dd152ae4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 1ffbcbabda 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 55b4c5734d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 09791e2a76 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards d58c62b5d1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 68f9990400 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards ab5eb7dea1 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 03b1118f8b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 0e5c8c3d86 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards a82cd619d9 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 31ed4bf87e 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 01b31a7cb5 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 9010505e19 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 9b4b953025 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 14fd312448 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 630fe20257 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new d8025f131e 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 384eb54b5b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new e004d1f245 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new a94a2e674c 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 64f5326300 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 37e7b66045 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 2b2481c93c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new 7adfe77c30 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new c680745fb7 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 9ba838d8af 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 3f163cacec 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new d3124f48ee 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new dc5deb9ed2 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new ca59b94dda 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 79c8143158 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 00b8510ece 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new f8b716aa4b 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new b0daf4ef33 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new cc76afff03 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new aa9e772210 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 080a93cb9c 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 950b2b50d5 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 5b7365b9b6 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new fa45654fb3 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new b503b59819 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new 825c89c4f5 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 78fd2f0902 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new fe36c9789e 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new 54852d018b 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new f6212c88ee 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 0511c9f8dc 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new e3589a99da 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 12d8c2c391 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 3a6c677ff1 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 1a2cb63ee7 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new cfb37900f1 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new d17d2628c4 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 225570d950 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new f49c6a76c1 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new f4d141ab4c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new d1844c512d 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new af45814383 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 1f16f221ac 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 73dccb559a 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 1cd64a3338 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 00cecfd7fa 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new d9e29d1c01 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new eae9aafd36 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 2d7ae3c97d 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 7541364b44 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 8b86607cc3 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 4fb84879ae 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 0626805fdf 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new dc141f721d 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new d6ccff1444 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new b48403cbff 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new bc367ce964 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 3cd2350465 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 3e7a79b00c 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 7f3ad6a671 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 7019b825c8 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 626808db16 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new b39141b8c7 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 0c03a4a97b 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f5b3bc1903 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new a538b5a530 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 5f2b2a21cb 212: force: #27: : Failure after baseline build: no new commits new c32b78bc0f 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 3dcf710d94 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 687417d133 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 77b5e0d92f 216: force: #43: : Failure after baseline build: no new commits new d7fe40565d 217: force: #45: 1: Success after linux: 1 commits new 47e92d1b96 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 2457df53af 219: force: #50: 1: Failure after linux: 2520 commits new d429c82828 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 6eb7c6d2a9 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new 6700265de5 222: force: #60: 1: Success after gdb: 16 commits new a747c8dbfd 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new d44905421b 224: force: #65: 1: Success after gdb: 50 commits new e731bfb41c 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 4fc97fb686 226: force: #70: 1: Success after baseline build: no new commits new 35a3273d30 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new 64eba622bd 228: force: #74: 1: Success after gdb: 53 commits new 21e259024b 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 9fa4ec57d1 230: onsuccess: #78: 1: Success after gdb: 2 commits new aefd1281ae 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new 6ed6ba6c95 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 382fc6794e 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 7ed5235ca9 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 47bc8c6ca6 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new 848c66489a 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 18771e5aee 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 23773c835d 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new 9db2c82c8b 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 03aa5c14f3 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new 37c3e3e36c 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new c35d0d1a2c 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new 8d323868f9 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 97907c47ab 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 0988c98976 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 commits new e3f8c9676c 246: onsuccess: #118: 1: [TCWG CI] Success after glibc: 7 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 (0474816d86) \ 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 2032 -> 1968 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 50492 -> 50164 bytes 04-build_abe-gcc/console.log.xz | Bin 235640 -> 235800 bytes 06-build_abe-linux/console.log.xz | Bin 8844 -> 8836 bytes 07-build_abe-glibc/console.log.xz | Bin 232788 -> 232152 bytes 08-build_abe-gdb/console.log.xz | Bin 48104 -> 47700 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 6080 -> 5516 bytes 11-check_regression/console.log.xz | Bin 4596 -> 4456 bytes 11-check_regression/results.compare2 | 151 +-- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 14 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 28 +- manifest.sh | 14 +- sumfiles/gdb.log.0.xz | Bin 2962660 -> 2951612 bytes sumfiles/gdb.log.1.xz | Bin 138536 -> 143224 bytes sumfiles/gdb.log.10.xz | Bin 10044 -> 0 bytes sumfiles/gdb.log.11.xz | Bin 10308 -> 0 bytes sumfiles/gdb.log.12.xz | Bin 10268 -> 0 bytes sumfiles/gdb.log.13.xz | Bin 10304 -> 0 bytes sumfiles/gdb.log.14.xz | Bin 10116 -> 0 bytes sumfiles/gdb.log.15.xz | Bin 10072 -> 0 bytes sumfiles/gdb.log.16.xz | Bin 10132 -> 0 bytes sumfiles/gdb.log.17.xz | Bin 10032 -> 0 bytes sumfiles/gdb.log.18.xz | Bin 10456 -> 0 bytes sumfiles/gdb.log.19.xz | Bin 10200 -> 0 bytes sumfiles/gdb.log.2.xz | Bin 11988 -> 8420 bytes sumfiles/gdb.log.20.xz | Bin 10328 -> 0 bytes sumfiles/gdb.log.21.xz | Bin 10176 -> 0 bytes sumfiles/gdb.log.22.xz | Bin 10428 -> 0 bytes sumfiles/gdb.log.23.xz | Bin 9836 -> 0 bytes sumfiles/gdb.log.24.xz | Bin 10096 -> 0 bytes sumfiles/gdb.log.3.xz | Bin 10056 -> 6544 bytes sumfiles/gdb.log.4.xz | Bin 10140 -> 0 bytes sumfiles/gdb.log.5.xz | Bin 10128 -> 0 bytes sumfiles/gdb.log.6.xz | Bin 10124 -> 0 bytes sumfiles/gdb.log.7.xz | Bin 10012 -> 0 bytes sumfiles/gdb.log.8.xz | Bin 9812 -> 0 bytes sumfiles/gdb.log.9.xz | Bin 10016 -> 0 bytes sumfiles/gdb.sum | 112 +- sumfiles/gdb.sum.0 | 131 +- sumfiles/gdb.sum.1 | 201 ++- sumfiles/gdb.sum.10 | 2152 ------------------------------ sumfiles/gdb.sum.11 | 2188 ------------------------------ sumfiles/gdb.sum.12 | 2221 ------------------------------- sumfiles/gdb.sum.13 | 2164 ------------------------------ sumfiles/gdb.sum.14 | 2167 ------------------------------ sumfiles/gdb.sum.15 | 2182 ------------------------------ sumfiles/gdb.sum.16 | 2161 ------------------------------ sumfiles/gdb.sum.17 | 2160 ------------------------------ sumfiles/gdb.sum.18 | 2218 ------------------------------- sumfiles/gdb.sum.19 | 2157 ------------------------------ sumfiles/gdb.sum.2 | 2327 +++----------------------------- sumfiles/gdb.sum.20 | 2193 ------------------------------ sumfiles/gdb.sum.21 | 2191 ------------------------------ sumfiles/gdb.sum.22 | 2219 ------------------------------- sumfiles/gdb.sum.23 | 2171 ------------------------------ sumfiles/gdb.sum.24 | 2180 ------------------------------ sumfiles/gdb.sum.3 | 2340 +++------------------------------ sumfiles/gdb.sum.4 | 2167 ------------------------------ sumfiles/gdb.sum.5 | 2186 ------------------------------ sumfiles/gdb.sum.6 | 2174 ------------------------------ sumfiles/gdb.sum.7 | 2157 ------------------------------ sumfiles/gdb.sum.8 | 2049 ----------------------------- sumfiles/gdb.sum.9 | 2144 ------------------------------ 69 files changed, 778 insertions(+), 50203 deletions(-) delete mode 100644 sumfiles/gdb.log.10.xz delete mode 100644 sumfiles/gdb.log.11.xz delete mode 100644 sumfiles/gdb.log.12.xz delete mode 100644 sumfiles/gdb.log.13.xz delete mode 100644 sumfiles/gdb.log.14.xz delete mode 100644 sumfiles/gdb.log.15.xz delete mode 100644 sumfiles/gdb.log.16.xz delete mode 100644 sumfiles/gdb.log.17.xz delete mode 100644 sumfiles/gdb.log.18.xz delete mode 100644 sumfiles/gdb.log.19.xz delete mode 100644 sumfiles/gdb.log.20.xz delete mode 100644 sumfiles/gdb.log.21.xz delete mode 100644 sumfiles/gdb.log.22.xz delete mode 100644 sumfiles/gdb.log.23.xz delete mode 100644 sumfiles/gdb.log.24.xz delete mode 100644 sumfiles/gdb.log.4.xz delete mode 100644 sumfiles/gdb.log.5.xz delete mode 100644 sumfiles/gdb.log.6.xz delete mode 100644 sumfiles/gdb.log.7.xz delete mode 100644 sumfiles/gdb.log.8.xz delete mode 100644 sumfiles/gdb.log.9.xz delete mode 100644 sumfiles/gdb.sum.10 delete mode 100644 sumfiles/gdb.sum.11 delete mode 100644 sumfiles/gdb.sum.12 delete mode 100644 sumfiles/gdb.sum.13 delete mode 100644 sumfiles/gdb.sum.14 delete mode 100644 sumfiles/gdb.sum.15 delete mode 100644 sumfiles/gdb.sum.16 delete mode 100644 sumfiles/gdb.sum.17 delete mode 100644 sumfiles/gdb.sum.18 delete mode 100644 sumfiles/gdb.sum.19 delete mode 100644 sumfiles/gdb.sum.20 delete mode 100644 sumfiles/gdb.sum.21 delete mode 100644 sumfiles/gdb.sum.22 delete mode 100644 sumfiles/gdb.sum.23 delete mode 100644 sumfiles/gdb.sum.24 delete mode 100644 sumfiles/gdb.sum.4 delete mode 100644 sumfiles/gdb.sum.5 delete mode 100644 sumfiles/gdb.sum.6 delete mode 100644 sumfiles/gdb.sum.7 delete mode 100644 sumfiles/gdb.sum.8 delete mode 100644 sumfiles/gdb.sum.9 -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig updated (ec0972879a -> 2f8cbc0ca1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from ec0972879a 60: onsuccess: #13: 21940: [TCWG CI] Success after binutils/ [...] new 2f8cbc0ca1 61: onsuccess: #14: 21953: [TCWG CI] Success after binutils/ [...] 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 2016 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27816 -> 27404 bytes 04-build_abe-stage1/console.log.xz | Bin 71752 -> 71484 bytes 05-build_abe-qemu/console.log.xz | Bin 32268 -> 31048 bytes 06-build_linux/console.log.xz | Bin 8392 -> 8088 bytes 08-check_regression/console.log.xz | Bin 4368 -> 4272 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++------------ manifest.sh | 32 +++++++++++------------ results | 2 +- 17 files changed, 63 insertions(+), 63 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig updated (a0154c79d0 -> e29fd652d9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-defconfig in repository toolchain/ci/base-artifacts. from a0154c79d0 57: onsuccess: #9: boot: [TCWG CI] Success after binutils/gc [...] new e29fd652d9 58: onsuccess: #10: boot: [TCWG CI] Success 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 2016 -> 2008 bytes 02-prepare_abe/console.log.xz | Bin 2492 -> 2540 bytes 03-build_abe-binutils/console.log.xz | Bin 27688 -> 27656 bytes 04-build_abe-stage1/console.log.xz | Bin 71532 -> 71424 bytes 05-build_abe-qemu/console.log.xz | Bin 32008 -> 31204 bytes 06-build_linux/console.log.xz | Bin 5020 -> 5068 bytes 07-boot_linux/console.log.xz | Bin 6084 -> 6112 bytes 08-check_regression/console.log.xz | Bin 4224 -> 3756 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 16 files changed, 54 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[binutils-gdb] branch master updated (3401f947d86 -> bcd5ead36a1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 3401f947d86 Improve documentation of GDB build requirements and options adds 03e323abf47 gdb: Fix reading of partial symtabs in dbxread.c adds bcd5ead36a1 gdb/testsuite: Default to assembler's preferred debug forma [...] No new revisions were added by this update. Summary of changes: gdb/dbxread.c | 6 +++--- gdb/testsuite/gdb.asm/asm-source.exp | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig updated (4d00bd8b6d -> 6d3b697ba7)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 4d00bd8b6d 54: onsuccess: #9: all: [TCWG CI] Success after binutils/llv [...] new 6d3b697ba7 55: onsuccess: #10: all: [TCWG CI] Success after binutils/ll [...] 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 2040 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2532 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27488 -> 26864 bytes 04-build_kernel_llvm/console.log.xz | Bin 63900 -> 65272 bytes 05-build_abe-qemu/console.log.xz | Bin 31752 -> 29980 bytes 06-build_linux/console.log.xz | Bin 2920 -> 2952 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4300 -> 4208 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++------------ manifest.sh | 32 +++++++++++------------ 17 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[binutils-gdb] branch users/bauermann/try-fix-dbxread created (now bcd5ead36a1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch users/bauermann/try-fix-dbxread in repository binutils-gdb. at bcd5ead36a1 gdb/testsuite: Default to assembler's preferred debug forma [...] This branch includes the following new commits: new 03e323abf47 gdb: Fix reading of partial symtabs in dbxread.c new bcd5ead36a1 gdb/testsuite: Default to assembler's preferred debug forma [...] The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm updated (905c09aea7 -> 31a051106d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-arm in repository toolchain/ci/base-artifacts. from 905c09aea7 10: onsuccess: #12: 1: [TCWG CI] Success after binutils/gcc/ [...] new 31a051106d 11: onsuccess: #13: 1: [TCWG CI] Success after binutils/gcc/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2112 -> 2064 bytes 02-prepare_abe/console.log.xz | Bin 2580 -> 2508 bytes 03-build_abe-binutils/console.log.xz | Bin 27568 -> 27192 bytes 04-build_abe-stage1/console.log.xz | Bin 88660 -> 89300 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8784 -> 9540 bytes 07-build_abe-glibc/console.log.xz | Bin 232976 -> 233032 bytes 08-build_abe-stage2/console.log.xz | Bin 224996 -> 225068 bytes 09-build_abe-gdb/console.log.xz | Bin 34784 -> 34732 bytes 10-build_abe-qemu/console.log.xz | Bin 31584 -> 30796 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3824 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2780 -> 2416 bytes 13-check_regression/console.log.xz | Bin 5188 -> 5656 bytes 13-check_regression/results.compare | 10 ++--- 13-check_regression/results.compare2 | 6 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 60 +++++++++++++++++------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 44 ++++++++++----------- manifest.sh | 48 +++++++++++------------ sumfiles/binutils.log.xz | Bin 61640 -> 61392 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 101044 -> 101076 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 114164 -> 114160 bytes sumfiles/ld.sum | 4 +- 32 files changed, 102 insertions(+), 92 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig updated (2a37625501 -> 7393f928ad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 2a37625501 58: onsuccess: #9: 21797: [TCWG CI] Success after binutils/g [...] new 7393f928ad 59: onsuccess: #10: 21797: [TCWG CI] Success after binutils/ [...] 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 2012 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 27856 -> 27196 bytes 04-build_abe-stage1/console.log.xz | Bin 71864 -> 71092 bytes 05-build_abe-qemu/console.log.xz | Bin 32396 -> 30264 bytes 06-build_linux/console.log.xz | Bin 9488 -> 9556 bytes 08-check_regression/console.log.xz | Bin 4296 -> 3832 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 44 +++++++++++++++-------------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 ++++++++++++------------- manifest.sh | 28 +++++++++++----------- 15 files changed, 54 insertions(+), 60 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (9b46f50d98 -> 0474816d86)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 9b46f50d98 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] discards cbd971978f 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] discards 21bbc7b9e2 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits discards e9d1250c8f 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] discards 07d2236430 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] discards 9b315297d5 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] discards 3f3c905202 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] discards 3e8e288bbd 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits discards 559dc32280 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] discards dc3610d9e4 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] discards 62ab113dbb 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] discards 5e74b2c481 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards e52a71d050 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] discards 0f1808846f 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits discards 2bf6df6edb 230: onsuccess: #78: 1: Success after gdb: 2 commits discards 8488dfd837 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] discards 1173b6fa62 228: force: #74: 1: Success after gdb: 53 commits discards a6001df7b7 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] discards 1487a753ae 226: force: #70: 1: Success after baseline build: no new commits discards 91c6d87731 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] discards 2200c731eb 224: force: #65: 1: Success after gdb: 50 commits discards 41baf6724f 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] discards 81ce15cf08 222: force: #60: 1: Success after gdb: 16 commits discards 4b15d49e2f 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] discards cd544bc448 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] discards 9506a69f49 219: force: #50: 1: Failure after linux: 2520 commits discards b0dbd3a7dc 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] discards 7b3d2c18bb 217: force: #45: 1: Success after linux: 1 commits discards 9517e20a8a 216: force: #43: : Failure after baseline build: no new commits discards 0b9116544c 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 83bd853c44 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] discards 1f8def1803 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards c6ffea83ac 212: force: #27: : Failure after baseline build: no new commits discards 7ba3fa0046 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 05519a7452 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards fbef1b5412 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards a8504ab2b5 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 7353f7a841 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards df18a028ae 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards d2100157d8 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards ef64397843 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 22c7ca9216 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards 9c677bb65a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 0c728491b1 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 97badd14cd 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 22bffd96f5 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 19c7f140cf 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 6513a1defd 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards f49a4576d6 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 79db58946d 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 31ae7f8aa9 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 6c36e57703 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 037426fb69 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] discards c5b119c17f 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] discards cc88d05a0d 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] discards d06da3c083 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards 9e92827bd4 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards 02df95a38d 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards 42051900ba 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards be30815b28 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards e02afea976 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 668759dece 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards 812eafc49e 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 9db9e0df66 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards 15781e7d58 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards e63a5dbd49 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards d71e475098 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 30ad9c7a7e 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards 34ce3753d5 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards 68e053224b 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 4d9ef834dc 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards 461275205d 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards cef133f600 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards e13a25a9c8 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 8bfe9e80fe 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards af560d67f2 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 5507e6ccc0 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 1dfdbef461 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards c4cf24f959 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards 162e6517cf 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 22d3cf5e19 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards f55f6378c1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 8abbc02b9b 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 5d3a5df7ec 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 62e1ba07bd 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards ba2076680d 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards a91f214cbc 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 29be62aedd 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards 7e3955431e 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 9800a30f47 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards d9698e1872 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 4249df71dd 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 7863cf6a19 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards d1b1c3b235 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 5a60f0f841 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards a268a39ad5 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards 51bc044a5f 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 42d8765c69 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 542d133665 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 42155914f3 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 274961d370 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new f13f74d402 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 14fd312448 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new 9b4b953025 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 9010505e19 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 01b31a7cb5 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 31ed4bf87e 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new a82cd619d9 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 0e5c8c3d86 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 03b1118f8b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new ab5eb7dea1 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 68f9990400 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new d58c62b5d1 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 09791e2a76 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 55b4c5734d 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 1ffbcbabda 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new 54dd152ae4 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 8be3cfe064 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new 46af2fcbe4 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 26af63a239 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 5ee9a56375 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new d2fdf0ea95 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new c9864dbd84 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 1d95ac46a7 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new 7caee715a2 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 2bda50012c 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new b28ea11811 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new 79789fb290 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new ac7bd2cbc1 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new ba55c6a72f 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 73bdfac4d5 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new bee4faac55 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 82e99f1529 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 068c84c4dc 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new d8301da591 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 7a22d2edd3 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 44146dfa4d 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new 496c4c3cc2 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 49d8fab516 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 85aaff83c4 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new 05c70d9c12 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new fb057406f5 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 4f8be2537c 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new e180c47c31 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new 5782a6cf6b 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new 27862313b3 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new 318f610a74 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 9f82b6cd82 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] new 45c8750dad 191: onsuccess: #694: 1: Success after binutils/gcc/linux/gl [...] new 79d35feccd 192: onsuccess: #695: 1: Success after binutils/gcc/linux/gl [...] new c1bd3cc429 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new edaee2c6bb 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 9626d02fc1 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 4b908ca037 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new e8a60ba0b0 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new db5ac75a1a 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 9fd709cc73 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 9a52d19154 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 7f8cd2eb2b 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new ff345a83a3 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 64eafdb08e 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new 71052f9da7 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 68b828ea44 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 24d0f739c4 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 4185c74ab2 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new e6b1d92b64 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new 7ace09eb47 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new 2d20eaab18 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 122de1926e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 214f7f0435 212: force: #27: : Failure after baseline build: no new commits new 3abec40cff 213: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 8e3fe46aa2 214: force: #39: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new de62228c2d 215: force: #41: 1: Failure after gdb-13-branchpoint-1470-g1 [...] new 4468a30f7a 216: force: #43: : Failure after baseline build: no new commits new ea06382dec 217: force: #45: 1: Success after linux: 1 commits new 35ffb3b842 218: force: #48: 1: Success after gdb-13-branchpoint-1471-g3 [...] new 5b5e7a4e3a 219: force: #50: 1: Failure after linux: 2520 commits new 680c808bd0 220: force: #51: 1: Success after v6.2-rc6-1149-g5b49da02ddb [...] new 16895a550d 221: force: #53: 1: Success after gdb-13-branchpoint-1472-g6 [...] new 6d2a2969f4 222: force: #60: 1: Success after gdb: 16 commits new 6b76df0daa 223: force: #63: 1: Failure after gdb-13-branchpoint-1489-g2 [...] new 2e54ca8860 224: force: #65: 1: Success after gdb: 50 commits new 44ec99a40a 225: force: #68: 1: Failure after gdb-13-branchpoint-1540-g4 [...] new 37273661d1 226: force: #70: 1: Success after baseline build: no new commits new 32f5d6f6cf 227: onsuccess: #72: 1: Success after binutils/gcc/linux/gli [...] new e32a0d1123 228: force: #74: 1: Success after gdb: 53 commits new 8170942eb6 229: force: #77: 1: Failure after gdb-13-branchpoint-1594-g4 [...] new 7e217887ed 230: onsuccess: #78: 1: Success after gdb: 2 commits new 8e8c4c3468 231: force: #89: 1: [TCWG CI] Failure after gdb: 31 commits new d392f8ec6b 232: force: #90: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 1d98d923ba 233: force: #92: 1: [TCWG CI] Failure after gdb-13-branchpoi [...] new 28e422f60f 234: force: #94: 1: [TCWG CI] Success after baseline build: [...] new 2fe853faff 235: onsuccess: #95: 1: [TCWG CI] Success after binutils/gcc [...] new a6f05447eb 236: onsuccess: #99: 1: [TCWG CI] Success after binutils: 22 [...] new 388ae1ceba 237: force: #103: 1: [TCWG CI] Failure after gdb: 16 commits new 0f392bef74 238: force: #104: 1: [TCWG CI] Failure after gdb-13-branchpo [...] new bd2d0879e6 239: force: #106: 1: [TCWG CI] Success after baseline build: [...] new 7fe63844e7 240: onsuccess: #107: 1: [TCWG CI] Success after binutils/gc [...] new dee0a2546f 241: onsuccess: #109: 1: [TCWG CI] Success after binutils/gc [...] new 6ec307fdec 242: onsuccess: #110: 1: [TCWG CI] Success after gdb: 2 commits new b404159108 243: onsuccess: #111: 1: [TCWG CI] Success after binutils/gc [...] new 88aa6c27d3 244: onsuccess: #112: 1: [TCWG CI] Success after binutils/gc [...] new 0474816d86 245: onsuccess: #117: 1: [TCWG CI] Success after gcc: 16 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 (9b46f50d98) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2092 -> 2032 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49864 -> 50492 bytes 04-build_abe-gcc/console.log.xz | Bin 236932 -> 235640 bytes 06-build_abe-linux/console.log.xz | Bin 8744 -> 8844 bytes 07-build_abe-glibc/console.log.xz | Bin 232408 -> 232788 bytes 08-build_abe-gdb/console.log.xz | Bin 48380 -> 48104 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3772 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 5560 -> 6080 bytes 11-check_regression/console.log.xz | Bin 6712 -> 4596 bytes 11-check_regression/results.compare2 | 221 ++-- 12-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 37 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 +- manifest.sh | 28 +- sumfiles/gdb.log.0.xz | Bin 2933292 -> 2962660 bytes sumfiles/gdb.log.1.xz | Bin 144600 -> 138536 bytes sumfiles/gdb.log.10.xz | Bin 0 -> 10044 bytes sumfiles/gdb.log.11.xz | Bin 0 -> 10308 bytes sumfiles/gdb.log.12.xz | Bin 0 -> 10268 bytes sumfiles/gdb.log.13.xz | Bin 0 -> 10304 bytes sumfiles/gdb.log.14.xz | Bin 0 -> 10116 bytes sumfiles/gdb.log.15.xz | Bin 0 -> 10072 bytes sumfiles/gdb.log.16.xz | Bin 0 -> 10132 bytes sumfiles/gdb.log.17.xz | Bin 0 -> 10032 bytes sumfiles/gdb.log.18.xz | Bin 0 -> 10456 bytes sumfiles/gdb.log.19.xz | Bin 0 -> 10200 bytes sumfiles/gdb.log.2.xz | Bin 21388 -> 11988 bytes sumfiles/gdb.log.20.xz | Bin 0 -> 10328 bytes sumfiles/gdb.log.21.xz | Bin 0 -> 10176 bytes sumfiles/gdb.log.22.xz | Bin 0 -> 10428 bytes sumfiles/gdb.log.23.xz | Bin 0 -> 9836 bytes sumfiles/gdb.log.24.xz | Bin 0 -> 10096 bytes sumfiles/gdb.log.3.xz | Bin 19812 -> 10056 bytes sumfiles/gdb.log.4.xz | Bin 6360 -> 10140 bytes sumfiles/gdb.log.5.xz | Bin 0 -> 10128 bytes sumfiles/gdb.log.6.xz | Bin 0 -> 10124 bytes sumfiles/gdb.log.7.xz | Bin 0 -> 10012 bytes sumfiles/gdb.log.8.xz | Bin 0 -> 9812 bytes sumfiles/gdb.log.9.xz | Bin 0 -> 10016 bytes sumfiles/gdb.sum | 108 +- sumfiles/gdb.sum.0 | 316 +++-- sumfiles/gdb.sum.1 | 420 +----- sumfiles/{gdb.sum.3 => gdb.sum.10} | 489 +------ sumfiles/{gdb.sum.3 => gdb.sum.11} | 499 +------ sumfiles/{gdb.sum.3 => gdb.sum.12} | 528 +------- sumfiles/{gdb.sum.3 => gdb.sum.13} | 487 +------ sumfiles/{gdb.sum.3 => gdb.sum.14} | 482 +------ sumfiles/{gdb.sum.3 => gdb.sum.15} | 501 +------ sumfiles/{gdb.sum.3 => gdb.sum.16} | 506 +------ sumfiles/{gdb.sum.3 => gdb.sum.17} | 479 +------ sumfiles/{gdb.sum.3 => gdb.sum.18} | 525 +------- sumfiles/{gdb.sum.3 => gdb.sum.19} | 484 +------ sumfiles/gdb.sum.2 | 510 +------- sumfiles/{gdb.sum.3 => gdb.sum.20} | 506 +------ sumfiles/{gdb.sum.3 => gdb.sum.21} | 504 +------ sumfiles/{gdb.sum.3 => gdb.sum.22} | 524 +------- sumfiles/{gdb.sum.3 => gdb.sum.23} | 492 +------ sumfiles/{gdb.sum.3 => gdb.sum.24} | 501 +------ sumfiles/gdb.sum.3 | 504 +------ sumfiles/gdb.sum.4 | 2328 ++++++++++++++++++++++++++++++--- sumfiles/{gdb.sum.3 => gdb.sum.5} | 491 +------ sumfiles/{gdb.sum.3 => gdb.sum.6} | 491 +------ sumfiles/{gdb.sum.3 => gdb.sum.7} | 482 +------ sumfiles/{gdb.sum.3 => gdb.sum.8} | 606 +-------- sumfiles/{gdb.sum.3 => gdb.sum.9} | 497 +------ 69 files changed, 3100 insertions(+), 11554 deletions(-) create mode 100644 sumfiles/gdb.log.10.xz create mode 100644 sumfiles/gdb.log.11.xz create mode 100644 sumfiles/gdb.log.12.xz create mode 100644 sumfiles/gdb.log.13.xz create mode 100644 sumfiles/gdb.log.14.xz create mode 100644 sumfiles/gdb.log.15.xz create mode 100644 sumfiles/gdb.log.16.xz create mode 100644 sumfiles/gdb.log.17.xz create mode 100644 sumfiles/gdb.log.18.xz create mode 100644 sumfiles/gdb.log.19.xz create mode 100644 sumfiles/gdb.log.20.xz create mode 100644 sumfiles/gdb.log.21.xz create mode 100644 sumfiles/gdb.log.22.xz create mode 100644 sumfiles/gdb.log.23.xz create mode 100644 sumfiles/gdb.log.24.xz create mode 100644 sumfiles/gdb.log.5.xz create mode 100644 sumfiles/gdb.log.6.xz create mode 100644 sumfiles/gdb.log.7.xz create mode 100644 sumfiles/gdb.log.8.xz create mode 100644 sumfiles/gdb.log.9.xz copy sumfiles/{gdb.sum.3 => gdb.sum.10} (81%) copy sumfiles/{gdb.sum.3 => gdb.sum.11} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.12} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.13} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.14} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.15} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.16} (81%) copy sumfiles/{gdb.sum.3 => gdb.sum.17} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.18} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.19} (81%) copy sumfiles/{gdb.sum.3 => gdb.sum.20} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.21} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.22} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.23} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.24} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.5} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.6} (82%) copy sumfiles/{gdb.sum.3 => gdb.sum.7} (81%) copy sumfiles/{gdb.sum.3 => gdb.sum.8} (77%) copy sumfiles/{gdb.sum.3 => gdb.sum.9} (81%) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (b6b32042c801 -> 08920e2ca63e)

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 b6b32042c801 226: onsuccess: #45: 2: [TCWG CI] Success after binutils/g [...] discards 173382b51a85 225: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] discards a8643b4af24b 224: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] discards e771d8059f0a 223: onsuccess: #42: 2: [TCWG CI] Success after binutils/g [...] discards 24f351873764 222: onsuccess: #41: 2: [TCWG CI] Success after binutils/g [...] discards e8e618c81169 221: onsuccess: #40: 2: [TCWG CI] Success after binutils/g [...] discards 30fb00039a5d 220: onsuccess: #39: 1: [TCWG CI] Success after gcc: 2 commits discards 15085ba7cd54 219: force: #38: 1: [TCWG CI] Failure after basepoints/gcc [...] discards fea15f036a71 218: force: #37: 2: [TCWG CI] Success after gcc: 40 commits discards 46f4222a4c21 217: onsuccess: #35: 2: [TCWG CI] Success after binutils: [...] discards 418b32bbc764 216: onsuccess: #32: 2: Success after binutils/gcc: 5 commits discards c77d5553e55c 215: onsuccess: #31: 2: Success after binutils/gcc: 7 commits discards 6ca682d9c1a5 214: onsuccess: #30: 2: Success after binutils/gcc: 34 commits discards b031bf0c9fe2 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits discards e68faa602d55 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits discards a761c0e27284 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits discards 64129c772436 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits discards d48cd3e4bd1d 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits discards 570f96f50a18 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits discards 412c22cf97c7 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits discards 792461fc37c8 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits discards c35d40a0cd31 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits discards 70a523281f34 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits discards 9071a16699ff 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits discards 04093caa7193 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits discards 786ee473fd80 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits discards 0fbb82d6c1e8 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits discards e2ff23a834df 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits discards 7eb90e38ad84 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits discards fcb204ef69d4 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits discards 694c40a12b8f 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits discards e16f6a5f6a71 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits discards 406c1d94489e 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards 0bde0c05b3e1 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits discards 283c0d5bf509 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits discards 32ee35387943 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits discards 0c99c31e39cc 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits discards 025aa277f247 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards a31a53fb8613 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits discards 121eb86d395b 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits discards d8f25083c187 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits discards ad458ebea7e0 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits discards 3eb558639476 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits discards 17eb3ed26682 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits discards ff7c5a589784 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits discards 0dda3b3e4fe1 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits discards c3d3cdb505f3 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits discards 192f3c6d3242 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits discards 19238d0b03b3 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits discards 85a8c6b3b076 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits discards 0662924d39e6 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits discards 93fd8f05df24 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits discards 0458b56371b0 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits discards 73bca49fa083 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits discards 27ed05a2d9af 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits discards 2699d7503a19 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits discards 40da6d304658 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits discards b01e65146ef1 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits discards 30062dd04b55 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits discards 8311d2e51881 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits discards 5f3e3a35fd80 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits discards db73197ebbc6 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits discards 58eeecdaea79 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits discards 9f2468a1a4e7 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits discards c88a0c3211af 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits discards 5ee83d3748cf 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits discards eb427bafdbd9 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits discards 95b7231ca207 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits discards 6e0105ed89ef 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits discards 09ad7447843b 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits discards 08177820f403 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits discards d9f2488935a2 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits discards 4421608eb37b 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits discards 7531af45db28 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits discards 91e655102701 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits discards c4d1e42ea96f 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits discards 8e20bc7519df 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits discards 40eb88821d80 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits discards e01d2e59a938 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits discards f644dc247cf2 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits discards 1305fde7ba44 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits discards aa0f35aed743 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits discards 2391ca8a5131 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits discards 664bd95eaefe 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits discards 3ce7c7da7919 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits discards d5f61bde75e0 141: onsuccess: #559: 1: Success after gcc: 4 commits discards af47b19ab34a 140: force: #558: 1: Failure after basepoints/gcc-13-4953- [...] discards 9fabaa097d5c 139: force: #557: 2: Success after gcc: 6 commits discards 2a53b0780717 138: onsuccess: #554: 2: Success after binutils: 10 commits discards 904ee3522a34 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits discards 7a2ac329074e 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits discards a555364ebfca 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits discards cc7495a7a0ff 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits discards a4fb7035add8 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits discards 5f4b5b7f348f 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits discards edb9cf748591 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits discards 0eb7ece128c0 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits discards 5323daaed494 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits discards 6a74b00bdeaa 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits discards 05678bfff2ab 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards 26749c2138eb 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new d17a5ab421c8 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 940724e69b6a 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new 703a1539247b 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits new 220a47dd1c6e 129: onsuccess: #544: 2: Success after binutils/gcc: 79 commits new 83e72c9bd942 130: onsuccess: #545: 2: Success after binutils/gcc: 9 commits new 0f06f0107750 131: onsuccess: #546: 2: Success after binutils/gcc: 24 commits new 4300729a657f 132: onsuccess: #547: 2: Success after binutils/gcc: 7 commits new 622152df9a45 133: onsuccess: #548: 2: Success after binutils/gcc: 29 commits new 7d4de2769011 134: onsuccess: #549: 2: Success after binutils/gcc: 9 commits new 727c9a2712ab 135: onsuccess: #550: 2: Success after binutils/gcc: 31 commits new ca96ec4849dd 136: onsuccess: #551: 2: Success after binutils/gcc: 18 commits new e9081d842a08 137: onsuccess: #552: 2: Success after binutils/gcc: 18 commits new 7e645bb45b7f 138: onsuccess: #554: 2: Success after binutils: 10 commits new f095d3a5dd2b 139: force: #557: 2: Success after gcc: 6 commits new f597b811b0cc 140: force: #558: 1: Failure after basepoints/gcc-13-4953- [...] new c3b4e502ebb7 141: onsuccess: #559: 1: Success after gcc: 4 commits new 4b4a449edac8 142: onsuccess: #561: 2: Success after binutils/gcc: 176 commits new ae079ef3155e 143: onsuccess: #562: 2: Success after binutils/gcc: 6 commits new d59f66e9892f 144: onsuccess: #563: 2: Success after binutils/gcc: 4 commits new ebd6bc581b20 145: onsuccess: #564: 2: Success after binutils/gcc: 30 commits new 4c5a466a9ada 146: onsuccess: #565: 2: Success after binutils/gcc: 115 commits new 0002f95def0e 147: onsuccess: #566: 2: Success after binutils/gcc: 50 commits new 0e89ae1d2fca 148: onsuccess: #567: 2: Success after binutils/gcc: 128 commits new c37de8038bac 149: onsuccess: #568: 2: Success after binutils/gcc: 69 commits new 13ae511e60b1 150: onsuccess: #569: 2: Success after binutils/gcc: 32 commits new e6f9390f4e64 151: onsuccess: #570: 2: Success after binutils/gcc: 36 commits new 9d3b5c516dd2 152: onsuccess: #571: 2: Success after binutils/gcc: 43 commits new 7e87937b6403 153: onsuccess: #572: 2: Success after binutils/gcc: 28 commits new 73bf6e9a1364 154: onsuccess: #573: 2: Success after binutils/gcc: 6 commits new e1f41b9c49a8 155: onsuccess: #574: 2: Success after binutils/gcc: 36 commits new c8626eeeeccc 156: onsuccess: #575: 2: Success after binutils/gcc: 27 commits new dddbdd16172c 157: onsuccess: #576: 2: Success after binutils/gcc: 80 commits new 67f700d1ff72 158: onsuccess: #577: 2: Success after binutils/gcc: 27 commits new 75f9c921ffba 159: onsuccess: #578: 2: Success after binutils/gcc: 130 commits new a1fbc6e5eccd 160: onsuccess: #579: 2: Success after binutils/gcc: 17 commits new 6e55ed36ba39 161: onsuccess: #580: 2: Success after binutils/gcc: 10 commits new f67a5e0c711a 162: onsuccess: #581: 2: Success after binutils/gcc: 6 commits new 47917c65388c 163: onsuccess: #582: 2: Success after binutils/gcc: 55 commits new 0bda497637dd 164: onsuccess: #583: 2: Success after binutils/gcc: 110 commits new 1eb92d7fbc73 165: onsuccess: #584: 2: Success after binutils/gcc: 45 commits new 6ec6c0ca6d75 166: onsuccess: #585: 2: Success after binutils/gcc: 59 commits new 968e20fad5c6 167: onsuccess: #586: 2: Success after binutils/gcc: 16 commits new 30f6b0b82251 168: onsuccess: #587: 2: Success after binutils/gcc: 2 commits new 0bb6a8ca43ad 169: onsuccess: #588: 2: Success after binutils/gcc: 7 commits new 03eea0cd026b 170: onsuccess: #589: 2: Success after binutils/gcc: 28 commits new 5efabadb273a 171: onsuccess: #590: 2: Success after binutils/gcc: 21 commits new c48b98397e9e 172: onsuccess: #592: 2: Success after binutils/gcc: 57 commits new 186e7f7c525a 173: onsuccess: #593: 2: Success after binutils/gcc: 74 commits new 7bcefa292da8 174: onsuccess: #594: 2: Success after binutils/gcc: 147 commits new 7acd5b9e9712 175: onsuccess: #595: 2: Success after binutils/gcc: 30 commits new f9f5882bf4a1 176: onsuccess: #596: 2: Success after binutils/gcc: 84 commits new 134ff49f9f58 177: onsuccess: #597: 2: Success after binutils/gcc: 86 commits new dcbdd17dc220 178: onsuccess: #598: 2: Success after binutils/gcc: 54 commits new 75bc7cb0f690 179: onsuccess: #599: 2: Success after binutils/gcc: 27 commits new 84da5d17fd8c 180: onsuccess: #600: 2: Success after binutils/gcc: 32 commits new 42120269404d 181: onsuccess: #601: 2: Success after binutils/gcc: 13 commits new b8838189490e 182: onsuccess: #602: 2: Success after binutils/gcc: 32 commits new 90b976b9e363 183: onsuccess: #603: 2: Success after binutils/gcc: 33 commits new 60f30d503d83 184: onsuccess: #604: 2: Success after binutils/gcc: 138 commits new d38bf82615e0 185: onsuccess: #605: 2: Success after binutils/gcc: 38 commits new 6b97facd8694 186: onsuccess: #1: 2: Success after binutils/gcc: 54 commits new 85e5becf18bc 187: onsuccess: #2: 2: Success after binutils/gcc: 22 commits new af3a858c886d 188: onsuccess: #3: 2: Success after binutils/gcc: 5 commits new 0a7896f8c5b7 189: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new faef40b7a773 190: onsuccess: #5: 2: Success after binutils/gcc: 23 commits new 012c36af2b02 191: onsuccess: #6: 2: Success after binutils/gcc: 65 commits new 5a7c362d2cdb 192: onsuccess: #7: 2: Success after binutils/gcc: 22 commits new ab99c1a35d62 193: onsuccess: #8: 2: Success after binutils/gcc: 37 commits new 93fc9973bce3 194: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 5c9fc47b19d6 195: onsuccess: #10: 2: Success after binutils/gcc: 28 commits new 8917b54d7eac 196: onsuccess: #11: 2: Success after binutils/gcc: 16 commits new 64e70832ea62 197: onsuccess: #12: 2: Success after binutils/gcc: 29 commits new f83bb88cae7b 198: onsuccess: #13: 2: Success after binutils/gcc: 58 commits new 6529521ed095 199: onsuccess: #14: 2: Success after binutils/gcc: 31 commits new fa2a07bc7348 200: onsuccess: #15: 2: Success after binutils/gcc: 26 commits new 1e0c29ae4717 201: onsuccess: #16: 2: Success after binutils/gcc: 55 commits new a7c07702bca3 202: onsuccess: #17: 2: Success after binutils/gcc: 25 commits new 380e1183ffbf 203: onsuccess: #18: 2: Success after binutils/gcc: 9 commits new e68caf2bc471 204: onsuccess: #19: 2: Success after binutils/gcc: 39 commits new f9119131eca5 205: onsuccess: #20: 2: Success after binutils/gcc: 59 commits new 54674d2f2f89 206: onsuccess: #21: 2: Success after binutils/gcc: 38 commits new 80958d86fdbe 207: onsuccess: #23: 2: Success after binutils/gcc: 75 commits new eb64766ade2f 208: onsuccess: #24: 2: Success after binutils/gcc: 44 commits new b926440d84a6 209: onsuccess: #25: 2: Success after binutils/gcc: 12 commits new 91d8b3ff5eda 210: onsuccess: #26: 2: Success after binutils/gcc: 27 commits new 089af93e6ef5 211: onsuccess: #27: 2: Success after binutils/gcc: 41 commits new dee9dd993463 212: onsuccess: #28: 2: Success after binutils/gcc: 34 commits new 386241052c2c 213: onsuccess: #29: 2: Success after binutils/gcc: 36 commits new 3574402b3a9a 214: onsuccess: #30: 2: Success after binutils/gcc: 34 commits new 18e4fb32e230 215: onsuccess: #31: 2: Success after binutils/gcc: 7 commits new c7d98af4789f 216: onsuccess: #32: 2: Success after binutils/gcc: 5 commits new 65ad95b534ce 217: onsuccess: #35: 2: [TCWG CI] Success after binutils: [...] new 3040d8e21f17 218: force: #37: 2: [TCWG CI] Success after gcc: 40 commits new 1f2b502f8739 219: force: #38: 1: [TCWG CI] Failure after basepoints/gcc [...] new df1b7ced4ae4 220: onsuccess: #39: 1: [TCWG CI] Success after gcc: 2 commits new 1b97135b1092 221: onsuccess: #40: 2: [TCWG CI] Success after binutils/g [...] new 3dc04b91a303 222: onsuccess: #41: 2: [TCWG CI] Success after binutils/g [...] new 6af28b7eb3c2 223: onsuccess: #42: 2: [TCWG CI] Success after binutils/g [...] new 0529f426c634 224: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] new 551a542dba94 225: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] new e7ffa48ee629 226: onsuccess: #45: 2: [TCWG CI] Success after binutils/g [...] new 08920e2ca63e 227: onsuccess: #46: 2: [TCWG CI] Success after binutils/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 (b6b32042c801) \ 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 1932 -> 1916 bytes 02-prepare_abe/console.log.xz | Bin 2500 -> 2528 bytes 04-build_abe-binutils/console.log.xz | Bin 35620 -> 35192 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 304808 -> 303832 bytes 06-check_regression/console.log.xz | Bin 2848 -> 2980 bytes 07-update_baseline/console.log | 44 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 21 +++++----- mail/last_good.sh | 20 +++++----- manifest.sh | 20 +++++----- 12 files changed, 57 insertions(+), 54 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[glibc] branch master updated (e9327e8584 -> c4468cd399)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from e9327e8584 hppa: Revise __TIMESIZE define to use __WORDSIZE new c4468cd399 hppa: Update struct __pthread_rwlock_arch_t comment. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/hppa/nptl/bits/struct_rwlock.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (0ad21a41bfe5 -> 357606d9b050)

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 0ad21a41bfe5 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 57639bb15978 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 24a81d2112a4 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 52720a7980ff 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] discards dbf1c6cd4ea6 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] discards e01279d4a8f1 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] discards 4116028211ad 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] discards 908183c8cd57 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] discards a059a222486c 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 22f85df4013c 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards afed723bfacf 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 7237d2c6e2d3 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards f03b99967a76 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards a9e88fabc268 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 54433cab4ad0 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards a5e2c08b949a 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards 7f3e37eba264 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards efbbef257f1b 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 9db94627906a 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 4636b84ca12b 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards d61a884c4d28 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards fa19e6bd78af 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards f4abf5ea00d8 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 041120cadebc 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 4e10773db892 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards c14d4558e8c3 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards eaa085b71cfa 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 1aa266002ffd 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] discards 23a717a2339c 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 96416e09fcb2 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] discards dbc0c96b71ba 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 079d467b22a2 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards 1e2e4fa926a2 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards ce9fe23eba2d 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] discards d71aa8c90023 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards f87878f0c126 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards 5c7e71193827 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] discards ef660c81c02c 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards e9262d7909c6 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] discards 435a14fdd754 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 1e66341af22c 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 97814c39c93c 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 64ec2ebe0e08 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] discards bfb611f17e19 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] discards a918937522d1 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] discards 24dd421731d5 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] discards 80afca26282e 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] discards d5a4290e82db 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] discards ac7a3c2ee5b4 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] discards 00f740981563 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] discards b4f2dde24192 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] discards 3c34d0cb54fb 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] discards bddd8e6bb1ae 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] discards 2c64ec37811d 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] discards 3d1dffe92c79 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] discards 9084d8de7d6d 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] discards beed4df70436 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] discards 5e4678482636 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] discards ea01c5f1541b 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] discards 398f4498c9e3 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] discards 1b844bbd87be 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] discards 5d2b0dd61729 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] discards 87ef4d39bead 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] discards 6879c7c3fa2f 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] discards fd40ffb57cc7 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] discards 45b437afdf31 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] discards 8a81edd017b9 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] discards 5205adae30fd 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] discards 8765e5342325 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] discards e8dcf091704b 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] discards da6ce2670959 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] discards 169c96357906 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] discards 32c7c926b1ae 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] discards 8b06f0baa589 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] discards d7580cf115fe 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] discards 1d58eeb15295 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] discards 51c931e6aac8 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] discards 7a7e0d69d441 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] discards 193a288fa53b 162: onsuccess: #624: 1: Success after linux: 10 commits discards 36c108bd360e 161: onsuccess: #623: 1: Success after glibc: 9 commits discards 9aa70d6680a5 160: onsuccess: #621: 1: Success after gcc: 11 commits discards 35d2b8ed5511 159: onsuccess: #620: 1: Success after binutils: 12 commits discards 1b03004a7843 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] discards 481734bc5aa8 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] discards 2c50eae3a0c4 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] discards 9dcd29caaf48 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] discards 9a664a6d58a7 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] discards 9ff3ec9b904d 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] discards 2d79e927620d 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] discards b1641cc09262 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] discards 3905dc2ca442 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] discards 86721285f0be 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] discards d8fc9d9cb382 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] discards e6598406ca00 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] discards a743c9f4648b 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] discards 88e72c8893b4 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] discards 364bdc2eb443 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] discards 00f22a0cab3b 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] discards 47b680b53052 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] discards 8ae1511a0bdf 141: onsuccess: #601: 1: Success after linux: 794 commits discards 67317dfc5e4e 140: onsuccess: #600: 1: Success after gcc: 23 commits new af925c9e2a19 140: onsuccess: #600: 1: Success after gcc: 23 commits new 2ba4e2cdffc0 141: onsuccess: #601: 1: Success after linux: 794 commits new ef4268183964 142: onsuccess: #602: 1: Success after binutils/gcc/linux/ [...] new 754c6ff635dc 143: onsuccess: #603: 1: Success after binutils/gcc/linux/ [...] new 3195314f9788 144: onsuccess: #604: 1: Success after binutils/gcc/gdb: 1 [...] new 7ec6743e6181 145: onsuccess: #605: 1: Success after binutils/gcc/linux/ [...] new 803ca4d9ba4e 146: onsuccess: #606: 1: Success after binutils/gcc/linux/ [...] new 416f0b94d73d 147: onsuccess: #607: 1: Success after binutils/gcc/linux/ [...] new 6ffc8557bc33 148: onsuccess: #608: 1: Success after binutils/gcc/linux/ [...] new e236d93c47c4 149: onsuccess: #609: 1: Success after binutils/gcc/linux/ [...] new 6c575de55374 150: onsuccess: #610: 1: Success after binutils/gcc/linux/ [...] new 41a047e36dba 151: onsuccess: #611: 1: Success after binutils/gcc/linux/ [...] new 68c7b29191d0 152: onsuccess: #612: 1: Success after binutils/gcc/gdb: 1 [...] new f31936c40566 153: onsuccess: #613: 1: Success after binutils/gcc/gdb: 4 [...] new e1e4e0397f19 154: onsuccess: #614: 1: Success after binutils/gcc/gdb: 1 [...] new 4e3cf481bdf9 155: onsuccess: #615: 1: Success after binutils/gcc/linux/ [...] new 8d715b101b73 156: onsuccess: #616: 1: Success after binutils/gcc/linux/ [...] new ed6fd381c28c 157: onsuccess: #617: 1: Success after binutils/gcc/linux/ [...] new 2a43467851ce 158: onsuccess: #618: 1: Success after binutils/gcc/linux/ [...] new 5423993a33d8 159: onsuccess: #620: 1: Success after binutils: 12 commits new 857e1cd8358d 160: onsuccess: #621: 1: Success after gcc: 11 commits new a98aca0949c7 161: onsuccess: #623: 1: Success after glibc: 9 commits new 66a98cbf8872 162: onsuccess: #624: 1: Success after linux: 10 commits new 3cdc5624fd82 163: onsuccess: #625: 1: Success after binutils/gcc/glibc/ [...] new e63eb108df6b 164: onsuccess: #626: 1: Success after binutils/gcc/linux/ [...] new c809889cc75e 165: onsuccess: #627: 1: Success after binutils/gcc/linux/ [...] new dc5a6c8e85a9 166: onsuccess: #628: 1: Success after binutils/gcc/linux/ [...] new 2ec3694a0e8b 167: onsuccess: #629: 1: Success after binutils/gcc/linux/ [...] new 074f6163fd5c 168: onsuccess: #630: 1: Success after binutils/gcc/linux/ [...] new fc98c6f3c533 169: onsuccess: #631: 1: Success after binutils/gcc/linux/ [...] new dc89901c88b1 170: onsuccess: #632: 1: Success after binutils/gcc/linux/ [...] new 2fee7bd6d0b4 171: onsuccess: #633: 1: Success after binutils/gcc/linux/ [...] new abd4314e5301 172: onsuccess: #634: 1: Success after binutils/gcc/linux/ [...] new bd03fc2548b6 173: onsuccess: #635: 1: Success after binutils/gcc/linux/ [...] new e9c5a333a58e 174: onsuccess: #636: 1: Success after binutils/gcc/linux/ [...] new 6885002fb65b 175: onsuccess: #637: 1: Success after binutils/gcc/linux/ [...] new 012d06c7849e 176: onsuccess: #638: 1: Success after binutils/gcc/linux/ [...] new 46d6f34fd858 177: onsuccess: #639: 1: Success after binutils/gcc/linux/ [...] new 7ade1fd10708 178: onsuccess: #640: 1: Success after binutils/gcc/linux/ [...] new f9a0683a445e 179: onsuccess: #641: 1: Success after binutils/gcc/linux/ [...] new ce1458bf3e78 180: onsuccess: #642: 1: Success after binutils/gcc/linux/ [...] new 493f20afda1b 181: onsuccess: #643: 1: Success after binutils/gcc/linux/ [...] new 3406b35f6953 182: onsuccess: #644: 1: Success after binutils/gcc/gdb: 3 [...] new 572b76c0f65c 183: onsuccess: #645: 1: Success after binutils/gcc/gdb: 2 [...] new bfef70563d60 184: onsuccess: #646: 1: Success after binutils/gcc/linux/ [...] new 5ed66ff8bf85 185: onsuccess: #647: 1: Success after binutils/gcc/linux/ [...] new ec03c5efcb79 186: onsuccess: #648: 1: Success after binutils/gcc/linux/ [...] new 243e86a5ca56 187: onsuccess: #649: 1: Success after binutils/gcc/linux/ [...] new 2154f0d5ba05 188: onsuccess: #650: 1: Success after binutils/gcc/linux/ [...] new 0b36bf19123c 189: onsuccess: #651: 1: Success after binutils/gcc/linux/ [...] new d1417341b676 190: onsuccess: #652: 1: Success after binutils/gcc/linux/ [...] new 105eca945463 191: onsuccess: #653: 1: Success after binutils/gcc/linux/ [...] new e7567842b196 192: onsuccess: #654: 1: Success after binutils/gcc/linux/ [...] new fcd20e928aa7 193: onsuccess: #655: 1: Success after binutils/gcc/linux/ [...] new c32bbf4be95b 194: onsuccess: #656: 1: Success after binutils/gcc/linux/ [...] new 8ee5ebee5ca2 195: onsuccess: #657: 1: Success after binutils/gcc/linux/ [...] new 05e1c69585a4 196: onsuccess: #659: 1: Success after binutils/gcc/linux/ [...] new 47abf5c8486d 197: onsuccess: #660: 1: Success after binutils/gcc/linux/ [...] new 66001e959ba3 198: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 76ff8d82dd6a 199: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new bf51276bf361 200: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new f8d6a71c5d98 201: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 8c3a61163ed0 202: onsuccess: #670: 1: Success after binutils/gcc/linux/ [...] new 407ca8ccb6f9 203: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new 6d7216364178 204: onsuccess: #672: 1: Success after binutils/gcc/linux/ [...] new c44cedad9862 205: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 28116647d859 206: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 3ea3a4f43bf4 207: onsuccess: #3: 1: Success after binutils/gcc/linux/gd [...] new c68de8636ddc 208: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new e4ebce030e24 209: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new bde56c09eae8 210: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 8b697db5fa42 211: onsuccess: #7: 1: Success after binutils/gcc/linux/gd [...] new a698f485e948 212: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new c078a45cf45a 213: onsuccess: #9: 1: Success after binutils/gcc/linux/gl [...] new 2b8e2872bafa 214: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 016cebb46336 215: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new b00db51dcc00 216: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new e329f3cfe9ac 217: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new f3af77ae6002 218: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 8121468b96a6 219: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 9dc46a6672e5 220: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 6c487910b816 221: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 38288e5f0ff5 222: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 58f87cbcd287 223: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 7b6db6f3278c 224: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new 85137bf2155b 225: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new 1079cb45a77d 226: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new 5a95fbdb40c6 227: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 7fba7f2ba45a 228: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 0472a06d022a 229: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new 369372c12f61 230: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 823df2933006 231: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 4dbd40215440 232: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 4c3a65bd48b9 233: onsuccess: #34: 1: [TCWG CI] Success after binutils/g [...] new a3b01ca108da 234: onsuccess: #35: 1: [TCWG CI] Success after binutils/g [...] new d67a266853f9 235: onsuccess: #36: 1: [TCWG CI] Success after binutils/g [...] new 033f51c06653 236: onsuccess: #37: 1: [TCWG CI] Success after binutils/g [...] new c640f39898de 237: onsuccess: #38: 1: [TCWG CI] Success after binutils/g [...] new 7ca28b0d2345 238: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 488d8e890d1f 239: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new b7b97e93b97a 240: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 357606d9b050 241: onsuccess: #42: 1: [TCWG CI] Success after binutils/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 (0ad21a41bfe5) \ 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 2096 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2552 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 49684 -> 49156 bytes 04-build_abe-gcc/console.log.xz | Bin 234420 -> 235392 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8728 -> 8732 bytes 07-build_abe-glibc/console.log.xz | Bin 232660 -> 232352 bytes 08-build_abe-gdb/console.log.xz | Bin 46944 -> 46560 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3776 -> 3776 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9292 -> 11252 bytes 11-check_regression/console.log.xz | Bin 5644 -> 6044 bytes 11-check_regression/extra-bisect-params | 1 + 11-check_regression/fails.sum | 10 + 11-check_regression/results.compare | 45 +- 11-check_regression/results.compare2 | 233 +- 11-check_regression/results.regressions | 44 + 12-update_baseline/console.log | 68 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 50 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 34 +- manifest.sh | 38 +- results | 44 + sumfiles/g++.log.sep.xz | Bin 106092 -> 36084 bytes sumfiles/g++.log.xz | Bin 2888448 -> 2878992 bytes sumfiles/g++.sum | 2 +- sumfiles/g++.sum.sep | 5574 ++++++++++++++----------------- sumfiles/gcc.log.sep.xz | Bin 75828 -> 68820 bytes sumfiles/gcc.log.xz | Bin 2454620 -> 2520476 bytes sumfiles/gcc.sum | 12 +- sumfiles/gcc.sum.sep | 4364 +++++++++++++++++++----- sumfiles/gfortran.log.sep.xz | Bin 25752 -> 13632 bytes sumfiles/gfortran.log.xz | Bin 955728 -> 962696 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 2024 ++++------- sumfiles/libatomic.log.xz | Bin 2284 -> 2284 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 230724 -> 230624 bytes sumfiles/libgomp.sum | 14 +- sumfiles/libitm.log.xz | Bin 2692 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 20848 -> 5560 bytes sumfiles/libstdc++.log.xz | Bin 466044 -> 483720 bytes sumfiles/libstdc++.sum | 5 +- sumfiles/libstdc++.sum.sep | 138 +- 50 files changed, 7182 insertions(+), 5538 deletions(-) create mode 100644 11-check_regression/extra-bisect-params create mode 100644 11-check_regression/fails.sum create mode 100644 11-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm updated (4be8c788ccc4 -> 482e6280d794)

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 4be8c788ccc4 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...] discards 6cb87958e4a2 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] discards 9884db755da0 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards e863664a94f6 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 596964da860b 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards 51e9f80f9321 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards 5b905b0a9a70 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards cd4c715550de 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards e1532fdbb6fc 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards b2903268a30c 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 02558bcb44ed 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards fdc1406e5186 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 7fbfdfc836a7 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards d7dc948fca29 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards c73ea77ca354 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 784996a26ba6 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 91cfcafe6cd5 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards 10425634ac94 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 516bc929b91e 121: force: #26: : Failure after baseline build: no new commits discards ce8b19569a07 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 157a818adf7d 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 592daaa61864 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 0e24906b7dc3 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 509ea5856898 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 98564d507ffb 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards bff703551579 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards bfa420b075a9 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards e9eafb230721 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards df06dd7b6fc6 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 73cf7b97adcf 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 7fcf81497654 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 462ee3d69fc2 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 432e57e1c96c 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards dbfac6f43096 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] discards 931192cb22d1 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards 0f953cf2ae35 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] discards 43acf098b379 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards b569507234be 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] discards 808b04f36b90 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] discards a647740b2a87 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] discards 62d0828d491a 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] discards 63409d1ea467 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] discards e47d26f0c991 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] discards 6bbb2113a8d3 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] discards b9537bb09304 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] discards 9c0fe1e7d304 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] discards c9e11fc21fcf 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] discards 3892206fd7ad 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] discards 4ff60f965e48 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] discards 085f8db4c7d6 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] discards 0bf97dfd86ee 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] discards 6ef3d279b723 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] discards 376f2280d432 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] discards 3d3b78bedd8b 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] discards ddce6d010579 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] discards f1d055b46b4a 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] discards 546929a510b1 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] discards baa0d94614dd 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] discards 216a20fbcf45 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] discards 0ca5dcbc3f74 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] discards 3981b902c748 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] discards 32b38d4924a6 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] discards cf7469892586 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] discards 68d658b81482 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] discards bc56eb1fa9e8 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] discards 25a171d40a67 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] discards 22cd425aa7e5 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] discards bda27e28e289 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] discards 20582ebad288 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] discards 1da943c6e9cb 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] discards 2f864923ba3b 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] discards 03ba639b6cf5 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] discards 0aefd4b0d9fb 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] discards 1accf83478a2 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits discards 2cadc82af358 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] discards 5648e572aa86 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] discards b9047781a7bc 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] discards c41ca310e83e 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] discards 936cb9a82109 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] discards ec7dc4cea767 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] discards f5df529c1504 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] discards 6cdded078304 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] discards ca710f6dfb01 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] discards d6f6a339422b 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] discards 0cdebd4ccecb 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] discards 34db341c95db 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits discards 29fe86cad227 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits discards 41392b5f437e 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] discards 4f9593f0d54d 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits discards ee2a81df7b96 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] discards 8f57e4c9d124 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] discards 9c9f44ec62c3 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] discards a8edca4e70a4 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] discards 42a9055997ea 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] discards b5ed899631f3 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] discards d5e8c7738e41 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits discards 0cc15a145fb7 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] discards 5f0c4d0f7918 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] discards 9ee6ebcaee76 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] discards a7adcde9a71a 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] discards 32c2a6a7417b 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 68d633188d91 39: onsuccess: #46: 1: Success after binutils/gcc/linux/gd [...] new 1a320ba9d4b3 40: onsuccess: #47: 1: Success after binutils/gcc/linux/gl [...] new e8f1857d8127 41: onsuccess: #48: 1: Success after binutils/gcc/linux/gl [...] new 5c4accbc205b 42: onsuccess: #49: 1: Success after binutils/gcc/linux/gd [...] new 804ea78032ad 43: onsuccess: #50: 1: Success after binutils/gcc/linux/gd [...] new 808d7fc8e632 44: onsuccess: #51: 1: Success after binutils/gcc/gdb: 15 commits new 1261c0d8b502 45: onsuccess: #52: 1: Success after binutils/gcc/linux/gl [...] new d5392fef6ea4 46: onsuccess: #53: 1: Success after binutils/gcc/linux/gl [...] new 776c7c0820f2 47: onsuccess: #54: 1: Success after binutils/gcc/linux/gl [...] new 4faec2c57b23 48: onsuccess: #55: 1: Success after binutils/gcc/linux/gl [...] new 83ba67772ea1 49: onsuccess: #56: 1: Success after binutils/gcc/linux/gd [...] new 9bf117c1c97a 50: onsuccess: #57: 1: Success after binutils/gcc/linux/gd [...] new 338de21b1940 51: onsuccess: #58: 1: Success after binutils/gcc/gdb: 46 commits new 7188236cbc83 52: onsuccess: #59: 1: Success after binutils/gcc/linux/gd [...] new d55003ed1655 53: onsuccess: #60: 1: Success after binutils/gcc/gdb: 42 commits new 91d6c9af059b 54: onsuccess: #61: 1: Success after binutils/gcc/gdb: 14 commits new 3f0db2db5eed 55: onsuccess: #62: 1: Success after binutils/gcc/linux/gd [...] new 4e86b436ffca 56: onsuccess: #63: 1: Success after binutils/gcc/linux/gl [...] new e88e03785df8 57: onsuccess: #64: 1: Success after binutils/gcc/linux/gd [...] new 3c54f1a1f08e 58: onsuccess: #65: 1: Success after binutils/gcc/linux/gd [...] new d043d728b9e5 59: onsuccess: #67: 1: Success after binutils/gcc/linux/gl [...] new 4f1f512e24af 60: onsuccess: #69: 1: Success after binutils/gcc/gdb: 103 [...] new 9c7e03859037 61: onsuccess: #70: 1: Success after binutils/gcc/glibc/gd [...] new b083eff5eb4f 62: onsuccess: #71: 1: Success after binutils/gcc/linux/gl [...] new bfd3da78c850 63: onsuccess: #72: 1: Success after binutils/gcc/linux/gl [...] new b63e0e195848 64: onsuccess: #73: 1: Success after binutils/gcc/linux/gl [...] new 82498b4454eb 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gd [...] new dba56efbb428 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 commits new 39d2e4cf36d7 67: onsuccess: #76: 1: Success after binutils/gcc/linux/gl [...] new deb82cf543fb 68: onsuccess: #77: 1: Success after binutils/gcc/linux/gl [...] new 542477775d38 69: onsuccess: #78: 1: Success after binutils/gcc/linux/gd [...] new c06219f816ca 70: onsuccess: #79: 1: Success after binutils/gcc/linux/gl [...] new 06f9aa800e89 71: onsuccess: #80: 1: Success after binutils/gcc/linux/gl [...] new aeb24f8d4c2a 72: onsuccess: #81: 1: Success after binutils/gcc/linux/gl [...] new ab8ed3f6b01f 73: onsuccess: #82: 1: Success after binutils/gcc/linux/gd [...] new a5d2194944bf 74: onsuccess: #83: 1: Success after binutils/gcc/linux/gd [...] new 0d85d4d65255 75: onsuccess: #84: 1: Success after binutils/gcc/linux/gd [...] new 482d4e8880fd 76: onsuccess: #85: 1: Success after binutils/gcc/linux/gd [...] new b8b6b307c076 77: onsuccess: #86: 1: Success after binutils/gcc/linux/gl [...] new fca10c3319a5 78: onsuccess: #87: 1: Success after binutils/gcc/linux/gl [...] new 6e632250e701 79: onsuccess: #88: 1: Success after binutils/gcc/linux/gd [...] new 3fe25ff863bb 80: onsuccess: #89: 1: Success after binutils/gcc/gdb: 198 [...] new 494eb3f3bc01 81: onsuccess: #90: 1: Success after binutils/gcc/linux/gl [...] new 1eb02cf18cbf 82: onsuccess: #91: 1: Success after binutils/gcc/linux/gd [...] new d967baefaf23 83: onsuccess: #92: 1: Success after binutils/gcc/linux/gd [...] new 093fb50da2d4 84: onsuccess: #93: 1: Success after binutils/gcc/linux/gl [...] new d5eb504c07fb 85: onsuccess: #94: 1: Success after binutils/gcc/linux/gl [...] new fe22079ab332 86: onsuccess: #95: 1: Success after binutils/gcc/linux/gl [...] new e47134bfd9cf 87: onsuccess: #96: 1: Success after binutils/gcc/linux/gl [...] new 92ac5e076430 88: onsuccess: #97: 1: Success after binutils/gcc/linux/gl [...] new 8109eb6736de 89: onsuccess: #98: 1: Success after binutils/gcc/linux/gl [...] new 14f8186f87a0 90: onsuccess: #99: 1: Success after binutils/gcc/linux/gd [...] new ab45ed164786 91: onsuccess: #100: 1: Success after binutils/gcc/linux/g [...] new 98a50a55528e 92: onsuccess: #101: 1: Success after binutils/gcc/linux/g [...] new 286e5911f999 93: onsuccess: #103: 1: Success after binutils/gcc/linux/g [...] new b527a52831bd 94: onsuccess: #104: 1: Success after binutils/gcc/linux/g [...] new ed22123e9c65 95: onsuccess: #105: 1: Success after binutils/gcc/linux/g [...] new a17aba3f64f0 96: onsuccess: #106: 1: Success after binutils/gcc/linux/g [...] new abc6bdc934ae 97: onsuccess: #107: 1: Success after binutils/gcc/linux/g [...] new 634d97b62bfd 98: onsuccess: #108: 1: Success after binutils/gcc/linux/g [...] new 82203f512417 99: onsuccess: #120: 1: Success after binutils/gcc/linux/g [...] new 14372617cd79 100: onsuccess: #121: 1: Success after binutils/gcc/glibc/ [...] new d6938a4e757c 101: onsuccess: #122: 1: Success after binutils/gcc/linux/ [...] new 14b6206f42e0 102: onsuccess: #123: 1: Success after binutils/gcc/linux/ [...] new 7f53dab842e6 103: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new cc4ef1bb1f6e 104: onsuccess: #2: 1: Success after binutils/gcc/linux/gl [...] new 7a6747dc3efd 105: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 45f91304b136 106: onsuccess: #4: 1: Success after binutils/gcc/linux/gl [...] new ae5a92249a7f 107: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 77aa80c762d6 108: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new f37e721c599c 109: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 76d262284891 110: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new f0c08b5e5e87 111: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 95c58f762875 112: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 7097578df87c 113: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new c10fc661816a 114: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new 0bf8f13ea341 115: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 37fbf82ab436 116: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 9566d2cb56ae 117: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new ee9c407a4798 118: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 62c2ff2ee844 119: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new fb911319f8c4 120: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 51934116dc62 121: force: #26: : Failure after baseline build: no new commits new 34313a409c23 122: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 916382eb9b6c 123: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new b3f27f0053f1 124: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 0e9e72627cca 125: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 2990926a79a2 126: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 3072ecbe1cd2 127: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new bc62e789001a 128: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new ff97e6d34b8d 129: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 1768200a4d7f 130: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new f3d577d41435 131: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new 8310e7faf58d 132: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 0c344f564ba1 133: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new e58ff801b3b2 134: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new ec8372b5e548 135: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new c50777f21692 136: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new fd39919f69bb 137: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 43d4299e3d04 138: onsuccess: #45: 1: [TCWG CI] Success after binutils/g [...] new e2ed3e053a22 139: onsuccess: #46: 1: [TCWG CI] Success after binutils/g [...] new 482e6280d794 140: onsuccess: #47: 1: [TCWG CI] Success after binutils/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 (4be8c788ccc4) \ 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 2076 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 49760 -> 49416 bytes 04-build_abe-gcc/console.log.xz | Bin 235172 -> 235304 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8724 -> 9480 bytes 07-build_abe-glibc/console.log.xz | Bin 232148 -> 232504 bytes 08-build_abe-gdb/console.log.xz | Bin 47316 -> 47480 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3784 -> 3764 bytes 10-build_abe-check_gdb/console.log.xz | Bin 3336 -> 2964 bytes 11-check_regression/console.log.xz | Bin 4596 -> 5052 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 42 ++++++++++++++-------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 50 +++++++++++++++++++++------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 34 +++++++++++------------ manifest.sh | 38 +++++++++++++------------- sumfiles/gdb.log.xz | Bin 14444 -> 14432 bytes sumfiles/gdb.sum | 4 +-- 26 files changed, 102 insertions(+), 90 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[glibc] branch master updated (21a171bcb2 -> e9327e8584)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from 21a171bcb2 libio: Remove unused pragma weak on vtable new e9327e8584 hppa: Revise __TIMESIZE define to use __WORDSIZE The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/unix/sysv/linux/hppa/bits/timesize.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O3 updated (73f5880d6187 -> c349b8cca1f3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-arm-master-O3 in repository toolchain/ci/base-artifacts. from 73f5880d6187 11: onsuccess: #13: 1: [TCWG CI] No change after binutils/ [...] new c349b8cca1f3 12: onsuccess: #15: 1: [TCWG CI] Success after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2072 -> 2364 bytes 02-prepare_abe/console.log.xz | Bin 2564 -> 2568 bytes 03-build_abe-binutils/console.log.xz | Bin 27172 -> 27692 bytes 04-build_abe-stage1/console.log.xz | Bin 90584 -> 90260 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 7560 -> 8496 bytes 07-build_abe-glibc/console.log.xz | Bin 234548 -> 235216 bytes 08-build_abe-stage2/console.log.xz | Bin 213336 -> 214664 bytes 09-benchmark/benchmark-build.log | 169 +- 09-benchmark/benchmark.log | 167 +- 09-benchmark/console.log.xz | Bin 4144 -> 4144 bytes 10-check_regression/bmk-specific-variability.csv | 112 +- .../compare-results-vs-first-internal.csv | 193 +- .../compare-results-vs-prev-internal.csv | 195 +- 10-check_regression/console.log.xz | Bin 16248 -> 17336 bytes .../csv-results-vs-first-0/md5sum.csv | 2222 +- .../csv-results-vs-first-0/results.csv | 726846 ++++++++-------- .../csv-results-vs-first-0/size.csv | 731490 ++++++++-------- 10-check_regression/csv-results-vs-first-0/sve.csv | 25964 +- .../csv-results-vs-first-0/vect.csv | 1736 +- .../csv-results-vs-first-1/md5sum.csv | 2508 +- .../csv-results-vs-first-1/perf.csv | 2848 +- .../csv-results-vs-first-1/results.csv | 802227 +++++++++--------- .../csv-results-vs-first-1/size.csv | 796123 +++++++++-------- 10-check_regression/csv-results-vs-first-1/sve.csv | 25730 +- .../csv-results-vs-first-1/vect.csv | 1872 +- .../csv-results-vs-prev-0/md5sum.csv | 2602 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2889 +- .../csv-results-vs-prev-0/results.csv | 788300 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 781786 ++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 26076 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 1642 +- .../csv-results-vs-prev-1/md5sum.csv | 2508 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2848 +- .../csv-results-vs-prev-1/results.csv | 802227 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/size.csv | 796123 +++++++++-------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 25730 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 1872 +- 10-check_regression/exe.improvement | 1 + 10-check_regression/extra-bisect-params | 2 +- 10-check_regression/mail-body.txt | 3 + 10-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.improvement | 2 + .../output-bmk-results/exe.improvement.diff | 5 + .../output-bmk-results/symbol.improvement | 8 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 9 +- .../output-bmk-results/symbol.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 2848 +- 10-check_regression/results-vs-first-internal.csv | 193 +- 10-check_regression/results-vs-first.csv | 193 +- 10-check_regression/results-vs-first.log | 1402 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 5 +- 10-check_regression/results-vs-prev-full.csv | 2946 +- 10-check_regression/results-vs-prev-internal.csv | 195 +- 10-check_regression/results-vs-prev.csv | 195 +- 10-check_regression/results-vs-prev.log | 1624 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 16 +- .../500.perlbench_r/results-metrics.json | 2 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 16 +- .../503.bwaves_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 16 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 16 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 16 +- .../510.parest_r/results-metadata.json | 16 +- .../511.povray_r/results-metadata.json | 16 +- .../511.povray_r/results-metrics.json | 4 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metadata.json | 16 +- .../520.omnetpp_r/results-metrics.json | 2 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 16 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 16 +- .../523.xalancbmk_r/results-metrics.json | 2 +- .../525.x264_r/results-metadata.json | 16 +- .../526.blender_r/results-metadata.json | 16 +- .../527.cam4_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metadata.json | 16 +- .../531.deepsjeng_r/results-metrics.json | 4 +- .../538.imagick_r/results-metadata.json | 16 +- .../538.imagick_r/results-metrics.json | 2 +- .../541.leela_r/results-metadata.json | 16 +- .../541.leela_r/results-metrics.json | 4 +- .../squad-vs-first/544.nab_r/results-metadata.json | 16 +- .../squad-vs-first/544.nab_r/results-metrics.json | 2 +- .../548.exchange2_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metadata.json | 16 +- .../549.fotonik3d_r/results-metrics.json | 2 +- .../554.roms_r/results-metadata.json | 16 +- .../squad-vs-first/557.xz_r/results-metadata.json | 16 +- .../squad-vs-first/557.xz_r/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 16 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 26 + mail/changes-list-short.txt | 1 + manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 27 - mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 36 +- results_id | 2 +- 111 files changed, 3194245 insertions(+), 3171129 deletions(-) create mode 100644 10-check_regression/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement create mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt copy manifest.sh => mail/last_good.sh (100%) delete mode 100644 mail/mail-body.txt delete mode 100644 mail/mail-subject.txt create mode 100644 mail/short-diag.txt -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[linux] branch master updated (76f598ba7d8e -> 99ddf2254feb)

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 76f598ba7d8e Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt [...] new 4ccf11c4e8a8 tracing/synthetic: Fix races on freeing last_cmd new 6455b6163d8c ring-buffer: Fix race while reader and writer are on the s [...] new ea65b41807a2 ftrace: Mark get_lock_parent_ip() __always_inline new b9f451a9029a tracing/timerlat: Notify new max thread latency new d3cba7f02cd8 tracing/osnoise: Fix notify new tracing_max_latency new f82e7ca019df tracing: Error if a trace event has an array for a __field() new 9d52727f8043 tracing: Have tracing_snapshot_instance_cond() write error [...] new e94891641c21 tracing: Fix ftrace_boot_snapshot command line logic new 3357c6e42964 tracing: Free error logs of tracing instances new 99ddf2254feb Merge tag 'trace-v6.3-rc5' of git://git.kernel.org/pub/scm [...] The 10 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: include/linux/ftrace.h | 2 +- include/trace/stages/stage5_get_offsets.h | 21 +++++++++++++++++---- kernel/trace/ring_buffer.c | 13 ++++++++++++- kernel/trace/trace.c | 28 +++++++++++++++------------- kernel/trace/trace_events_synth.c | 19 +++++++++++++++---- kernel/trace/trace_osnoise.c | 4 +++- 6 files changed, 63 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O2 updated (a91d5b3f6321 -> 55266d11fefa)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017rate/gnu-aarch64-master-O2 in repository toolchain/ci/base-artifacts. from a91d5b3f6321 15: onsuccess: #18: 1: [TCWG CI] Success after binutils/gc [...] new 55266d11fefa 16: onsuccess: #19: 1: [TCWG CI] Success after binutils/gc [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2040 -> 2080 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2572 bytes 03-build_abe-binutils/console.log.xz | Bin 27140 -> 28200 bytes 04-build_abe-stage1/console.log.xz | Bin 71568 -> 71792 bytes 06-build_abe-linux/console.log.xz | Bin 8308 -> 8488 bytes 07-build_abe-glibc/console.log.xz | Bin 241508 -> 244028 bytes 08-build_abe-stage2/console.log.xz | Bin 176552 -> 178340 bytes 09-benchmark/benchmark-build.log | 142 +- 09-benchmark/benchmark.log | 140 +- 09-benchmark/console.log.xz | Bin 4096 -> 4108 bytes 10-check_regression/bmk-specific-variability.csv | 111 +- .../compare-results-vs-first-internal.csv | 193 +- .../compare-results-vs-prev-internal.csv | 193 +- 10-check_regression/console.log.xz | Bin 17068 -> 16176 bytes .../csv-results-vs-first-1/md5sum.csv | 2349 +- .../csv-results-vs-first-1/perf.csv | 2824 +- .../csv-results-vs-first-1/results.csv | 11155 +- .../csv-results-vs-first-1/size.csv | 680353 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 24478 +- .../csv-results-vs-first-1/vect.csv | 234 +- .../csv-results-vs-prev-0/md5sum.csv | 2456 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2785 +- .../csv-results-vs-prev-0/results.csv | 33359 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 587238 ++++++++------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 14752 +- 10-check_regression/csv-results-vs-prev-0/vect.csv | 260 +- .../csv-results-vs-prev-1/md5sum.csv | 2349 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2824 +- .../csv-results-vs-prev-1/results.csv | 11155 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 680353 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 24478 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 234 +- .../output-bmk-results/exe.improvement | 1 - .../output-bmk-results/exe.improvement.diff | 1 - .../output-bmk-results/symbol.improvement | 7 +- .../output-bmk-results/symbol.regression | 8 +- 10-check_regression/results-vs-first-brief.csv | 56 +- 10-check_regression/results-vs-first-full.csv | 2761 +- 10-check_regression/results-vs-first-internal.csv | 193 +- 10-check_regression/results-vs-first.csv | 193 +- 10-check_regression/results-vs-first.log | 1216 +- 10-check_regression/results-vs-prev-brief.csv | 56 +- 10-check_regression/results-vs-prev-compare.csv | 5 +- 10-check_regression/results-vs-prev-full.csv | 2891 +- 10-check_regression/results-vs-prev-internal.csv | 193 +- 10-check_regression/results-vs-prev.csv | 193 +- 10-check_regression/results-vs-prev.log | 1478 +- dashboard/dashboard-generate.sh | 2 +- .../500.perlbench_r/results-metadata.json | 12 +- .../squad-vs-first/502.gcc_r/results-metadata.json | 12 +- .../squad-vs-first/502.gcc_r/results-metrics.json | 2 +- .../503.bwaves_r/results-metadata.json | 12 +- .../503.bwaves_r/results-metrics.json | 2 +- .../squad-vs-first/505.mcf_r/results-metadata.json | 12 +- .../squad-vs-first/505.mcf_r/results-metrics.json | 2 +- .../507.cactuBSSN_r/results-metadata.json | 12 +- .../507.cactuBSSN_r/results-metrics.json | 2 +- .../508.namd_r/results-metadata.json | 12 +- .../squad-vs-first/508.namd_r/results-metrics.json | 2 +- .../510.parest_r/results-metadata.json | 12 +- .../511.povray_r/results-metadata.json | 12 +- .../511.povray_r/results-metrics.json | 2 +- .../squad-vs-first/519.lbm_r/results-metadata.json | 12 +- .../520.omnetpp_r/results-metadata.json | 12 +- .../squad-vs-first/521.wrf_r/results-metadata.json | 12 +- .../squad-vs-first/521.wrf_r/results-metrics.json | 2 +- .../523.xalancbmk_r/results-metadata.json | 12 +- .../525.x264_r/results-metadata.json | 12 +- .../526.blender_r/results-metadata.json | 12 +- .../527.cam4_r/results-metadata.json | 12 +- .../531.deepsjeng_r/results-metadata.json | 12 +- .../531.deepsjeng_r/results-metrics.json | 2 +- .../538.imagick_r/results-metadata.json | 12 +- .../541.leela_r/results-metadata.json | 12 +- .../squad-vs-first/544.nab_r/results-metadata.json | 12 +- .../548.exchange2_r/results-metadata.json | 12 +- .../548.exchange2_r/results-metrics.json | 2 +- .../549.fotonik3d_r/results-metadata.json | 12 +- .../549.fotonik3d_r/results-metrics.json | 2 +- .../554.roms_r/results-metadata.json | 12 +- .../squad-vs-first/554.roms_r/results-metrics.json | 2 +- .../squad-vs-first/557.xz_r/results-metadata.json | 12 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 98 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 44 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 36 +- manifest.sh | 32 +- results_id | 2 +- 92 files changed, 1054792 insertions(+), 1039407 deletions(-) delete mode 100644 10-check_regression/output-bmk-results/exe.improvement delete mode 100644 10-check_regression/output-bmk-results/exe.improvement.diff -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[gcc] branch master updated (85cefbc66e7 -> 3bfd0420e4a)

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 85cefbc66e7 Fix 22_locale/locale/cons/12658_thread-2.cc on hppa. new 9d63ce7c4c0 libstdc++: Harmonize <version> and other headers new 6f0d67b9129 libstdc++: Add a test for <version> FTM redefinitions new bff26ac1627 libstdc++: Downgrade DEBUG to ASSERTIONS when !HOSTED new 3bfd0420e4a libstdc++: Fix some freestanding test failures The 4 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: libstdc++-v3/include/bits/c++config | 7 ++ libstdc++-v3/include/bits/ptr_traits.h | 11 ++- libstdc++-v3/include/bits/unique_ptr.h | 11 ++- libstdc++-v3/include/precompiled/stdc++.h | 1 - libstdc++-v3/include/std/memory | 6 ++ libstdc++-v3/include/std/version | 90 ++++++++++++---------- libstdc++-v3/testsuite/17_intro/versionconflict.cc | 7 ++ libstdc++-v3/testsuite/18_support/96817.cc | 1 + .../testsuite/18_support/bad_exception/59392.cc | 1 + .../testsuite/20_util/scoped_allocator/108952.cc | 1 + .../testsuite/20_util/uses_allocator/lwg3527.cc | 1 + .../atomic/operators/pointer_partial_void.cc | 1 + libstdc++-v3/testsuite/lib/libstdc++.exp | 1 + 13 files changed, 89 insertions(+), 50 deletions(-) create mode 100644 libstdc++-v3/testsuite/17_intro/versionconflict.cc -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap_profiled_lto updated (809faf445a6e -> eaafeba91c6a)

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 809faf445a6e 206: onsuccess: #49: 2: [TCWG CI] Success after binutils/g [...] discards 0317d4d156c6 205: onsuccess: #48: 2: [TCWG CI] Success after binutils/g [...] discards 383f54d2d4ce 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/g [...] discards bb2406660339 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/g [...] discards 012db638398a 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/g [...] discards 50159a69416a 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] discards b4afad7ec4d3 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] discards 696ed6798abb 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits discards 64ddaad4ef71 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc [...] discards 708a760851e8 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits discards 1d8156190a5f 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: [...] discards 5161eb0a624a 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits discards f4186514c47d 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits discards 132335b27ebd 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits discards add606f17470 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits discards 3045a6a66903 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits discards a1cd54ea5ef3 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits discards 8302e42fc2e2 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits discards 12ef4b7bc01e 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits discards 7470ab7a4e79 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits discards c9ae8ba2cf73 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits discards a3e6215d1e22 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits discards bfa7f951d42e 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits discards 918fee352c42 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits discards b8041df41080 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits discards b3464e5a6a6a 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits discards b49cc584c638 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits discards 6db2c7270cac 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits discards 3810149d4c78 178: onsuccess: #16: 0: Success after binutils: 15 commits discards a8a9616b4b56 177: force: #15: 0: Failure after gdb-13-branchpoint-1318- [...] discards 4d7a75168836 176: force: #14: 2: Success after binutils: 18 commits discards e212702481d3 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits discards e6cdd208228b 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits discards 5a6e0f24b85b 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits discards a008ba795491 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits discards df307258d771 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits discards b78652babde9 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits discards 1255dc0a8ca1 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits discards 2ab89f8146a5 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits discards 738118a6b5e9 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits discards 4ca18f9f21a1 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits discards 7f4b77945fb4 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits discards 0db63d5402ee 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits discards 1702defb8101 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits discards ac87f0939a2e 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits discards 74809b748543 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits discards 83591790c881 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits discards 69077da78738 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits discards 22c879b7d64f 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits discards 767b517ac6de 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits discards 95aff8159978 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits discards dab3ebc954f1 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits discards 4bea643fc035 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits discards 5f31fd3dd229 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits discards 7967e57542a4 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits discards 48c27c8aa97d 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits discards 10a9178a22bd 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits discards 9c1ac4be110b 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits discards 3e161123d6d8 148: onsuccess: #571: 2: Success after gcc: 4 commits discards 472da224b272 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits discards a43de7f1a168 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits discards 31434bf0c2f2 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits discards 656cd60f3678 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits discards f7c712b48f57 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits discards 60c806adb31f 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits discards 0073209a2b34 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits discards 56442c9dc4d4 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits discards 5c33e0cb730d 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits discards 36c82346f963 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits discards d6c73e192a29 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits discards 9615549f51d9 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits discards 13d4afa22781 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits discards 190b809d6de3 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits discards 4bcf60efeb15 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits discards 5b94baf9dc93 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits discards 6f49781ad726 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits discards 451378ae023f 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits discards 33fd109f5b56 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits discards 06f63e48d96d 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits discards 049159c90d8b 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits discards 72a341cc653d 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits discards ab4ec10df86d 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits discards 80b06d1ecdaa 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits discards 66e2407a07d1 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits discards 063c4731ed63 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits discards 466e6d4c9049 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits discards b4108ee6948c 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits discards a9b87e9bfa30 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits discards 22b2d17edbe2 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits discards f84584b9583b 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits discards 1d436854777e 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits discards 1fb7bec28149 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits discards 014863247818 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits discards db1bc2e9335c 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits discards df0cc59e5dfa 112: onsuccess: #527: 1: Success after binutils: 10 commits discards 6403b77029c1 111: force: #526: 1: Failure after binutils: 5 commits discards 529371a46eed 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits discards 6cde9e44dfdf 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits discards df1734be3663 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits discards cbcfedb10396 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits discards cc7b20c133b6 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits new f20d59db2338 106: onsuccess: #516: 2: Success after binutils/gcc: 27 commits new 404efad78538 107: onsuccess: #517: 2: Success after binutils/gcc: 64 commits new f5aefefd805c 108: onsuccess: #518: 2: Success after binutils/gcc: 3 commits new 0ba1b884db30 109: onsuccess: #519: 2: Success after binutils/gcc: 12 commits new 1e8e936952a1 110: onsuccess: #520: 2: Success after binutils/gcc: 47 commits new 7065740c67e6 111: force: #526: 1: Failure after binutils: 5 commits new 567e3359bdca 112: onsuccess: #527: 1: Success after binutils: 10 commits new 4dd4ef150a86 113: onsuccess: #528: 2: Success after binutils/gcc: 187 commits new ad8dcfc3b917 114: onsuccess: #529: 2: Success after binutils/gcc: 4 commits new 199ee464a7b1 115: onsuccess: #530: 2: Success after binutils/gcc: 9 commits new ebf9a2cbc179 116: onsuccess: #531: 2: Success after binutils/gcc: 55 commits new cd439a75a01f 117: onsuccess: #533: 2: Success after binutils/gcc: 81 commits new 182aa00439c7 118: onsuccess: #534: 2: Success after binutils/gcc: 58 commits new e3b2f8d4ca4f 119: onsuccess: #535: 2: Success after binutils/gcc: 74 commits new 15cb1b9e1efc 120: onsuccess: #536: 2: Success after binutils/gcc: 9 commits new 4df341310964 121: onsuccess: #537: 2: Success after binutils/gcc: 24 commits new a27575362ada 122: onsuccess: #538: 2: Success after binutils/gcc: 6 commits new b90acb323e34 123: onsuccess: #539: 2: Success after binutils/gcc: 29 commits new e8189c7ee64a 124: onsuccess: #540: 2: Success after binutils/gcc: 9 commits new f764ecf901aa 125: onsuccess: #541: 2: Success after binutils/gcc: 20 commits new 47a104e0be0e 126: onsuccess: #542: 2: Success after binutils/gcc: 11 commits new 7fc4f2c15f44 127: onsuccess: #543: 2: Success after binutils/gcc: 18 commits new 8c24074b5e7f 128: onsuccess: #544: 2: Success after binutils/gcc: 18 commits new 44c93e8074e3 129: onsuccess: #545: 2: Success after binutils/gcc: 30 commits new 78c228bd7528 130: onsuccess: #546: 2: Success after binutils/gcc: 51 commits new 787ee7620523 131: onsuccess: #547: 2: Success after binutils/gcc: 37 commits new 56ceb1068c73 132: onsuccess: #551: 2: Success after binutils/gcc: 79 commits new cee1a2122ad9 133: onsuccess: #552: 2: Success after binutils/gcc: 6 commits new 11a7c570842c 134: onsuccess: #556: 2: Success after binutils/gcc: 106 commits new c9da87557447 135: onsuccess: #557: 2: Success after binutils/gcc: 52 commits new ca0a648875e1 136: onsuccess: #558: 2: Success after binutils/gcc: 41 commits new 0549810a152c 137: onsuccess: #559: 2: Success after binutils/gcc: 128 commits new 62b14b2136f0 138: onsuccess: #560: 2: Success after binutils/gcc: 74 commits new bb65486b6943 139: onsuccess: #562: 2: Success after binutils/gcc: 73 commits new 128233de626b 140: onsuccess: #563: 2: Success after binutils/gcc: 40 commits new a0e2bfc59ab3 141: onsuccess: #564: 2: Success after binutils/gcc: 23 commits new d42ce35e2323 142: onsuccess: #565: 2: Success after binutils/gcc: 4 commits new 032919da042a 143: onsuccess: #566: 2: Success after binutils/gcc: 41 commits new 8eeffa547969 144: onsuccess: #567: 2: Success after binutils/gcc: 36 commits new c5b49c025dbf 145: onsuccess: #568: 2: Success after binutils/gcc: 72 commits new d5a577d0b7a9 146: onsuccess: #569: 2: Success after binutils/gcc: 157 commits new 9c7978ab7ccb 147: onsuccess: #570: 2: Success after binutils/gcc: 24 commits new c32dbcb2288b 148: onsuccess: #571: 2: Success after gcc: 4 commits new c97ad3029523 149: onsuccess: #573: 2: Success after binutils/gcc: 178 commits new 64cd441838c3 150: onsuccess: #574: 2: Success after binutils/gcc: 51 commits new ed0d63ee5834 151: onsuccess: #575: 2: Success after binutils/gcc: 49 commits new 1bac7a2ed001 152: onsuccess: #576: 2: Success after binutils/gcc: 9 commits new 6b4621dc7cec 153: onsuccess: #577: 2: Success after binutils/gcc: 8 commits new 37eef42744ec 154: onsuccess: #578: 2: Success after binutils/gcc: 32 commits new 4928b90740d2 155: onsuccess: #579: 2: Success after binutils/gcc: 35 commits new 6b732bd11cc9 156: onsuccess: #581: 2: Success after binutils/gcc: 45 commits new dde2319eec43 157: onsuccess: #582: 2: Success after binutils/gcc: 68 commits new 41f3733e50d2 158: onsuccess: #583: 2: Success after binutils/gcc: 146 commits new 1fdc34ba17aa 159: onsuccess: #584: 2: Success after binutils/gcc: 87 commits new a4c5c32f56ae 160: onsuccess: #585: 2: Success after binutils/gcc: 36 commits new 2ee87e3d69ac 161: onsuccess: #591: 2: Success after binutils/gcc: 271 commits new 8c1e4f195fe0 162: onsuccess: #592: 2: Success after binutils/gcc: 139 commits new 39346491fd7c 163: onsuccess: #593: 2: Success after binutils/gcc: 48 commits new 05659e1162c5 164: onsuccess: #1: 2: Success after binutils/gcc: 23 commits new 712ccdfebb01 165: onsuccess: #2: 2: Success after binutils/gcc: 38 commits new 0137559bc6a9 166: onsuccess: #3: 2: Success after binutils/gcc: 4 commits new f8376589e8fa 167: onsuccess: #4: 2: Success after binutils/gcc: 8 commits new a3f9a040400c 168: onsuccess: #5: 2: Success after binutils/gcc: 22 commits new 547e484d960b 169: onsuccess: #6: 2: Success after binutils/gcc: 66 commits new 5e5279a04c3b 170: onsuccess: #7: 2: Success after binutils/gcc: 23 commits new 54c4b7a5db87 171: onsuccess: #8: 2: Success after binutils/gcc: 36 commits new 7f8faba6bc3a 172: onsuccess: #9: 2: Success after binutils/gcc: 48 commits new 75b1aad7b67d 173: onsuccess: #10: 2: Success after binutils/gcc: 29 commits new 0876ade94f0a 174: onsuccess: #11: 2: Success after binutils/gcc: 10 commits new 0cc7f57c1e7a 175: onsuccess: #12: 2: Success after binutils/gcc: 34 commits new 37b73f427219 176: force: #14: 2: Success after binutils: 18 commits new b46627053fe8 177: force: #15: 0: Failure after gdb-13-branchpoint-1318- [...] new 15e19d76fa70 178: onsuccess: #16: 0: Success after binutils: 15 commits new d60fe1891343 179: onsuccess: #17: 2: Success after binutils/gcc: 56 commits new e69e44d001b1 180: onsuccess: #18: 2: Success after binutils/gcc: 26 commits new 7c532da1f41d 181: onsuccess: #19: 2: Success after binutils/gcc: 51 commits new 7fb304c01fe4 182: onsuccess: #20: 2: Success after binutils/gcc: 27 commits new 7b0c5b918de1 183: onsuccess: #21: 2: Success after binutils/gcc: 11 commits new 8cd017e72da3 184: onsuccess: #22: 2: Success after binutils/gcc: 34 commits new 0789cb6233cc 185: onsuccess: #23: 2: Success after binutils/gcc: 61 commits new 94f4aec6f667 186: onsuccess: #24: 2: Success after binutils/gcc: 41 commits new 861e5fe46c5e 187: onsuccess: #25: 2: Success after binutils/gcc: 34 commits new f42bb2afc6cb 188: onsuccess: #27: 2: Success after binutils/gcc: 63 commits new 39834cc05381 189: onsuccess: #28: 2: Success after binutils/gcc: 32 commits new 3e3aca7ba794 190: onsuccess: #29: 2: Success after binutils/gcc: 27 commits new 25bf6ce01ea1 191: onsuccess: #30: 2: Success after binutils/gcc: 42 commits new 6280a64ea086 192: onsuccess: #31: 2: Success after binutils/gcc: 25 commits new 2ffea3859646 193: onsuccess: #32: 2: Success after binutils/gcc: 42 commits new 4d583023bd5c 194: onsuccess: #34: 2: Success after binutils/gcc: 45 commits new e619f7a710e3 195: onsuccess: #35: 2: Success after binutils/gcc: 5 commits new d6400a894ac4 196: onsuccess: #38: 2: [TCWG CI] Success after binutils: [...] new 4033aa24bcb7 197: force: #40: 2: [TCWG CI] Success after gcc: 40 commits new ae69387e71a2 198: force: #41: 1: [TCWG CI] Failure after basepoints/gcc [...] new e572ae50ca04 199: onsuccess: #42: 1: [TCWG CI] Success after gcc: 2 commits new 9f9d1a7efa1d 200: onsuccess: #43: 2: [TCWG CI] Success after binutils/g [...] new 07a6d6c2912f 201: onsuccess: #44: 2: [TCWG CI] Success after binutils/g [...] new ee22f1273cd3 202: onsuccess: #45: 2: [TCWG CI] Success after binutils/g [...] new 353b964642db 203: onsuccess: #46: 2: [TCWG CI] Success after binutils/g [...] new e27b9b12d1d2 204: onsuccess: #47: 2: [TCWG CI] Success after binutils/g [...] new 8ad0cfcbb28f 205: onsuccess: #48: 2: [TCWG CI] Success after binutils/g [...] new a7054f0b7e7c 206: onsuccess: #49: 2: [TCWG CI] Success after binutils/g [...] new eaafeba91c6a 207: onsuccess: #50: 2: [TCWG CI] Success after binutils/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 (809faf445a6e) \ 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 1920 -> 1964 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2536 bytes 04-build_abe-binutils/console.log.xz | Bin 49616 -> 49088 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 613356 -> 607300 bytes 06-check_regression/console.log.xz | Bin 2844 -> 3080 bytes 07-update_baseline/console.log | 62 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/changes-list-long.txt | 21 ++++--- mail/last_good.sh | 20 +++---- manifest.sh | 20 +++---- 12 files changed, 66 insertions(+), 63 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

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

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_aosp-code_size-surfaceflinger/oriole-master in repository toolchain/ci/base-artifacts. from 928fec6acc58 10: onsuccess: #61: 2: [TCWG CI] Success after aosp_superp [...] new 3cf9a09cdce5 11: onsuccess: #62: 2: [TCWG CI] Success after aosp_superp [...] 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 2184 -> 2012 bytes 02-build_aosp_toolchain/console.log.xz | Bin 197724 -> 197772 bytes 03-build_shadow_llvm/console.log.xz | Bin 130636 -> 130800 bytes 04-build_aosp/console.log.xz | Bin 69332 -> 69636 bytes 05-process_shadow_data/console.log.xz | Bin 272 -> 272 bytes 06-check_regression/aosp.improvements | 1 + 06-check_regression/binary.improvements | 1 + 06-check_regression/console.log.xz | Bin 7028 -> 6812 bytes 06-check_regression/results-vs-first.csv | 12 ++--- 06-check_regression/results-vs-prev.csv | 84 +++++++++++++++---------------- dashboard/dashboard-generate.sh | 2 +- git/aosp_superproject_rev | 2 +- git/llvm_rev | 2 +- git/toolchain_superproject_rev | 2 +- mail/changes-list-long.txt | 32 ++++++------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 26 +++++----- manifest.sh | 26 +++++----- size.csv | 68 ++++++++++++------------- 19 files changed, 129 insertions(+), 131 deletions(-) create mode 100644 06-check_regression/aosp.improvements create mode 100644 06-check_regression/binary.improvements -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allyesconfig updated (ef9ee99488c7 -> a67265989913)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from ef9ee99488c7 70: onsuccess: #11: all: [TCWG CI] Success after binutils/ [...] new a67265989913 71: onsuccess: #12: all: [TCWG CI] Success after binutils/ [...] 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 2012 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2516 bytes 03-build_abe-binutils/console.log.xz | Bin 27352 -> 27280 bytes 04-build_kernel_llvm/console.log.xz | Bin 63428 -> 66800 bytes 05-build_abe-qemu/console.log.xz | Bin 30460 -> 31340 bytes 06-build_linux/console.log.xz | Bin 3204 -> 3200 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4340 -> 4196 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/changes-list-long.txt | 48 +++++++++++++++++------------------ mail/changes-list-short.txt | 2 +- mail/last_good.sh | 32 +++++++++++------------ manifest.sh | 32 +++++++++++------------ 17 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/master-arm updated (ca1eb72926dd -> 8b888f4b1589)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards ca1eb72926dd 235: onsuccess: #44: 6: [TCWG CI] Success after binutils/g [...] discards 3c54e644f40e 234: onsuccess: #43: 6: [TCWG CI] Success after binutils/g [...] discards aa7588f17585 233: onsuccess: #42: 6: [TCWG CI] Success after binutils/g [...] discards 2e26d0a8f3fe 232: onsuccess: #41: 6: [TCWG CI] Success after binutils/g [...] discards caf4c2901932 231: onsuccess: #39: 6: [TCWG CI] Success after binutils/g [...] discards dedc480db0d3 230: onsuccess: #38: 6: [TCWG CI] Success after binutils/g [...] discards 3e1882bc038a 229: onsuccess: #37: 6: [TCWG CI] Success after binutils/g [...] discards 5621805c61f2 228: onsuccess: #35: 6: Success after binutils/gcc/linux/g [...] discards 3ebb81748bf7 227: onsuccess: #34: 6: Success after binutils/gcc/linux/g [...] discards 1ff85c9a5579 226: onsuccess: #32: 6: Success after binutils/gcc/linux/g [...] discards 6a64bf19e4bd 225: onsuccess: #31: 6: Success after binutils/gcc/linux/g [...] discards 9dfe9ee8ecc6 224: onsuccess: #30: 6: Success after binutils/gcc/linux/g [...] discards 31586f05daa7 223: onsuccess: #29: 6: Success after binutils/gcc/linux/g [...] discards 832e4aacd4ab 222: onsuccess: #28: 6: Success after binutils/gcc/linux/g [...] discards 99c70b1da312 221: onsuccess: #26: 6: Success after binutils/gcc/linux/g [...] discards 7be88f6b6d27 220: onsuccess: #25: 6: Success after binutils/gcc/linux/g [...] discards 925cf66134eb 219: onsuccess: #24: 6: Success after binutils/gcc/linux/g [...] discards cd7c7ca02fe5 218: onsuccess: #23: 6: Success after binutils/gcc/linux/g [...] discards 6802da519802 217: onsuccess: #22: 6: Success after binutils/gcc/linux/g [...] discards 5a1391a3bf0f 216: onsuccess: #21: 6: Success after binutils/gcc/linux/g [...] discards da40363c53e8 215: onsuccess: #20: 6: Success after binutils/gcc/linux/g [...] discards ee5627b6e53c 214: onsuccess: #19: 6: Success after binutils/gcc/linux/g [...] discards 5cd0fb7bf5b6 213: onsuccess: #18: 6: Success after binutils/gcc/linux/g [...] discards be94ed82342a 212: onsuccess: #17: 6: Success after binutils/gcc/linux/g [...] discards 3f1166a8133f 211: onsuccess: #12: 6: Success after binutils/gcc/linux/g [...] discards 9adfcae8fb20 210: onsuccess: #11: 6: Success after binutils/gcc/linux/g [...] discards ac3496ae9b04 209: onsuccess: #10: 6: Success after binutils/gcc/linux/g [...] discards a36bbe645f7e 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gl [...] discards 426ecb6a56d4 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gl [...] discards a0c987de82ed 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gd [...] discards 262e292fb6cb 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gl [...] discards 5b2e7613441c 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gl [...] discards 2ae660b5e016 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gl [...] discards d901380aee73 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gd [...] discards ca54ee779c2c 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gl [...] discards 7cd45a9c2890 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gl [...] discards a7ab2c4390eb 199: onsuccess: #630: 6: Success after binutils/gcc/linux/ [...] discards f89795a2de86 198: onsuccess: #629: 6: Success after binutils/gcc/linux/ [...] discards 03de77148549 197: onsuccess: #628: 6: Success after binutils/gcc/linux/ [...] discards 454732e5241b 196: onsuccess: #621: 6: Success after binutils/gcc/linux/ [...] discards 575e5aeed4c2 195: onsuccess: #620: 6: Success after binutils/gcc/linux/ [...] discards afaecb82c382 194: onsuccess: #619: 6: Success after binutils/gcc/linux/ [...] discards cdfc805d62a8 193: onsuccess: #618: 6: Success after binutils/gcc/linux/ [...] discards e3613a4158d7 192: onsuccess: #617: 6: Success after binutils/gcc/linux/ [...] discards 376aa73b9b05 191: onsuccess: #615: 6: Success after binutils/gcc/linux/ [...] discards 3346eab78849 190: onsuccess: #614: 6: Success after binutils/gcc/linux/ [...] discards f03a3ccf31d7 189: onsuccess: #613: 6: Success after binutils/gcc/linux/ [...] discards 50135a17ee3a 188: onsuccess: #612: 6: Success after binutils/gcc/linux/ [...] discards 34421c7d967a 187: onsuccess: #611: 6: Success after binutils/gcc/linux/ [...] discards 10c3775f866d 186: onsuccess: #610: 6: Success after binutils/gcc/linux/ [...] discards ea9f8041e137 185: onsuccess: #609: 6: Success after binutils/gcc/linux/ [...] discards d3f5e32b65b5 184: onsuccess: #608: 6: Success after binutils/gcc/linux/ [...] discards 3d4506e26681 183: onsuccess: #607: 6: Success after binutils/gcc/linux/ [...] discards 198a10290274 182: onsuccess: #606: 6: Success after binutils/gcc/linux/ [...] discards 22c161bb9ae2 181: onsuccess: #605: 6: Success after binutils/gcc/linux/ [...] discards 4fc412b929d6 180: onsuccess: #604: 6: Success after binutils/gcc/linux/ [...] discards 9c2a94d4f2dc 179: onsuccess: #603: 6: Success after binutils/gcc/linux/ [...] discards b248d0641dc7 178: onsuccess: #602: 6: Success after binutils/gcc/linux/ [...] discards 2839f5fc9161 177: onsuccess: #601: 6: Success after binutils/gcc/linux/ [...] discards e430f44dc1c4 176: onsuccess: #600: 6: Success after binutils/gcc/linux/ [...] discards abfa1f6ba126 175: onsuccess: #599: 6: Success after binutils/gcc/linux/ [...] discards c3cf0a908912 174: onsuccess: #598: 6: Success after binutils/gcc/linux/ [...] discards 494eee4104a0 173: onsuccess: #597: 6: Success after binutils/gcc/linux/ [...] discards bcdacf2e4883 172: onsuccess: #596: 6: Success after binutils/gcc/linux/ [...] discards dd2adc4099f4 171: onsuccess: #595: 6: Success after binutils/gcc/linux/ [...] discards ed5e4d47c304 170: onsuccess: #594: 6: Success after binutils/gcc/linux/ [...] discards 0d72eaa1357c 169: onsuccess: #593: 6: Success after binutils/gcc/linux/ [...] discards 66445883471c 168: onsuccess: #591: 6: Success after binutils/gcc/linux/ [...] discards 1c8886844852 167: onsuccess: #590: 6: Success after binutils/gcc/linux/ [...] discards 91675debd2e7 166: onsuccess: #589: 6: Success after binutils/gcc/linux/ [...] discards 55b9993f95aa 165: onsuccess: #588: 6: Success after binutils/gcc/linux/ [...] discards f21282771511 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/ [...] discards ca403c6f4a35 163: onsuccess: #586: 6: Success after binutils/gcc/linux/ [...] discards 777483a1f34b 162: onsuccess: #579: 6: Success after gcc: 11 commits discards 8021db3ba86b 161: onsuccess: #578: 6: Success after binutils: 15 commits discards 6b66e5110e3b 160: onsuccess: #576: 6: Success after binutils/gcc/linux/ [...] discards 27463caf3845 159: onsuccess: #575: 6: Success after binutils/gcc/linux/ [...] discards d1929fad8f47 158: onsuccess: #574: 6: Success after binutils/gcc/linux/ [...] discards d13c83c422c9 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 [...] discards c13cb2de2d32 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 1 [...] discards 8637a2871333 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 3 [...] discards f0965e8fc86a 154: onsuccess: #570: 6: Success after binutils/gcc/linux/ [...] discards 15760e6e6398 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 4 [...] discards ccd26b54ef7b 152: onsuccess: #568: 6: Success after binutils/gcc/linux/ [...] discards 50ddb1fc218d 151: onsuccess: #567: 6: Success after binutils/gcc/linux/ [...] discards b209e349b617 150: onsuccess: #566: 6: Success after binutils/gcc/linux/ [...] discards ce14885a1a7f 149: onsuccess: #565: 6: Success after binutils/gcc/linux/ [...] discards ff27c5f8c352 148: onsuccess: #564: 6: Success after binutils/gcc/linux/ [...] discards cf70ec1d2f01 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...] discards 3e627eaa138d 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] discards 858251f4f75a 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] discards f14299efc0e7 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] discards 3e2422c9b84e 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] discards 179940d9d2f0 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] discards aabbc6a6c394 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] discards af9f488b7ad0 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] discards b516e7e057ef 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] discards 4884f45d82f7 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] discards f01b47458780 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] discards adc94110be21 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] discards 83b588230fcb 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] new d39628dc1431 135: onsuccess: #550: 6: Success after binutils/gcc/linux/ [...] new 5aed475b8d7d 136: onsuccess: #551: 6: Success after binutils/gcc/linux/ [...] new e9cdaa402a88 137: onsuccess: #553: 6: Success after binutils/gcc/linux/ [...] new 89212e2b4158 138: onsuccess: #554: 6: Success after binutils/gcc/linux/ [...] new e1923d0a6df0 139: onsuccess: #555: 6: Success after binutils/gcc/linux/ [...] new 68e42610a530 140: onsuccess: #556: 6: Success after binutils/gcc/linux/ [...] new 337abcf4afb3 141: onsuccess: #557: 6: Success after binutils/gcc/linux/ [...] new cba239abe482 142: onsuccess: #558: 6: Success after binutils/gcc/linux/ [...] new b6253ceeb7bc 143: onsuccess: #559: 6: Success after binutils/gcc/linux/ [...] new c2c72736530a 144: onsuccess: #560: 6: Success after binutils/gcc/linux/ [...] new 4033f14a7a10 145: onsuccess: #561: 6: Success after binutils/gcc/linux/ [...] new 12c858b0c8f8 146: onsuccess: #562: 6: Success after binutils/gcc/gdb: 1 [...] new 12ce90607672 147: onsuccess: #563: 6: Success after binutils/gcc/linux/ [...] new 5a424874ee24 148: onsuccess: #564: 6: Success after binutils/gcc/linux/ [...] new ac5888ddb769 149: onsuccess: #565: 6: Success after binutils/gcc/linux/ [...] new bcd6fb0cc491 150: onsuccess: #566: 6: Success after binutils/gcc/linux/ [...] new d2f4679a2e5a 151: onsuccess: #567: 6: Success after binutils/gcc/linux/ [...] new aabaaa597aa7 152: onsuccess: #568: 6: Success after binutils/gcc/linux/ [...] new b79c98a43c24 153: onsuccess: #569: 6: Success after binutils/gcc/gdb: 4 [...] new 5d7942d86201 154: onsuccess: #570: 6: Success after binutils/gcc/linux/ [...] new 61ccf4523873 155: onsuccess: #571: 6: Success after binutils/gcc/gdb: 3 [...] new 80d282269337 156: onsuccess: #572: 6: Success after binutils/gcc/gdb: 1 [...] new 916a6522c46b 157: onsuccess: #573: 6: Success after binutils/gcc/gdb: 9 [...] new ce0547b628c3 158: onsuccess: #574: 6: Success after binutils/gcc/linux/ [...] new d6930656ffbe 159: onsuccess: #575: 6: Success after binutils/gcc/linux/ [...] new 27e543db1e36 160: onsuccess: #576: 6: Success after binutils/gcc/linux/ [...] new 5b03c890ea35 161: onsuccess: #578: 6: Success after binutils: 15 commits new 89dcc0e8e6ed 162: onsuccess: #579: 6: Success after gcc: 11 commits new f33239be5a3e 163: onsuccess: #586: 6: Success after binutils/gcc/linux/ [...] new f87326a4aa45 164: onsuccess: #587: 6: Success after binutils/gcc/glibc/ [...] new ca1ac8f0055d 165: onsuccess: #588: 6: Success after binutils/gcc/linux/ [...] new 959a661ae74b 166: onsuccess: #589: 6: Success after binutils/gcc/linux/ [...] new 8d012cb5ed20 167: onsuccess: #590: 6: Success after binutils/gcc/linux/ [...] new 7df4df6ff94c 168: onsuccess: #591: 6: Success after binutils/gcc/linux/ [...] new ab9249b87887 169: onsuccess: #593: 6: Success after binutils/gcc/linux/ [...] new 25dbbc541e5e 170: onsuccess: #594: 6: Success after binutils/gcc/linux/ [...] new d433336bfdbd 171: onsuccess: #595: 6: Success after binutils/gcc/linux/ [...] new 79360931557e 172: onsuccess: #596: 6: Success after binutils/gcc/linux/ [...] new bd2647f8c406 173: onsuccess: #597: 6: Success after binutils/gcc/linux/ [...] new d9307db74185 174: onsuccess: #598: 6: Success after binutils/gcc/linux/ [...] new 6d28bf5b69a3 175: onsuccess: #599: 6: Success after binutils/gcc/linux/ [...] new b7c101a0cdbb 176: onsuccess: #600: 6: Success after binutils/gcc/linux/ [...] new 2e6819c6bc4e 177: onsuccess: #601: 6: Success after binutils/gcc/linux/ [...] new d4ce3b517e50 178: onsuccess: #602: 6: Success after binutils/gcc/linux/ [...] new fdacab93db40 179: onsuccess: #603: 6: Success after binutils/gcc/linux/ [...] new 862caa009d0f 180: onsuccess: #604: 6: Success after binutils/gcc/linux/ [...] new d243c4f19b48 181: onsuccess: #605: 6: Success after binutils/gcc/linux/ [...] new a80589c53e1b 182: onsuccess: #606: 6: Success after binutils/gcc/linux/ [...] new a89be8bc99d3 183: onsuccess: #607: 6: Success after binutils/gcc/linux/ [...] new 303518cc410d 184: onsuccess: #608: 6: Success after binutils/gcc/linux/ [...] new 151de666daa9 185: onsuccess: #609: 6: Success after binutils/gcc/linux/ [...] new 1f806ac90b41 186: onsuccess: #610: 6: Success after binutils/gcc/linux/ [...] new dcaa47a375f9 187: onsuccess: #611: 6: Success after binutils/gcc/linux/ [...] new 719cac085ac9 188: onsuccess: #612: 6: Success after binutils/gcc/linux/ [...] new 1b2b4631507c 189: onsuccess: #613: 6: Success after binutils/gcc/linux/ [...] new 74c402ce251c 190: onsuccess: #614: 6: Success after binutils/gcc/linux/ [...] new 6f542d022f78 191: onsuccess: #615: 6: Success after binutils/gcc/linux/ [...] new 8e7b7acd6af8 192: onsuccess: #617: 6: Success after binutils/gcc/linux/ [...] new 36ae53aa26e1 193: onsuccess: #618: 6: Success after binutils/gcc/linux/ [...] new d9ff282969ea 194: onsuccess: #619: 6: Success after binutils/gcc/linux/ [...] new 11a3cd61c8fe 195: onsuccess: #620: 6: Success after binutils/gcc/linux/ [...] new 3b6664d1db33 196: onsuccess: #621: 6: Success after binutils/gcc/linux/ [...] new f089c88ad18f 197: onsuccess: #628: 6: Success after binutils/gcc/linux/ [...] new 860485b60068 198: onsuccess: #629: 6: Success after binutils/gcc/linux/ [...] new cba7e65a519c 199: onsuccess: #630: 6: Success after binutils/gcc/linux/ [...] new 6e691ba7a008 200: onsuccess: #1: 6: Success after binutils/gcc/linux/gl [...] new dc42bb428cd1 201: onsuccess: #2: 6: Success after binutils/gcc/linux/gl [...] new c386a8a7f5df 202: onsuccess: #3: 6: Success after binutils/gcc/linux/gd [...] new d836ee975fb6 203: onsuccess: #4: 6: Success after binutils/gcc/linux/gl [...] new e07b4d5bd1eb 204: onsuccess: #5: 6: Success after binutils/gcc/linux/gl [...] new 0c6dbfcc926b 205: onsuccess: #6: 6: Success after binutils/gcc/linux/gl [...] new 576c9fcfe9bb 206: onsuccess: #7: 6: Success after binutils/gcc/linux/gd [...] new d0b74682d8f7 207: onsuccess: #8: 6: Success after binutils/gcc/linux/gl [...] new 6d61dab9b12b 208: onsuccess: #9: 6: Success after binutils/gcc/linux/gl [...] new 95ebf7a5872c 209: onsuccess: #10: 6: Success after binutils/gcc/linux/g [...] new fe69acade3e0 210: onsuccess: #11: 6: Success after binutils/gcc/linux/g [...] new c447b254e85f 211: onsuccess: #12: 6: Success after binutils/gcc/linux/g [...] new 56cbba8b00cf 212: onsuccess: #17: 6: Success after binutils/gcc/linux/g [...] new 0c0f604b7c55 213: onsuccess: #18: 6: Success after binutils/gcc/linux/g [...] new 8903503d71e9 214: onsuccess: #19: 6: Success after binutils/gcc/linux/g [...] new 944841de514a 215: onsuccess: #20: 6: Success after binutils/gcc/linux/g [...] new 067cffb298ba 216: onsuccess: #21: 6: Success after binutils/gcc/linux/g [...] new a58084c16665 217: onsuccess: #22: 6: Success after binutils/gcc/linux/g [...] new d722cb864ef5 218: onsuccess: #23: 6: Success after binutils/gcc/linux/g [...] new daeaf5b9ad86 219: onsuccess: #24: 6: Success after binutils/gcc/linux/g [...] new b01645cc6378 220: onsuccess: #25: 6: Success after binutils/gcc/linux/g [...] new 14e90e1dde7c 221: onsuccess: #26: 6: Success after binutils/gcc/linux/g [...] new 2092e5f7aaad 222: onsuccess: #28: 6: Success after binutils/gcc/linux/g [...] new 9f4a5893f897 223: onsuccess: #29: 6: Success after binutils/gcc/linux/g [...] new b61cccfb3343 224: onsuccess: #30: 6: Success after binutils/gcc/linux/g [...] new 5568c93965bf 225: onsuccess: #31: 6: Success after binutils/gcc/linux/g [...] new 7804b4d32059 226: onsuccess: #32: 6: Success after binutils/gcc/linux/g [...] new 66032dac43d8 227: onsuccess: #34: 6: Success after binutils/gcc/linux/g [...] new c4ab49500160 228: onsuccess: #35: 6: Success after binutils/gcc/linux/g [...] new d27a98ea8c41 229: onsuccess: #37: 6: [TCWG CI] Success after binutils/g [...] new 5a791e620dc8 230: onsuccess: #38: 6: [TCWG CI] Success after binutils/g [...] new 05b38fffa34a 231: onsuccess: #39: 6: [TCWG CI] Success after binutils/g [...] new 2468af96e9c1 232: onsuccess: #41: 6: [TCWG CI] Success after binutils/g [...] new f85a86833f97 233: onsuccess: #42: 6: [TCWG CI] Success after binutils/g [...] new 500070baeb2e 234: onsuccess: #43: 6: [TCWG CI] Success after binutils/g [...] new 43bafee9f74b 235: onsuccess: #44: 6: [TCWG CI] Success after binutils/g [...] new 8b888f4b1589 236: onsuccess: #45: 6: [TCWG CI] Success after binutils/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 (ca1eb72926dd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 2048 -> 2240 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2540 bytes 04-build_abe-binutils/console.log.xz | Bin 49284 -> 49492 bytes 05-build_abe-gcc/console.log.xz | Bin 235284 -> 234860 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8848 -> 8724 bytes 08-build_abe-glibc/console.log.xz | Bin 232164 -> 232948 bytes 09-build_abe-gdb/console.log.xz | Bin 47432 -> 46644 bytes 10-check_regression/console.log.xz | Bin 4364 -> 4448 bytes 11-update_baseline/console.log | 40 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/changes-list-long.txt | 53 ++++++++++++++++++++--------------- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 38 ++++++++++++------------- manifest.sh | 38 ++++++++++++------------- 20 files changed, 95 insertions(+), 88 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

3 years, 1 month

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023