Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[gcc] branch master updated (d0b961b802d -> 7735b117bcd)

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 d0b961b802d tree-optimization/109304 - properly handle instrumented aliases new 7735b117bcd config: -pthread shouldn't link with -lpthread on Solaris The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/sol2.h | 1 - 1 file changed, 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/llvm-aarch64-master-Oz_LTO updated (4268868ee051 -> a65f2ba40ddc)

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_LTO in repository toolchain/ci/base-artifacts. from 4268868ee051 63: onsuccess: #18: 1: [TCWG CI] Success after llvm: 179 commits new a65f2ba40ddc 64: onsuccess: #19: 1: [TCWG CI] Success after llvm: 207 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 2144 -> 1888 bytes 02-build_bmk_llvm/console.log.xz | Bin 99816 -> 100536 bytes 03-benchmark/benchmark-build.log | 95 +- 03-benchmark/benchmark.log | 93 +- 03-benchmark/console.log.xz | Bin 3772 -> 3832 bytes .../compare-results-vs-first-internal.csv | 42 +- .../compare-results-vs-prev-internal.csv | 44 +- 04-check_regression/console.log.xz | Bin 6736 -> 6972 bytes .../csv-results-vs-first-1/perf.csv | 86 +- .../csv-results-vs-first-1/results.csv | 4490 ++++++++------- .../csv-results-vs-first-1/size.csv | 4412 +++++++-------- 04-check_regression/csv-results-vs-prev-0/perf.csv | 83 +- .../csv-results-vs-prev-0/results.csv | 5982 ++++++++++---------- 04-check_regression/csv-results-vs-prev-0/size.csv | 5905 +++++++++---------- 04-check_regression/csv-results-vs-prev-1/perf.csv | 86 +- .../csv-results-vs-prev-1/results.csv | 4490 ++++++++------- 04-check_regression/csv-results-vs-prev-1/size.csv | 4412 +++++++-------- 04-check_regression/results-vs-first-brief.csv | 43 +- 04-check_regression/results-vs-first-full.csv | 90 +- 04-check_regression/results-vs-first-internal.csv | 45 +- 04-check_regression/results-vs-first.csv | 45 +- 04-check_regression/results-vs-first.log | 1046 ++-- 04-check_regression/results-vs-prev-brief.csv | 45 +- 04-check_regression/results-vs-prev-compare.csv | 3 + 04-check_regression/results-vs-prev-full.csv | 94 +- 04-check_regression/results-vs-prev-internal.csv | 47 +- 04-check_regression/results-vs-prev.csv | 47 +- 04-check_regression/results-vs-prev.log | 1044 ++-- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 8 +- .../squad-vs-first/401.bzip2/results-metadata.json | 8 +- .../squad-vs-first/403.gcc/results-metadata.json | 8 +- .../410.bwaves/results-metadata.json | 8 +- .../416.gamess/results-metadata.json | 8 +- .../squad-vs-first/429.mcf/results-metadata.json | 8 +- .../squad-vs-first/433.milc/results-metadata.json | 8 +- .../434.zeusmp/results-metadata.json | 8 +- .../435.gromacs/results-metadata.json | 8 +- .../436.cactusADM/results-metadata.json | 8 +- .../437.leslie3d/results-metadata.json | 8 +- .../squad-vs-first/444.namd/results-metadata.json | 8 +- .../squad-vs-first/445.gobmk/results-metadata.json | 8 +- .../447.dealII/results-metadata.json | 8 +- .../450.soplex/results-metadata.json | 8 +- .../453.povray/results-metadata.json | 8 +- .../454.calculix/results-metadata.json | 8 +- .../squad-vs-first/456.hmmer/results-metadata.json | 8 +- .../squad-vs-first/458.sjeng/results-metadata.json | 8 +- .../459.GemsFDTD/results-metadata.json | 8 +- .../462.libquantum/results-metadata.json | 8 +- .../464.h264ref/results-metadata.json | 8 +- .../squad-vs-first/465.tonto/results-metadata.json | 8 +- .../squad-vs-first/470.lbm/results-metadata.json | 8 +- .../471.omnetpp/results-metadata.json | 8 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 8 +- .../squad-vs-first/481.wrf/results-metadata.json | 8 +- .../482.sphinx3/results-metadata.json | 8 +- .../483.xalancbmk/results-metadata.json | 8 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 8 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 227 +- 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 +- 68 files changed, 16662 insertions(+), 16626 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_binutils/master-aarch64 updated (2f42ad3965bd -> ee96ce70cabe)

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-aarch64 in repository toolchain/ci/base-artifacts. from 2f42ad3965bd 6: onsuccess: #10: 1: [TCWG CI] Success after binutils/gcc [...] new ee96ce70cabe 7: onsuccess: #11: 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 2100 -> 2072 bytes 02-prepare_abe/console.log.xz | Bin 2584 -> 2532 bytes 03-build_abe-binutils/console.log.xz | Bin 27260 -> 27764 bytes 04-build_abe-stage1/console.log.xz | Bin 71012 -> 71312 bytes 06-build_abe-linux/console.log.xz | Bin 8236 -> 8720 bytes 07-build_abe-glibc/console.log.xz | Bin 241572 -> 241900 bytes 08-build_abe-stage2/console.log.xz | Bin 201736 -> 201940 bytes 09-build_abe-gdb/console.log.xz | Bin 34604 -> 35112 bytes 10-build_abe-qemu/console.log.xz | Bin 32548 -> 32416 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3836 bytes 12-build_abe-check_binutils/console.log.xz | Bin 2088 -> 2780 bytes 13-check_regression/console.log.xz | Bin 5264 -> 5316 bytes 13-check_regression/results.compare | 4 +- 13-check_regression/results.compare2 | 4 +- 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 | 59 ++++++++++++++--------------- mail/last_good.sh | 42 ++++++++++---------- manifest.sh | 44 ++++++++++----------- sumfiles/binutils.log.xz | Bin 62340 -> 61956 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150732 -> 150828 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 107608 -> 107644 bytes sumfiles/ld.sum | 4 +- 29 files changed, 87 insertions(+), 88 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (5faa8766c041 -> cc35ab57a213)

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 5faa8766c041 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 2c3c478dc6b5 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 2274e7909982 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards b7d5ac7bb717 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards eda59dafd103 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 99047e1b5d43 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 1350b8c7d8d0 476: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] discards 50afbb90f111 475: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 5996b6ab1e75 474: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards d9c08946aa29 473: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards f3d849f341a2 472: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards 715d302b2419 471: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 3cca4515a866 470: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards aef5caff1457 469: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 90f7348611af 468: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] discards e8c8e0362b24 467: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] discards 8f2f89b972c9 466: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards 478e66ac4029 465: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] discards 8fed4434fc5a 464: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] discards 058a438273a5 463: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] discards ede85e15d7ea 462: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] discards b8192e8e7d16 461: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] discards c45e4a955e45 460: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] discards c0e34facb2d8 459: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 01c50914c1aa 458: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 569bc8114fb7 457: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 755fdc8fd1c9 456: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards 606109ca357e 455: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards f0bcfad58b0b 454: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 3ffbc9f46ff0 453: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards 832e37775d81 452: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards 5fcd9501d2b8 451: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards a07e26863aaa 450: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 10f799293320 449: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 542fad9f3d11 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 6d89edea5190 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 544266aed89d 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 2233c6056edc 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] discards 9d6defdabed1 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards b28cdfd68e07 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] discards d08c9eca6983 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gd [...] discards b268dfbfdb3f 441: onsuccess: #2266: 1: Success after binutils/gcc/linux [...] discards ca11e6d96f9d 440: onsuccess: #2265: 1: Success after binutils/gcc/linux [...] discards 4fd0a2f1f4d9 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: [...] discards a91a9e5b3391 438: onsuccess: #2263: 1: Success after binutils/gcc/linux [...] discards b288bb2878ad 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc [...] discards 3063bf41314c 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards 0d5e9bf2df34 435: onsuccess: #2259: 1: Success after binutils/gcc/linux [...] discards 5a751034edf0 434: onsuccess: #2258: 1: Success after binutils/gcc/linux [...] discards c7dbe8b4cd01 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/q [...] discards 5a899e3d90ad 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards a1f153dbc240 431: onsuccess: #2255: 1: Success after binutils/gcc/linux [...] discards fa19823b51db 430: onsuccess: #2254: 1: Success after binutils/gcc/linux [...] discards 0d2459ff68b1 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc [...] discards 2f2956d82807 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 42a44f753545 427: onsuccess: #2251: 1: Success after binutils/gcc/linux [...] discards 1208e3e18484 426: onsuccess: #2250: 1: Success after binutils/linux/gdb [...] discards 478e9b7ca719 425: onsuccess: #2249: 1: Success after binutils/gcc/linux [...] discards 9ea933c25a8b 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards abe6438b3ec0 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards efa84e12a900 422: onsuccess: #2246: 1: Success after binutils/gcc/linux [...] discards 995e94bcc9c8 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc [...] discards 23575c09bf60 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 5deb57b5df78 419: onsuccess: #2243: 1: Success after binutils/gcc/linux [...] discards 99fb58960d66 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: [...] discards 47d725572b91 417: onsuccess: #2238: 1: Success after binutils/gcc/linux [...] discards 26a9ba6984ee 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc [...] discards 29fe16792e16 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: [...] discards d9ebba7714bc 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: [...] discards b3481552e52a 413: onsuccess: #2234: 1: Success after binutils/gcc/linux [...] discards 069b43fee469 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc [...] discards 41b00ccf9ce0 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards f94cd3b3a85b 410: onsuccess: #2231: 1: Success after binutils/gcc/linux [...] discards d7e70d27133f 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc [...] discards 144f0dab2d7d 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: [...] discards 715f6aa16281 407: onsuccess: #2228: 1: Success after binutils/gcc/linux [...] discards 73e59bfe2e00 406: onsuccess: #2227: 1: Success after binutils/linux/gli [...] discards b7e2f786aca6 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards e847e00b6332 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: [...] discards b3ea9bd82f85 403: onsuccess: #2224: 1: Success after binutils/gcc/linux [...] discards f181ae1f91b7 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: [...] discards bab1aa27842a 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: [...] discards 78323d211c67 400: onsuccess: #2221: 1: Success after binutils/gcc/linux [...] discards 94fd5c8e0b9e 399: onsuccess: #2220: 1: Success after binutils/gcc/linux [...] discards 6f249f28fcfd 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/q [...] discards d20846613baf 397: onsuccess: #2218: 1: Success after binutils/gcc/linux [...] discards 0be1cdd63f46 396: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] discards 754215d25e32 395: onsuccess: #2216: 1: Success after binutils/gcc/linux [...] discards 08406a26f943 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: [...] discards 86e90c6e6d70 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: [...] discards 451f095f3794 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc [...] discards d0ad5816f346 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/q [...] discards 0956830f2ef5 390: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] discards b8a3c472ce17 389: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] discards 55ab9c9e849d 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc [...] discards 2cfdfc39f21e 387: onsuccess: #2208: 1: Success after gcc: 2 commits discards 627131998a4f 386: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] discards 0ff27583b915 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc [...] discards bdd0fecbd43a 384: onsuccess: #2205: 1: Success after gcc: 2 commits discards 45b16deaa51e 383: onsuccess: #2204: 1: Success after binutils/gcc/linux [...] discards 66047ba7d2d7 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 996e669261eb 382: onsuccess: #2203: 1: Success after gcc/qemu: 42 commits new 7d4a1b52bd0b 383: onsuccess: #2204: 1: Success after binutils/gcc/linux [...] new 78177ee2abbc 384: onsuccess: #2205: 1: Success after gcc: 2 commits new bba692fbb24b 385: onsuccess: #2206: 1: Success after binutils/gcc/glibc [...] new 31027822fb4a 386: onsuccess: #2207: 1: Success after binutils/gcc/linux [...] new de67c67462e6 387: onsuccess: #2208: 1: Success after gcc: 2 commits new 4a5f823b370f 388: onsuccess: #2209: 1: Success after binutils/gcc/glibc [...] new 3c44c202141a 389: onsuccess: #2210: 1: Success after binutils/gcc/linux [...] new 7be9e3bac7b6 390: onsuccess: #2211: 1: Success after binutils/gcc/linux [...] new 178d76655253 391: onsuccess: #2212: 1: Success after binutils/gcc/gdb/q [...] new 4f858ddd545e 392: onsuccess: #2213: 1: Success after binutils/gcc/glibc [...] new 9d5e5bcab731 393: onsuccess: #2214: 1: Success after binutils/gcc/gdb: [...] new d8d05c9dde8f 394: onsuccess: #2215: 1: Success after binutils/gcc/gdb: [...] new da94b2ab64ff 395: onsuccess: #2216: 1: Success after binutils/gcc/linux [...] new 60bda766f3f0 396: onsuccess: #2217: 1: Success after binutils/gcc/linux [...] new 53aa85d63cac 397: onsuccess: #2218: 1: Success after binutils/gcc/linux [...] new 529e921585c0 398: onsuccess: #2219: 1: Success after binutils/gcc/gdb/q [...] new 87ad21f4c2ea 399: onsuccess: #2220: 1: Success after binutils/gcc/linux [...] new efab87a1f4fd 400: onsuccess: #2221: 1: Success after binutils/gcc/linux [...] new 281723f4ad53 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: [...] new 82f3d0437dec 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: [...] new b5052896e1e1 403: onsuccess: #2224: 1: Success after binutils/gcc/linux [...] new c3a3cd07acd0 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: [...] new 14c2e6bb9a13 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new a32427cc2b2a 406: onsuccess: #2227: 1: Success after binutils/linux/gli [...] new 5fb7a5118f4d 407: onsuccess: #2228: 1: Success after binutils/gcc/linux [...] new ce6df31444d8 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: [...] new bb21d7dcdb5b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc [...] new f77b70253884 410: onsuccess: #2231: 1: Success after binutils/gcc/linux [...] new dd027a2296e8 411: onsuccess: #2232: 1: Success after gcc: 3 commits new b5d1dea0c9bf 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc [...] new 2adbbc9fd77f 413: onsuccess: #2234: 1: Success after binutils/gcc/linux [...] new 021f9ee3150b 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: [...] new 34edaa7295dd 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: [...] new b757db7a05fd 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc [...] new 428dfe42a19a 417: onsuccess: #2238: 1: Success after binutils/gcc/linux [...] new 5ccb4c3b21db 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: [...] new 44f30b4ae959 419: onsuccess: #2243: 1: Success after binutils/gcc/linux [...] new 865665c8d866 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new 6b56166407da 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc [...] new 2a77eea73019 422: onsuccess: #2246: 1: Success after binutils/gcc/linux [...] new 9379c2bb5bc1 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 4e89c993062c 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 77a5907d3be8 425: onsuccess: #2249: 1: Success after binutils/gcc/linux [...] new 21c3c2abc612 426: onsuccess: #2250: 1: Success after binutils/linux/gdb [...] new f864db1fa3b1 427: onsuccess: #2251: 1: Success after binutils/gcc/linux [...] new b41016816315 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 272697d7d4eb 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc [...] new 984938ba115c 430: onsuccess: #2254: 1: Success after binutils/gcc/linux [...] new e9ed581104e5 431: onsuccess: #2255: 1: Success after binutils/gcc/linux [...] new 726dbc58fe1f 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 22e72128f8ad 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/q [...] new 595a1c234d37 434: onsuccess: #2258: 1: Success after binutils/gcc/linux [...] new 04a418cd582c 435: onsuccess: #2259: 1: Success after binutils/gcc/linux [...] new e8adff636a0c 436: onsuccess: #2260: 1: Success after gcc: 7 commits new ddb48186604c 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc [...] new b58f5c5fbdad 438: onsuccess: #2263: 1: Success after binutils/gcc/linux [...] new 3f3a11ba4b1e 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: [...] new a2670a5d59f3 440: onsuccess: #2265: 1: Success after binutils/gcc/linux [...] new 7458d30fe80c 441: onsuccess: #2266: 1: Success after binutils/gcc/linux [...] new 7473e0f916e6 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gd [...] new e17111bae55a 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu [...] new 7c7eb0e3b2cb 444: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new 49f84cc41184 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gd [...] new 01628200fc78 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new caf7c56a261f 447: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new ce8c5b0edae7 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new ae7b552d1547 449: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new 36b253bc916f 450: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 75748fb1443f 451: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 9bc95bcf6910 452: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new ce749d17c7ae 453: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new c098c2afa903 454: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new e049ed032393 455: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new 8fdab3725ded 456: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new e79e936f9d06 457: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new e62bab794e2d 458: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 1ae23d417077 459: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new 7aa975ca2503 460: onsuccess: #21: 1: Success after binutils/gcc/linux/g [...] new 0bd78d58e398 461: onsuccess: #22: 1: Success after binutils/gcc/linux/g [...] new 15ce764cfd3b 462: onsuccess: #23: 1: Success after binutils/gcc/linux/g [...] new b325f277168c 463: onsuccess: #24: 1: Success after binutils/gcc/linux/g [...] new 514a869eb3ab 464: onsuccess: #25: 1: Success after binutils/gcc/linux/g [...] new 3d70f605853a 465: onsuccess: #26: 1: Success after binutils/gcc/linux/g [...] new ecbd93b8444c 466: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 4875748b635f 467: onsuccess: #28: 1: Success after binutils/gcc/linux/g [...] new 02f3263b5025 468: onsuccess: #29: 1: Success after binutils/gcc/linux/g [...] new f2c3cb68c228 469: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 69746c1c023a 470: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 47ded3011ab5 471: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 9eef4ac70244 472: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 9b0bae7b4182 473: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 7342e308e872 474: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new 4165a2fd97b9 475: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 7e20ce63ab83 476: onsuccess: #37: 1: Success after binutils/gcc/linux/g [...] new ea56e2071959 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new d0732fd9d795 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new d986098c48ec 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new 59173e994e38 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 64832fa14efc 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new 741e20236830 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new cc35ab57a213 483: onsuccess: #45: 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 (5faa8766c041) \ 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 2080 -> 2096 bytes 02-prepare_abe/console.log.xz | Bin 2524 -> 2500 bytes 03-build_abe-binutils/console.log.xz | Bin 26636 -> 28328 bytes 04-build_abe-stage1/console.log.xz | Bin 88468 -> 89140 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8208 -> 8728 bytes 07-build_abe-glibc/console.log.xz | Bin 232368 -> 233908 bytes 08-build_abe-stage2/console.log.xz | Bin 223636 -> 225264 bytes 09-build_abe-gdb/console.log.xz | Bin 34132 -> 35856 bytes 10-build_abe-qemu/console.log.xz | Bin 31260 -> 31968 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3804 bytes 12-build_abe-check_gcc/console.log.xz | Bin 6440 -> 6764 bytes 13-check_regression/console.log.xz | Bin 5656 -> 6168 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 9 + 13-check_regression/results.compare | 36 +- 13-check_regression/results.compare2 | 59 +- 13-check_regression/results.regressions | 29 + 14-update_baseline/console.log | 60 +- 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 | 57 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 42 +- manifest.sh | 44 +- results | 29 + sumfiles/g++.log.sep.xz | Bin 142600 -> 139688 bytes sumfiles/g++.log.xz | Bin 2683312 -> 2687532 bytes sumfiles/g++.sum | 21 +- sumfiles/g++.sum.sep | 4576 +++++++++++++++-- sumfiles/gcc.log.sep.xz | Bin 119612 -> 103548 bytes sumfiles/gcc.log.xz | Bin 2210100 -> 2210028 bytes sumfiles/gcc.sum | 7 +- sumfiles/gcc.sum.sep | 8449 +++++++------------------------ sumfiles/gfortran.log.sep.xz | Bin 36784 -> 39120 bytes sumfiles/gfortran.log.xz | Bin 902176 -> 901644 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 4258 ++++++++-------- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 217152 -> 217480 bytes sumfiles/libgomp.sum | 10 +- sumfiles/libitm.log.xz | Bin 2688 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 13084 -> 14760 bytes sumfiles/libstdc++.log.xz | Bin 447456 -> 446472 bytes sumfiles/libstdc++.sum | 8 +- sumfiles/libstdc++.sum.sep | 512 +- 52 files changed, 8617 insertions(+), 9610 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 updated (c3479ea69927 -> 8c458f29baa1)

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 c3479ea69927 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] discards 5b2ff4abe190 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] discards 96de7517a9fc 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] discards f9f4df06261c 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] discards fc11a232d4b1 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] discards 9b10e501c6af 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] discards 051bedb094dc 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] discards 739079da9ec3 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] discards 3d0a625571a3 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] discards 5625bd16f505 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] discards c006043b0ce6 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] discards 157498951aac 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] discards 92ac6507ce77 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] discards 0dfec8bc5903 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] discards a34ca75ac229 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 01143c900a51 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] discards 3a88d06044c6 212: force: #24: 1: Success after binutils: 2 commits discards a9b70b3c0cd3 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards 476607b3d615 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] discards 762d86c5a82e 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] discards 7bf34a79f9b1 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] discards 28533e842f30 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] discards cd73ca51f2b4 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] discards 009732f7e383 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] discards 971d855cfd07 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] discards e4f2ca958626 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] discards daa6c37b4353 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] discards ba2a9a9d97d7 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] discards 549a1095c64c 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] discards 1a4913ab3910 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] discards 0af1a99f6352 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] discards 6f46f329ae4f 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] discards 6a67e5d7348d 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] discards 879f3e162567 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] discards cfdb55372c1b 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] discards 8afba0af14e0 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] discards f6417a8b0135 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] discards 663c8cbca821 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] discards c394e3bfb62b 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] discards 0600e5be600c 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] discards f4c9971cb576 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] discards aaf251232397 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] discards 1ea629ca6d29 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] discards 52eae46336a1 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] discards fad378af9df1 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] discards 547bd354453e 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] discards 28bdf678160e 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] discards b07d06e62d2f 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] discards 7faec62ead26 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] discards 24b150b2a5fe 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] discards d07fca7149a1 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] discards 335374cd94b6 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] discards 5167ff319e78 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] discards 7bea3839f387 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] discards f94e1d68dd2d 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] discards f7866ccb9e54 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] discards 7eccc0c8db24 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] discards 07d8ca2dde96 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] discards 4ae57ee91f52 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] discards 1b8337d77bb2 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] discards 6d553a239c5c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] discards 57b5143a2818 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] discards a5490fa8f20d 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] discards 280517072a81 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] discards cb74982baf15 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] discards e1490f6f2bdd 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] discards f91a0ae498d3 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] discards c4165a5df61a 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] discards 8649ef5391df 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] discards 8dd67d3436fa 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] discards 5c8cc60279c9 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] discards ec05e3fcea36 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] discards 75b181b2845e 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] discards 27a979e37bb7 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] discards c555f331c482 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] discards 8cfa0a7a3dcf 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] discards dab667874fef 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] discards 5e2fc803e7c2 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] discards a6d73c187d74 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] discards f108bda37dd8 149: onsuccess: #684: 1: Success after linux: 10 commits discards 80de2316a9ee 148: onsuccess: #683: 1: Success after glibc: 9 commits discards 52ff11b1c6f8 147: onsuccess: #681: 1: Success after gcc: 6 commits discards c7dbf5f344e7 146: onsuccess: #680: 1: Success after binutils: 20 commits discards 5a727817fb4a 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] discards 83da85c8ca87 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] discards e89b63bf92d4 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] discards 46146bd99358 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] discards 1077a84494b8 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] discards 5e777a8f04d1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] discards ec1856e1cb5e 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] discards 790ba1f66a49 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] discards 59581f825063 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] discards ed50c619c728 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] discards 1fa9517392d9 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] discards b5857c44b63b 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] discards dffc92e3742e 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] discards 689c28f217b2 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] discards cc47ff57d7cd 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] discards 2854a5b47fa3 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] discards 9d3dfab39fc7 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] discards 5cd0b3d954af 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new f13d0080c704 128: onsuccess: #661: 1: Success after binutils/gcc/linux/ [...] new 846351a1fd65 129: onsuccess: #662: 1: Success after binutils/gcc/linux/ [...] new 8f358b185dd4 130: onsuccess: #663: 1: Success after binutils/gcc/linux/ [...] new b008ada3194a 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/ [...] new 31d20fe9930d 132: onsuccess: #665: 1: Success after binutils/gcc/linux/ [...] new c88976e18105 133: onsuccess: #666: 1: Success after binutils/gcc/linux/ [...] new b86a92acf2ad 134: onsuccess: #667: 1: Success after binutils/gcc/linux/ [...] new b04f80cf0c42 135: onsuccess: #668: 1: Success after binutils/gcc/linux/ [...] new de692f72b262 136: onsuccess: #669: 1: Success after binutils/gcc/linux/ [...] new 7e54febbcb64 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 4 [...] new 5c6084d88410 138: onsuccess: #671: 1: Success after binutils/gcc/linux/ [...] new b58e52972431 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 2 [...] new 46f4fba8b435 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 2 [...] new 95bba4743fee 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 1 [...] new 702e0e596edb 142: onsuccess: #675: 1: Success after binutils/gcc/linux/ [...] new 9185e9ef25a1 143: onsuccess: #676: 1: Success after binutils/gcc/linux/ [...] new a6aef6cad6f6 144: onsuccess: #677: 1: Success after binutils/gcc/linux/ [...] new cf8cda970e8c 145: onsuccess: #678: 1: Success after binutils/gcc/linux/ [...] new 4730eab9c57f 146: onsuccess: #680: 1: Success after binutils: 20 commits new df2a9d50c8a9 147: onsuccess: #681: 1: Success after gcc: 6 commits new 3e0e92a57870 148: onsuccess: #683: 1: Success after glibc: 9 commits new 0d3cd0ee3b85 149: onsuccess: #684: 1: Success after linux: 10 commits new 4d2ddd438307 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/ [...] new c0b886386ed5 151: onsuccess: #686: 1: Success after binutils/gcc/linux/ [...] new 7847cb0f968d 152: onsuccess: #687: 1: Success after binutils/gcc/linux/ [...] new 29ad57c95e6d 153: onsuccess: #688: 1: Success after binutils/gcc/linux/ [...] new aacf1e3445b0 154: onsuccess: #689: 1: Success after binutils/gcc/linux/ [...] new fe36e96cb8af 155: onsuccess: #690: 1: Success after binutils/gcc/linux/ [...] new 05eb218d30f2 156: onsuccess: #691: 1: Success after binutils/gcc/linux/ [...] new 116bd3157a8f 157: onsuccess: #692: 1: Success after binutils/gcc/linux/ [...] new 168a97ea306e 158: onsuccess: #693: 1: Success after binutils/gcc/linux/ [...] new 77a7b23289f0 159: onsuccess: #694: 1: Success after binutils/gcc/linux/ [...] new 63e14627e8a0 160: onsuccess: #695: 1: Success after binutils/gcc/linux/ [...] new e4fc9c235adf 161: onsuccess: #696: 1: Success after binutils/gcc/linux/ [...] new 389239239fb6 162: onsuccess: #697: 1: Success after binutils/gcc/linux/ [...] new d81cf55f563b 163: onsuccess: #698: 1: Success after binutils/gcc/linux/ [...] new 48dcd4009d75 164: onsuccess: #699: 1: Success after binutils/gcc/linux/ [...] new 7e2edb5c8044 165: onsuccess: #700: 1: Success after binutils/gcc/linux/ [...] new e2d5d19b0aa6 166: onsuccess: #701: 1: Success after binutils/gcc/linux/ [...] new 2cd5f0d91919 167: onsuccess: #702: 1: Success after binutils/gcc/linux/ [...] new a3f3a9028005 168: onsuccess: #703: 1: Success after binutils/gcc/linux/ [...] new 74f9e2785237 169: onsuccess: #704: 1: Success after binutils/gcc/linux/ [...] new aa39407ef183 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/ [...] new 59a63452dc25 171: onsuccess: #706: 1: Success after binutils/gcc/linux/ [...] new 628e8f64ad10 172: onsuccess: #707: 1: Success after binutils/gcc/linux/ [...] new a4897a41ff2f 173: onsuccess: #708: 1: Success after binutils/gcc/linux/ [...] new bde7f53796e3 174: onsuccess: #709: 1: Success after binutils/gcc/linux/ [...] new f718a02b654d 175: onsuccess: #710: 1: Success after binutils/gcc/linux/ [...] new 3c045ebf5d39 176: onsuccess: #711: 1: Success after binutils/gcc/linux/ [...] new 499f6f243709 177: onsuccess: #712: 1: Success after binutils/gcc/linux/ [...] new b69474c793f2 178: onsuccess: #714: 1: Success after binutils/gcc/linux/ [...] new 159aca40adc8 179: onsuccess: #715: 1: Success after binutils/gcc/linux/ [...] new 5a11bbbc3d16 180: onsuccess: #716: 1: Success after binutils/gcc/linux/ [...] new 67f35e072af5 181: onsuccess: #717: 1: Success after binutils/gcc/linux/ [...] new 04170f39798d 182: onsuccess: #718: 1: Success after binutils/gcc/linux/ [...] new 8c57bfedb42c 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 2 [...] new bf64d1ce9bc6 184: onsuccess: #720: 1: Success after binutils/gcc/linux/ [...] new c1c0d5642f17 185: onsuccess: #721: 1: Success after binutils/gcc/linux/ [...] new 0d917a62745b 186: onsuccess: #722: 1: Success after binutils/gcc/linux/ [...] new dfd33479463e 187: onsuccess: #723: 1: Success after binutils/gcc/linux/ [...] new 5a6fcb805b3b 188: onsuccess: #724: 1: Success after binutils/gcc/linux/ [...] new ba86421a4596 189: onsuccess: #725: 1: Success after binutils/gcc/linux/ [...] new f753faca5c5c 190: onsuccess: #726: 1: Success after binutils/gcc/linux/ [...] new 17ead7b98077 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gl [...] new 845c624d1b6a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gd [...] new 98c781a0c2be 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gl [...] new 93d1b1a49317 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gd [...] new 765a43e93adc 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gl [...] new fd5cf3b01eb2 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gl [...] new 4059f7fba120 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gl [...] new 58e5a338b37a 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gl [...] new efe51bcb9dcd 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gd [...] new 4ba2dc96c398 200: onsuccess: #10: 1: Success after binutils/gcc/linux/g [...] new c645a4090aa5 201: onsuccess: #11: 1: Success after binutils/gcc/linux/g [...] new 923bd488c80f 202: onsuccess: #12: 1: Success after binutils/gcc/linux/g [...] new 09826850b641 203: onsuccess: #13: 1: Success after binutils/gcc/linux/g [...] new a48b788cd3ab 204: onsuccess: #14: 1: Success after binutils/gcc/linux/g [...] new 86ff93eab152 205: onsuccess: #15: 1: Success after binutils/gcc/linux/g [...] new 67937e41d005 206: onsuccess: #16: 1: Success after binutils/gcc/linux/g [...] new b45711124f37 207: onsuccess: #17: 1: Success after binutils/gcc/linux/g [...] new 3462e35b8a58 208: onsuccess: #18: 1: Success after binutils/gcc/linux/g [...] new 91f17edd6d49 209: onsuccess: #19: 1: Success after binutils/gcc/linux/g [...] new 296a1f94dd84 210: onsuccess: #20: 1: Success after binutils/gcc/linux/g [...] new eb2545b6cb56 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 4d7db6fd029d 212: force: #24: 1: Success after binutils: 2 commits new 9395fe56d4d3 213: force: #25: 1: Failure after gdb-13-branchpoint-1445- [...] new 3e23c69b5712 214: onsuccess: #26: 1: Success after binutils: 12 commits new 0fb55f8adc73 215: onsuccess: #27: 1: Success after binutils/gcc/linux/g [...] new 2381c30c9b54 216: onsuccess: #30: 1: Success after binutils/gcc/linux/g [...] new 1b21953ebb54 217: onsuccess: #31: 1: Success after binutils/gcc/linux/g [...] new 250b8fa5a311 218: onsuccess: #32: 1: Success after binutils/gcc/linux/g [...] new 264334cea8f3 219: onsuccess: #33: 1: Success after binutils/gcc/linux/g [...] new 1499b0c92538 220: onsuccess: #34: 1: Success after binutils/gcc/linux/g [...] new 8df151b5b5f9 221: onsuccess: #35: 1: Success after binutils/gcc/linux/g [...] new f3dfafcc7b03 222: onsuccess: #36: 1: Success after binutils/gcc/linux/g [...] new 97937c2b9569 223: onsuccess: #39: 1: [TCWG CI] Success after binutils/g [...] new 7cb21fc94d6b 224: onsuccess: #40: 1: [TCWG CI] Success after binutils/g [...] new dba4a56e4e98 225: onsuccess: #41: 1: [TCWG CI] Success after binutils/g [...] new b5ddab437cb9 226: onsuccess: #42: 1: [TCWG CI] Success after binutils/g [...] new 8d5e03471eeb 227: onsuccess: #43: 1: [TCWG CI] Success after binutils/g [...] new a45d3e98fe46 228: onsuccess: #44: 1: [TCWG CI] Success after binutils/g [...] new 8c458f29baa1 229: onsuccess: #45: 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 (c3479ea69927) \ 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 2036 -> 2024 bytes 02-prepare_abe/console.log.xz | Bin 2536 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 34864 -> 35512 bytes 04-build_abe-gcc/console.log.xz | Bin 203492 -> 203356 bytes 06-build_abe-linux/console.log.xz | Bin 8168 -> 8676 bytes 07-build_abe-glibc/console.log.xz | Bin 241320 -> 242028 bytes 08-build_abe-gdb/console.log.xz | Bin 34508 -> 35304 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3800 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2100 -> 2784 bytes 11-check_regression/console.log.xz | Bin 4952 -> 5084 bytes 11-check_regression/results.compare | 4 +- 11-check_regression/results.compare2 | 4 +- 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 | 59 ++++++++++++------------- mail/last_good.sh | 36 +++++++-------- manifest.sh | 38 ++++++++-------- sumfiles/binutils.log.xz | Bin 62980 -> 62668 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 150792 -> 150780 bytes sumfiles/gas.sum | 4 +- sumfiles/ld.log.xz | Bin 122660 -> 122616 bytes sumfiles/ld.sum | 4 +- 28 files changed, 115 insertions(+), 116 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-arm-master-O3_LTO updated (9851b33260ac -> 9d40ef14a1c1)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_vect-spec2k6/gnu-arm-master-O3_LTO in repository toolchain/ci/base-artifacts. from 9851b33260ac 11: onsuccess: #16: 1: [TCWG CI] Success after binutils/gc [...] new 9d40ef14a1c1 12: onsuccess: #17: 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 2296 -> 2320 bytes 02-prepare_abe/console.log.xz | Bin 2560 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 27300 -> 28328 bytes 04-build_abe-stage1/console.log.xz | Bin 89600 -> 90240 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8288 -> 8308 bytes 07-build_abe-glibc/console.log.xz | Bin 233412 -> 233952 bytes 08-build_abe-stage2/console.log.xz | Bin 211148 -> 210868 bytes 09-benchmark/benchmark-build.log | 99 +- 09-benchmark/benchmark.log | 97 +- 09-benchmark/console.log.xz | Bin 4064 -> 4048 bytes .../compare-results-vs-first-internal.csv | 77 +- .../compare-results-vs-prev-internal.csv | 79 +- 10-check_regression/console.log.xz | Bin 10672 -> 10228 bytes .../csv-results-vs-first-1/perf.csv | 152 +- .../csv-results-vs-first-1/results.csv | 6634 ++--- .../csv-results-vs-first-1/size.csv | 6542 ++--- 10-check_regression/csv-results-vs-prev-0/perf.csv | 158 +- .../csv-results-vs-prev-0/results.csv | 28092 ++++++++++--------- 10-check_regression/csv-results-vs-prev-0/size.csv | 28046 +++++++++--------- 10-check_regression/csv-results-vs-prev-0/sve.csv | 86 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 152 +- .../csv-results-vs-prev-1/results.csv | 6634 ++--- 10-check_regression/csv-results-vs-prev-1/size.csv | 6542 ++--- .../output-bmk-results/exe.improvement | 4 + .../output-bmk-results/exe.improvement.diff | 1 + .../output-bmk-results/exe.regression | 4 +- .../output-bmk-results/exe.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 168 +- 10-check_regression/results-vs-first-internal.csv | 81 +- 10-check_regression/results-vs-first.csv | 81 +- 10-check_regression/results-vs-first.log | 1364 +- 10-check_regression/results-vs-prev-brief.csv | 72 +- 10-check_regression/results-vs-prev-full.csv | 178 +- 10-check_regression/results-vs-prev-internal.csv | 85 +- 10-check_regression/results-vs-prev.csv | 85 +- 10-check_regression/results-vs-prev.log | 1456 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 12 +- .../squad-vs-first/401.bzip2/results-metadata.json | 12 +- .../squad-vs-first/403.gcc/results-metadata.json | 12 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../410.bwaves/results-metadata.json | 12 +- .../squad-vs-first/410.bwaves/results-metrics.json | 2 +- .../416.gamess/results-metadata.json | 12 +- .../squad-vs-first/416.gamess/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 12 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 12 +- .../squad-vs-first/434.zeusmp/results-metrics.json | 2 +- .../435.gromacs/results-metadata.json | 12 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 12 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 12 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 12 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 12 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 12 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 12 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 12 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../454.calculix/results-metadata.json | 12 +- .../454.calculix/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 12 +- .../squad-vs-first/458.sjeng/results-metadata.json | 12 +- .../459.GemsFDTD/results-metadata.json | 12 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 12 +- .../464.h264ref/results-metadata.json | 12 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/465.tonto/results-metadata.json | 12 +- .../squad-vs-first/465.tonto/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 12 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 12 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 12 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 12 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 12 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 398 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 42 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 35 +- manifest.sh | 32 +- results_id | 2 +- 100 files changed, 44530 insertions(+), 43422 deletions(-) create mode 100644 10-check_regression/output-bmk-results/exe.improvement create 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.

1 year, 7 months

[gcc] branch master updated (d634e6088f1 -> d0b961b802d)

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 d634e6088f1 rs6000: Fix vector_set_var_p9 by considering BE [PR108807] new d0b961b802d tree-optimization/109304 - properly handle instrumented aliases 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/gcc.dg/pr109304.c | 12 ++++++++++++ gcc/tree-profile.cc | 9 ++++++--- 2 files changed, 18 insertions(+), 3 deletions(-) create mode 100644 gcc/testsuite/gcc.dg/pr109304.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[binutils-gdb] branch master updated (19cacf67293 -> 02d44d76584)

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 19cacf67293 Use bfd_alloc memory for read_debugging_info storage new 02d44d76584 bfd+ld: when / whether to generate .c files 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: bfd/Makefile.am | 2 +- bfd/Makefile.in | 2 +- ld/Makefile.am | 5 +++-- ld/Makefile.in | 5 +++-- ld/deffilep.y | 2 +- ld/ldgram.y | 4 ++-- ld/ldlex.l | 4 ++-- 7 files changed, 13 insertions(+), 11 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-Os updated (02289c6cf646 -> 2e382feaf594)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_size-spec2k6/gnu-aarch64-master-Os in repository toolchain/ci/base-artifacts. from 02289c6cf646 86: onsuccess: #28: 1: [TCWG CI] Success after gcc: 18 commits new 2e382feaf594 87: onsuccess: #29: 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 2152 -> 2036 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2552 bytes 03-build_abe-binutils/console.log.xz | Bin 27332 -> 28412 bytes 04-build_abe-stage1/console.log.xz | Bin 70844 -> 71500 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8392 -> 8276 bytes 07-build_abe-glibc/console.log.xz | Bin 242160 -> 242572 bytes 08-build_abe-stage2/console.log.xz | Bin 176272 -> 176196 bytes 09-benchmark/benchmark-build.log | 111 +- 09-benchmark/benchmark.log | 109 +- 09-benchmark/console.log.xz | Bin 3940 -> 3960 bytes 10-check_regression/bmk-specific-variability.csv | 155 +- .../compare-results-vs-first-internal.csv | 217 +- .../compare-results-vs-prev-internal.csv | 230 +- 10-check_regression/console.log.xz | Bin 15540 -> 16580 bytes .../csv-results-vs-first-1/md5sum.csv | 2358 +- .../csv-results-vs-first-1/perf.csv | 2756 +- .../csv-results-vs-first-1/results.csv | 10489 +- .../csv-results-vs-first-1/size.csv | 932780 +++++++++--------- 10-check_regression/csv-results-vs-first-1/sve.csv | 28 +- .../csv-results-vs-first-1/vect.csv | 16 +- .../csv-results-vs-prev-0/md5sum.csv | 1607 +- 10-check_regression/csv-results-vs-prev-0/perf.csv | 2622 +- .../csv-results-vs-prev-0/results.csv | 6981 +- 10-check_regression/csv-results-vs-prev-0/size.csv | 3859 +- .../csv-results-vs-prev-1/md5sum.csv | 2358 +- 10-check_regression/csv-results-vs-prev-1/perf.csv | 2756 +- .../csv-results-vs-prev-1/results.csv | 10489 +- 10-check_regression/csv-results-vs-prev-1/size.csv | 932780 +++++++++--------- 10-check_regression/csv-results-vs-prev-1/sve.csv | 28 +- 10-check_regression/csv-results-vs-prev-1/vect.csv | 16 +- .../output-bmk-results/exe.improvement | 6 + .../output-bmk-results/exe.improvement.diff | 1 + .../output-bmk-results/exe.regression | 2 +- .../output-bmk-results/exe.regression.diff | 2 +- .../output-bmk-results/symbol.improvement | 6 +- .../output-bmk-results/symbol.improvement.diff | 2 +- .../output-bmk-results/symbol.regression | 12 +- .../output-bmk-results/symbol.regression.diff | 2 +- 10-check_regression/results-vs-first-brief.csv | 68 +- 10-check_regression/results-vs-first-full.csv | 2685 +- 10-check_regression/results-vs-first-internal.csv | 224 +- 10-check_regression/results-vs-first.csv | 224 +- 10-check_regression/results-vs-first.log | 1634 +- 10-check_regression/results-vs-prev-brief.csv | 68 +- 10-check_regression/results-vs-prev-compare.csv | 26 +- 10-check_regression/results-vs-prev-full.csv | 2865 +- 10-check_regression/results-vs-prev-internal.csv | 230 +- 10-check_regression/results-vs-prev.csv | 230 +- 10-check_regression/results-vs-prev.log | 1824 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 12 +- .../squad-vs-first/401.bzip2/results-metadata.json | 12 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 12 +- .../410.bwaves/results-metadata.json | 12 +- .../416.gamess/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metadata.json | 12 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 12 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../434.zeusmp/results-metadata.json | 12 +- .../435.gromacs/results-metadata.json | 12 +- .../435.gromacs/results-metrics.json | 2 +- .../436.cactusADM/results-metadata.json | 12 +- .../436.cactusADM/results-metrics.json | 2 +- .../437.leslie3d/results-metadata.json | 12 +- .../437.leslie3d/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 12 +- .../squad-vs-first/445.gobmk/results-metadata.json | 12 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 12 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 12 +- .../453.povray/results-metadata.json | 12 +- .../454.calculix/results-metadata.json | 12 +- .../squad-vs-first/456.hmmer/results-metadata.json | 12 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 12 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../459.GemsFDTD/results-metadata.json | 12 +- .../459.GemsFDTD/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 12 +- .../464.h264ref/results-metadata.json | 12 +- .../squad-vs-first/465.tonto/results-metadata.json | 12 +- .../squad-vs-first/465.tonto/results-metrics.json | 4 +- .../squad-vs-first/470.lbm/results-metadata.json | 12 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 12 +- .../squad-vs-first/473.astar/results-metadata.json | 12 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../squad-vs-first/481.wrf/results-metadata.json | 12 +- .../squad-vs-first/481.wrf/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 12 +- .../483.xalancbmk/results-metadata.json | 12 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 12 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 122 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- mail/changes-list-long.txt | 26 +- mail/changes-list-short.txt | 2 +- mail/last_good.sh | 22 +- manifest.sh | 33 +- results_id | 2 +- 106 files changed, 961984 insertions(+), 961481 deletions(-) create mode 100644 10-check_regression/output-bmk-results/exe.improvement create 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.

1 year, 7 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-defconfig updated (d88eaf04a33c -> c88fb2510129)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-stable-defconfig in repository toolchain/ci/base-artifacts. from d88eaf04a33c 60: onsuccess: #8: boot: Success after binutils/gcc/linux/ [...] new c88fb2510129 61: onsuccess: #10: boot: [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 1988 -> 2020 bytes 02-prepare_abe/console.log.xz | Bin 2508 -> 2548 bytes 03-build_abe-binutils/console.log.xz | Bin 26656 -> 28240 bytes 04-build_abe-stage1/console.log.xz | Bin 89372 -> 89320 bytes 05-build_abe-qemu/console.log.xz | Bin 30656 -> 32392 bytes 06-build_linux/console.log.xz | Bin 4564 -> 4572 bytes 07-boot_linux/console.log.xz | Bin 5652 -> 5648 bytes 08-check_regression/console.log.xz | Bin 4204 -> 4176 bytes 08-check_regression/jira-body.txt | 1 - 08-check_regression/mail-body.txt | 31 ------------------------------- 08-check_regression/mail-subject.txt | 1 - 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 | 26 ++++++++++++++++++++++++++ mail/changes-list-short.txt | 1 + mail/jira-body.txt | 1 - manifest.sh => mail/last_good.sh | 0 mail/mail-body.txt | 31 ------------------------------- mail/mail-subject.txt | 1 - mail/short-diag.txt | 1 + manifest.sh | 32 ++++++++++++++++---------------- 24 files changed, 49 insertions(+), 87 deletions(-) delete mode 100644 08-check_regression/jira-body.txt delete mode 100644 08-check_regression/mail-body.txt delete mode 100644 08-check_regression/mail-subject.txt create mode 100644 mail/changes-list-long.txt create mode 100644 mail/changes-list-short.txt delete mode 100644 mail/jira-body.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.

1 year, 7 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023