Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/llvm-aarch64-master-O3 updated (190b4770aa -> 5566a75b3a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_bmk-code_speed-spec2k6/llvm-aarch64-master-O3 in repository toolchain/ci/base-artifacts. from 190b4770aa 49: onsuccess: #25: 1: [TCWG CI] No change after binutils/gc [...] new 5566a75b3a 50: onsuccess: #26: 1: [TCWG CI] No change after llvm: 183 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 1800 -> 1844 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 31160 -> 31816 bytes 04-build_abe-stage1/console.log.xz | Bin 71148 -> 72076 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8720 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 244000 -> 246000 bytes 08-build_abe-stage2/console.log.xz | Bin 175620 -> 181212 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 63908 -> 62116 bytes 10-benchmark/benchmark-build.log | 130 +- 10-benchmark/benchmark.log | 128 +- 10-benchmark/console.log.xz | Bin 4208 -> 4280 bytes 11-check_regression/console.log.xz | Bin 10972 -> 10304 bytes .../csv-results-vs-first-0/md5sum.csv | 1432 +- .../csv-results-vs-first-0/results.csv | 22336 +- .../csv-results-vs-first-0/size.csv | 229714 +++++++-------- 11-check_regression/csv-results-vs-first-0/sve.csv | 18 +- .../csv-results-vs-first-0/vect.csv | 18948 +- .../csv-results-vs-first-1/md5sum.csv | 1652 +- .../csv-results-vs-first-1/perf.csv | 1912 +- .../csv-results-vs-first-1/results.csv | 205654 +++++++------ .../csv-results-vs-first-1/size.csv | 270704 +++++++++--------- 11-check_regression/csv-results-vs-first-1/sve.csv | 24 +- .../csv-results-vs-prev-0/md5sum.csv | 1670 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 1958 +- .../csv-results-vs-prev-0/results.csv | 204182 ++++++------- 11-check_regression/csv-results-vs-prev-0/size.csv | 269342 ++++++++--------- 11-check_regression/csv-results-vs-prev-0/sve.csv | 22 +- .../csv-results-vs-prev-1/md5sum.csv | 1652 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 1912 +- .../csv-results-vs-prev-1/results.csv | 205654 +++++++------ 11-check_regression/csv-results-vs-prev-1/size.csv | 270704 +++++++++--------- 11-check_regression/csv-results-vs-prev-1/sve.csv | 24 +- 11-check_regression/results-vs-first-brief.csv | 44 +- 11-check_regression/results-vs-first-full.csv | 1890 +- 11-check_regression/results-vs-first-internal.csv | 149 +- 11-check_regression/results-vs-first.csv | 149 +- 11-check_regression/results-vs-first.log | 816 +- 11-check_regression/results-vs-prev-brief.csv | 44 +- 11-check_regression/results-vs-prev-compare.csv | 9 +- 11-check_regression/results-vs-prev-full.csv | 2018 +- 11-check_regression/results-vs-prev-internal.csv | 151 +- 11-check_regression/results-vs-prev.csv | 151 +- 11-check_regression/results-vs-prev.log | 1042 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 10 +- .../400.perlbench/results-metrics.json | 2 +- .../squad-vs-first/401.bzip2/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metadata.json | 10 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metadata.json | 10 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 10 +- .../447.dealII/results-metadata.json | 10 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 10 +- .../squad-vs-first/450.soplex/results-metrics.json | 2 +- .../453.povray/results-metadata.json | 10 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metadata.json | 10 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 10 +- .../squad-vs-first/470.lbm/results-metadata.json | 10 +- .../471.omnetpp/results-metadata.json | 10 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 10 +- .../482.sphinx3/results-metadata.json | 10 +- .../483.xalancbmk/results-metadata.json | 10 +- .../squad-vs-first/Mean/results-metadata.json | 10 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 74 +- git/llvm_rev | 2 +- mail/jira-body.txt | 26 +- mail/mail-body.txt | 26 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 1259332 -> 401664 bytes save-temps/401.bzip2.tar.xz | Bin 92008 -> 42728 bytes save-temps/403.gcc.tar.xz | Bin 3536536 -> 1214176 bytes save-temps/410.bwaves.tar.xz | Bin 15240 -> 0 bytes save-temps/416.gamess.tar.xz | Bin 4118768 -> 0 bytes save-temps/429.mcf.tar.xz | Bin 36544 -> 22308 bytes save-temps/433.milc.tar.xz | Bin 165368 -> 58720 bytes save-temps/434.zeusmp.tar.xz | Bin 126080 -> 0 bytes save-temps/435.gromacs.tar.xz | Bin 956692 -> 0 bytes save-temps/436.cactusADM.tar.xz | Bin 709776 -> 0 bytes save-temps/437.leslie3d.tar.xz | Bin 47112 -> 0 bytes save-temps/444.namd.tar.xz | Bin 165180 -> 44912 bytes save-temps/445.gobmk.tar.xz | Bin 1836896 -> 620148 bytes save-temps/447.dealII.tar.xz | Bin 6437144 -> 878220 bytes save-temps/450.soplex.tar.xz | Bin 731120 -> 207588 bytes save-temps/453.povray.tar.xz | Bin 1385108 -> 460732 bytes save-temps/454.calculix.tar.xz | Bin 1233932 -> 0 bytes save-temps/456.hmmer.tar.xz | Bin 371356 -> 123556 bytes save-temps/458.sjeng.tar.xz | Bin 144080 -> 50788 bytes save-temps/459.GemsFDTD.tar.xz | Bin 150768 -> 0 bytes save-temps/462.libquantum.tar.xz | Bin 62008 -> 23760 bytes save-temps/464.h264ref.tar.xz | Bin 556680 -> 176052 bytes save-temps/465.tonto.tar.xz | Bin 2229060 -> 0 bytes save-temps/470.lbm.tar.xz | Bin 26824 -> 15536 bytes save-temps/471.omnetpp.tar.xz | Bin 1098832 -> 369768 bytes save-temps/473.astar.tar.xz | Bin 89276 -> 41856 bytes save-temps/481.wrf.tar.xz | Bin 1593700 -> 0 bytes save-temps/482.sphinx3.tar.xz | Bin 248684 -> 94416 bytes save-temps/483.xalancbmk.tar.xz | Bin 11895996 -> 3181884 bytes 107 files changed, 850328 insertions(+), 866261 deletions(-) delete mode 100644 save-temps/410.bwaves.tar.xz delete mode 100644 save-temps/416.gamess.tar.xz delete mode 100644 save-temps/434.zeusmp.tar.xz delete mode 100644 save-temps/435.gromacs.tar.xz delete mode 100644 save-temps/436.cactusADM.tar.xz delete mode 100644 save-temps/437.leslie3d.tar.xz delete mode 100644 save-temps/454.calculix.tar.xz delete mode 100644 save-temps/459.GemsFDTD.tar.xz delete mode 100644 save-temps/465.tonto.tar.xz delete mode 100644 save-temps/481.wrf.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (d03cb9a209 -> 39853f3c21)

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 d03cb9a209 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] discards 43d51b3531 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits discards 11093a8821 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] discards 69279c9c4c 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] discards 6b653c0201 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits discards 19ed77df43 439: onsuccess: #2176: 7: Success after linux: 11 commits discards b5556c4333 438: onsuccess: #2175: 7: Success after gcc: 7 commits discards f0e26bccdf 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits discards ff99f7f410 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] discards ba32c3902b 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] discards edf08e5807 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits discards c4a9e5401b 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] discards 5f842693ef 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] discards b21701ed16 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] discards 48ad0aa9dc 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] discards 71cd6cfa3b 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] discards b465a5c6d2 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] discards 04fa0b9856 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits discards 635e0605fc 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] discards 2cf48a3bc1 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] discards c5d3c78588 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] discards 352df04e8b 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits discards b97a69a0ef 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] discards 995c732833 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] discards 6f3338ea73 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] discards c75a5fb316 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits discards 5ad25ffb5b 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] discards ff8d057afb 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits discards 75696d562f 416: onsuccess: #2152: 7: Success after gcc: 50 commits discards fb9fb823e1 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] discards cbb2d0ab65 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] discards 570678c37c 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] discards a7c930a35a 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits discards f154108b4d 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits discards 4f16e8c9e4 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] discards 13e56ad647 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] discards 1270ba1d3e 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] discards a5c793b9a9 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] discards ad7e1ca2de 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] discards 89fdba0758 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] discards cbf3213725 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] discards da03152275 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits discards e2668da049 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] discards c650b6dafb 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] discards c73b383135 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] discards 84e2d89969 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] discards a39fac9373 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] discards ca55f2bc8c 397: onsuccess: #2132: 7: Success after gcc: 2 commits discards ab37181725 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 40c763b2f7 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] discards 2e66837c83 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] discards 71ea0cbb86 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits discards ef80e7fe12 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] discards 92e82e0f5f 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] discards 3178ebe537 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards e23c1cfae0 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits discards e5de56006e 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits discards 37ccd06daa 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits discards ae26cedc8f 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] discards cf660bb761 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] discards 107b701f85 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] discards e1984cd212 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] discards f0eb2f0b9a 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] discards 9d00f85ef2 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] discards e7ed7826d7 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] discards 9b9413dfc4 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards c0cac1d4c1 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] discards 9096bc2ee2 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] discards a1422c19ba 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards b3429b9c37 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] discards dddf4fd305 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] discards 40bf7b3108 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards c5eabe5aac 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] discards 0a0820bf10 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] discards 3aae45f7e8 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] discards 3315d18fe3 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards f9432fb1d7 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] discards 201574f2ea 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] discards bada4388c6 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] discards 79aa4ae84f 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits discards e631c80368 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits discards 4861d33add 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] discards 6be3fb46cc 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] discards a9864a0da9 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits discards c4482c78d9 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 7b3c429b99 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] discards 54a9d4d9d9 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] discards b641938a44 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] discards 31efaf8a89 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 58d5d9bfd5 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] discards 53b9797cd2 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits discards 87abf80674 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 5f5c7b0a67 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits discards 1be7ff286f 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] discards 1e7d7a70e0 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards f208424efc 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 514b3c4883 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] discards 43f6bf7dd8 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] discards 4f6aa7d848 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits discards fe860dca09 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] discards a3c80ff10f 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 76c870f7dc 344: onsuccess: #2078: 7: Success after binutils/gcc/gdb: 6 commits new 0c50369269 345: onsuccess: #2079: 7: Success after binutils/gcc/linux/g [...] new c088b6dfbd 346: onsuccess: #2080: 7: Success after binutils/gdb: 142 commits new f81e4cd891 347: onsuccess: #2081: 7: Success after binutils/gcc/linux/g [...] new 878a8308d0 348: onsuccess: #2082: 7: Success after binutils/gcc/glibc/g [...] new 7b185cc8f0 349: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new e322d095c2 350: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 5b440dc19c 351: onsuccess: #2085: 7: Success after binutils/gcc/gdb: 19 [...] new d2975e4d42 352: onsuccess: #2086: 7: Success after binutils/gcc/gdb: 9 commits new 85ab4ff76c 353: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new e4650715b7 354: onsuccess: #2088: 7: Success after binutils/gcc/gdb: 7 commits new 4f10bab403 355: onsuccess: #2089: 7: Success after binutils/gcc/linux/g [...] new d04cce02d9 356: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new 817c125781 357: onsuccess: #2091: 7: Success after binutils/gcc/linux/g [...] new c10658e53e 358: onsuccess: #2092: 7: Success after binutils/gcc/gdb: 10 [...] new 97fb63c87b 359: onsuccess: #2093: 7: Success after binutils/gcc/linux/g [...] new afa30841f2 360: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new f30cc8970e 361: onsuccess: #2095: 7: Success after gcc/linux: 15 commits new f95fa6e971 362: onsuccess: #2096: 7: Success after binutils/gcc/linux/g [...] new 7640cf3966 363: onsuccess: #2097: 7: Success after binutils/gcc/gdb: 25 [...] new 685dee1413 364: onsuccess: #2098: 7: Success after binutils/gdb: 4 commits new e5d82ea9c7 365: onsuccess: #2099: 7: Success after gcc/linux: 21 commits new 2a4ce9237b 366: onsuccess: #2100: 7: Success after binutils/gcc/glibc/g [...] new 1ee3c4a2d8 367: onsuccess: #2101: 7: Success after binutils/gcc/linux/g [...] new 888edc3e43 368: onsuccess: #2102: 7: Success after binutils/gcc/linux/g [...] new db69e5c2f5 369: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new 131aca7833 370: onsuccess: #2104: 7: Success after binutils/gcc/linux/g [...] new 0e9ad49c88 371: onsuccess: #2105: 7: Success after binutils/gcc/gdb/qem [...] new 096317e416 372: onsuccess: #2106: 7: Success after binutils/gcc/linux/g [...] new 4d14a4978e 373: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new 72d2987014 374: onsuccess: #2109: 7: Success after binutils/gcc/linux/g [...] new aa2830cef6 375: onsuccess: #2110: 7: Success after binutils/gcc/linux/g [...] new f1f335b613 376: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 79b433446c 377: onsuccess: #2112: 7: Success after binutils/gcc/gdb: 16 [...] new e4511aae24 378: onsuccess: #2113: 7: Success after binutils/gcc/linux/g [...] new 24771c80c0 379: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new 9f7bf8e097 380: onsuccess: #2115: 7: Success after binutils/gcc/linux/g [...] new 25af809a0e 381: onsuccess: #2116: 7: Success after binutils/gcc/linux/g [...] new b0cc8c0584 382: onsuccess: #2117: 7: Success after binutils/gcc/linux/g [...] new 7adb04245d 383: onsuccess: #2118: 7: Success after binutils/gcc/glibc/g [...] new 6642689c87 384: onsuccess: #2119: 7: Success after binutils/gcc/linux/g [...] new 1f1cad9b47 385: onsuccess: #2120: 7: Success after binutils/gcc/gdb/qem [...] new 0aac47439c 386: onsuccess: #2121: 7: Success after binutils/gcc/glibc/g [...] new 68e0776a08 387: onsuccess: #2122: 7: Success after gcc/linux/qemu: 117 commits new 9bb40fe712 388: onsuccess: #2123: 7: Success after binutils/gcc/gdb: 3 commits new 2e5937d447 389: onsuccess: #2124: 7: Success after binutils/gcc/gdb: 5 commits new 83e1383184 390: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new b09799a562 391: onsuccess: #2126: 7: Success after binutils/gcc/linux/g [...] new 403a9f448f 392: onsuccess: #2127: 7: Success after glibc-2.37.9000-17-g [...] new 30741bfb58 393: onsuccess: #2128: 7: Success after gcc/qemu: 42 commits new fbcba46ff7 394: onsuccess: #2129: 7: Success after binutils/gcc/linux/g [...] new 817f5325c4 395: onsuccess: #2130: 7: Success after binutils/gcc/gdb/qem [...] new 23e05a460c 396: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new 1b265b69d5 397: onsuccess: #2132: 7: Success after gcc: 2 commits new 33fbb923b7 398: onsuccess: #2133: 7: Success after binutils/gcc/glibc/g [...] new 6abe1b3c80 399: onsuccess: #2134: 7: Success after binutils/gcc/linux/g [...] new 02706118ab 400: onsuccess: #2135: 7: Success after binutils/gcc/linux/g [...] new 46b828662d 401: onsuccess: #2136: 7: Success after binutils/gcc/glibc/g [...] new 8f6972932b 402: onsuccess: #2137: 7: Success after binutils/gcc/gdb: 22 [...] new 7c92a81fb0 403: onsuccess: #2138: 7: Success after binutils/gcc/gdb: 4 commits new e8631d959a 404: onsuccess: #2139: 7: Success after basepoints/gcc-13-57 [...] new 21977ef0ac 405: onsuccess: #2141: 7: Success after binutils/gcc/linux/g [...] new 72f1f3dd57 406: onsuccess: #2142: 7: Success after binutils/gcc/gdb: 14 [...] new 65ad295703 407: onsuccess: #2143: 7: Success after binutils/gcc/linux/g [...] new 9ffaa73aed 408: onsuccess: #2144: 7: Success after binutils/gcc/gdb/qem [...] new 45f793b141 409: onsuccess: #2145: 7: Success after binutils/gcc/linux/g [...] new 1afc58589b 410: onsuccess: #2146: 7: Success after binutils/gcc/linux/g [...] new 3658305ecb 411: onsuccess: #2147: 7: Success after binutils/gcc/gdb: 9 commits new e3b19e23a1 412: onsuccess: #2148: 7: Success after binutils/gcc/gdb: 6 commits new afa2288089 413: onsuccess: #2149: 7: Success after binutils/gcc/linux/g [...] new 1345308b9b 414: onsuccess: #2150: 7: Success after binutils/gcc/linux/g [...] new 629758b35e 415: onsuccess: #2151: 7: Success after binutils/gcc/gdb: 93 [...] new ee27735025 416: onsuccess: #2152: 7: Success after gcc: 50 commits new 74870f3624 417: onsuccess: #2153: 7: Success after linux/glibc: 27 commits new 23f91de1ef 418: onsuccess: #2154: 7: Success after binutils/gcc/linux/g [...] new 1073103ea7 419: onsuccess: #2155: 7: Success after binutils/gcc/gdb: 4 commits new a1d591cdd7 420: onsuccess: #2156: 7: Success after binutils/gcc/gdb: 27 [...] new ef0d1e7c13 421: onsuccess: #2157: 7: Success after binutils/gcc/linux/g [...] new 7faf85a6f2 422: onsuccess: #2158: 7: Success after binutils/gcc/linux/g [...] new 8b9900d213 423: onsuccess: #2159: 7: Success after binutils/gcc/gdb: 5 commits new 40d679ce2c 424: onsuccess: #2160: 7: Success after binutils/gcc/glibc/g [...] new d95cb28420 425: onsuccess: #2161: 7: Success after binutils/gcc/linux/g [...] new c18a7f615a 426: onsuccess: #2162: 7: Success after binutils/gcc/gdb: 13 [...] new c60200d240 427: onsuccess: #2163: 7: Success after binutils/gdb: 4 commits new c609e6cc86 428: onsuccess: #2165: 7: Success after binutils/gcc/glibc/g [...] new 63ac0f1195 429: onsuccess: #2166: 7: Success after binutils/gcc/linux/g [...] new 112d216bbe 430: onsuccess: #2167: 7: Success after binutils/gcc/gdb/qem [...] new c8ec12ef37 431: onsuccess: #2168: 7: Success after binutils/gcc/gdb/qem [...] new d63e4602db 432: onsuccess: #2169: 7: Success after binutils/gcc/linux/g [...] new d61597d3e6 433: onsuccess: #2170: 7: Success after binutils/gcc/linux/g [...] new ac9764b9d4 434: onsuccess: #2171: 7: Success after gcc/glibc: 5 commits new d5430a11d0 435: onsuccess: #2172: 7: Success after binutils/gcc/glibc/g [...] new 3616633980 436: onsuccess: #2173: 7: Success after binutils/gcc/linux/g [...] new 1fb37fcdd6 437: onsuccess: #2174: 7: Success after gcc/linux: 9 commits new b661f9b93b 438: onsuccess: #2175: 7: Success after gcc: 7 commits new 1ee079b832 439: onsuccess: #2176: 7: Success after linux: 11 commits new 0e52d946b2 440: onsuccess: #2177: 7: Success after binutils/gcc/gdb: 6 commits new e492e1ed4a 441: onsuccess: #2178: 7: Success after binutils/linux/gdb: [...] new 94a51e5e06 442: onsuccess: #2179: 7: Success after binutils/gcc/linux/g [...] new c3d4927a88 443: onsuccess: #2180: 7: Success after binutils/gdb: 2 commits new 310ebc8b42 444: onsuccess: #2181: 7: Success after binutils/gcc/glibc/g [...] new 39853f3c21 445: onsuccess: #2182: 7: Success after binutils/gcc/glibc/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 (d03cb9a209) \ 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 1764 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2772 bytes 04-build_abe-binutils/console.log.xz | Bin 30676 -> 30624 bytes 05-build_abe-stage1/console.log.xz | Bin 89060 -> 88664 bytes 07-build_abe-linux/console.log.xz | Bin 8336 -> 8344 bytes 08-build_abe-glibc/console.log.xz | Bin 235532 -> 235492 bytes 09-build_abe-stage2/console.log.xz | Bin 226408 -> 225536 bytes 10-build_abe-gdb/console.log.xz | Bin 38552 -> 38440 bytes 11-build_abe-qemu/console.log.xz | Bin 31528 -> 31844 bytes 12-check_regression/console.log.xz | Bin 4116 -> 4716 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 ++++++++++++------------- 21 files changed, 62 insertions(+), 62 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 updated (aacffde510 -> ea20b0b8c5)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards aacffde510 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards df220d34fe 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards 7b74e7e5a4 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards 36d52b1c97 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 4100467a2b 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 89d4cfb58a 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 0c5d01513a 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 8e95056e9a 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 4d24521366 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards 007c691da7 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards 3e33fd5240 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards a0656819e8 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards b2ff26fb37 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards b20e247c19 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 23e4b6b3b5 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards d3f917eb84 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards c2edda202f 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards fea038f79d 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards a3010fcf21 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 2a904c5fed 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 50bf6fc12e 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards 42fc48e697 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards 928472e7af 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards aae594d0e2 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards aa466d14ea 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards 4ff1b6f333 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards 98036c0b71 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards 3acdb5ea74 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 007335a0d8 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards aa8b149e3c 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 45e5c2e97e 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 2b2ac13995 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards 3d4171af3b 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards de08478743 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards bd1bdd3910 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 94d8449f97 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 3dd8134d9d 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 78dc148fae 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards cf46fe8cfe 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 65dbdb21a2 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards d0eeec3a1b 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 1276bc71e1 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 50298f5c39 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards d087cad5e6 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards 5fa4c41b28 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 2267ed7d22 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards 6068ca43ed 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards eb79292011 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 1c9b682596 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards d2ad1fa165 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits discards f28fd8b0b9 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] discards 16de2163e4 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] discards e6c5ff8f49 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] discards 5cbd488002 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] discards 3edf46d8ca 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] discards ea267485b0 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] discards 5173cf1e17 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits discards fa82dbd581 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] discards 78efefc78a 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] discards 1d458715e0 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] discards 04df4292b8 43: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] discards 874f21c8e5 42: onsuccess: #53: 1: Success after linux: 3008 commits discards 90d52a2be4 41: onsuccess: #51: 1: Success after binutils: 12 commits discards a468361d30 40: onsuccess: #49: 1: Success after linux: 219 commits discards c762943fdf 39: onsuccess: #48: 1: Success after glibc: 2 commits discards 93f264d1ea 38: onsuccess: #46: 1: Success after binutils: 26 commits discards ae9161791a 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] discards 2732cb0893 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] discards 3e6425ed5b 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] discards 38264475af 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] discards adb25bd6b0 33: onsuccess: #40: 1: Success after binutils/gcc/linux/glib [...] discards bd1bcff2c4 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] discards 86f88692df 31: onsuccess: #38: 1: Success after linux: 12 commits discards 6c16a778e0 30: onsuccess: #36: 1: Success after binutils: 18 commits discards 7eb76deddb 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] discards f8300dcc95 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] discards 6e2e8b6fc5 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] discards f0aed4cf3f 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] discards 12cf5b1ba2 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] discards e446d10359 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] discards 8e8d120010 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] discards 437220cf5e 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] discards 748ba338c7 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] discards e638cd66df 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] discards d2bf21c3e0 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] discards 9531686f7d 18: onsuccess: #23: 1: Success after binutils/gcc/gdb: 64 commits discards 95e460815f 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 52 commits discards f0c65a6f8c 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] discards a7b566ca4c 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] discards b4c5866099 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] discards 8ba6d3dfa5 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] discards 4dd3bd5766 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] discards 3129960480 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] discards 5a4bf62b05 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] discards 83ec6ee2df 9: onsuccess: #13: 1: Success after binutils: 3 commits discards ada1f667c4 8: onsuccess: #10: 1: Success after binutils: 5 commits discards 6dffbb2a8c 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 2 [...] discards 8d030e17a7 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] discards e5b1808000 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] discards b0209b47af 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] discards 2ca09b6dff 3: onsuccess: #4: 1: Success after binutils/gcc/linux/glibc/ [...] new 3fe85ed4a2 3: onsuccess: #4: 1: Success after binutils/gcc/linux/glibc/ [...] new 70a32918fc 4: onsuccess: #5: 1: Success after binutils/gcc/linux/glibc/ [...] new a30d6de530 5: onsuccess: #6: 1: Success after binutils/gcc/linux/glibc/ [...] new 32e5124362 6: onsuccess: #7: 1: Success after binutils/gcc/linux/glibc/ [...] new 177cfdc3e2 7: onsuccess: #8: 1: Success after binutils/gcc/linux/gdb: 2 [...] new 207adb5860 8: onsuccess: #10: 1: Success after binutils: 5 commits new 3ff356323b 9: onsuccess: #13: 1: Success after binutils: 3 commits new d5ddefe63c 10: onsuccess: #15: 1: Success after binutils/gcc/linux/glib [...] new 18294047fc 11: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb: [...] new dd33af8322 12: onsuccess: #17: 1: Success after binutils/gcc/linux/glib [...] new 54b7491f58 13: onsuccess: #18: 1: Success after binutils/gcc/linux/gdb: [...] new 944ea8d8d9 14: onsuccess: #19: 1: Success after binutils/gcc/linux/gdb: [...] new ad98357656 15: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb: [...] new 45c740ea23 16: onsuccess: #21: 1: Success after binutils/gcc/linux/glib [...] new 40ef705add 17: onsuccess: #22: 1: Success after binutils/gcc/gdb: 52 commits new 23d4ca64d5 18: onsuccess: #23: 1: Success after binutils/gcc/gdb: 64 commits new b3e855dd92 19: onsuccess: #24: 1: Success after binutils/gcc/linux/gdb: [...] new 4405fef160 20: onsuccess: #25: 1: Success after binutils/gcc/linux/gdb: [...] new 1ccd65972d 21: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb: [...] new f151686002 22: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb: [...] new 3a5be7ea91 23: onsuccess: #28: 1: Success after binutils/gcc/linux/glib [...] new 11d6c8af25 24: onsuccess: #29: 1: Success after binutils/gcc/linux/glib [...] new 32e36359bf 25: onsuccess: #30: 1: Success after binutils/gcc/linux/glib [...] new 3b08d0c3fd 26: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb: [...] new e2197899cd 27: onsuccess: #32: 1: Success after binutils/gcc/linux/glib [...] new 1582bdddc4 28: onsuccess: #33: 1: Success after binutils/gcc/linux/glib [...] new c767ce5a5a 29: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb: [...] new 973e9f3009 30: onsuccess: #36: 1: Success after binutils: 18 commits new cff9616135 31: onsuccess: #38: 1: Success after linux: 12 commits new a5335ac1a8 32: onsuccess: #39: 1: Success after binutils/gcc/linux/glib [...] new 62ebb52e75 33: onsuccess: #40: 1: Success after binutils/gcc/linux/glib [...] new 5865fe823f 34: onsuccess: #41: 1: Success after binutils/gcc/linux/glib [...] new 4e2837646d 35: onsuccess: #42: 1: Success after binutils/gcc/linux/glib [...] new 812160ffd2 36: onsuccess: #43: 1: Success after binutils/gcc/linux/gdb: [...] new a25c0da468 37: onsuccess: #44: 1: Success after binutils/gcc/linux/gdb: [...] new 007b1ec595 38: onsuccess: #46: 1: Success after binutils: 26 commits new 6b74c26e71 39: onsuccess: #48: 1: Success after glibc: 2 commits new 32be18d773 40: onsuccess: #49: 1: Success after linux: 219 commits new 05a6b46403 41: onsuccess: #51: 1: Success after binutils: 12 commits new 4bf0ce1b07 42: onsuccess: #53: 1: Success after linux: 3008 commits new dbf259863d 43: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new a3b3f4b403 44: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] new e153d8ed56 45: onsuccess: #56: 1: Success after binutils/gcc/linux/glib [...] new cd6bc99a80 46: onsuccess: #57: 1: Success after binutils/gcc/linux/gdb: [...] new cc948c3fa8 47: onsuccess: #58: 1: Success after binutils/gcc/gdb: 14 commits new 33826de298 48: onsuccess: #59: 1: Success after binutils/gcc/linux/glib [...] new de0fc6f731 49: onsuccess: #60: 1: Success after binutils/gcc/linux/glib [...] new 1c3ef1751a 50: onsuccess: #61: 1: Success after binutils/gcc/linux/glib [...] new 8d12c8e652 51: onsuccess: #62: 1: Success after binutils/gcc/linux/glib [...] new d21b77c226 52: onsuccess: #63: 1: Success after binutils/gcc/linux/glib [...] new 6e49b92d09 53: onsuccess: #64: 1: Success after binutils/gcc/linux/gdb: [...] new d1da84d353 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new e706f0315c 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 6ff4edfb7b 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 7189bf68d4 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 77aca039cb 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new cc465a4a99 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 5d19a13676 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new 5958e57198 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 22294b3b0a 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 8a6b0e3af1 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 8fb6262131 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new b09f8972ae 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 77a405207e 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 5c17a257df 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new f138bd6753 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 0ed4443928 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new 8abd0e3f21 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new ea49e64791 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 3c7975af76 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 0748ae0957 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new 77b53e63d6 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 8a514b61e1 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new b61f89df4c 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new b11e5569b6 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new bc2615f05d 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 144a4231d1 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 6d630d2efe 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new b106e5c213 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 8dc25ba1bc 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 9da2f92cc5 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new 013640cae0 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new d46de7b586 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new b3f5e355f8 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 163f1d208d 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 251e7ad5e9 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new e5624dff87 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new d6988875ef 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new cde397df0d 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new 185d0c1545 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 342ea415d8 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new 9a83e10aa6 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 101aca4996 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new 4c7a48c297 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new d94634fd9b 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new f6b7203187 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new f5a79456d7 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new d9c3657dae 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 6866271337 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new ec6f830d62 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new 50f35d0ef9 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new ea20b0b8c5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (aacffde510) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 38580 -> 38684 bytes 04-build_abe-gcc/console.log.xz | Bin 205628 -> 203720 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8296 bytes 07-build_abe-glibc/console.log.xz | Bin 245540 -> 243328 bytes 08-build_abe-gdb/console.log.xz | Bin 39256 -> 38860 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3800 -> 3816 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2460 -> 2436 bytes 11-check_regression/console.log.xz | Bin 5408 -> 5900 bytes 11-check_regression/results.compare | 4 +-- 11-check_regression/results.compare2 | 6 ++-- 12-update_baseline/console.log | 64 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++---------- sumfiles/gdb.log.xz | Bin 11932 -> 11904 bytes sumfiles/gdb.sum | 30 ++++++++-------- 26 files changed, 80 insertions(+), 80 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[glibc] branch master updated (3f98a5c027 -> 97830304bb)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository glibc. from 3f98a5c027 Linux: Remove generic Implies new 97830304bb arm: Support gcc older than 10 for find_zero_all The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: sysdeps/arm/armv6t2/string-fza.h | 6 ++++++ 1 file changed, 6 insertions(+) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 updated (0ea8b1db22 -> 9cceca22b3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 0ea8b1db22 192: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 7c1fa2c0d2 191: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards 299bccbecb 190: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards f3bc53a2f7 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 commits discards 54057ba109 188: onsuccess: #941: 1: Success after binutils/gcc/linux/gl [...] discards d47071400d 187: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 57433e3f0a 186: onsuccess: #938: 1: Success after binutils/gcc/linux/gl [...] discards 759ddad0e9 185: onsuccess: #937: 1: Success after binutils/gcc/linux/gd [...] discards 23cd700e8e 184: onsuccess: #936: 1: Success after binutils/gcc/linux/gl [...] discards 74c3598266 183: onsuccess: #935: 1: Success after binutils/gcc/linux/gl [...] discards 72a40e0d80 182: onsuccess: #933: 1: Success after binutils/gcc/linux/gl [...] discards 51b3de755a 181: onsuccess: #932: 1: Success after binutils/gcc/linux/gl [...] discards 2637273706 180: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 58fc0002ba 179: onsuccess: #930: 1: Success after binutils/gcc/linux/gl [...] discards c00572044f 178: onsuccess: #929: 1: Success after binutils/gcc/linux/gl [...] discards 68c9bbb3b4 177: onsuccess: #928: 1: Success after binutils/gcc/linux/gl [...] discards 426603bc09 176: onsuccess: #927: 1: Success after binutils/gcc/linux/gl [...] discards 9fe4b25f59 175: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 5b7b276372 174: onsuccess: #925: 1: Success after binutils/gcc/linux/gd [...] discards d31d2df855 173: onsuccess: #924: 1: Success after binutils/gcc/linux/gl [...] discards b2900e43af 172: onsuccess: #923: 1: Success after binutils/gcc/linux/gd [...] discards 5aa7e46d03 171: onsuccess: #922: 1: Success after binutils/gcc/linux/gl [...] discards e12f4caeed 170: onsuccess: #921: 1: Success after binutils/gcc/linux/gl [...] discards b2e0228422 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 768188a732 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] discards 8d626fdc4e 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] discards 6b6095aa5a 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] discards 4360bd0854 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards 2c064194d3 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] discards d49bcb8d5b 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] discards 09cf150569 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] discards caa5218ce8 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards 345accd561 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] discards f06950a72b 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] discards 01f0082c47 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards 02edd25900 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards a9683555aa 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards 8e481a7608 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards 1f7757a285 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards d5c99a7867 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards fc497d9c94 152: onsuccess: #903: 1: Success after linux: 22 commits discards 374c8b4e86 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 8b18dc0bfa 150: onsuccess: #900: 1: Success after gcc: 11 commits discards cb6bdb692f 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 1baba31a69 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards bcf53dbe39 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards b4600d043a 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards ebed630264 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 812c02e865 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 3502a996ec 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards cf227bd74a 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards febe1c6146 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 1153f33656 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 4992a80819 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 10288fdb80 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 8120f78d43 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards d2ec93aa4d 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 317ee918e9 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 0d263e4a1d 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards c8022264ac 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 45fb581871 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards 52a9f12b25 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 636bebae44 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 4e548421db 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 05a89605bb 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 34a62b70ae 127: onsuccess: #874: 1: Success after linux: 219 commits discards 1eed376de2 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 123909620c 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 7be156053d 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards eefcbd2fb0 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards 4e84fb4455 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards f5271aeb12 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards 15164ca7e5 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 7e7857d476 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards fd413b11f0 118: onsuccess: #863: 1: Success after linux: 12 commits discards 7d5cc41905 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 561a74f6bc 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 943613efad 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 5516323c49 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards f128cdedc5 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 8ea2d37c84 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards 5e4708647d 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards b34fa38d93 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 5d75f5c515 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards cd1dcd60b8 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 2617c11367 107: onsuccess: #849: 1: Success after binutils: 5 commits discards f2144f295a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards 315a9f85c2 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards 2e19e15f5f 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 6ae019e7bb 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 1730965945 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 8fed19f8ac 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards db594dff5b 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards d8f8d9e61e 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards 62a3878532 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 59be755497 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards f36c180b14 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 1afccba5ff 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 8941df4f4a 94: onsuccess: #832: 1: Success after binutils: 5 commits discards fe941c8bc1 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 4e73538ad3 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new 05f28cf632 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new f0f178c857 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 23c608b511 94: onsuccess: #832: 1: Success after binutils: 5 commits new 3cdcc7d180 95: onsuccess: #835: 1: Success after binutils: 3 commits new 16370c99bc 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new f3d103d49d 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 3c18e33f76 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 26204d0a33 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 86028dd8a2 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 0bb83544bd 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 1fee907a2e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 2a80175034 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new b95ef0163e 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new ba33936afa 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new f2bb739b8b 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new b6c292b01d 107: onsuccess: #849: 1: Success after binutils: 5 commits new adf2518004 108: onsuccess: #850: 1: Success after gcc: 2 commits new a0643401ea 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 3c0c29ce0b 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 7990ac96c7 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 70ffe60670 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 32d4fbf8ac 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new 0389c0c45c 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 9d76ee35f0 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 6f973208c8 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 95377edea4 117: onsuccess: #861: 1: Success after binutils: 18 commits new c973c5f9b7 118: onsuccess: #863: 1: Success after linux: 12 commits new 05e8d90117 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 495cd599ea 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new aa2f70f97d 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 07e5042d1d 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 70fd3bf3d3 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new d1481a1641 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new c3f15d3ccb 125: onsuccess: #871: 1: Success after binutils: 26 commits new 0231c08c82 126: onsuccess: #873: 1: Success after glibc: 2 commits new 16d11a6399 127: onsuccess: #874: 1: Success after linux: 219 commits new 5db41cd34a 128: onsuccess: #876: 1: Success after binutils: 12 commits new 6027a64177 129: onsuccess: #878: 1: Success after linux: 3008 commits new 2be127bceb 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new c09494f529 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 820c18a1f2 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new f2af21f789 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 88e299201f 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 27c3d858aa 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 356a6b1090 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 85617215a6 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 583318553f 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new cfdf209409 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 4130e5962b 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new c93ded6f20 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 0e9560cc99 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 7ae4f5ec3f 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 3eec284106 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new b3d33a0241 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 54fd3289d2 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 79fa74f450 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new d7bd7e7e5f 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 076bc143bb 149: onsuccess: #899: 1: Success after binutils: 15 commits new 7ca4936c5f 150: onsuccess: #900: 1: Success after gcc: 11 commits new d3fb91bf42 151: onsuccess: #902: 1: Success after glibc: 8 commits new e8eabc69f7 152: onsuccess: #903: 1: Success after linux: 22 commits new 43bf72fa08 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 1bc4c92533 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 4c0d720773 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new a76e95a1db 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new f3ca58fa07 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new 8b74b2a6d4 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new c835263478 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] new 625e44b5e0 160: onsuccess: #911: 1: Success after binutils/gcc/linux/gl [...] new 4554fbb42a 161: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new bcb2548cfd 162: onsuccess: #913: 1: Success after binutils/gcc/linux/gl [...] new ab7180f79c 163: onsuccess: #914: 1: Success after binutils/gcc/linux/gl [...] new f50dc08f2c 164: onsuccess: #915: 1: Success after binutils/gcc/linux/gl [...] new b16e77c56c 165: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new c3a6069fb2 166: onsuccess: #917: 1: Success after binutils/gcc/linux/gd [...] new fed52adf18 167: onsuccess: #918: 1: Success after binutils/gcc/linux/gd [...] new 06399a728e 168: onsuccess: #919: 1: Success after binutils/gcc/linux/gd [...] new 9e2b03f2ed 169: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new b303d5ab9d 170: onsuccess: #921: 1: Success after binutils/gcc/linux/gl [...] new 558bc637e1 171: onsuccess: #922: 1: Success after binutils/gcc/linux/gl [...] new 977084eab4 172: onsuccess: #923: 1: Success after binutils/gcc/linux/gd [...] new 44534536eb 173: onsuccess: #924: 1: Success after binutils/gcc/linux/gl [...] new c39308682a 174: onsuccess: #925: 1: Success after binutils/gcc/linux/gd [...] new b0283d74a2 175: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new ecdcf7a038 176: onsuccess: #927: 1: Success after binutils/gcc/linux/gl [...] new 73123b52aa 177: onsuccess: #928: 1: Success after binutils/gcc/linux/gl [...] new a84e86f3ce 178: onsuccess: #929: 1: Success after binutils/gcc/linux/gl [...] new f18f874dc2 179: onsuccess: #930: 1: Success after binutils/gcc/linux/gl [...] new 68b1e2a9c1 180: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new d718bbe673 181: onsuccess: #932: 1: Success after binutils/gcc/linux/gl [...] new cdc81801a2 182: onsuccess: #933: 1: Success after binutils/gcc/linux/gl [...] new 2889f6525a 183: onsuccess: #935: 1: Success after binutils/gcc/linux/gl [...] new a340bc114f 184: onsuccess: #936: 1: Success after binutils/gcc/linux/gl [...] new 1ffb55570c 185: onsuccess: #937: 1: Success after binutils/gcc/linux/gd [...] new a42cd6fb6b 186: onsuccess: #938: 1: Success after binutils/gcc/linux/gl [...] new ee7922eba1 187: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 9e5ce1bc9e 188: onsuccess: #941: 1: Success after binutils/gcc/linux/gl [...] new fe7d98aaa7 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 commits new a28886d10f 190: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new ba01cec129 191: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new 314080705b 192: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 9cceca22b3 193: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0ea8b1db22) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1948 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2740 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 38676 -> 38856 bytes 04-build_abe-gcc/console.log.xz | Bin 203648 -> 205412 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8232 bytes 07-build_abe-glibc/console.log.xz | Bin 243280 -> 243180 bytes 08-build_abe-gdb/console.log.xz | Bin 38892 -> 38908 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3768 -> 3772 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2464 -> 3336 bytes 11-check_regression/console.log.xz | Bin 5676 -> 6620 bytes 11-check_regression/results.compare | 16 +- 11-check_regression/results.compare2 | 63 ++++-- 12-update_baseline/console.log | 40 ++-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/g++.log.xz | Bin 3677600 -> 3713600 bytes sumfiles/g++.sum | 132 +++++++------ sumfiles/gcc.log.xz | Bin 3210032 -> 3215560 bytes sumfiles/gcc.sum | 360 ++++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1080912 -> 1079392 bytes sumfiles/gfortran.sum | 38 ++-- sumfiles/libatomic.log.xz | Bin 2268 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 235436 -> 235280 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 447684 -> 449168 bytes sumfiles/libstdc++.sum | 8 +- 38 files changed, 406 insertions(+), 333 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (b0c667ff52 -> 647d4d6b9f)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards b0c667ff52 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] discards fc6e550653 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] discards e1580b47dc 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] discards b7199f1633 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] discards fb0f8ca09d 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] discards bef95c4f3a 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] discards 4e220446fd 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] discards c2f0766f10 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] discards 9bebbeabec 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] discards b87fb396f5 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] discards a2939a7bfa 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] discards 919b1ba0ea 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] discards 2e479b048f 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] discards aa248b6f75 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] discards a7eba945b3 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] discards 949cfa7975 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] discards dbc5cef510 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] discards 4499f79e2d 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] discards 48d4269d0b 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] discards 2a4f1a36e2 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] discards 956d07d2c2 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] discards 29d3e1588a 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] discards 9be430e87e 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] discards 284d06b2a6 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] discards bf7d07157f 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] discards 19b229cf72 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] discards 1436cda49b 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] discards 30a366f5ad 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] discards 2ab7b8e890 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] discards 0a1a0c1293 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] discards bf9009e933 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] discards 30ca4e8fa3 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 29427a3e0b 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards addea34fe5 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 45660149f6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 20f215f6e6 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 4d25c8be5f 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 1d354583e6 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards 427a2e7798 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 1d13871b5e 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards 3394fa3970 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards d2f3a30ab1 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards 68f14950ba 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 487812b573 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards 2200c3440d 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 801ac9f130 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards 3b8c5880e7 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 0d6f61a2d6 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 571c39c4f5 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards c8d8c9d240 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 3ab9f2f13d 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards f63a2e1829 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 327a5551ba 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 0d339b14ce 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 7606e4a881 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 91f3a66b9d 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 72a5d0d51a 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 9d7914ba3b 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 9ecc058c3c 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 87d2160bf2 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards a578c53b23 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards a6f819f265 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards d2151d6a82 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards de23a21a01 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 0e7ce00529 125: onsuccess: #614: 1: Success after linux: 12 commits discards eacca464bf 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 87f364cd98 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards 13e618f680 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards deb933b139 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 2d5cb7a31c 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 9b687a4f9e 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 37e5e44290 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 59d936d2fb 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 429250a2b7 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards 26b06183fa 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards 0062146411 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards aadc489013 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards cc6d72cb3c 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards b1313cf833 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 54a1c285ef 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards 0277375d6a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards 1b21224d2a 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards ae9aaae4cf 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards 44b96d3429 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards a6ee5a00e4 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards 95f572a900 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards e91ac0fbb4 103: onsuccess: #589: 1: Success after binutils: 3 commits discards 074aa57bfd 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 2d40eefc0c 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards f11e18dafd 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 644e3efb5f 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards c9aea07307 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 15a9cec444 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 6416d023f4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 20a4ae4d80 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 6207688b9d 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards b2a76ce97b 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 3e314ea829 92: onsuccess: #575: 1: Success after linux: 34 commits discards a973dfed67 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 58f5008fa2 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 50ae9531dd 89: onsuccess: #570: 1: Success after linux: 11 commits new 8e95f38420 89: onsuccess: #570: 1: Success after linux: 11 commits new 3543fb042a 90: onsuccess: #572: 1: Success after binutils: 15 commits new 2c4dd7364b 91: onsuccess: #574: 1: Success after glibc: 3 commits new 05a4d897e6 92: onsuccess: #575: 1: Success after linux: 34 commits new d47acc8c89 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new fa73e37fd9 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 0cd2e473b4 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new f6435620cf 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 4db917047d 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new e5d145643e 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 973b78bc1e 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 9aa1b13c18 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new b6f5c17ff3 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 1d78fb565c 102: onsuccess: #586: 1: Success after binutils: 5 commits new 2a8cd64af0 103: onsuccess: #589: 1: Success after binutils: 3 commits new 977cb3a859 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 327857d071 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 49a82d2cba 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new 491fe73170 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 9631aa5302 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 4cc6ab0157 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 430cea79e4 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new 83b66e7ebc 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 6e43f5946c 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new b09ba4b5dc 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new 85050d66d5 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 2a02fddee2 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 84e0632277 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new cb548a671c 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new 7ec3e77709 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new c148b4b2e9 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new 589222bbd0 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 8d2e017147 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 48e016918a 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 18d90349b8 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new d36adbfa1b 124: onsuccess: #612: 1: Success after binutils: 18 commits new 04c0c74187 125: onsuccess: #614: 1: Success after linux: 12 commits new f5fa47c33c 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new afcda7a9c3 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new edf3f1dff2 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 544f76944b 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new c6f0c02bcb 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 53be2c1df2 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 1c0094c3f0 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 02251e4c49 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new be687b8bba 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 1959f6b8ad 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 6c81989988 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 322fbf077e 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 9bfbaa69bb 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 8699331f02 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 7136829712 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new f5a0687d88 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 4ca615bcb5 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 49bccd7fd5 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new 02eaf189db 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 15e036530f 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new d493671e84 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new 0d7d2a2680 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 568d1158e0 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 7a2dc79361 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new 813b674a7c 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new 03af8378da 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new 6ad831ff9b 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new c8f80b5fc5 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 7e85107be1 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new 517c1b2ccc 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new 4c979d9e04 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new 0c83ab1ad6 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 57b108e14f 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new c4374287ca 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] new 08fe38cc55 160: onsuccess: #654: 1: Success after binutils/gcc/linux/gl [...] new dc45b7d8b9 161: onsuccess: #655: 1: Success after binutils/gcc/linux/gl [...] new 79b60a729c 162: onsuccess: #656: 1: Success after binutils/gcc/linux/gl [...] new 08455a8e53 163: onsuccess: #657: 1: Success after binutils/gcc/linux/gl [...] new 4fdb7f2f5e 164: onsuccess: #658: 1: Success after binutils/gcc/linux/gl [...] new 810dad4a81 165: onsuccess: #659: 1: Success after binutils/gcc/linux/gl [...] new 61d5364d56 166: onsuccess: #660: 1: Success after binutils/gcc/linux/gd [...] new e49140e3be 167: onsuccess: #661: 1: Success after binutils/gcc/linux/gd [...] new 34e9f2575d 168: onsuccess: #662: 1: Success after binutils/gcc/linux/gd [...] new fe8caf4a45 169: onsuccess: #663: 1: Success after binutils/gcc/linux/gd [...] new eb75ca1ab8 170: onsuccess: #664: 1: Success after binutils/gcc/linux/gl [...] new c812c0bd6c 171: onsuccess: #665: 1: Success after binutils/gcc/linux/gl [...] new 91634b8eae 172: onsuccess: #666: 1: Success after binutils/gcc/linux/gd [...] new 2aa04383ff 173: onsuccess: #667: 1: Success after binutils/gcc/gdb: 180 [...] new c527387d8e 174: onsuccess: #668: 1: Success after binutils/gcc/linux/gl [...] new 593223a5fe 175: onsuccess: #669: 1: Success after binutils/gcc/linux/gd [...] new 632da3b7a0 176: onsuccess: #670: 1: Success after binutils/gcc/linux/gl [...] new 5ecd523d40 177: onsuccess: #671: 1: Success after binutils/gcc/linux/gl [...] new 1d15ca9adf 178: onsuccess: #672: 1: Success after binutils/gcc/linux/gl [...] new 7e5e342c0b 179: onsuccess: #673: 1: Success after binutils/gcc/linux/gl [...] new b44501a730 180: onsuccess: #674: 1: Success after binutils/gcc/linux/gd [...] new 574d151c69 181: onsuccess: #675: 1: Success after binutils/gcc/linux/gl [...] new 26fc5ad551 182: onsuccess: #676: 1: Success after binutils/gcc/linux/gl [...] new f7dd0c72f7 183: onsuccess: #677: 1: Success after binutils/gcc/linux/gl [...] new 966657e504 184: onsuccess: #678: 1: Success after binutils/gcc/glibc/gd [...] new 7385951d61 185: onsuccess: #679: 1: Success after binutils/gcc/linux/gl [...] new 662a53f811 186: onsuccess: #680: 1: Success after binutils/gcc/linux/gl [...] new ea3c564f74 187: onsuccess: #681: 1: Success after binutils/gcc/linux/gd [...] new bbd4c95d45 188: onsuccess: #682: 1: Success after binutils/gcc/linux/gl [...] new d341b1a0f3 189: onsuccess: #683: 1: Success after binutils/gcc/linux/gl [...] new 647d4d6b9f 190: onsuccess: #693: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b0c667ff52) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 52308 -> 52304 bytes 04-build_abe-gcc/console.log.xz | Bin 236996 -> 237492 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8900 -> 8364 bytes 07-build_abe-glibc/console.log.xz | Bin 236816 -> 235060 bytes 08-build_abe-gdb/console.log.xz | Bin 51732 -> 50684 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3760 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2704 -> 2208 bytes 11-check_regression/console.log.xz | Bin 15252 -> 33704 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 1255 +- 11-check_regression/mail-body.txt | 209 +- 11-check_regression/results.compare | 1335 +- 11-check_regression/results.compare2 | 7213 +- 11-check_regression/results.regressions | 167 +- 12-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 211 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 167 +- sumfiles/gdb.log.xz | Bin 2844416 -> 2813056 bytes sumfiles/gdb.sum | 174143 +++++++++++++++-------------- 31 files changed, 95505 insertions(+), 89313 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (84587f479d -> 9712092852)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 84587f479d 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc/g [...] discards 66c00218e8 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits discards 5f87200cb5 429: onsuccess: #2133: 7: Success after binutils/gcc/linux/g [...] discards dc02e919e9 428: onsuccess: #2132: 7: Success after binutils/linux/gdb: [...] discards 586a115705 427: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] discards 5764a953a0 426: onsuccess: #2130: 7: Success after gcc: 7 commits discards b983c35331 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits discards 90b0d57898 424: onsuccess: #2128: 7: Success after binutils/gcc/linux/g [...] discards 52f1b6e735 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc/g [...] discards d31781f847 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits discards 0e3ae1ca12 421: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] discards da50db0fae 420: onsuccess: #2124: 7: Success after binutils/gcc/linux/g [...] discards 0fa58390f7 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/qem [...] discards 7be0df359f 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/qem [...] discards 99e9bbfa50 417: onsuccess: #2121: 7: Success after binutils/gcc/linux/g [...] discards d9a1b987e6 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc/g [...] discards 64f1ab6f09 415: onsuccess: #2119: 7: Success after gcc: 37 commits discards 617d5c2532 414: onsuccess: #2118: 7: Success after binutils: 5 commits discards e7e491ff60 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits discards ebabd0afa7 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc/g [...] discards 39f5a56b93 411: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] discards 6225c2b486 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc/g [...] discards 5d3d4c1783 409: onsuccess: #2112: 7: Success after gcc: 3 commits discards 0c6a2d4272 408: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] discards 91a597f8e4 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc/g [...] discards 95a7efb83f 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] discards 579ac29e5e 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits discards 3da30b9e38 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] discards b29aaff3d3 403: onsuccess: #2106: 7: Success after glibc: 12 commits discards da64f7dae6 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] discards a05b2e4075 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] discards 399697bfc6 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] discards b97a4c6214 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits discards 7128b689ac 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits discards c78f8893a6 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits discards 2454eaa182 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] discards f2df185a62 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] discards 61c6088767 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] discards b32aecb645 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits discards 9916538583 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] discards c29d6874c6 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] discards 2322370bc2 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] discards 95344b2828 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] discards ef7c1dfca9 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] discards 9c10045fd0 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] discards 74cfcc1c3a 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] discards 904c8bcc01 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards f9793946f4 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards d9f1a57a15 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards c04cd329d2 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards 2b38990847 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards 5a0bd0e294 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 306a423519 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 7f4f4452f1 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards ff59788ede 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards 021bae9979 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards 58fb4025b7 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 8fed19cb46 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards d793d37502 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards 17e3b54bd6 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 7119d08252 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards c8b847d79a 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards 0e6d030480 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards cfad647e59 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards 0be87e7476 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 4daa984695 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards 77f2096290 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards 2ddba9fda7 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 0afb26ef49 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards c1e8fc2431 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards c85bff82b5 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards cecdfa4136 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 32cc5ffde2 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards 372e3e7c47 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards f3f8b785a7 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards b21936e600 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards 4c69e7e5cc 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 4c331ad4c3 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards f2a2fae1eb 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards d189db3d74 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards e1d51787a1 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 0c8801d3a1 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 4030aafcfa 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 8bac33c8de 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards 357a66e44c 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards bc81136487 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards e333493b04 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 6e271d5806 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards 0ff7087ee1 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 89a5e8c69a 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards 8b614adc50 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 5bae4b0ff8 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards 00872fc00a 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards ead742be72 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards 5fcf7d9db6 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 45def63e03 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 0f322a2fc6 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards 93a7f7b6f6 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 290714dfb2 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 629d175477 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards c2530e11e6 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 16f2840f05 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 08bfb0be23 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 3d52a8526a 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new 8616f85cc4 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new 6a238e55b0 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new c1af0ebf91 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 0edd79148f 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 6132791de2 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new 8e0ad8bbec 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 0df40f433d 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new f6571ad68a 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new aef163c9e8 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 77df066cbd 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new fcacab9ed4 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 5e84df6cb2 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new a74a7f3f66 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new 9a43a9972f 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new b8d20b538b 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new e59c7b95a9 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 48517b7590 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new f8ef2f523a 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new a77ada25e0 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new da2380a114 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new e68d2804a3 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new dac141e3e5 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new e4893bcf5a 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 346fef4a73 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 8945062d62 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new 793c6783b0 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 532bfc2aef 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new f67f6528cf 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 4ca9cdb5a0 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new aa0dd2255e 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new 4695343167 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new 7b30c41086 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 9cc8361721 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 1884047e4f 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 3f49d6cf4e 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new c6fc333a4c 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 63090bf62f 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 479309d97f 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new f95ac6c4b3 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 944a977e8e 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new d32f655b06 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 00264ac020 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new 4fe660aefd 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new 423800b41b 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 48e450d014 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new 1b0a8e2751 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new efb7c7399b 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new bdf61f8f24 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new a9886f0a20 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new d1cdcaf579 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new ee0d0045e9 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new a3d0d7ae73 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new cc6becc04c 386: onsuccess: #2087: 7: Success after binutils/gcc/linux/g [...] new 01a0995a90 387: onsuccess: #2089: 7: Success after binutils/gcc/gdb/qem [...] new 57efab5da6 388: onsuccess: #2090: 7: Success after binutils/gcc/glibc/g [...] new dbeb2cd85d 389: onsuccess: #2091: 7: Success after binutils/gcc/gdb: 12 [...] new 8254d08425 390: onsuccess: #2092: 7: Success after basepoints/gcc-13-57 [...] new de2b382251 391: onsuccess: #2094: 7: Success after binutils/gcc/linux/g [...] new cb821f7d1e 392: onsuccess: #2095: 7: Success after binutils/gcc/linux/g [...] new acfbe3f2b9 393: onsuccess: #2096: 7: Success after gcc/linux: 45 commits new cd3733564f 394: onsuccess: #2097: 7: Success after binutils/gcc/gdb/qem [...] new 3889628e33 395: onsuccess: #2098: 7: Success after binutils/gcc/linux/g [...] new 834c142f4d 396: onsuccess: #2099: 7: Success after binutils/gcc/linux/g [...] new a06e28215e 397: onsuccess: #2100: 7: Success after binutils/gcc/gdb: 9 commits new 0021efa9ad 398: onsuccess: #2101: 7: Success after binutils/gcc/gdb: 6 commits new c9380b195f 399: onsuccess: #2102: 7: Success after binutils/gcc/gdb: 9 commits new 7d1b8df025 400: onsuccess: #2103: 7: Success after binutils/gcc/linux/g [...] new f9d1355891 401: onsuccess: #2104: 7: Success after binutils/gcc/gdb: 85 [...] new 3ad3d992de 402: onsuccess: #2105: 7: Success after binutils/gcc/gdb: 58 [...] new 5d92619bea 403: onsuccess: #2106: 7: Success after glibc: 12 commits new f9f952bee9 404: onsuccess: #2107: 7: Success after binutils/gcc/linux/g [...] new efe4ba9524 405: onsuccess: #2108: 7: Success after binutils/gcc/gdb: 3 commits new e605d222d0 406: onsuccess: #2109: 7: Success after binutils/gcc/gdb: 26 [...] new d36bee0304 407: onsuccess: #2110: 7: Success after binutils/gcc/glibc/g [...] new 3f4a6470c4 408: onsuccess: #2111: 7: Success after binutils/gcc/linux/g [...] new 3eb75a624e 409: onsuccess: #2112: 7: Success after gcc: 3 commits new e8664792d7 410: onsuccess: #2113: 7: Success after binutils/gcc/glibc/g [...] new 1fd255c9cd 411: onsuccess: #2114: 7: Success after binutils/gcc/linux/g [...] new efa714275c 412: onsuccess: #2115: 7: Success after binutils/gcc/glibc/g [...] new 5de181391b 413: onsuccess: #2116: 7: Success after binutils/gdb: 4 commits new 3b08f84283 414: onsuccess: #2118: 7: Success after binutils: 5 commits new b2559b0280 415: onsuccess: #2119: 7: Success after gcc: 37 commits new f7e0317904 416: onsuccess: #2120: 7: Success after binutils/gcc/glibc/g [...] new 12f53afe4f 417: onsuccess: #2121: 7: Success after binutils/gcc/linux/g [...] new bac76f5a4f 418: onsuccess: #2122: 7: Success after binutils/gcc/gdb/qem [...] new 59a441f206 419: onsuccess: #2123: 7: Success after binutils/gcc/gdb/qem [...] new 68044562b9 420: onsuccess: #2124: 7: Success after binutils/gcc/linux/g [...] new 9081939bfe 421: onsuccess: #2125: 7: Success after binutils/gcc/linux/g [...] new 57afe67cae 422: onsuccess: #2126: 7: Success after gcc/glibc: 5 commits new 5b7d24ae9c 423: onsuccess: #2127: 7: Success after binutils/gcc/glibc/g [...] new 33ea541dea 424: onsuccess: #2128: 7: Success after binutils/gcc/linux/g [...] new f4ca890b6f 425: onsuccess: #2129: 7: Success after gcc/linux: 9 commits new bb1adc2130 426: onsuccess: #2130: 7: Success after gcc: 7 commits new 4c601beb2f 427: onsuccess: #2131: 7: Success after binutils/gcc/linux/g [...] new e27915c70d 428: onsuccess: #2132: 7: Success after binutils/linux/gdb: [...] new ea0bc185a3 429: onsuccess: #2133: 7: Success after binutils/gcc/linux/g [...] new 7ef1a6f771 430: onsuccess: #2134: 7: Success after binutils/gdb: 2 commits new 05a30f1d3f 431: onsuccess: #2135: 7: Success after binutils/gcc/glibc/g [...] new 9712092852 432: onsuccess: #2136: 7: Success after binutils/gcc/glibc/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 (84587f479d) \ 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 1696 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 30908 -> 31020 bytes 05-build_abe-stage1/console.log.xz | Bin 70900 -> 71544 bytes 07-build_abe-linux/console.log.xz | Bin 8320 -> 8344 bytes 08-build_abe-glibc/console.log.xz | Bin 243904 -> 243672 bytes 09-build_abe-stage2/console.log.xz | Bin 202344 -> 202628 bytes 10-build_abe-gdb/console.log.xz | Bin 38704 -> 38656 bytes 11-build_abe-qemu/console.log.xz | Bin 31876 -> 32312 bytes 12-check_regression/console.log.xz | Bin 4092 -> 4652 bytes 13-update_baseline/console.log | 32 ++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 44 +++++++++++++++++------------------ 21 files changed, 47 insertions(+), 47 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig updated (c919d1dd00 -> e38a56b78d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from c919d1dd00 43: onsuccess: #485: boot: Success after binutils/gcc/linux/ [...] new e38a56b78d 44: onsuccess: #486: boot: Success after binutils/gcc/qemu: [...] 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 1756 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31220 -> 30940 bytes 04-build_abe-stage1/console.log.xz | Bin 71352 -> 71508 bytes 05-build_abe-qemu/console.log.xz | Bin 31868 -> 32224 bytes 06-build_linux/console.log.xz | Bin 4332 -> 4336 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 4236 -> 4080 bytes 09-update_baseline/console.log | 9 +++++++++ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 17 files changed, 30 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (19005d19891 -> c22ff449275)

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 19005d19891 gdb: revert one erroneous bool-ification change new c22ff449275 opcodes: style m68k disassembler output 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: opcodes/m68k-dis.c | 354 +++++++++++++++++++++++++++++++++++------------------ 1 file changed, 238 insertions(+), 116 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-defconfig updated (b0135d8812 -> cdfcf03bd0)

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-defconfig in repository toolchain/ci/base-artifacts. from b0135d8812 41: onsuccess: #497: boot: Success after binutils/llvm/linux [...] new cdfcf03bd0 42: onsuccess: #498: boot: Success after binutils/llvm/qemu: [...] 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 1772 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30972 -> 31128 bytes 04-build_kernel_llvm/console.log.xz | Bin 66504 -> 66408 bytes 05-build_abe-qemu/console.log.xz | Bin 32100 -> 32356 bytes 06-build_linux/console.log.xz | Bin 3348 -> 3356 bytes 07-boot_linux/console.log.xz | Bin 6116 -> 6152 bytes 08-check_regression/console.log.xz | Bin 4340 -> 4008 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits February 2023