Tcwg-commits April 2023

tcwg-commits@lists.linaro.org

5 participants
5583 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-cpu2017rate/llvm-arm-master-O2 updated (3b06ceee8c -> d5625de837)

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-cpu2017rate/llvm-arm-master-O2 in repository toolchain/ci/base-artifacts. from 3b06ceee8c 5: onsuccess: #6: 1: [TCWG CI] Success after llvm: 211 commits new d5625de837 6: force: #8: 1: [TCWG CI] https://ci.linaro.org/job/tcwg_bm [...] 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 2080 -> 1892 bytes 02-build_bmk_llvm/console.log.xz | Bin 231976 -> 231608 bytes 03-benchmark/benchmark-build.log | 117 +- 03-benchmark/benchmark.log | 115 +- 03-benchmark/console.log.xz | Bin 3932 -> 3932 bytes 04-check_regression/bmk-specific-variability.csv | 68 +- 04-check_regression/console.log.xz | Bin 9792 -> 8352 bytes 04-check_regression/mail-body.txt | 18 - 04-check_regression/mail-subject.txt | 1 - .../results_id.first | 0 dashboard/dashboard-generate.sh | 17 - dashboard/dashboard-push.sh | 7 - jenkins/dashboard-push.sh | 7 - jenkins/notify.sh | 3 + mail/changes-list-long.txt | 8 - mail/changes-list-short.txt | 1 - mail/check-regression-status.txt | 1 + mail/last_good.sh | 19 - mail/short-diag.txt | 1 - manifest.sh | 15 +- results-vs-first/compare-results-internal.csv | 105 +- results-vs-first/csv-results-0/md5sum.csv | 24 +- results-vs-first/csv-results-0/results.csv | 24 +- results-vs-first/csv-results-1/md5sum.csv | 945 +- results-vs-first/csv-results-1/perf.csv | 1412 +- results-vs-first/csv-results-1/results.csv | 130479 ++++++++++------- results-vs-first/csv-results-1/size.csv | 30225 ++++ results-vs-first/csv-results-1/sve.csv | 3 + results-vs-first/interesting-symbols.csv | 14 +- results-vs-first/results-brief.csv | 40 +- results-vs-first/results-full.csv | 1422 +- results-vs-first/results-internal.csv | 114 +- results-vs-first/results.csv | 114 +- results-vs-first/tcwg-benchmark-results.log | 1806 +- results-vs-prev/compare-results-internal.csv | 100 +- results-vs-prev/compare-results.csv | 3 +- results-vs-prev/csv-results-0/md5sum.csv | 1156 +- results-vs-prev/csv-results-0/perf.csv | 1475 +- results-vs-prev/csv-results-0/results.csv | 130489 +++++++----------- results-vs-prev/csv-results-0/size.csv | 31117 +---- results-vs-prev/csv-results-0/sve.csv | 3 - results-vs-prev/csv-results-1/md5sum.csv | 943 +- results-vs-prev/csv-results-1/perf.csv | 1412 +- results-vs-prev/csv-results-1/results.csv | 130479 ++++++++++------- results-vs-prev/csv-results-1/size.csv | 30225 ++++ results-vs-prev/csv-results-1/sve.csv | 3 + results-vs-prev/interesting-symbols.csv | 14 +- results-vs-prev/results-brief.csv | 40 +- results-vs-prev/results-full.csv | 1548 +- results-vs-prev/results-internal.csv | 114 +- results-vs-prev/results.csv | 114 +- results-vs-prev/tcwg-benchmark-results.log | 2178 +- results_id | 2 +- save-temps/500.perlbench_r.tar.xz | Bin 2543752 -> 0 bytes save-temps/505.mcf_r.tar.xz | Bin 49904 -> 0 bytes save-temps/508.namd_r.tar.xz | Bin 519344 -> 0 bytes save-temps/510.parest_r.tar.xz | Bin 12 -> 0 bytes save-temps/511.povray_r.tar.xz | Bin 1427216 -> 0 bytes save-temps/519.lbm_r.tar.xz | Bin 22744 -> 0 bytes save-temps/520.omnetpp_r.tar.xz | Bin 3796396 -> 0 bytes save-temps/525.x264_r.tar.xz | Bin 1133268 -> 0 bytes save-temps/526.blender_r.tar.xz | Bin 18234792 -> 0 bytes save-temps/531.deepsjeng_r.tar.xz | Bin 178432 -> 0 bytes save-temps/541.leela_r.tar.xz | Bin 405532 -> 0 bytes save-temps/544.nab_r.tar.xz | Bin 234804 -> 0 bytes save-temps/557.xz_r.tar.xz | Bin 291184 -> 0 bytes 66 files changed, 280040 insertions(+), 218500 deletions(-) delete mode 100644 04-check_regression/mail-body.txt delete mode 100644 04-check_regression/mail-subject.txt rename results_id.first => 04-check_regression/results_id.first (100%) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100755 jenkins/dashboard-push.sh create mode 100755 jenkins/notify.sh delete mode 100644 mail/changes-list-long.txt delete mode 100644 mail/changes-list-short.txt create mode 100644 mail/check-regression-status.txt delete mode 100644 mail/last_good.sh delete mode 100644 mail/short-diag.txt delete mode 100644 save-temps/500.perlbench_r.tar.xz delete mode 100644 save-temps/505.mcf_r.tar.xz delete mode 100644 save-temps/508.namd_r.tar.xz delete mode 100644 save-temps/510.parest_r.tar.xz delete mode 100644 save-temps/511.povray_r.tar.xz delete mode 100644 save-temps/519.lbm_r.tar.xz delete mode 100644 save-temps/520.omnetpp_r.tar.xz delete mode 100644 save-temps/525.x264_r.tar.xz delete mode 100644 save-temps/526.blender_r.tar.xz delete mode 100644 save-temps/531.deepsjeng_r.tar.xz delete mode 100644 save-temps/541.leela_r.tar.xz delete mode 100644 save-temps/544.nab_r.tar.xz delete mode 100644 save-temps/557.xz_r.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch releases/gcc-12 updated (64efeac03cb -> ec689e968a0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 64efeac03cb Fortran: fix compile-time simplification of SET_EXPONENT [P [...] new ec689e968a0 Daily bump. 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/DATESTAMP | 2 +- gcc/fortran/ChangeLog | 10 ++++++++++ gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 19 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (4b264481cd -> 20d3c521d5)

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_build/master-arm in repository toolchain/ci/base-artifacts. discards 4b264481cd 509: onsuccess: #56: 7: [TCWG CI] https://ci.linaro.org/job/ [...] discards 209dd2a521 508: onsuccess: #55: 7: [TCWG CI] https://ci.linaro.org/job/ [...] discards 89aec6b7ae 507: onsuccess: #54: 7: [TCWG CI] https://ci.linaro.org/job/ [...] discards 4ed0475e0e 506: onsuccess: #53: 7: [TCWG CI] https://ci.linaro.org/job/ [...] discards 660e3548c8 505: onsuccess: #52: 7: [TCWG CI] Success after binutils/gcc [...] discards 90d767c4e0 504: onsuccess: #51: 7: [TCWG CI] Success after binutils/gcc [...] discards ab4558de05 503: onsuccess: #50: 7: [TCWG CI] Success after binutils/gcc [...] discards 018a5698f6 502: onsuccess: #49: 7: [TCWG CI] Success after binutils/gcc [...] discards b8e0c1e573 501: onsuccess: #47: 7: [TCWG CI] Success after binutils/gcc [...] discards a540d319db 500: onsuccess: #46: 7: [TCWG CI] Success after binutils/gcc [...] discards 18b49088c6 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/gcc [...] discards 484e588b4d 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/gcc [...] discards ecff7f776d 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/gcc [...] discards af4193c3dc 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/gcc [...] discards b00ab7fd71 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/gcc [...] discards 147bf92956 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/gcc [...] discards 6e087fc100 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/gcc [...] discards bae714663a 492: onsuccess: #37: 7: Success after binutils/gcc/linux/gli [...] discards f2b1b7bd72 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gdb [...] discards 0ade5a365b 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gdb [...] discards 1b26bc6d97 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gdb [...] discards dc85a182b3 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gli [...] discards 42ab614753 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gdb [...] discards ec852eb770 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gdb [...] discards 0a93b4cd4f 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gdb [...] discards d9ae17be54 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gdb [...] discards 2f5cef372a 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gdb [...] discards cd27069c75 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gdb [...] discards a3d3fbfdbf 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gli [...] discards 7e0faa144a 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gli [...] discards 57a57b1c68 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gdb [...] discards cce2948296 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gdb [...] discards 0345d4c7c9 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gli [...] discards 0c5fe5cd58 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gdb [...] discards 93f99878a7 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gli [...] discards d8063b974f 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gli [...] discards 9089a040c1 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gli [...] discards 2467727fa9 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gdb [...] discards bdf6bb5a6e 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gdb [...] discards a073cbe3f1 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gdb [...] discards cd561ef8d2 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gli [...] discards 0b3f2a8c17 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gli [...] discards 9978c52d47 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gli [...] discards 23ae50f7bb 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gli [...] discards c8bb4e9918 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb: [...] discards 1e7cd30aad 464: onsuccess: #8: 7: Success after binutils/gcc/linux/glib [...] discards 099a0ffd04 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits discards db545204f6 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits discards d5500430c5 461: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] discards 775ef5e3a6 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits discards cfc2c3cdcf 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] discards 0407417421 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits discards 8982b7154d 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] discards 9334984f0a 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] discards be9ac3aafd 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] discards 6e6768a8ad 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] discards 2bdd84fb1e 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] discards 065ef5c9c2 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] discards acf001aca5 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] discards aeb65562c3 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] discards 0cf843c6d3 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] discards 77b78329a8 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] discards c1cfab6262 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] discards 28b824545d 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] discards 192d483f45 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] discards b86ffe7758 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] discards c0853a70c1 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards d0088d5bd3 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] discards 59a994d65e 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards f47662f8c1 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits discards b99207e025 439: onsuccess: #2176: 7: Success after linux: 11 commits discards 8988ad0d87 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards cc31c32fa1 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards 90687459e1 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] discards dad19e2ed8 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] discards 99f30e2ff9 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards c3ec10f6be 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] discards 4038d76444 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] discards 903d88d335 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] discards 7bd7ab4e57 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] discards a50b3544bb 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] discards a714dd626e 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] discards 5db30777a3 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 534f29721b 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] discards 735295eee2 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] discards 82a6b70484 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] discards 1c51362fe6 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits discards 380a0d53e8 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] discards b7ebffa328 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] discards 771961891b 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards 4583b867ac 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards 1fbf56edde 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards 273d50f8ad 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 304797446a 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards a18c5a4b61 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards 22f7ec6e2c 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards 358965de9f 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards 1849c798b1 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards 52adb5d6aa 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 3a53970da0 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 107490d4e7 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 666e2b1520 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 3d4bafd5ef 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new f120bd9856 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new 1124911366 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new 766d3912ab 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new 670cb9c9a1 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 97a45abab2 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new dff17db5a1 416: onsuccess: #2152: 7: Success after gcc: 50 commits new f89e897cba 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 8e5b47ce26 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new 7b5fa7f3d1 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new e58c3700f4 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new 7e18aab08a 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] new 9a78661b9e 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] new 14becafa2a 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits new 48d6229f43 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] new a5208dc6a5 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] new a37c8bd86c 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] new 6369189b12 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new cca4e1e84c 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] new 90ff22efa7 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] new 4f3e500fcf 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] new 2b78746df0 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] new e24106faa5 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] new f85b5afd5c 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] new 4df901f42c 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new 48312ca82b 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] new 1828a1f2db 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] new ae929a5205 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new 572e1cdd2e 438: onsuccess: #2175: 7: Success after gcc: 7 commits new b171055fb2 439: onsuccess: #2176: 7: Success after linux: 11 commits new 2b70a73ca0 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits new 22bfb2fe42 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new 559e86265b 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] new 76a094b6f2 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new cc0aee702e 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] new 5b9838fc60 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/g [...] new a1c0861d06 446: onsuccess: #2183: 7: Success after binutils/gcc/linux/g [...] new b311f1af88 447: onsuccess: #2184: 7: Success after binutils/gcc/linux/g [...] new d515ba3f8d 448: onsuccess: #2185: 7: Success after binutils/gcc/gdb/qem [...] new 85de5f7713 449: onsuccess: #2186: 7: Success after binutils/gcc/linux/g [...] new dbe025cdb3 450: onsuccess: #2188: 7: Success after binutils/gcc/linux/g [...] new e51104fb7c 451: onsuccess: #2189: 7: Success after binutils/gcc/gdb: 11 [...] new 7f425ef1e1 452: onsuccess: #2190: 7: Success after binutils/gcc/linux/g [...] new b45d065eb9 453: onsuccess: #2191: 7: Success after binutils/gcc/linux/g [...] new 4602d46512 454: onsuccess: #2192: 7: Success after binutils/linux/glibc [...] new 6eaf699361 455: onsuccess: #2193: 7: Success after binutils/gcc/gdb: 13 [...] new 6be83d1571 456: onsuccess: #1: 7: Success after binutils/gcc/linux/glib [...] new 11a029307a 457: onsuccess: #2194: 7: Success after binutils/gcc/linux/g [...] new 644a2f4678 458: onsuccess: #2: 7: Success after gcc/linux/glibc: 581 commits new 37436cb3df 459: onsuccess: #3: 7: Success after binutils/gcc/glibc/gdb/ [...] new 986f57f84f 460: onsuccess: #4: 7: Success after binutils/gcc/gdb: 5 commits new e56eeb42dd 461: onsuccess: #5: 7: Success after binutils/gcc/linux/glib [...] new fa33aee4b8 462: onsuccess: #6: 7: Success after gcc/linux: 385 commits new 2535f4d66a 463: onsuccess: #7: 7: Success after binutils/gcc/gdb: 5 commits new d6e5df1114 464: onsuccess: #8: 7: Success after binutils/gcc/linux/glib [...] new 831d8dd336 465: onsuccess: #9: 7: Success after binutils/gcc/linux/gdb: [...] new fcf1a53217 466: onsuccess: #10: 7: Success after binutils/gcc/linux/gli [...] new af84160ce8 467: onsuccess: #11: 7: Success after binutils/gcc/linux/gli [...] new f6c3c22579 468: onsuccess: #12: 7: Success after binutils/gcc/linux/gli [...] new 2da6e9c490 469: onsuccess: #13: 7: Success after binutils/gcc/linux/gli [...] new 05ff0cd312 470: onsuccess: #14: 7: Success after binutils/gcc/linux/gdb [...] new 349ec81e14 471: onsuccess: #15: 7: Success after binutils/gcc/linux/gdb [...] new 3e06749d5d 472: onsuccess: #16: 7: Success after binutils/gcc/linux/gdb [...] new 5894640d2b 473: onsuccess: #17: 7: Success after binutils/gcc/linux/gli [...] new c06c010914 474: onsuccess: #18: 7: Success after binutils/gcc/linux/gli [...] new b7961e111a 475: onsuccess: #19: 7: Success after binutils/gcc/linux/gli [...] new 48607e08f2 476: onsuccess: #20: 7: Success after binutils/gcc/linux/gdb [...] new 5071c6bbc7 477: onsuccess: #21: 7: Success after binutils/gcc/linux/gli [...] new 6b72f64d75 478: onsuccess: #22: 7: Success after binutils/gcc/linux/gdb [...] new 42fbd23ac4 479: onsuccess: #23: 7: Success after binutils/gcc/linux/gdb [...] new 9c5a178e61 480: onsuccess: #24: 7: Success after binutils/gcc/linux/gli [...] new 1f0075149d 481: onsuccess: #25: 7: Success after binutils/gcc/linux/gli [...] new 4a714272ef 482: onsuccess: #26: 7: Success after binutils/gcc/linux/gdb [...] new 9568ca1ea1 483: onsuccess: #27: 7: Success after binutils/gcc/linux/gdb [...] new 4b49b11c9e 484: onsuccess: #28: 7: Success after binutils/gcc/linux/gdb [...] new b0ccad7082 485: onsuccess: #29: 7: Success after binutils/gcc/linux/gdb [...] new ca28d55311 486: onsuccess: #30: 7: Success after binutils/gcc/linux/gdb [...] new 6d8a85a63f 487: onsuccess: #31: 7: Success after binutils/gcc/linux/gdb [...] new 8f7fe28001 488: onsuccess: #32: 7: Success after binutils/gcc/linux/gli [...] new 8db58ae945 489: onsuccess: #33: 7: Success after binutils/gcc/linux/gdb [...] new 6ea04fe8a9 490: onsuccess: #34: 7: Success after binutils/gcc/linux/gdb [...] new 38fbece5bd 491: onsuccess: #35: 7: Success after binutils/gcc/linux/gdb [...] new 3039086743 492: onsuccess: #37: 7: Success after binutils/gcc/linux/gli [...] new 4364b02f0d 493: onsuccess: #39: 7: [TCWG CI] Success after binutils/gcc [...] new 5ffbc067cb 494: onsuccess: #40: 7: [TCWG CI] Success after binutils/gcc [...] new 8b17317be3 495: onsuccess: #41: 7: [TCWG CI] Success after binutils/gcc [...] new 7300ff9157 496: onsuccess: #42: 7: [TCWG CI] Success after binutils/gcc [...] new 0fa5e7cf13 497: onsuccess: #43: 7: [TCWG CI] Success after binutils/gcc [...] new 763f000671 498: onsuccess: #44: 7: [TCWG CI] Success after binutils/gcc [...] new ae041acc3d 499: onsuccess: #45: 7: [TCWG CI] Success after binutils/gcc [...] new 31e4b3b4b6 500: onsuccess: #46: 7: [TCWG CI] Success after binutils/gcc [...] new daecb63ff4 501: onsuccess: #47: 7: [TCWG CI] Success after binutils/gcc [...] new b4a14f252b 502: onsuccess: #49: 7: [TCWG CI] Success after binutils/gcc [...] new 0c7f213a66 503: onsuccess: #50: 7: [TCWG CI] Success after binutils/gcc [...] new 53222a8a0b 504: onsuccess: #51: 7: [TCWG CI] Success after binutils/gcc [...] new 1ffecf38e0 505: onsuccess: #52: 7: [TCWG CI] Success after binutils/gcc [...] new dd17b9cc66 506: onsuccess: #53: 7: [TCWG CI] https://ci.linaro.org/job/ [...] new c30dd0ae33 507: onsuccess: #54: 7: [TCWG CI] https://ci.linaro.org/job/ [...] new 3fa8f6cde9 508: onsuccess: #55: 7: [TCWG CI] https://ci.linaro.org/job/ [...] new 262cc98419 509: onsuccess: #56: 7: [TCWG CI] https://ci.linaro.org/job/ [...] new 20d3c521d5 510: onsuccess: #57: 7: [TCWG CI] https://ci.linaro.org/job/ [...] 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 (4b264481cd) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...] 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 2088 -> 2056 bytes 02-prepare_abe/console.log.xz | Bin 2612 -> 2536 bytes 04-build_abe-binutils/console.log.xz | Bin 27080 -> 27052 bytes 05-build_abe-stage1/console.log.xz | Bin 89532 -> 88932 bytes 07-build_abe-linux/console.log.xz | Bin 8608 -> 8480 bytes 08-build_abe-glibc/console.log.xz | Bin 233480 -> 233712 bytes 09-build_abe-stage2/console.log.xz | Bin 225688 -> 225440 bytes 10-build_abe-gdb/console.log.xz | Bin 34496 -> 34356 bytes 11-build_abe-qemu/console.log.xz | Bin 30836 -> 30920 bytes 12-check_regression/console.log.xz | Bin 552 -> 548 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 34 +++++++++--------- 17 files changed, 56 insertions(+), 56 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (5b91434f7b -> 82e5cb4afd)

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-arm in repository toolchain/ci/base-artifacts. discards 5b91434f7b 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 066eab3d33 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 16f0412a06 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 6bcd1b35ef 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards bf28126c14 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards c667cacab8 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 048d97ac52 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards b24772c6af 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards ae87be290f 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 61d7cfc36b 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 037b5457b2 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards f96e9411ed 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards 36ce985dfe 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 3e8fe27916 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 5296bc0fcd 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 2dd7948ec0 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 4dfd057fc9 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards f619c230c8 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards 7d78ddeafc 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards d7e643f6c5 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 991fcf2892 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards b85b4fc8a5 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards c880d034da 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 5d2462b66e 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards da00606b6f 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards de9c43b032 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 7ccba97783 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards 432eab3365 215: onsuccess: #26: 1: Success after binutils: 10 commits discards 8037c2ac61 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] discards 9620dee8d6 213: force: #24: 1: Success after binutils: 2 commits discards 7fc2c5be82 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits discards fcad16e66e 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards 4400a7b83b 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards ccdefef1c0 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards 6bcae5b003 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards 995bffea3b 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards ed355216e3 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 76c124c68f 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 70fda19c98 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards d29d3a2a86 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] discards d03eebdd27 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards b40b6da6e2 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 9cc6dabed1 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3c976c10c7 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] discards 5c198c0a4f 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards 4fdfadcade 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards b33f8f7120 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards 7315dc35a7 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 7e5eaef61b 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] discards 6b9ee10037 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards 9e7aab4fdc 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] discards 45100fd6cb 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] discards a5cde1c66d 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 2f8e288843 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] discards ec4a564f73 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 9a9dbe6876 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] discards ead1f49f5c 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 419c853bba 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] discards a87bf5a265 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] discards 133299e0ef 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] discards d1b05ee795 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] discards 4848676c32 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] discards 9019102154 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 6d29e56d19 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 1dde72d429 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] discards f1de6dad0e 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards a07bd7b283 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards c39f8f60d0 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] discards 7838c8ce2f 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 3755ef42de 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] discards 2660f88273 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 3f48d95980 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] discards ddd2f3a476 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] discards ea234cee94 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] discards 5e0e06c109 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] discards 3d56772cc8 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 6f2b9bba32 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] discards bf33778cc6 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 5c91b4ca0e 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 9a6ca6d7a6 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] discards a85473f3f4 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards da76bd7471 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] discards 1b20468d6a 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] discards c36f598207 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] discards 05baf78a52 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] discards f08395013a 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] discards 0e117178b2 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] discards aaa89e0e5d 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] discards f92055351b 154: onsuccess: #583: 1: Success after linux: 10 commits discards d882a95dc0 153: onsuccess: #582: 1: Success after glibc: 9 commits discards 3a8fa5cc0e 152: onsuccess: #580: 1: Success after gcc: 6 commits discards ad31f1c21c 151: onsuccess: #579: 1: Success after binutils: 21 commits discards 112a3d6e1b 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] discards f2c84d1acd 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] discards 82052eda9e 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] discards 3a54fa9101 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] discards 8258f95e21 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits discards f615575c8c 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits discards 6c5649d968 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits discards 6209fcea41 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] discards 0bd71d8e02 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new a0210c548d 142: onsuccess: #569: 1: Success after binutils/gcc/gdb: 46 commits new b3c14cbe8b 143: onsuccess: #570: 1: Success after binutils/gcc/linux/gd [...] new 35ca02f27c 144: onsuccess: #571: 1: Success after binutils/gcc/gdb: 28 commits new a35e9115d4 145: onsuccess: #572: 1: Success after binutils/gcc/gdb: 27 commits new 8035946959 146: onsuccess: #573: 1: Success after binutils/gcc/gdb: 11 commits new fb5030b43e 147: onsuccess: #574: 1: Success after binutils/gcc/linux/gl [...] new 00eb590df9 148: onsuccess: #575: 1: Success after binutils/gcc/linux/gd [...] new 90f9f62064 149: onsuccess: #576: 1: Success after binutils/gcc/linux/gd [...] new 0e466b8350 150: onsuccess: #577: 1: Success after binutils/gcc/linux/gd [...] new f0541a54a8 151: onsuccess: #579: 1: Success after binutils: 21 commits new 70e094bba1 152: onsuccess: #580: 1: Success after gcc: 6 commits new 70d4add427 153: onsuccess: #582: 1: Success after glibc: 9 commits new 9d6afa7e50 154: onsuccess: #583: 1: Success after linux: 10 commits new 94683d4bb3 155: onsuccess: #584: 1: Success after binutils/gcc/glibc/gd [...] new 0d2496d01b 156: onsuccess: #585: 1: Success after binutils/gcc/linux/gl [...] new 00f62df265 157: onsuccess: #586: 1: Success after binutils/gcc/linux/gl [...] new 3fa7d860ce 158: onsuccess: #587: 1: Success after binutils/gcc/linux/gl [...] new fddb970158 159: onsuccess: #588: 1: Success after binutils/gcc/linux/gd [...] new d9b1542b89 160: onsuccess: #589: 1: Success after binutils/gcc/linux/gd [...] new c303cf64cd 161: onsuccess: #590: 1: Success after binutils/gcc/linux/gl [...] new 697202a16a 162: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new e6d9920d73 163: onsuccess: #592: 1: Success after binutils/gcc/linux/gl [...] new 96d2132504 164: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new be60b70530 165: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 44df1c7d7b 166: onsuccess: #595: 1: Success after binutils/gcc/linux/gl [...] new bc1bff2e77 167: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 78ac2b4812 168: onsuccess: #597: 1: Success after binutils/gcc/linux/gd [...] new c65f82292d 169: onsuccess: #598: 1: Success after binutils/gcc/linux/gd [...] new a68c36b650 170: onsuccess: #599: 1: Success after binutils/gcc/linux/gl [...] new 1ca1f619ea 171: onsuccess: #600: 1: Success after binutils/gcc/linux/gl [...] new a4e872998a 172: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 61e8397f56 173: onsuccess: #602: 1: Success after binutils/gcc/linux/gl [...] new 8bfbbc6e58 174: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new da6047524f 175: onsuccess: #604: 1: Success after binutils/gcc/glibc/gd [...] new 71b8d686b4 176: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new a7d9085c2c 177: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new a4de8b8ca9 178: onsuccess: #607: 1: Success after binutils/gcc/linux/gl [...] new bdd18100cd 179: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 9e3a9abdb8 180: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 874d506e49 181: onsuccess: #610: 1: Success after binutils/gcc/linux/gl [...] new ae05ca0e3e 182: onsuccess: #611: 1: Success after binutils/gcc/linux/gl [...] new ccf4dfbb94 183: onsuccess: #612: 1: Success after binutils/gcc/glibc/gd [...] new ccd1485c95 184: onsuccess: #614: 1: Success after binutils/gcc/linux/gl [...] new 4c51adfcd3 185: onsuccess: #615: 1: Success after binutils/gcc/linux/gd [...] new 1a5e9f41ad 186: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 8256880019 187: onsuccess: #617: 1: Success after binutils/gcc/linux/gl [...] new df73088f55 188: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 82fde81bc2 189: onsuccess: #619: 1: Success after binutils/gcc/linux/gl [...] new 654e5abbae 190: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 7d4510b20b 191: onsuccess: #626: 1: Success after binutils/gcc/linux/gl [...] new 0386ea237a 192: onsuccess: #627: 1: Success after binutils/gcc/linux/gl [...] new 7e2954f799 193: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new 0302295643 194: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb: [...] new 607ac5e5fa 195: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new e0f326bb0c 196: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 5378f123d2 197: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 68246e81df 198: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new cc621bd3cf 199: onsuccess: #7: 1: Success after binutils/gcc/linux/glib [...] new 3561c3949a 200: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new d7e9239a2a 201: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new ebb3e73b1a 202: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 1688e250d0 203: onsuccess: #11: 1: Success after binutils/gcc/linux/gdb [...] new afdd0d1d06 204: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new a1193d9b5b 205: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 4b080c673f 206: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 17d940ba98 207: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new 69c98ed286 208: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new e552e253da 209: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new f2ecc8ea53 210: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 18c1dc4f8d 211: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new 5744b45fca 212: onsuccess: #23: 1: Success after gcc/linux/gdb: 40 commits new 8e7a6372c0 213: force: #24: 1: Success after binutils: 2 commits new a48e0c7ca8 214: force: #25: 1: Failure after gdb-13-branchpoint-1445-g2 [...] new 5fa48545b2 215: onsuccess: #26: 1: Success after binutils: 10 commits new 6a9d428314 216: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 2c126c3743 217: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new 9b2930acff 218: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new d5f05eb858 219: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new d944736cd3 220: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 130080b5ff 221: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 51350e4574 222: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 82d19be59e 223: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new ca14037e01 224: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 23132dc147 225: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 1433fa18a7 226: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 52b6abf3b9 227: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new 121f2471e9 228: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new 7f373a8a95 229: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 43decccef9 230: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new 0db3e58492 231: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 496eae0edd 232: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new 1a4561b97f 233: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 43e8c0ba1e 234: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new b2e855f87e 235: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new 2876191fe8 236: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new 39e5b717dc 237: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 040240ad3d 238: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new eeb2bd0c8f 239: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 55591dfb99 240: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new e81b6a8692 241: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new cce5d46bb8 242: force: #59: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new 82e5cb4afd 243: force: #65: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] 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 (5b91434f7b) \ 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 2224 -> 2176 bytes 02-prepare_abe/console.log.xz | Bin 2496 -> 2504 bytes 03-build_abe-binutils/console.log.xz | Bin 48656 -> 49896 bytes 04-build_abe-gcc/console.log.xz | Bin 235724 -> 236504 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8972 -> 8904 bytes 07-build_abe-glibc/console.log.xz | Bin 233072 -> 235272 bytes 08-build_abe-gdb/console.log.xz | Bin 46476 -> 46728 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3808 -> 3836 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2300 -> 3024 bytes 11-check_regression/console.log.xz | Bin 1628 -> 1604 bytes 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.regressions | 8 +++--- 11-check_regression/trigger-bisect | 2 +- 12-update_baseline/console.log | 44 ++++++++++++++--------------- git/binutils_rev | 2 +- jenkins/notify.sh | 2 +- mail/results.compare | 8 +++--- mail/results.regressions | 8 +++--- manifest.sh | 16 +++++------ results | 8 +++--- sumfiles/binutils.log.xz | Bin 62188 -> 62476 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 100644 -> 100592 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 132284 -> 132300 bytes sumfiles/ld.sum | 2 +- 27 files changed, 57 insertions(+), 57 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/interesting-commits] branch master updated (faa7174e -> 96940b9b)

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 faa7174e Add entry 040e64b09d4422c7d3c51bee098043782112b924 from https [...] new 96940b9b Add entry b8d1a3a8ef9aff015ae963522287f7785bc552ec 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: .../tcwg_gnu_native_check_binutils/master-arm/build_url | 2 +- .../master-arm}/last_good | 0 .../master-arm}/summary.txt | 4 ++-- .../status.txt | 10 +++++----- 4 files changed, 8 insertions(+), 8 deletions(-) copy binutils/sha1/{2d5783fad77c2cb9cdcb396d65fe0a60e3d8938b => b8d1a3a8ef9aff015a [...] copy binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/{tcwg_gnu_woa_check_bi [...] copy binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/{tcwg_gnu_woa_check_bi [...] copy binutils/sha1/b8d1a3a8ef9aff015ae963522287f7785bc552ec/{tcwg_gnu_woa_check_bi [...] -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allyesconfig updated (0b53123986 -> 821e1a1d32)

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-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 0b53123986 77: onsuccess: #12: all: [TCWG CI] https://ci.linaro.org/job [...] new 821e1a1d32 78: onsuccess: #13: all: [TCWG CI] https://ci.linaro.org/job [...] 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 2028 -> 2016 bytes 02-prepare_abe/console.log.xz | Bin 2540 -> 2496 bytes 03-build_abe-binutils/console.log.xz | Bin 27552 -> 27300 bytes 04-build_kernel_llvm/console.log.xz | Bin 66304 -> 65644 bytes 05-build_abe-qemu/console.log.xz | Bin 31900 -> 31236 bytes 06-build_linux/console.log.xz | Bin 3112 -> 3604 bytes 08-check_regression/console.log.xz | Bin 1220 -> 524 bytes dashboard/dashboard-generate.sh | 17 ------------- dashboard/dashboard-push.sh | 7 ------ dashboard/squad-vs-first/results-functional.json | 1 - git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- jenkins/dashboard-push.sh | 7 ------ jenkins/notify.sh | 2 +- manifest.sh | 30 +++++++++++------------ 17 files changed, 19 insertions(+), 53 deletions(-) delete mode 100755 dashboard/dashboard-generate.sh delete mode 100755 dashboard/dashboard-push.sh delete mode 100644 dashboard/squad-vs-first/results-functional.json delete mode 100755 jenkins/dashboard-push.sh -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch releases/gcc-11 updated (8378858a6c2 -> ed643a18359)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 8378858a6c2 Daily bump. new ed643a18359 Daily bump. 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/DATESTAMP | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch releases/gcc-10 updated (c2a0042db4f -> 22055748e5f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from c2a0042db4f Daily bump. new 22055748e5f Daily bump. 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/DATESTAMP | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[gcc] branch master updated (2e2b6ec156e -> 55085c7e3c9)

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 2e2b6ec156e Fix fallout of previous change on x86/Linux new 55085c7e3c9 Daily bump. 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/ChangeLog | 22 ++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/ada/ChangeLog | 8 ++++++++ gcc/cp/ChangeLog | 6 ++++++ gcc/testsuite/ChangeLog | 17 +++++++++++++++++ 5 files changed, 54 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

[binutils-gdb] branch master updated (672008e6dca -> b01ee1bf90f)

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 672008e6dca Automatic date update in version.in new b01ee1bf90f Automatic date update in version.in 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/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits April 2023