Tcwg-commits March 2023

tcwg-commits@lists.linaro.org

5 participants
3834 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz updated (258b7d42c06 -> d21af21b9c3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz in repository toolchain/ci/base-artifacts. from 258b7d42c06 48: onsuccess: #6: 1: [TCWG CI] No change after llvm: 378 commits new d21af21b9c3 49: onsuccess: #7: 1: [TCWG CI] No change after llvm: 219 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 1984 -> 1756 bytes 02-build_bmk_llvm/console.log.xz | Bin 99424 -> 99508 bytes 03-benchmark/benchmark-build.log | 104 +- 03-benchmark/benchmark.log | 102 +- 03-benchmark/console.log.xz | Bin 3756 -> 3824 bytes .../compare-results-vs-first-internal.csv | 140 +- .../compare-results-vs-prev-internal.csv | 158 +- 04-check_regression/console.log.xz | Bin 9628 -> 9924 bytes .../csv-results-vs-first-1/md5sum.csv | 1518 +- .../csv-results-vs-first-1/perf.csv | 1975 +- .../csv-results-vs-first-1/results.csv | 2716 +- .../csv-results-vs-first-1/size.csv | 320 +- .../csv-results-vs-prev-0/md5sum.csv | 1729 +- 04-check_regression/csv-results-vs-prev-0/perf.csv | 2112 +- .../csv-results-vs-prev-0/results.csv | 3018 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 39400 +++++++++---------- 04-check_regression/csv-results-vs-prev-0/sve.csv | 18 +- .../csv-results-vs-prev-1/md5sum.csv | 1518 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 1975 +- .../csv-results-vs-prev-1/results.csv | 2716 +- 04-check_regression/csv-results-vs-prev-1/size.csv | 320 +- 04-check_regression/results-vs-first-brief.csv | 42 +- 04-check_regression/results-vs-first-full.csv | 2033 +- 04-check_regression/results-vs-first-internal.csv | 140 +- 04-check_regression/results-vs-first.csv | 140 +- 04-check_regression/results-vs-first.log | 766 +- 04-check_regression/results-vs-prev-brief.csv | 42 +- 04-check_regression/results-vs-prev-compare.csv | 14 +- 04-check_regression/results-vs-prev-full.csv | 2167 +- 04-check_regression/results-vs-prev-internal.csv | 146 +- 04-check_regression/results-vs-prev.csv | 146 +- 04-check_regression/results-vs-prev.log | 952 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../410.bwaves/results-metadata.json | 10 +- .../416.gamess/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 10 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 10 +- .../435.gromacs/results-metadata.json | 10 +- .../436.cactusADM/results-metadata.json | 10 +- .../437.leslie3d/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../453.povray/results-metadata.json | 10 +- .../454.calculix/results-metadata.json | 10 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 10 +- .../462.libquantum/results-metadata.json | 10 +- .../464.h264ref/results-metadata.json | 10 +- .../squad-vs-first/465.tonto/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metrics.json | 4 +- .../471.omnetpp/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/llvm_rev | 2 +- mail/jira-body.txt | 12 +- mail/mail-body.txt | 12 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results_id | 2 +- 78 files changed, 33385 insertions(+), 33528 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (7f53fce5fc7 -> e9431dda650)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards 7f53fce5fc7 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] discards b3f14586b61 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] discards a4edd6790c7 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] discards d2e488ae828 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] discards 910d492149a 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 840ab0b3189 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards ca467ff95d4 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] discards b7aa6062162 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] discards 56028225ca0 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards dd7bacb3ae4 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] discards 4b117ba2a57 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 7928d25eb94 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards ecb6b6c4c3e 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] discards ed443a7ed87 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] discards ec682eb80cb 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards d05539b1f70 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 25b1654206e 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards a84796ffbcf 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] discards 50b5b7f531b 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards b5f728e1df3 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards ac6f9a75203 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] discards ae35656d6ec 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] discards 850e539afa5 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] discards 87d1870fa11 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] discards c63957b5e65 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] discards be7a9ee4e69 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] discards f0adab3bf91 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 5136dd046f2 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] discards f0bea39dd9d 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] discards e6576c55a23 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] discards 726bc2640e7 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards 71a68f14340 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] discards c1ffb5acb77 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] discards 8560553a6a1 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] discards 7e3ef7c0ca1 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 11c0528729b 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] discards 2c30232c766 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards 534027ceb72 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] discards 33a5c548227 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards 5dca8a4466c 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 767f97b6573 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] discards 55c19efce19 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] discards 48cdc635570 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 57a6e164358 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] discards 846a403089a 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] discards 261e4a3355e 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] discards db8d12a24e7 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] discards a6ff0b95df2 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] discards 8bd8250012c 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] discards 1f3aa91fb74 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] discards 7447f587d5f 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] discards 85f67e7dfa0 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 4d036b29d19 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] discards 111683d893a 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] discards 6503167677a 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] discards debeabc2b86 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] discards 5d4d83f9af0 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] discards 32b0f1162a8 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards a082916ed8a 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] discards 61e1d507654 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] discards 887ed876442 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] discards 711af6e1dd5 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] discards 1d0c5697745 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] discards f4b7c4501cc 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] discards a392e0d6fd4 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] discards 303f6dcacf2 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] discards 0474bf722db 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards 1fcc1930c95 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] discards 2d52630c14c 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] discards 9c003fc5dba 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] discards 42d459ccbbb 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] discards f7fbeb44512 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] discards 8f19a7e43f9 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 49bdaef6249 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 731728ad6cb 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] discards df90ceb64e6 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 302c5c35dcb 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards c00d723965b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] discards b57fe529b29 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 3d72a9d229d 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] discards 5ac80f05039 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits discards b3f14d84744 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] discards 5acb3b4c34b 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] discards cd680b544e0 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] discards 4e6d1afc1d6 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits discards 2d78161462d 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] discards d2989dbe626 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] discards 9a554957ff6 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] discards ce2f0a62d15 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] discards d0dc45168ac 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards 3d8cd183877 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] discards f33bcb827bd 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] discards 94392dac559 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards c9c035dd38d 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] discards c6ad2f0234e 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] discards e82f8b088f3 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] discards a33a5f0ad39 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] discards 79745ae5c7f 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] discards 9507ab5208d 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards 68eb7e46a7f 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/ [...] discards 1c8bc84397c 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/ [...] new 05d8840f17a 362: onsuccess: #2182: 1: Success after binutils/gcc/linux/ [...] new ef36d07a6db 363: onsuccess: #2183: 1: Success after binutils/gcc/linux/ [...] new ecc3cc877d3 364: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new 09e677f72bf 365: onsuccess: #2185: 1: Success after binutils/gcc/linux/ [...] new b3d2ec49f5b 366: onsuccess: #2186: 1: Success after binutils/gcc/linux/ [...] new d0328cedb13 367: onsuccess: #2187: 1: Success after binutils/gcc/gdb: 1 [...] new d6398364c51 368: onsuccess: #2188: 1: Success after binutils/gcc/linux/ [...] new 98140ab5671 369: onsuccess: #2189: 1: Success after binutils/gcc/linux/ [...] new 93b70b44c22 370: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new 83fb28ef922 371: onsuccess: #2191: 1: Success after binutils/gcc/gdb: 1 [...] new 10acfc62b6e 372: onsuccess: #2192: 1: Success after binutils/gcc/linux/ [...] new 85f9a8f3230 373: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new ee39111a431 374: onsuccess: #2194: 1: Success after binutils/gcc/linux/ [...] new e81df29cebd 375: onsuccess: #2195: 1: Success after binutils/gcc/gdb/qe [...] new f125ee0b07d 376: onsuccess: #2197: 1: Success after binutils/gcc/linux/ [...] new e1e2c4e1355 377: onsuccess: #2198: 1: Success after binutils/gcc/gdb: 3 [...] new 667acdbcb66 378: onsuccess: #2199: 1: Success after binutils/gdb: 4 commits new a6587f00c26 379: onsuccess: #2200: 1: Success after binutils/gcc/linux/ [...] new d3e053833f2 380: onsuccess: #2201: 1: Success after binutils/gcc/linux/ [...] new a028cf4c7f5 381: onsuccess: #2202: 1: Success after glibc-2.37.9000-17- [...] new a66fdd8d05b 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new da5506bf04d 383: onsuccess: #2204: 1: Success after binutils/gcc/linux/ [...] new 082f5735ef6 384: onsuccess: #2205: 1: Success after gcc: 2 commits new a538ead8d32 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc/ [...] new 0ca2ef33cbf 386: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new 1c193f7fe98 387: onsuccess: #2208: 1: Success after gcc: 2 commits new ffb76ba16e9 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc/ [...] new 28e14f091e9 389: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 933fc7c05b1 390: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 4ac79e76955 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/qe [...] new e2d4beefed6 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc/ [...] new 8ae68eb312e 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: 1 [...] new 752ec6291b1 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: 8 [...] new 4c24e359cc1 395: onsuccess: #2216: 1: Success after binutils/gcc/linux/ [...] new d898dd13527 396: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 2b9d51eb90b 397: onsuccess: #2218: 1: Success after binutils/gcc/linux/ [...] new 3a3c3f4534a 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/qe [...] new f27e6af2ff0 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/ [...] new 1f7c2962eff 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/ [...] new 9c8614b446b 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 1 [...] new 1fb82635a70 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 1 [...] new 12f1b7b5471 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/ [...] new 95711c4c3bb 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 1 [...] new df874aa9f57 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 078e39a7800 406: onsuccess: #2227: 1: Success after binutils/linux/glib [...] new 60c3980e85f 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/ [...] new 6fdd38f51d3 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 2 [...] new 8bee0d09188 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/ [...] new ff94ceb2a7c 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/ [...] new 5c1163eea19 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 97b6d57de6a 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/ [...] new 89b91a389e8 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/ [...] new 803ba204b34 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 1 [...] new 26c662efbb0 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 1 [...] new 8538d76e3c3 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/ [...] new a974b93e455 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/ [...] new bf8fb91952e 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 [...] new f51fc5e6e44 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/ [...] new 4d4da0d9262 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 314cef172df 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/ [...] new ef33819331e 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/ [...] new 3ca4499e656 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 8d8b41b03cd 424: onsuccess: #2248: 1: Success after gcc: 6 commits new dd915596258 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/ [...] new 14ff8842456 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 4ea426966d9 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/ [...] new 40480db35f2 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 55e301a880d 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/ [...] new b60980c78b9 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/ [...] new 44a48b6db16 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/ [...] new 82310f71c09 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 37d933e31b4 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qe [...] new e508ef96d04 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/ [...] new 95818ee40a4 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/ [...] new bb8b655c441 436: onsuccess: #2260: 1: Success after gcc: 7 commits new e03c3225c20 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/ [...] new 26edcace19e 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/ [...] new b1d82b2d6a5 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 1 [...] new cad1a765d0a 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/ [...] new ec081be5c85 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/ [...] new a981bce3307 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb [...] new 2b844412c3b 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 5728d1ec2ae 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 7175bf1b693 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb [...] new 7f8685096a9 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 3b8c6362f7b 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 7e372fe5bb6 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 1f705eef9ab 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gl [...] new 6610d6926d1 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gl [...] new 5499b062954 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new be11dae4edb 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 6245c75b764 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gd [...] new dd9eaec3179 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new f01a641557c 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gd [...] new 2bf7cedf0ff 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gl [...] new 268167e5eb9 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 02d169b6265 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new b04bff1c623 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gd [...] new 7c0948cb530 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gl [...] new 6145bae6d1a 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gd [...] new 1700c94f06a 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gl [...] new e9431dda650 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7f53fce5fc7) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2840 -> 2856 bytes 03-build_abe-binutils/console.log.xz | Bin 30684 -> 30844 bytes 04-build_abe-stage1/console.log.xz | Bin 89324 -> 89304 bytes 06-build_abe-linux/console.log.xz | Bin 8336 -> 8604 bytes 07-build_abe-glibc/console.log.xz | Bin 236240 -> 236472 bytes 08-build_abe-stage2/console.log.xz | Bin 225952 -> 225852 bytes 09-build_abe-gdb/console.log.xz | Bin 38172 -> 38296 bytes 10-build_abe-qemu/console.log.xz | Bin 32132 -> 32352 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3796 -> 3840 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2560 -> 2580 bytes 13-check_regression/console.log.xz | Bin 6752 -> 7248 bytes 13-check_regression/results.compare | 16 ++++---- 13-check_regression/results.compare2 | 72 ++++++++++++++++++++++++---------- 14-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 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 48 +++++++++++------------ sumfiles/g++.log.xz | Bin 2651940 -> 2650980 bytes sumfiles/g++.sum | 19 +++++++-- sumfiles/gcc.log.xz | Bin 2229600 -> 2231136 bytes sumfiles/gcc.sum | 24 ++++++++++-- sumfiles/gfortran.log.xz | Bin 894712 -> 903020 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2284 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217092 -> 217196 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2688 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 442628 -> 446116 bytes 39 files changed, 168 insertions(+), 107 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (e10f8ff1868 -> 5059b469655)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts. discards e10f8ff1868 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 52a98099d8c 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 52174616fa4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7db776d2096 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 994d58cb560 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards f9a376b341e 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 575bd77bd8e 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 35ff8571f00 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 6b262eada56 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 0982cca8d2f 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 4100b880516 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards a5d20ff98c9 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards f185faae621 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 91e61b543af 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 0160ef2eab5 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 4c3e086f16d 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards fc9ec55fd3c 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 9e7486edf59 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 5b86e20aff8 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 019277b6298 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards 5826ad2e9d5 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards 5c463acfdfb 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 1ea67267f96 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 83f6f5d4409 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 24eebbebc2c 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards fd8642737d6 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 82c9bc5d6e5 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards e0725da3d64 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards ddb7ad522cd 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards 7d67a5359ac 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 4ffbf9f1777 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 0cd69df1f39 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 126f8ac15c7 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards 547aec28713 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards fa5da74a72f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 6fbcc76badc 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards da711585b79 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 15b52ae4275 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 4f05d041770 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards c2e16d523c2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards b8c4bc60599 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards ad7680a1195 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards c1affd1e835 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 210d8210db8 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 8860f6f514a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 2c6f58d6c03 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards b5eb9462576 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 50948fec34c 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards a65f7a4fb15 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards 6391bd774c6 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards da5654e0d54 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 0129cc459a5 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 27cc924c5dd 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards e765053fcb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards f0759c04b97 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 690c018d936 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 90b41997756 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 9d823c85f45 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards 2857f233865 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards b73da87c597 149: onsuccess: #684: 1: Success after linux: 10 commits discards d4d75c87286 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 7fbb7b30d56 147: onsuccess: #681: 1: Success after gcc: 6 commits discards 1aeaac5dc9f 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 79f5215ca41 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards ae09a89492d 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 7d18a7f0867 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards d3d4456a55f 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards a79f4dc52c2 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards 1728e496188 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards d773774fecb 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards 01c3cfb30dc 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 36e92d04807 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards bf9e1902806 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 5c3be21610b 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c52b3a6c4b4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 306fd965e0c 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards e9bbea3e8ae 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 215459c3fac 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards 6a88c997040 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards aee043a0ead 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 564ecb14ff2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 4d2747d656c 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 87a4e32c8bb 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 5e442368f22 125: onsuccess: #658: 1: Success after linux: 3224 commits discards d406054d25a 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 0b856a42089 123: onsuccess: #655: 1: Success after binutils: 22 commits discards 2a6361ae108 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 534d58b2829 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 915fe4f72fd 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards f122715a048 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards c0149f08cc5 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ebed2cd09e9 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] discards 3f7da9ab580 116: onsuccess: #647: 1: Success after linux: 3 commits discards 1f8ed6e118e 115: onsuccess: #645: 1: Success after binutils: 27 commits discards f8213ca93ba 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards 1f802382b9d 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards e4b3fff9dd3 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 5196f25fb6e 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] discards f3397a3e92c 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] discards 466d8568f7f 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] discards 611291b48fa 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new f0a476d520d 108: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 8ff885aa967 109: onsuccess: #638: 1: Success after binutils/gcc/linux/g [...] new 9aa4510464f 110: onsuccess: #639: 1: Success after binutils/gcc/linux/g [...] new a4b2fa7529b 111: onsuccess: #640: 1: Success after binutils/gcc/linux/g [...] new 96990d266b4 112: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new dc04f1c5cc4 113: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 08c439fc658 114: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new b4c86e17091 115: onsuccess: #645: 1: Success after binutils: 27 commits new 7dca430a2e6 116: onsuccess: #647: 1: Success after linux: 3 commits new d4ff572e381 117: onsuccess: #648: 1: Success after binutils/gcc/linux/g [...] new 6775ae9c417 118: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 2f9e0689cbe 119: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 774d1059f2b 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new 58607a914e4 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new fd0081a4af2 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new ca1842d04ff 123: onsuccess: #655: 1: Success after binutils: 22 commits new 75e1a1ce51c 124: onsuccess: #657: 1: Success after glibc: 2 commits new bc5fdef5001 125: onsuccess: #658: 1: Success after linux: 3224 commits new 5358c79a7ac 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new 6ae0eb5cb03 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 4bae8978ed2 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 36799515a10 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 95752f9e4ad 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new d12d3efd1b1 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new d0ecebaab97 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new f72d959600d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new c7d6db7fdd4 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 6c289b4f26c 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 175cf7f8848 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 134e9c7f4fe 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new f27664af743 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 9f53c7701c2 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new e5c51f9f676 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 9b1f4c85825 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 83116881812 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new ac14422c464 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 3ba97d8bba5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new ffc7398c874 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new cd0a9df1e62 146: onsuccess: #680: 1: Success after binutils: 20 commits new 99ef5a2f839 147: onsuccess: #681: 1: Success after gcc: 6 commits new 4a11af19fd5 148: onsuccess: #683: 1: Success after glibc: 9 commits new 7c4252a4d75 149: onsuccess: #684: 1: Success after linux: 10 commits new 4ef069beed7 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new aeb91ccfc06 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 0588b64d690 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new 0e2b69a62f3 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new 4ea5e392b2c 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 72a1f315ee7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new dc5706e9c10 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new d8f92499c4e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 240222ddeff 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 33aa139441d 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 680c032451d 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 091ae60f7cf 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new ecbadcec1b1 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new 2b2eb83b4d0 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new c7c73be73a2 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new ef6c0ea4e19 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 103aa1e547e 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 4daa45c9bcf 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new dcd6707f409 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new b6586bd6c5b 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 0baaf7cffd9 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new 65775091d45 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new fc36d5c2a38 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 8db3b2163e9 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new 5f0375e748f 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 464aac3f9e1 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 41ae7da2b20 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 4a24704ca5f 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new 4949c0c0533 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 3d8595c916e 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 1ed6752cfd3 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 7f5302946cd 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new e39f6a7da3d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new 29beb7fddbb 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new e975a2d24af 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 19e43330f85 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new 75805201811 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new b178c8b3825 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new ce07fe9028c 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new a30fd7fae7e 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 8e628f317fc 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 518c12f1099 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new 27d8d923cb4 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2d62b3e4d72 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 903eebd1dae 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 9893872529e 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 2570ce5e5bf 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 90f8b7029cb 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 7365becd81b 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 46ebd4ed6ac 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 7f38deb443f 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new e281e216fce 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new e044f113530 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 0ef22e8227f 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new fb88acd9620 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 7d0aec42b78 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new c492868ed1f 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new bafe3629d39 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new a0ecedc8c54 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 5059b469655 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (e10f8ff1868) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 38660 -> 38872 bytes 04-build_abe-gcc/console.log.xz | Bin 203552 -> 203768 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8228 -> 8552 bytes 07-build_abe-glibc/console.log.xz | Bin 244156 -> 244316 bytes 08-build_abe-gdb/console.log.xz | Bin 38348 -> 38440 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3816 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2028 -> 2184 bytes 11-check_regression/console.log.xz | Bin 5880 -> 6052 bytes 11-check_regression/results.compare | 8 +- 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/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 62776 -> 62888 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 83940 -> 83976 bytes sumfiles/gas.sum | 274 +++++++++++------------ sumfiles/ld.log.xz | Bin 122244 -> 122228 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 396 insertions(+), 396 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[gcc] branch master updated (a9835599fdb -> e17936f842d)

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 a9835599fdb Daily bump. new e17936f842d New testcase 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/testsuite/g++.dg/torture/20230313.C | 109 ++++++++++++++++++++++++++++++++ 1 file changed, 109 insertions(+) create mode 100644 gcc/testsuite/g++.dg/torture/20230313.C -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-coremark/gnu_eabi-arm_eabi-master-O2 updated (a411cd99dac -> 8a87c019b1e)

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-coremark/gnu_eabi-arm_eabi-master-O2 in repository toolchain/ci/base-artifacts. from a411cd99dac 52: onsuccess: #5: 1: [TCWG CI] No change after binutils/gc [...] new 8a87c019b1e 53: onsuccess: #6: 1: [TCWG CI] No change 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 1780 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 30692 -> 31016 bytes 04-build_abe-stage1/console.log.xz | Bin 87772 -> 87304 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-newlib/console.log.xz | Bin 14484 -> 14580 bytes 07-build_abe-stage2/console.log.xz | Bin 162836 -> 162428 bytes 08-benchmark/benchmark-build.log | 106 +++--- 08-benchmark/benchmark.log | 104 +++--- 08-benchmark/console.log.xz | Bin 4036 -> 4048 bytes 09-check_regression/console.log.xz | Bin 6128 -> 5824 bytes 09-check_regression/results-vs-first.log | 86 ++--- 09-check_regression/results-vs-prev.log | 88 ++--- 10-update_baseline/console.log | 9 - dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/Coremark/results-metadata.json | 12 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- .../squad-vs-first/coremark/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 406 ++++++++++----------- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 27 +- mail/mail-body.txt | 27 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results_id | 2 +- 26 files changed, 457 insertions(+), 468 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig updated (95ad18656af -> b442560794a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-next-allnoconfig in repository toolchain/ci/base-artifacts. from 95ad18656af 52: onsuccess: #4: boot: Success after binutils/llvm/linux/ [...] new b442560794a 53: onsuccess: #5: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2856 bytes 03-build_abe-binutils/console.log.xz | Bin 31156 -> 31128 bytes 04-build_kernel_llvm/console.log.xz | Bin 66360 -> 66624 bytes 05-build_abe-qemu/console.log.xz | Bin 31588 -> 32824 bytes 06-build_linux/console.log.xz | Bin 3044 -> 3572 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4216 -> 4264 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 24 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig updated (ad5baa694b6 -> 11171da4784)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-stable-allnoconfig in repository toolchain/ci/base-artifacts. from ad5baa694b6 52: onsuccess: #4: boot: Success after binutils/llvm/qemu: [...] new 11171da4784 53: onsuccess: #5: boot: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 31224 -> 31392 bytes 04-build_kernel_llvm/console.log.xz | Bin 66252 -> 66312 bytes 05-build_abe-qemu/console.log.xz | Bin 31852 -> 33116 bytes 06-build_linux/console.log.xz | Bin 3312 -> 3336 bytes 08-check_regression/console.log.xz | Bin 3764 -> 4280 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-cpu2017speed/llvm-aarch64-master-O2_LTO updated (141cc941732 -> 1b4272ee9ed)

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-cpu2017speed/llvm-aarch64-master-O2_LTO in repository toolchain/ci/base-artifacts. from 141cc941732 5: force: #8: 1: [TCWG CI] 644.nab_s slowed down by 4% afte [...] new 1b4272ee9ed 6: force: #9: 1: [TCWG CI] 600.perlbench_s failed to build [...] 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 1872 -> 1976 bytes 02-build_bmk_llvm/console.log.xz | Bin 99404 -> 99552 bytes 03-benchmark/benchmark-build.log | 107 +- 03-benchmark/benchmark.log | 105 +- 03-benchmark/console.log.xz | Bin 3808 -> 3840 bytes .../compare-results-vs-first-internal.csv | 32 +- .../compare-results-vs-prev-internal.csv | 50 +- 04-check_regression/console.log.xz | Bin 6180 -> 6436 bytes .../csv-results-vs-first-1/perf.csv | 141 +- .../csv-results-vs-first-1/results.csv | 4504 +------------------- .../csv-results-vs-first-1/size.csv | 4364 +------------------ 04-check_regression/csv-results-vs-first-1/sve.csv | 1 - 04-check_regression/csv-results-vs-prev-0/perf.csv | 155 +- .../csv-results-vs-prev-0/results.csv | 161 +- 04-check_regression/csv-results-vs-prev-0/size.csv | 4 +- 04-check_regression/csv-results-vs-prev-1/perf.csv | 141 +- .../csv-results-vs-prev-1/results.csv | 4504 +------------------- 04-check_regression/csv-results-vs-prev-1/size.csv | 4364 +------------------ 04-check_regression/csv-results-vs-prev-1/sve.csv | 1 - 04-check_regression/exe.regression | 2 +- 04-check_regression/extra-bisect-params | 2 +- 04-check_regression/jira-body.txt | 2 +- 04-check_regression/mail-body.txt | 2 +- 04-check_regression/mail-subject.txt | 2 +- .../output-bmk-results/exe.regression.diff | 2 +- 04-check_regression/results-vs-first-brief.csv | 36 +- 04-check_regression/results-vs-first-full.csv | 143 +- 04-check_regression/results-vs-first-internal.csv | 46 +- 04-check_regression/results-vs-first.csv | 46 +- 04-check_regression/results-vs-first.log | 555 ++- 04-check_regression/results-vs-prev-brief.csv | 38 +- 04-check_regression/results-vs-prev-compare.csv | 6 +- 04-check_regression/results-vs-prev-full.csv | 153 +- 04-check_regression/results-vs-prev-internal.csv | 48 +- 04-check_regression/results-vs-prev.csv | 48 +- 04-check_regression/results-vs-prev.log | 715 ++-- 04-check_regression/results.regressions | 4 +- 04-check_regression/trigger-bisect | 4 +- .../error_code-1 => trigger-notify} | 0 dashboard/dashboard-generate.sh | 2 +- .../600.perlbench_s/results-functional.json | 4 +- .../600.perlbench_s/results-metadata.json | 10 +- .../600.perlbench_s/results-metrics.json | 2 - .../squad-vs-first/602.gcc_s/results-metadata.json | 10 +- .../603.bwaves_s/results-metadata.json | 10 +- .../squad-vs-first/605.mcf_s/results-metadata.json | 10 +- .../607.cactuBSSN_s/results-metadata.json | 10 +- .../squad-vs-first/619.lbm_s/results-metadata.json | 10 +- .../620.omnetpp_s/results-metadata.json | 10 +- .../squad-vs-first/621.wrf_s/results-metadata.json | 10 +- .../623.xalancbmk_s/results-metadata.json | 10 +- .../625.x264_s/results-metadata.json | 10 +- .../627.cam4_s/results-functional.json | 4 - .../627.cam4_s/results-metadata.json | 9 - .../squad-vs-first/627.cam4_s/results-metrics.json | 2 - .../628.pop2_s/results-functional.json | 4 - .../628.pop2_s/results-metadata.json | 9 - .../squad-vs-first/628.pop2_s/results-metrics.json | 2 - .../631.deepsjeng_s/results-metadata.json | 10 +- .../638.imagick_s/results-metadata.json | 10 +- .../641.leela_s/results-metadata.json | 10 +- .../squad-vs-first/644.nab_s/results-metadata.json | 10 +- .../648.exchange2_s/results-metadata.json | 10 +- .../649.fotonik3d_s/results-metadata.json | 10 +- .../654.roms_s/results-metadata.json | 10 +- .../squad-vs-first/657.xz_s/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 96 +- dashboard/squad-vs-first/summary-annotation.txt | 2 +- git/llvm_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 830 ++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 13 +- mail/mail-body.txt | 13 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 4 +- results_id | 2 +- 81 files changed, 2489 insertions(+), 19214 deletions(-) copy 04-check_regression/{output-bmk-results/error_code-1 => trigger-notify} (100%) delete mode 100644 dashboard/squad-vs-first/627.cam4_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/627.cam4_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/627.cam4_s/results-metrics.json delete mode 100644 dashboard/squad-vs-first/628.pop2_s/results-functional.json delete mode 100644 dashboard/squad-vs-first/628.pop2_s/results-metadata.json delete mode 100644 dashboard/squad-vs-first/628.pop2_s/results-metrics.json create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/interesting-commits] branch master updated (18f02a28 -> 08b1617a)

by tcwg-buildslave

This is an automated email from the git hooks/post-receive script. "tcwg-buildslave pushed a change to branch master in repository toolchain/ci/interesting-commits. from 18f02a28 Add entry 6b03ce374e0dc64868b4b6665056dfc3fda0e98f from https [...] new 08b1617a Add entry 6b03ce374e0dc64868b4b6665056dfc3fda0e98f from https [...] 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: .../llvm-aarch64-master-O2_LTO/build_url | 1 + .../llvm-aarch64-master-O2_LTO}/last_good | 0 .../llvm-aarch64-master-O2_LTO}/summary.txt | 2 +- .../tcwg_bmk-code_speed-cpu2017speed/status.txt | 23 ++++++++++++++++++++++ 4 files changed, 25 insertions(+), 1 deletion(-) create mode 100644 llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/tcwg_bmk-cod [...] copy llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/{tcwg_bmk-code_speed-cpu20 [...] copy llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/{tcwg_bmk-code_speed-cpu20 [...] create mode 100644 llvm/sha1/6b03ce374e0dc64868b4b6665056dfc3fda0e98f/tcwg_bmk-cod [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (d9f6e6864a0 -> 843a63965b3)

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 d9f6e6864a0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards de67044a1fc 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 34c497e064a 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 38791f22057 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards db469e122db 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 2d25e775ad2 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards fad3effe4a6 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 4300f87f953 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 22a6aae1cb7 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e05f1ee7935 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 6138398974c 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 11bdb1eedba 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 65ca1168547 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards d99fb45f684 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 40ab4749c9f 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards 7f444169df5 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards cc59c9282fc 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e05f49addb9 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards b6fb4055127 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards 1886130caee 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards ee38660ad4c 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] discards d797c12765f 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] discards c0364508599 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] discards 01118ee48ae 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] discards 80537b6fa0d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] discards b11ed300fbd 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] discards 17750f98542 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 7b4bb8ab9fd 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 2552534de75 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 89a5657294b 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] discards 86bc69bce24 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] discards d521e94ee61 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] discards f088a94bd7f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 55cfa18838e 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] discards 5ee6bcedef2 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 72ed91c2e56 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards 4e68bd01056 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] discards 05f74e351d7 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards a05fa658a78 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards 6cf40f9e0ed 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] discards e2536ccb572 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 8c318840f83 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 92c21c1ce9f 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 5be151b9d6e 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards a7885f98b30 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 0310b9d7f45 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] discards e8dfb5b0286 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] discards 4cf1b4f74e5 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] discards 411879111fb 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] discards 38ffb51e0a6 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] discards 84c956eb672 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 989eb7ec4e9 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards 3a013a94170 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] discards 8d5d3bd1b58 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] discards 72e7251733e 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] discards ea9b950f730 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] discards c0aa3fbc62a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] discards c3c72236b4c 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] discards 6b1fb13c16a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] discards b5be86edf4d 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] discards b08c10e45fd 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] discards 815afc3ca08 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards c2daddf74c4 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] discards bb354348b77 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] discards 8ca0e8a1f93 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] discards 737e76fa3b4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] discards e1a6751e92c 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] discards 380b46779c9 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] discards f4830d400ab 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] discards 4b689853286 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] discards 647d4c6b4f0 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] discards a678a9c0ec5 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] discards ef4faccaed7 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] discards 4b4981cdacc 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] discards 60c0d72fafe 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] discards f5c8135c2e6 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] discards 4fba228c61b 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] discards 95ae81fa8e4 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] discards 11c0a5f0101 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] discards 6afebdb904e 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] discards f4539b8dae1 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] discards 47e28ca4461 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] discards 410e7e86878 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] discards 84da46d299f 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] discards d7498dceafc 125: onsuccess: #614: 1: Success after linux: 12 commits discards d24c0f3bb0f 124: onsuccess: #612: 1: Success after binutils: 18 commits discards ee6d10d996c 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] discards 171e1a1e13e 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] discards e5aa926f78f 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] discards 3d3bf36501b 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] discards 009082bc885 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] discards f91ab5739bc 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] discards de324bc55c5 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] discards 4cb4612d15b 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] discards 0f0f700c6ed 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] discards b6418235e34 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] discards 37e8e3663b4 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] discards 5a93c33f065 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] discards 81f6f35cc9b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] discards f8d6f726fe3 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] discards 645a5af1edb 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new c6624184a6a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/g [...] new b3c39cf8686 110: onsuccess: #597: 1: Success after binutils/gcc/linux/g [...] new 4f493135207 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 [...] new aa170b58b37 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 [...] new 13120ed1900 113: onsuccess: #600: 1: Success after binutils/gcc/linux/g [...] new 6063578be88 114: onsuccess: #601: 1: Success after binutils/gcc/linux/g [...] new ef07a1f045a 115: onsuccess: #602: 1: Success after binutils/gcc/linux/g [...] new 3329c259a5c 116: onsuccess: #603: 1: Success after binutils/gcc/linux/g [...] new 599cde5d5d9 117: onsuccess: #604: 1: Success after binutils/gcc/linux/g [...] new 2cc1cd0bf90 118: onsuccess: #605: 1: Success after binutils/gcc/linux/g [...] new 105878a9a3c 119: onsuccess: #606: 1: Success after binutils/gcc/linux/g [...] new 6f239b0cfe2 120: onsuccess: #607: 1: Success after binutils/gcc/linux/g [...] new 5359229d65c 121: onsuccess: #608: 1: Success after binutils/gcc/linux/g [...] new 2ada3eb63e3 122: onsuccess: #609: 1: Success after binutils/gcc/linux/g [...] new 2e04c578b75 123: onsuccess: #610: 1: Success after binutils/gcc/linux/g [...] new fa2a7732632 124: onsuccess: #612: 1: Success after binutils: 18 commits new 102760424e8 125: onsuccess: #614: 1: Success after linux: 12 commits new 24d2f1db67c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/g [...] new 7a053d2a420 127: onsuccess: #616: 1: Success after binutils/gcc/linux/g [...] new 5b39117f529 128: onsuccess: #618: 1: Success after binutils/gcc/linux/g [...] new e130f2f60c4 129: onsuccess: #619: 1: Success after binutils/gcc/linux/g [...] new e43fa9b2f8a 130: onsuccess: #620: 1: Success after binutils/gcc/linux/g [...] new b7fc0852f41 131: onsuccess: #621: 1: Success after binutils/gcc/linux/g [...] new 317152e2184 132: onsuccess: #622: 1: Success after binutils/gcc/linux/g [...] new 4a922fa4316 133: onsuccess: #623: 1: Success after binutils/gcc/linux/g [...] new a3775f4c6c1 134: onsuccess: #624: 1: Success after binutils/gcc/linux/g [...] new 52e4e5fdf99 135: onsuccess: #625: 1: Success after binutils/gcc/linux/g [...] new 9047508a2a2 136: onsuccess: #626: 1: Success after binutils/gcc/linux/g [...] new 1b689c86179 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 [...] new 94282aa9a44 138: onsuccess: #628: 1: Success after binutils/gcc/linux/g [...] new f216d096aef 139: onsuccess: #629: 1: Success after binutils/gcc/linux/g [...] new 75478275eb6 140: onsuccess: #631: 1: Success after binutils/gcc/linux/g [...] new 68320755907 141: onsuccess: #633: 1: Success after binutils/gcc/linux/g [...] new 456e3d7171a 142: onsuccess: #634: 1: Success after binutils/gcc/linux/g [...] new bc5a6d04aca 143: onsuccess: #635: 1: Success after binutils/gcc/linux/g [...] new 8c737a73e12 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 [...] new 4d769533d69 145: onsuccess: #637: 1: Success after binutils/gcc/linux/g [...] new 1e4d6ff1248 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 [...] new c86bc00012b 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 [...] new 0265148f714 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 9388fc72536 149: onsuccess: #641: 1: Success after binutils/gcc/linux/g [...] new 528f53d74d0 150: onsuccess: #642: 1: Success after binutils/gcc/linux/g [...] new 0bbe166770a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/g [...] new 2ac340c8f05 152: onsuccess: #645: 1: Success after binutils/gcc/linux/g [...] new 3ced90d5b82 153: onsuccess: #647: 1: Success after binutils/gcc/linux/g [...] new b69763224bb 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/g [...] new 6b9cfb7aeda 155: onsuccess: #649: 1: Success after binutils/gcc/linux/g [...] new 8c5c6869ec8 156: onsuccess: #650: 1: Success after binutils/gcc/linux/g [...] new 1c1901288e6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new a1a6e55a3fd 158: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new ee41aac31b5 159: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 0d0cff6bf0f 160: onsuccess: #654: 1: Success after binutils/gcc/linux/g [...] new 1d5d4117e3e 161: onsuccess: #655: 1: Success after binutils/gcc/linux/g [...] new 8eeb2157e29 162: onsuccess: #656: 1: Success after binutils/gcc/linux/g [...] new 16efcfb5dc1 163: onsuccess: #657: 1: Success after binutils/gcc/linux/g [...] new a262026cceb 164: onsuccess: #658: 1: Success after binutils/gcc/linux/g [...] new 553ba70ad58 165: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new b4f3f7d7429 166: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new e9d8937ddd7 167: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new e4938e4cbc2 168: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new 8e91dcfe338 169: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 661b465a4f9 170: onsuccess: #664: 1: Success after binutils/gcc/linux/g [...] new 4135dc5b380 171: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 7572d623767 172: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 07d65b4c68c 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 18 [...] new 894d1509e45 174: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 982667c39ca 175: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new c615975e6db 176: onsuccess: #670: 1: Success after binutils/gcc/linux/g [...] new a9c9e8868fd 177: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new ef477daaeb5 178: onsuccess: #672: 1: Success after binutils/gcc/linux/g [...] new 590ee53cee7 179: onsuccess: #673: 1: Success after binutils/gcc/linux/g [...] new 8c877a08781 180: onsuccess: #674: 1: Success after binutils/gcc/linux/g [...] new a0a798b74b5 181: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new bfcfac28e42 182: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new 603ce77a94e 183: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new 9e4d86b28c3 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/g [...] new cec6fdd503f 185: onsuccess: #679: 1: Success after binutils/gcc/linux/g [...] new aacee198f33 186: onsuccess: #680: 1: Success after binutils/gcc/linux/g [...] new 461ef46a400 187: onsuccess: #681: 1: Success after binutils/gcc/linux/g [...] new b15780a725c 188: onsuccess: #682: 1: Success after binutils/gcc/linux/g [...] new f07877716b3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/g [...] new 236a61389b1 190: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new 47dc63488f9 191: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 3c8bfba9bf4 192: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new 47051986b26 193: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new c4f0751efc8 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ca179141a55 195: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new daf4c66b800 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new a11d465ab3c 197: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new fde376660ff 198: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new a1f4b90ed18 199: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new aafffe63629 200: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 578ee32f0eb 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 56730fd9bff 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ad30838fe0a 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new aad283b2a2a 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 53e73159606 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new bb3a48bb7f3 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 514a9a36b5f 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new c1e23aaa2e1 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 91c3c47e0f3 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 843a63965b3 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (d9f6e6864a0) \ 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 1760 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 52192 -> 52596 bytes 04-build_abe-gcc/console.log.xz | Bin 236912 -> 237232 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8280 -> 8572 bytes 07-build_abe-glibc/console.log.xz | Bin 235992 -> 235552 bytes 08-build_abe-gdb/console.log.xz | Bin 50988 -> 51316 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3756 -> 3796 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2000 -> 2160 bytes 11-check_regression/console.log.xz | Bin 7516 -> 7972 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 24 +- 11-check_regression/mail-body.txt | 91 +- 11-check_regression/results.compare | 52 +- 11-check_regression/results.compare2 | 235 +- 11-check_regression/results.regressions | 52 +- 12-update_baseline/console.log | 66 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 93 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 52 +- sumfiles/gdb.log.xz | Bin 2929564 -> 2931788 bytes sumfiles/gdb.sum | 4433 ++++++++++++++++--------------- 31 files changed, 2648 insertions(+), 2506 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits March 2023