Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch master updated (0b2c1369d03 -> 1e7d2b2d22c)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 0b2c1369d03 PR target/107548: Handle vec_select in STV on x86. new 1e7d2b2d22c Fortran: Typo/unicode-o fixes The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/fortran/dump-parse-tree.cc | 2 +- gcc/fortran/trans-openmp.cc | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-master-aarch64-spec2k6-Os_LTO updated (9a35f7e408 -> 094726c36d)

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_llvm_apm/llvm-master-aarch64-spec2k6-Os_LTO in repository toolchain/ci/base-artifacts. from 9a35f7e408 34: onsuccess: #318: 1: [TCWG CI] No change after binutils/g [...] new 094726c36d 35: onsuccess: #323: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1844 -> 1840 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32256 -> 32224 bytes 04-build_abe-stage1/console.log.xz | Bin 75112 -> 74140 bytes 06-build_abe-linux/console.log.xz | Bin 8700 -> 8712 bytes 07-build_abe-glibc/console.log.xz | Bin 246180 -> 245540 bytes 08-build_abe-stage2/console.log.xz | Bin 187148 -> 180684 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 64704 -> 64620 bytes 10-benchmark/benchmark-build.log | 106 +- 10-benchmark/benchmark.log | 104 +- 10-benchmark/console.log.xz | Bin 3820 -> 3936 bytes 11-check_regression/console.log.xz | Bin 7804 -> 7712 bytes .../csv-results-vs-first-0/results.csv | 32160 +- .../csv-results-vs-first-0/size.csv | 344834 ++++++++--------- .../csv-results-vs-first-0/vect.csv | 19 - .../csv-results-vs-first-1/perf.csv | 164 +- .../csv-results-vs-first-1/results.csv | 56648 +-- .../csv-results-vs-first-1/size.csv | 320886 ++++++++-------- .../csv-results-vs-first-1/vect.csv | 19 - 11-check_regression/csv-results-vs-prev-0/perf.csv | 154 +- .../csv-results-vs-prev-0/results.csv | 49642 ++- 11-check_regression/csv-results-vs-prev-0/size.csv | 345967 +++++++++--------- 11-check_regression/csv-results-vs-prev-0/vect.csv | 11037 - 11-check_regression/csv-results-vs-prev-1/perf.csv | 164 +- .../csv-results-vs-prev-1/results.csv | 56648 +-- 11-check_regression/csv-results-vs-prev-1/size.csv | 320886 ++++++++-------- 11-check_regression/csv-results-vs-prev-1/vect.csv | 19 - 11-check_regression/results-vs-first-brief.csv | 48 +- 11-check_regression/results-vs-first-full.csv | 172 +- 11-check_regression/results-vs-first-internal.csv | 58 +- 11-check_regression/results-vs-first.csv | 58 +- 11-check_regression/results-vs-first.log | 872 +- 11-check_regression/results-vs-prev-brief.csv | 48 +- 11-check_regression/results-vs-prev-full.csv | 182 +- 11-check_regression/results-vs-prev-internal.csv | 58 +- 11-check_regression/results-vs-prev.csv | 58 +- 11-check_regression/results-vs-prev.log | 926 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metrics.json | 2 +- .../squad-vs-first/403.gcc/results-metadata.json | 18 +- .../squad-vs-first/429.mcf/results-metadata.json | 18 +- .../squad-vs-first/429.mcf/results-metrics.json | 2 +- .../squad-vs-first/433.milc/results-metadata.json | 18 +- .../squad-vs-first/444.namd/results-metadata.json | 18 +- .../squad-vs-first/444.namd/results-metrics.json | 2 +- .../squad-vs-first/445.gobmk/results-metadata.json | 18 +- .../squad-vs-first/445.gobmk/results-metrics.json | 2 +- .../447.dealII/results-metadata.json | 18 +- .../squad-vs-first/447.dealII/results-metrics.json | 2 +- .../450.soplex/results-metadata.json | 18 +- .../453.povray/results-metadata.json | 18 +- .../squad-vs-first/453.povray/results-metrics.json | 2 +- .../squad-vs-first/456.hmmer/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 18 +- .../462.libquantum/results-metadata.json | 18 +- .../462.libquantum/results-metrics.json | 2 +- .../464.h264ref/results-metadata.json | 18 +- .../squad-vs-first/470.lbm/results-metadata.json | 18 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 18 +- .../squad-vs-first/473.astar/results-metadata.json | 18 +- .../482.sphinx3/results-metadata.json | 18 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 18 +- .../squad-vs-first/Mean/results-metadata.json | 18 +- dashboard/squad-vs-first/Mean/results-metrics.json | 2 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 58 +- mail/mail-body.txt | 58 +- mail/mail-subject.txt | 2 +- manifest.sh | 42 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 2929656 -> 2646288 bytes save-temps/401.bzip2.tar.xz | Bin 301040 -> 243284 bytes save-temps/403.gcc.tar.xz | Bin 7625560 -> 6996296 bytes save-temps/410.bwaves.tar.xz | Bin 53080 -> 107112 bytes save-temps/416.gamess.tar.xz | Bin 17149476 -> 21432372 bytes save-temps/429.mcf.tar.xz | Bin 71796 -> 70156 bytes save-temps/433.milc.tar.xz | Bin 370604 -> 421756 bytes save-temps/434.zeusmp.tar.xz | Bin 530532 -> 1025228 bytes save-temps/435.gromacs.tar.xz | Bin 2368288 -> 2678788 bytes save-temps/436.cactusADM.tar.xz | Bin 1833968 -> 1798020 bytes save-temps/437.leslie3d.tar.xz | Bin 176528 -> 290888 bytes save-temps/444.namd.tar.xz | Bin 674188 -> 521928 bytes save-temps/445.gobmk.tar.xz | Bin 2723592 -> 2562484 bytes save-temps/447.dealII.tar.xz | Bin 11643184 -> 12582720 bytes save-temps/450.soplex.tar.xz | Bin 1472664 -> 1331376 bytes save-temps/453.povray.tar.xz | Bin 2672576 -> 2606192 bytes save-temps/454.calculix.tar.xz | Bin 3557816 -> 4963408 bytes save-temps/456.hmmer.tar.xz | Bin 988732 -> 856092 bytes save-temps/458.sjeng.tar.xz | Bin 322344 -> 322192 bytes save-temps/459.GemsFDTD.tar.xz | Bin 640068 -> 904484 bytes save-temps/462.libquantum.tar.xz | Bin 116332 -> 137584 bytes save-temps/464.h264ref.tar.xz | Bin 3324868 -> 2050556 bytes save-temps/465.tonto.tar.xz | Bin 8355464 -> 10743388 bytes save-temps/470.lbm.tar.xz | Bin 52176 -> 107576 bytes save-temps/471.omnetpp.tar.xz | Bin 1522300 -> 1474160 bytes save-temps/473.astar.tar.xz | Bin 160528 -> 153884 bytes save-temps/481.wrf.tar.xz | Bin 9113560 -> 11935268 bytes save-temps/482.sphinx3.tar.xz | Bin 586712 -> 578032 bytes save-temps/483.xalancbmk.tar.xz | Bin 17713580 -> 16441108 bytes 109 files changed, 773784 insertions(+), 768791 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (3e3d808679 -> be9b298c7d)

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 3e3d808679 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 10ec35f645 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] discards e6b563c9b6 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards bf63ef0787 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 781b367bc6 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 61ca898959 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 02123f1602 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 5b3a7146ac 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards e64d145095 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards b3d74c3675 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards 3acdbc60db 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards f342e5ff63 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards ed9de9461a 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 7f90d8be80 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 1097c2c82b 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards c1f4cf96bd 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards 0ce8c0e3df 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 622116593c 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards cf21709512 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards bc92ca7ab8 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards ca6615c384 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards d6f9e85f9d 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards ef7a6d8c30 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards f22b2c61a7 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 454019fe59 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards 06da2b7daa 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards a6d62e51d1 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 5b56f316f1 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards 544f0cc778 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards 3b6a654934 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards ccce411ab7 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards a044b674a5 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards d602bf7ba8 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards 019fd03aed 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards 2e74bb8995 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards a04738a280 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards e548258d82 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards feee083b87 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards e19a9eeb81 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards 68dea539f2 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 33e36c137a 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] discards 8cddd76df2 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] discards d74b29e27a 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] discards aefa053745 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards 3f21c52d92 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits discards 374b6ef458 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] discards 40faaabed0 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 34615cffc4 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] discards 80975b5ca9 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] discards 2dcb0060cc 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits discards e12d1e01c2 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 3398a06891 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] discards a3b369edde 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] discards a2a9e06866 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] discards 825031d7b9 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] discards 5ba6e32adc 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards 1598f3348e 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards a8f8bb5636 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] discards 5f91748d0a 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards fe1cefe21a 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] discards 232b9e9635 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards b6e8366af5 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] discards 8c5e17df91 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] discards 0cb4998305 220: force: #1948: 5: Success after gcc: 4 commits discards 1aca1687f0 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 0de0df4561 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards 5649f75bfa 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] discards c6f5db8930 216: onsuccess: #1940: 7: Success after linux: 12 commits discards d104855df4 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards c601143d40 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards d5be9f6f81 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 8d471a4ea5 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 760e827041 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards b3a4e4b917 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits discards 463f1c3e89 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] discards ee2cfe8bfa 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 765794f6a8 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] discards 7a5467c4aa 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] discards e74e8b533f 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] discards ef71b61afd 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] discards ca0dd8e12b 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] discards d4a274d752 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/g [...] discards 61ea070e78 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/g [...] discards caf92f5e9c 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/g [...] discards 49bfd9787c 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] discards 67507a5b4a 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] discards 21550ace7c 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] discards 4efd96a8f9 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards 16f59acfb9 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards f82c8c23f6 194: force: #1853: 7: Success after gcc: 26 commits discards 10defbf8d7 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards c4d47d5758 192: onsuccess: #1848: 7: Success after linux: 213 commits discards f96cbd212b 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards d811034a32 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards d10d34c6c9 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards a72750613c 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards 50bb4eaa54 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards b586ea4b33 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards a7ec4dc5cd 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards da28e3ca6d 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards 58543e0d01 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new 5ed09a6dbd 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new b581eba8fe 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new 5e10fe677b 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new ab503f584b 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 91129f6aee 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new 241ff7093e 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new 44d0d1ccec 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new fd40256dcf 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 232c5a6ad0 191: onsuccess: #1846: 7: Success after binutils: 4 commits new 0c5ee72656 192: onsuccess: #1848: 7: Success after linux: 213 commits new 23ef79b053 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 85113c1769 194: force: #1853: 7: Success after gcc: 26 commits new ad505a9a42 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new 0874ee6a9a 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 4292d43557 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] new 4c859b52ee 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] new a7b3b27db1 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] new 801fdd7c5a 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/g [...] new 3507617093 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/g [...] new 001a392408 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/g [...] new 2df08d5329 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] new 3aeb5eb0ad 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] new 576d1872a7 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] new 5d0cf0ac6b 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] new 9e4c864ade 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] new 5ce8e766f1 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new e6381e1bc2 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] new cc0a6d8741 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits new 6a8ed2438d 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new d7a6f92af6 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 2af73a1966 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 80959f9a8d 214: onsuccess: #1937: 7: Success after binutils: 4 commits new 8dfbf8778a 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 40376a54b7 216: onsuccess: #1940: 7: Success after linux: 12 commits new f2999c4f75 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] new a7b2fa6bb1 218: onsuccess: #1943: 5: Success after gdb: 3 commits new 9d045da658 219: onsuccess: #1945: 5: Success after binutils: 8 commits new d661d7bf82 220: force: #1948: 5: Success after gcc: 4 commits new 4b311819d4 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] new 00f1f285bd 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] new 6a132b5ad8 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new 8f36dd752e 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] new f475fab70b 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new b2356f3fd5 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] new 4e2222f3a9 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 5bc410a7fa 228: onsuccess: #1956: 7: Success after gcc: 5 commits new 70fdd6524e 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] new f2ca835eee 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] new b2bf8d4740 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] new ace1010229 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] new 483c559f8b 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 46a7eb0393 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits new cbfd5dad57 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] new d6258709a0 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] new a774a62a2c 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new 0a2c00ea87 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] new befb935311 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits new 513461e1b5 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new c70a637e0c 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] new 23caeaea3d 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new f39511332b 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new b59e57fa56 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 536042662a 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new 5904b72e12 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new efeb598cfd 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new 829786aecc 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 61bf065b5f 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new 2565370483 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new acf57ce6e1 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 18c8494893 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new 8e24a19957 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new f42c968690 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 3056b4180d 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new a3b6cdb343 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new 0a535cd5b2 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new afd444ad28 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 0a7a5f36ed 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new ca2c4bde03 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new baca214529 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new 2ef1fae756 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new d8d8becf88 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new cd2f6d619f 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new a449ea6f1c 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new ecc9e8ee09 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new 65c9d0a819 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new ee4dedc5c6 268: onsuccess: #1997: 7: Success after glibc: 2 commits new a49eb8af37 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new ac04d8b834 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 1d9325a781 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new 5f0ee11bbc 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 145bc4610d 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 043ffd2079 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 0bf0df38a6 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 34d9559680 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new 86ddac9735 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new d9064dc1cf 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new 4707201fbb 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 44adb99896 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new f094ab90ba 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 1cd89ce929 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] new 45cb822803 283: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new be9b298c7d 284: onsuccess: #2013: 7: Success after binutils/gcc/gdb: 33 [...] 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 (3e3d808679) \ 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 1688 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 31968 -> 31716 bytes 05-build_abe-stage1/console.log.xz | Bin 92040 -> 92080 bytes 07-build_abe-linux/console.log.xz | Bin 8760 -> 8772 bytes 08-build_abe-glibc/console.log.xz | Bin 236544 -> 237060 bytes 09-build_abe-stage2/console.log.xz | Bin 228336 -> 228276 bytes 10-build_abe-gdb/console.log.xz | Bin 39220 -> 39240 bytes 11-build_abe-qemu/console.log.xz | Bin 31248 -> 31044 bytes 12-check_regression/console.log.xz | Bin 4444 -> 3820 bytes 13-update_baseline/console.log | 54 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++------------ 19 files changed, 52 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto updated (47df45d267 -> 6cb502bf11)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-aarch64-bootstrap_profiled_lto in repository toolchain/ci/base-artifacts. discards 47df45d267 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits discards c9ac9eedf1 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits discards 673ec7b7a5 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits discards dec26eebd1 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits discards 4a5974c1d2 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits discards cbe303ac5c 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits discards 4e4cdfd5fc 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits discards 8be5a09cef 120: onsuccess: #535: 1: Success after binutils: 10 commits discards 39e4bc88e3 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] discards af6b60dfe6 118: force: #533: 2: Success after binutils: 4 commits discards 72f7c4531e 117: onsuccess: #531: 2: Success after gcc: 65 commits discards b779f121ad 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits discards 2359c78382 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits discards fe612a021e 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits discards 64b4dbc29e 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits discards e61d822cdf 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits discards 8f81e384ae 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits discards 0efb4b1512 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits discards 1ba934c1e8 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits discards d11c50af95 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits discards 1d82c66aad 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits discards 290043c0e1 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits discards c213837196 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits discards aefd4e4606 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits discards 7dbb3c5345 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits discards c2d692ca64 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits discards 701ef0a26f 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits discards 71f676aa3b 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits discards c5ff24840f 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits discards fc64d2986a 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits discards 4280b51976 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits discards 5dc1ad5ed7 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits discards 11faa12996 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits discards efff49a178 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits discards c2d546743e 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits discards b6953a5d05 92: onsuccess: #499: 2: Success after binutils: 4 commits discards a79c2a5d89 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits discards 3f15b448bf 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits discards 8fb007183a 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits discards 385d11c2a6 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits discards 0f1b318f89 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits discards 78e81a4dd5 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits discards a7f972a602 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits discards 2d0a29d43a 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits discards e1cbe18fc3 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits discards a2ab499d48 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits discards 65f4c84f17 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits discards 5b471e00b1 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits discards 16c5982f64 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits discards 8fe7b381f2 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits discards fc975dea02 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits discards b6250277a3 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits discards 7eb2c4aec5 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits discards de41580521 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits discards 1215969bed 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits discards f1b2d92a3c 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits discards e8216ccc36 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits discards f608eac84e 70: onsuccess: #475: 2: Success after binutils/gcc: 44 commits discards 83e2b52d8a 69: onsuccess: #474: 2: Success after binutils/gcc: 46 commits discards f3e096c558 68: onsuccess: #473: 2: Success after binutils/gcc: 9 commits discards fa51d7a737 67: onsuccess: #472: 2: Success after binutils/gcc: 5 commits discards 90b72a306f 66: onsuccess: #471: 2: Success after binutils/gcc: 53 commits discards 4a7aa7f839 65: onsuccess: #470: 2: Success after binutils/gcc: 28 commits discards 73538e8fc6 64: onsuccess: #469: 2: Success after binutils/gcc: 41 commits discards a9fdc3ee8a 63: onsuccess: #468: 2: Success after binutils/gcc: 61 commits discards cc1a918347 62: onsuccess: #467: 1: Success after binutils/gcc: 50 commits discards 66bcd56422 61: onsuccess: #466: 1: Success after binutils/gcc: 12 commits discards ccb684b6ac 60: onsuccess: #465: 1: Success after basepoints/gcc-13-3173 [...] discards a5783a4ced 59: force: #464: 1: Failure after basepoints/gcc-13-3172-gf3 [...] discards 0632737743 58: force: #463: 2: Success after gcc: 30 commits discards de383ddd1c 57: onsuccess: #460: 2: Success after binutils: 8 commits discards 5db6a88738 56: onsuccess: #458: 2: Success after binutils/gcc: 54 commits discards eeba9ef3e3 55: onsuccess: #457: 2: Success after binutils/gcc: 30 commits discards becbcb09cb 54: onsuccess: #456: 2: Success after binutils/gcc: 47 commits discards 065d804394 53: onsuccess: #455: 2: Success after binutils/gcc: 34 commits discards 61739e08cc 52: onsuccess: #454: 2: Success after binutils/gcc: 183 commits discards 3dcb749ee7 51: onsuccess: #453: 1: Success after gcc: 20 commits discards a8f031c09a 50: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] discards 6efa50e7a9 49: force: #451: 2: Success after basepoints/gcc-13-2886-g8b [...] discards aee9df4fee 48: onsuccess: #448: 2: Success after binutils: 6 commits discards 8bfdfe1036 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits discards 558db30c48 46: onsuccess: #445: 2: Success after binutils/gcc: 12 commits discards 217a85b1fe 45: onsuccess: #444: 2: Success after binutils/gcc: 9 commits discards b0d5c0ce5d 44: onsuccess: #443: 2: Success after binutils/gcc: 100 commits discards 023100400f 43: onsuccess: #441: 2: Success after binutils/gcc: 36 commits discards 9444eeb964 42: onsuccess: #440: 2: Success after binutils/gcc: 41 commits discards c512c04a4f 41: onsuccess: #439: 2: Success after binutils/gcc: 8 commits discards 3b15355b0d 40: onsuccess: #438: 2: Success after binutils/gcc: 7 commits discards 1a9a9aa3d6 39: onsuccess: #437: 2: Success after binutils/gcc: 6 commits discards 5d995d15f5 38: onsuccess: #436: 2: Success after binutils/gcc: 25 commits discards 7f0c21ad90 37: onsuccess: #435: 2: Success after binutils/gcc: 19 commits discards 0d6b5dba5c 36: onsuccess: #434: 2: Success after binutils/gcc: 34 commits discards b88c154778 35: onsuccess: #433: 2: Success after binutils/gcc: 29 commits discards f191e619a5 34: onsuccess: #432: 2: Success after binutils/gcc: 68 commits discards 362fdbdeb1 33: onsuccess: #431: 2: Success after binutils/gcc: 4 commits discards ad0a265ef0 32: onsuccess: #430: 2: Success after binutils/gcc: 7 commits discards e33b97a7db 31: onsuccess: #429: 2: Success after binutils/gcc: 25 commits discards 0c5b1d4a09 30: onsuccess: #428: 2: Success after binutils/gcc: 30 commits discards 08ff8eed14 29: onsuccess: #427: 2: Success after binutils/gcc: 34 commits discards 267f5ee11b 28: onsuccess: #426: 2: Success after binutils/gcc: 60 commits discards 52f4d6d58a 27: onsuccess: #425: 2: Success after binutils/gcc: 64 commits new 1bc0814a35 27: onsuccess: #425: 2: Success after binutils/gcc: 64 commits new 071a3e5d9f 28: onsuccess: #426: 2: Success after binutils/gcc: 60 commits new 7fac56c5ef 29: onsuccess: #427: 2: Success after binutils/gcc: 34 commits new e9f713a78c 30: onsuccess: #428: 2: Success after binutils/gcc: 30 commits new f1c19d599d 31: onsuccess: #429: 2: Success after binutils/gcc: 25 commits new 1011a01587 32: onsuccess: #430: 2: Success after binutils/gcc: 7 commits new 870e40edd4 33: onsuccess: #431: 2: Success after binutils/gcc: 4 commits new bed0fa4e1e 34: onsuccess: #432: 2: Success after binutils/gcc: 68 commits new 5b1ad1491b 35: onsuccess: #433: 2: Success after binutils/gcc: 29 commits new 5deac1a5f6 36: onsuccess: #434: 2: Success after binutils/gcc: 34 commits new 3063cbcec1 37: onsuccess: #435: 2: Success after binutils/gcc: 19 commits new c0f61e1ef8 38: onsuccess: #436: 2: Success after binutils/gcc: 25 commits new 795cc79a77 39: onsuccess: #437: 2: Success after binutils/gcc: 6 commits new 54f8ef8222 40: onsuccess: #438: 2: Success after binutils/gcc: 7 commits new e88c56f645 41: onsuccess: #439: 2: Success after binutils/gcc: 8 commits new a9f858c45b 42: onsuccess: #440: 2: Success after binutils/gcc: 41 commits new a8606348eb 43: onsuccess: #441: 2: Success after binutils/gcc: 36 commits new 7871eb35bd 44: onsuccess: #443: 2: Success after binutils/gcc: 100 commits new 8e380cb4c7 45: onsuccess: #444: 2: Success after binutils/gcc: 9 commits new 62bf37113a 46: onsuccess: #445: 2: Success after binutils/gcc: 12 commits new ffe92cea24 47: onsuccess: #446: 2: Success after binutils/gcc: 54 commits new fc3b6af207 48: onsuccess: #448: 2: Success after binutils: 6 commits new 2b972af3c5 49: force: #451: 2: Success after basepoints/gcc-13-2886-g8b [...] new e9f630c826 50: force: #452: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new 4ce926cc74 51: onsuccess: #453: 1: Success after gcc: 20 commits new ba5080e002 52: onsuccess: #454: 2: Success after binutils/gcc: 183 commits new 656e95ecf0 53: onsuccess: #455: 2: Success after binutils/gcc: 34 commits new 7c7eb3f983 54: onsuccess: #456: 2: Success after binutils/gcc: 47 commits new c15469cbbe 55: onsuccess: #457: 2: Success after binutils/gcc: 30 commits new d29dffdb42 56: onsuccess: #458: 2: Success after binutils/gcc: 54 commits new c8f187bead 57: onsuccess: #460: 2: Success after binutils: 8 commits new 676be4b0b6 58: force: #463: 2: Success after gcc: 30 commits new d376851f89 59: force: #464: 1: Failure after basepoints/gcc-13-3172-gf3 [...] new e3e9e0362c 60: onsuccess: #465: 1: Success after basepoints/gcc-13-3173 [...] new 5d5662d13f 61: onsuccess: #466: 1: Success after binutils/gcc: 12 commits new a8e27fc586 62: onsuccess: #467: 1: Success after binutils/gcc: 50 commits new 427f1094e2 63: onsuccess: #468: 2: Success after binutils/gcc: 61 commits new 44175d7b29 64: onsuccess: #469: 2: Success after binutils/gcc: 41 commits new 8197e63d39 65: onsuccess: #470: 2: Success after binutils/gcc: 28 commits new 7e6d1c89e6 66: onsuccess: #471: 2: Success after binutils/gcc: 53 commits new 7be81ca661 67: onsuccess: #472: 2: Success after binutils/gcc: 5 commits new 4147a0bca7 68: onsuccess: #473: 2: Success after binutils/gcc: 9 commits new ec1532cfaa 69: onsuccess: #474: 2: Success after binutils/gcc: 46 commits new e233d8ce40 70: onsuccess: #475: 2: Success after binutils/gcc: 44 commits new d872293f05 71: onsuccess: #476: 2: Success after binutils/gcc: 47 commits new aa57869d0f 72: onsuccess: #477: 2: Success after binutils/gcc: 47 commits new edeb47941a 73: onsuccess: #478: 2: Success after binutils/gcc: 39 commits new 51de579edf 74: onsuccess: #479: 2: Success after binutils/gcc: 6 commits new dbb7c726e5 75: onsuccess: #480: 2: Success after binutils/gcc: 6 commits new 57476ed993 76: onsuccess: #481: 2: Success after binutils/gcc: 76 commits new c874f819fc 77: onsuccess: #482: 2: Success after binutils/gcc: 34 commits new 5fff9c928b 78: onsuccess: #483: 2: Success after binutils/gcc: 30 commits new 5bc2e08a15 79: onsuccess: #484: 2: Success after binutils/gcc: 34 commits new 4897c7884b 80: onsuccess: #485: 2: Success after binutils/gcc: 24 commits new d272735831 81: onsuccess: #486: 2: Success after binutils/gcc: 3 commits new 7f174a6a8b 82: onsuccess: #488: 2: Success after binutils/gcc: 65 commits new 4c3734d8d2 83: onsuccess: #489: 2: Success after binutils/gcc: 33 commits new 6cc4481572 84: onsuccess: #490: 2: Success after binutils/gcc: 42 commits new 6cec06d63c 85: onsuccess: #491: 2: Success after binutils/gcc: 71 commits new 7ba71fecba 86: onsuccess: #492: 2: Success after binutils/gcc: 22 commits new 9d053c4211 87: onsuccess: #493: 2: Success after binutils/gcc: 13 commits new 759ecc475b 88: onsuccess: #494: 2: Success after binutils/gcc: 139 commits new 442efa7971 89: onsuccess: #495: 2: Success after binutils/gcc: 62 commits new 0ed200d089 90: onsuccess: #496: 2: Success after binutils/gcc: 49 commits new a587cd864e 91: onsuccess: #497: 2: Success after binutils/gcc: 58 commits new de4e7ad8ac 92: onsuccess: #499: 2: Success after binutils: 4 commits new 264b11c960 93: onsuccess: #501: 2: Success after binutils/gcc: 301 commits new b502c9e0b2 94: onsuccess: #502: 2: Success after binutils/gcc: 37 commits new afe185f1e2 95: onsuccess: #506: 2: Success after binutils/gcc: 29 commits new 58205c7843 96: onsuccess: #507: 2: Success after binutils/gcc: 55 commits new 815798257e 97: onsuccess: #508: 2: Success after binutils/gcc: 46 commits new 8c460b7e51 98: onsuccess: #509: 2: Success after binutils/gcc: 27 commits new 46d2c52f6f 99: onsuccess: #510: 2: Success after binutils/gcc: 48 commits new d7de18017d 100: onsuccess: #512: 2: Success after binutils/gcc: 27 commits new 5a2c43449b 101: onsuccess: #513: 2: Success after binutils/gcc: 6 commits new bcb57d1033 102: onsuccess: #514: 2: Success after binutils/gcc: 118 commits new 349f6fc2d8 103: onsuccess: #515: 2: Success after binutils/gcc: 22 commits new e4074a299b 104: onsuccess: #516: 2: Success after binutils/gcc: 44 commits new dbe644cc01 105: onsuccess: #517: 2: Success after binutils/gcc: 52 commits new 2e577040ef 106: onsuccess: #518: 2: Success after binutils/gcc: 31 commits new e8918ad0fd 107: onsuccess: #519: 2: Success after binutils/gcc: 8 commits new 91f5f6977a 108: onsuccess: #520: 2: Success after binutils/gcc: 13 commits new bd0551a7a1 109: onsuccess: #521: 2: Success after binutils/gcc: 32 commits new 2e49f8ff93 110: onsuccess: #522: 2: Success after binutils/gcc: 47 commits new 8c350697a0 111: onsuccess: #523: 2: Success after binutils/gcc: 26 commits new 1173ac72b3 112: onsuccess: #524: 2: Success after binutils/gcc: 32 commits new aea1ba61bb 113: onsuccess: #525: 2: Success after binutils/gcc: 35 commits new 5a84ba2a36 114: onsuccess: #526: 2: Success after binutils/gcc: 3 commits new bba5c9c05d 115: onsuccess: #527: 2: Success after binutils/gcc: 11 commits new 7acde866a5 116: onsuccess: #528: 2: Success after binutils/gcc: 48 commits new f2a727e7e4 117: onsuccess: #531: 2: Success after gcc: 65 commits new ae5ed9c56f 118: force: #533: 2: Success after binutils: 4 commits new 0e463e5a9a 119: force: #534: 1: Failure after gdb-12-branchpoint-3046-g [...] new ddda455f30 120: onsuccess: #535: 1: Success after binutils: 10 commits new 32efb051eb 121: onsuccess: #536: 1: Success after binutils/gcc: 76 commits new ac9a52ca85 122: onsuccess: #537: 2: Success after binutils/gcc: 36 commits new 98f2f2a655 123: onsuccess: #538: 2: Success after binutils/gcc: 14 commits new 522a9b120b 124: onsuccess: #539: 2: Success after binutils/gcc: 9 commits new 24c88edc71 125: onsuccess: #540: 2: Success after binutils/gcc: 53 commits new 7b81d2a136 126: onsuccess: #541: 2: Success after binutils/gcc: 17 commits new 92e15c27e9 127: onsuccess: #542: 2: Success after binutils/gcc: 66 commits new 6cb502bf11 128: onsuccess: #543: 2: Success after binutils/gcc: 52 commits This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (47df45d267) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-aar [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1744 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 39860 -> 39528 bytes 05-build_abe-bootstrap_profiled_lto/console.log.xz | Bin 531004 -> 532508 bytes 06-check_regression/console.log.xz | Bin 3016 -> 3096 bytes 07-update_baseline/console.log | 64 ++++++++++----------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +++---- 13 files changed, 48 insertions(+), 48 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm updated (d6329ba605 -> 48e70a22a2)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-arm in repository toolchain/ci/base-artifacts. discards d6329ba605 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] discards 46a994d17f 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] discards 3b501572c2 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] discards 97764872da 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] discards 02ed1a8580 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 7c5958be77 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards 42518d02da 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards d490c809e6 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] discards 164892f879 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] discards bb8ae502b5 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] discards 383520ed5e 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] discards 34fa7b62b4 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] discards 5fb6c7f673 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] discards 811ac8ed4f 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] discards 6941d014b2 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards b338355e4f 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards de9152c051 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] discards 3b1202b7bc 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] discards 086415d428 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 5096fb5ee8 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] discards 2eb35818ea 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] discards 71e7337426 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] discards 777b7fb8d0 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] discards c1997730cb 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] discards 07f5ac328f 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] discards c76cd8765f 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] discards 281ee521ce 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] discards 489017a396 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] discards ca80e4a54e 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits discards c8285dbe84 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] discards 59c88af62c 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] discards 2e1724a471 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] discards f5ea9de675 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] discards 9e1ee6f32d 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] discards 337d0106e5 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] discards b44d535931 104: onsuccess: #530: 1: Success after gcc: 7 commits discards 9216064a77 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 7b2579d069 102: onsuccess: #527: 1: Success after binutils: 5 commits discards a12bca8f4e 101: onsuccess: #524: 1: Success after binutils: 2 commits discards 5baa47e6be 100: onsuccess: #521: 1: Success after binutils: 10 commits discards a16206ca83 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards cdc21b1b93 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] discards 7a9646e3f0 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards edfcf91bf8 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards 8f22b92d1a 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] discards 8492a765a0 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] discards 9a54ff5aeb 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards f4dd598001 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] discards bf0518a3d5 91: onsuccess: #511: 1: Success after linux: 27 commits discards eddabd94e4 90: onsuccess: #510: 1: Success after glibc: 5 commits discards ebe49acfda 89: onsuccess: #508: 1: Success after binutils: 12 commits discards 1e56ace188 88: onsuccess: #506: 1: Success after linux: 34 commits discards d940a46402 87: onsuccess: #505: 1: Success after glibc: 7 commits discards 40368941c4 86: onsuccess: #503: 1: Success after binutils: 12 commits discards faba783fe1 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards b6d6341ac0 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards a4f633a208 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] discards ae5a54db52 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] discards b4581ffb65 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards bb106cd039 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards 129a04070f 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 00a05a8afb 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] discards 31828fc9f5 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] discards 1c7895fa9b 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] discards 06ff731e8a 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] discards 21e800418a 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] discards 43c255e17a 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] discards 19a4a88aac 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] discards d89e8ee449 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] discards 72b1a971c5 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] discards a7370c4ecd 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards f28ea761cc 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] discards 05db803403 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 4a8b9f809c 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] discards c4aead1e48 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] discards 5b2a034c3e 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards 17df1c467a 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] discards c086ee0522 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] discards d588c8d04a 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] discards 86591342c1 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] discards d91443fecf 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] discards f582fb82af 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] discards 6786c6f966 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] discards 2fa54cbba7 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] discards d77072fbf8 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] discards 076bcb9d41 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] discards aaa8300de1 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] discards f156f67bfe 52: onsuccess: #467: 1: Success after binutils: 9 commits discards 1e635ba813 51: onsuccess: #464: 1: Success after binutils: 6 commits discards eb6ec1dd13 50: onsuccess: #461: 1: Success after binutils: 12 commits discards d5d3f8709b 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] discards 5ebeff2605 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] discards 2b7548cc18 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards fc4afda078 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 2a25e4bdbc 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] discards dc78471ce4 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] discards c5e2b1cae6 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] discards 5ff2457a2c 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] discards 6af6e34af6 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] discards 1297ea24eb 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] discards 186ec2772e 39: onsuccess: #447: 1: Success after binutils: 5 commits new d852a0d156 39: onsuccess: #447: 1: Success after binutils: 5 commits new 86a7b0a418 40: onsuccess: #449: 1: Success after glibc-2.36.9000-121-g5 [...] new 8538cc11d6 41: onsuccess: #450: 1: Success after binutils/gcc/linux/gli [...] new c74409cdd1 42: onsuccess: #451: 1: Success after binutils/gcc/glibc/gdb [...] new 801b3d9d2a 43: onsuccess: #452: 1: Success after binutils/gcc/linux/gdb [...] new 049c71b775 44: onsuccess: #453: 1: Success after binutils/gcc/glibc/gdb [...] new 3c43bc6381 45: onsuccess: #454: 1: Success after binutils/gcc/linux/gli [...] new 0d15a240a5 46: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 8c2e78f12e 47: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 9a656c0753 48: onsuccess: #458: 1: Success after binutils/gcc/linux/gdb [...] new 60aa750228 49: onsuccess: #459: 1: Success after binutils/gcc/linux/gdb [...] new 5d241c1384 50: onsuccess: #461: 1: Success after binutils: 12 commits new c0877b90d6 51: onsuccess: #464: 1: Success after binutils: 6 commits new 56c9e7ec38 52: onsuccess: #467: 1: Success after binutils: 9 commits new 096b2a8f9e 53: onsuccess: #469: 1: Success after binutils/gcc/linux/gli [...] new e4fb8885c7 54: onsuccess: #470: 1: Success after binutils/gcc/linux/gli [...] new c02f890d88 55: onsuccess: #471: 1: Success after binutils/gcc/linux/gli [...] new 616ca514ec 56: onsuccess: #472: 1: Success after binutils/gcc/linux/gdb [...] new dab8020e2e 57: onsuccess: #473: 1: Success after binutils/gcc/linux/gli [...] new 5441204552 58: onsuccess: #474: 1: Success after binutils/gcc/linux/gli [...] new b2cd5d98a2 59: onsuccess: #475: 1: Success after binutils/gcc/linux/gli [...] new d72f0a6bff 60: onsuccess: #476: 1: Success after binutils/gcc/linux/gli [...] new b258bc7ef8 61: onsuccess: #477: 1: Success after binutils/gcc/linux/gli [...] new 483b197d95 62: onsuccess: #478: 1: Success after binutils/gcc/linux/gli [...] new 6b786f67c1 63: onsuccess: #479: 1: Success after binutils/gcc/linux/gli [...] new 6eb661763c 64: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 58ff13fc9c 65: onsuccess: #481: 1: Success after binutils/gcc/linux/gdb [...] new fcd52f7c94 66: onsuccess: #482: 1: Success after binutils/gcc/linux/gli [...] new 1a5ab6639e 67: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 5535e84d65 68: onsuccess: #484: 1: Success after binutils/gcc/linux/gli [...] new 54e0a1c658 69: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new d41d073a97 70: onsuccess: #486: 1: Success after binutils/gcc/linux/gli [...] new c335354f3c 71: onsuccess: #487: 1: Success after binutils/gcc/linux/gdb [...] new 5a506c8152 72: onsuccess: #488: 1: Success after binutils/gcc/linux/gli [...] new 5061e4c75e 73: onsuccess: #489: 1: Success after binutils/gcc/glibc/gdb [...] new 13a25c378b 74: onsuccess: #490: 1: Success after binutils/gcc/linux/gli [...] new e5e881120a 75: onsuccess: #491: 1: Success after binutils/gcc/linux/gdb [...] new 02fc581d04 76: onsuccess: #492: 1: Success after binutils/gcc/linux/gdb [...] new 65d9b0efe5 77: onsuccess: #493: 1: Success after binutils/gcc/linux/gdb [...] new b239434b79 78: onsuccess: #494: 1: Success after binutils/gcc/linux/gli [...] new 7657b0e445 79: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new 7bf2bec380 80: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new c6eb3e9881 81: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new af5b5ce18d 82: onsuccess: #498: 1: Success after binutils/gcc/linux/gli [...] new b371e92d98 83: onsuccess: #499: 1: Success after binutils/gcc/linux/gdb [...] new 57f8bf8629 84: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 920317dfdf 85: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new c3b561c92d 86: onsuccess: #503: 1: Success after binutils: 12 commits new 4d23ec1a46 87: onsuccess: #505: 1: Success after glibc: 7 commits new a30f031add 88: onsuccess: #506: 1: Success after linux: 34 commits new 8acff65794 89: onsuccess: #508: 1: Success after binutils: 12 commits new b31f74818a 90: onsuccess: #510: 1: Success after glibc: 5 commits new fdc7012606 91: onsuccess: #511: 1: Success after linux: 27 commits new 65e96e1ae9 92: onsuccess: #512: 1: Success after binutils/gcc/linux/gli [...] new aeab9e6f15 93: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new d888c43039 94: onsuccess: #514: 1: Success after binutils/gcc/linux/gdb [...] new 43f3e453a8 95: onsuccess: #515: 1: Success after binutils/gcc/linux/gdb [...] new 72dd3af9ba 96: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new aaaf86e312 97: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 624a6a3036 98: onsuccess: #518: 1: Success after binutils/gcc/linux/gli [...] new 76b9c8f5d9 99: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new 039863e323 100: onsuccess: #521: 1: Success after binutils: 10 commits new f0ca82864c 101: onsuccess: #524: 1: Success after binutils: 2 commits new 35314f1eb6 102: onsuccess: #527: 1: Success after binutils: 5 commits new a967a788d5 103: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new c41076b6ea 104: onsuccess: #530: 1: Success after gcc: 7 commits new 0315910c9a 105: onsuccess: #531: 1: Success after binutils/gcc/linux/gd [...] new a5e27970be 106: onsuccess: #532: 1: Success after binutils/gcc/linux/gl [...] new a51e1be137 107: onsuccess: #533: 1: Success after binutils/gcc/linux/gd [...] new e3ca6d6776 108: onsuccess: #534: 1: Success after binutils/gcc/linux/gd [...] new 88bff2d9ab 109: onsuccess: #535: 1: Success after binutils/gcc/linux/gd [...] new c7de524883 110: onsuccess: #536: 1: Success after binutils/gcc/glibc/gd [...] new fac062e5e9 111: onsuccess: #537: 1: Success after binutils/gcc/gdb: 69 commits new 7a4bb0bcce 112: onsuccess: #538: 1: Success after binutils/gcc/linux/gd [...] new 8a59b9290c 113: onsuccess: #539: 1: Success after binutils/gcc/linux/gd [...] new c771dd3eb2 114: onsuccess: #541: 1: Success after binutils/gcc/linux/gd [...] new 15fc40fb21 115: onsuccess: #542: 1: Success after binutils/gcc/linux/gl [...] new ef76d04715 116: onsuccess: #543: 1: Success after binutils/gcc/linux/gl [...] new 505494b3e8 117: onsuccess: #544: 1: Success after binutils/gcc/linux/gl [...] new f64c2f4368 118: onsuccess: #545: 1: Success after binutils/gcc/linux/gd [...] new f02660d514 119: onsuccess: #546: 1: Success after binutils/gcc/linux/gd [...] new 30aaac4e1a 120: onsuccess: #547: 1: Success after binutils/gcc/linux/gl [...] new 3bf5601089 121: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new dc12d229e8 122: onsuccess: #549: 1: Success after binutils/gcc/linux/gd [...] new 59f7cb1d88 123: onsuccess: #550: 1: Success after binutils/gcc/linux/gd [...] new e466cde023 124: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 01e919b2ae 125: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new 1887bb3af5 126: onsuccess: #553: 1: Success after binutils/gcc/linux/gl [...] new 6ec55e04ab 127: onsuccess: #554: 1: Success after binutils/gcc/linux/gl [...] new d945f65d05 128: onsuccess: #555: 1: Success after binutils/gcc/linux/gd [...] new c384b54312 129: onsuccess: #556: 1: Success after binutils/gcc/linux/gd [...] new f92d6abfa3 130: onsuccess: #557: 1: Success after binutils/gcc/linux/gl [...] new 48906f5f8d 131: onsuccess: #558: 1: Success after binutils/gcc/linux/gl [...] new 13a5d41f84 132: onsuccess: #559: 1: Success after binutils/gcc/linux/gd [...] new 5eff371ab2 133: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 9fa7ef5d67 134: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new eadb43fa94 135: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new 4039d3a9d2 136: onsuccess: #563: 1: Success after binutils/gcc/glibc/gd [...] new 7e9e1c8fcc 137: onsuccess: #564: 1: Success after binutils/gcc/linux/gl [...] new b2179b6a59 138: onsuccess: #565: 1: Success after binutils/gcc/linux/gl [...] new f04b513417 139: onsuccess: #566: 1: Success after binutils/gcc/linux/gl [...] new 48e70a22a2 140: onsuccess: #567: 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 (d6329ba605) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2736 bytes 03-build_abe-binutils/console.log.xz | Bin 54008 -> 52416 bytes 04-build_abe-gcc/console.log.xz | Bin 235836 -> 238636 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8528 -> 8788 bytes 07-build_abe-glibc/console.log.xz | Bin 236644 -> 236760 bytes 08-build_abe-gdb/console.log.xz | Bin 52280 -> 51600 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3820 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2192 -> 2180 bytes 11-check_regression/console.log.xz | Bin 6028 -> 6240 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 36 +-- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++-- sumfiles/binutils.log.xz | Bin 62884 -> 62576 bytes sumfiles/binutils.sum | 62 +++--- sumfiles/gas.log.xz | Bin 100472 -> 100504 bytes sumfiles/gas.sum | 272 +++++++++++------------ sumfiles/ld.log.xz | Bin 132420 -> 132416 bytes sumfiles/ld.sum | 344 ++++++++++++++--------------- 30 files changed, 392 insertions(+), 392 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk_llvm_apm/llvm-release-arm-spec2k6-Os updated (e87684a8ec -> 59002cf738)

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_llvm_apm/llvm-release-arm-spec2k6-Os in repository toolchain/ci/base-artifacts. from e87684a8ec 29: onsuccess: #163: 1: [TCWG CI] No change after v6.0.10-41 [...] new 59002cf738 30: onsuccess: #166: 1: [TCWG CI] No change after binutils/g [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1700 -> 1824 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2780 bytes 03-build_abe-binutils/console.log.xz | Bin 30420 -> 30036 bytes 04-build_abe-stage1/console.log.xz | Bin 87880 -> 87376 bytes 05-clean_sysroot/console.log.xz | Bin 336 -> 336 bytes 06-build_abe-linux/console.log.xz | Bin 8708 -> 7948 bytes 07-build_abe-glibc/console.log.xz | Bin 232140 -> 231076 bytes 08-build_abe-stage2/console.log.xz | Bin 211804 -> 208596 bytes 09-build_llvm-true-false-/console.log.xz | Bin 60620 -> 0 bytes 09-build_llvm-true-false-cflags-/console.log.xz | Bin 0 -> 60220 bytes 10-benchmark/benchmark-build.log | 106 +- 10-benchmark/benchmark.log | 104 +- 10-benchmark/console.log.xz | Bin 3832 -> 3996 bytes 11-check_regression/console.log.xz | Bin 10360 -> 12560 bytes .../csv-results-vs-first-0/md5sum.csv | 1754 +- .../csv-results-vs-first-0/results.csv | 413192 ++++++++--------- .../csv-results-vs-first-0/size.csv | 416010 +++++++++--------- .../csv-results-vs-first-0/vect.csv | 19 - .../csv-results-vs-first-1/md5sum.csv | 1931 +- .../csv-results-vs-first-1/perf.csv | 2585 +- .../csv-results-vs-first-1/results.csv | 399815 +++++++++-------- .../csv-results-vs-first-1/size.csv | 395164 ++++++++--------- .../csv-results-vs-first-1/vect.csv | 10208 - .../csv-results-vs-prev-0/md5sum.csv | 2152 +- 11-check_regression/csv-results-vs-prev-0/perf.csv | 2496 +- .../csv-results-vs-prev-0/results.csv | 402982 +++++++++-------- 11-check_regression/csv-results-vs-prev-0/size.csv | 395164 ++++++++--------- 11-check_regression/csv-results-vs-prev-0/vect.csv | 20308 +- .../csv-results-vs-prev-1/md5sum.csv | 1931 +- 11-check_regression/csv-results-vs-prev-1/perf.csv | 2585 +- .../csv-results-vs-prev-1/results.csv | 399815 +++++++++-------- 11-check_regression/csv-results-vs-prev-1/size.csv | 395164 ++++++++--------- 11-check_regression/csv-results-vs-prev-1/vect.csv | 10208 - 11-check_regression/mail-body.txt | 5 - 11-check_regression/results-vs-first-brief.csv | 48 +- 11-check_regression/results-vs-first-full.csv | 2561 +- 11-check_regression/results-vs-first-internal.csv | 172 +- 11-check_regression/results-vs-first.csv | 172 +- 11-check_regression/results-vs-first.log | 928 +- 11-check_regression/results-vs-prev-brief.csv | 42 +- 11-check_regression/results-vs-prev-compare.csv | 1 + 11-check_regression/results-vs-prev-full.csv | 2667 +- 11-check_regression/results-vs-prev-internal.csv | 166 +- 11-check_regression/results-vs-prev.csv | 166 +- 11-check_regression/results-vs-prev.log | 931 +- dashboard/dashboard-generate.sh | 2 +- .../400.perlbench/results-metadata.json | 18 +- .../squad-vs-first/401.bzip2/results-metadata.json | 18 +- .../squad-vs-first/403.gcc/results-metadata.json | 18 +- .../squad-vs-first/403.gcc/results-metrics.json | 2 +- .../squad-vs-first/429.mcf/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metadata.json | 18 +- .../squad-vs-first/433.milc/results-metrics.json | 2 +- .../squad-vs-first/444.namd/results-metadata.json | 18 +- .../squad-vs-first/445.gobmk/results-metadata.json | 18 +- .../447.dealII/results-metadata.json | 18 +- .../450.soplex/results-metadata.json | 18 +- .../453.povray/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metadata.json | 18 +- .../squad-vs-first/456.hmmer/results-metrics.json | 2 +- .../squad-vs-first/458.sjeng/results-metadata.json | 18 +- .../squad-vs-first/458.sjeng/results-metrics.json | 2 +- .../462.libquantum/results-metadata.json | 18 +- .../464.h264ref/results-metadata.json | 18 +- .../464.h264ref/results-metrics.json | 2 +- .../squad-vs-first/470.lbm/results-metadata.json | 18 +- .../squad-vs-first/470.lbm/results-metrics.json | 2 +- .../471.omnetpp/results-metadata.json | 18 +- .../471.omnetpp/results-metrics.json | 2 +- .../squad-vs-first/473.astar/results-metadata.json | 18 +- .../squad-vs-first/473.astar/results-metrics.json | 2 +- .../482.sphinx3/results-metadata.json | 18 +- .../482.sphinx3/results-metrics.json | 2 +- .../483.xalancbmk/results-metadata.json | 18 +- .../483.xalancbmk/results-metrics.json | 2 +- .../squad-vs-first/Mean/results-metadata.json | 18 +- dashboard/squad-vs-first/dashboard-push-squad.sh | 82 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- mail/jira-body.txt | 31 +- mail/mail-body.txt | 36 +- mail/mail-subject.txt | 2 +- manifest.sh | 40 +- results | 2 +- results_id | 2 +- save-temps/400.perlbench.tar.xz | Bin 401664 -> 0 bytes save-temps/401.bzip2.tar.xz | Bin 42728 -> 0 bytes save-temps/403.gcc.tar.xz | Bin 1214176 -> 0 bytes save-temps/429.mcf.tar.xz | Bin 22308 -> 0 bytes save-temps/433.milc.tar.xz | Bin 58720 -> 0 bytes save-temps/444.namd.tar.xz | Bin 44912 -> 0 bytes save-temps/445.gobmk.tar.xz | Bin 620148 -> 0 bytes save-temps/447.dealII.tar.xz | Bin 878220 -> 0 bytes save-temps/450.soplex.tar.xz | Bin 207588 -> 0 bytes save-temps/453.povray.tar.xz | Bin 460732 -> 0 bytes save-temps/456.hmmer.tar.xz | Bin 123556 -> 0 bytes save-temps/458.sjeng.tar.xz | Bin 50788 -> 0 bytes save-temps/462.libquantum.tar.xz | Bin 23760 -> 0 bytes save-temps/464.h264ref.tar.xz | Bin 176052 -> 0 bytes save-temps/470.lbm.tar.xz | Bin 15536 -> 0 bytes save-temps/471.omnetpp.tar.xz | Bin 369768 -> 0 bytes save-temps/473.astar.tar.xz | Bin 41856 -> 0 bytes save-temps/482.sphinx3.tar.xz | Bin 94416 -> 0 bytes save-temps/483.xalancbmk.tar.xz | Bin 3181884 -> 0 bytes 107 files changed, 1626833 insertions(+), 1655306 deletions(-) delete mode 100644 09-build_llvm-true-false-/console.log.xz create mode 100644 09-build_llvm-true-false-cflags-/console.log.xz delete mode 100644 save-temps/400.perlbench.tar.xz delete mode 100644 save-temps/401.bzip2.tar.xz delete mode 100644 save-temps/403.gcc.tar.xz delete mode 100644 save-temps/429.mcf.tar.xz delete mode 100644 save-temps/433.milc.tar.xz delete mode 100644 save-temps/444.namd.tar.xz delete mode 100644 save-temps/445.gobmk.tar.xz delete mode 100644 save-temps/447.dealII.tar.xz delete mode 100644 save-temps/450.soplex.tar.xz delete mode 100644 save-temps/453.povray.tar.xz delete mode 100644 save-temps/456.hmmer.tar.xz delete mode 100644 save-temps/458.sjeng.tar.xz delete mode 100644 save-temps/462.libquantum.tar.xz delete mode 100644 save-temps/464.h264ref.tar.xz delete mode 100644 save-temps/470.lbm.tar.xz delete mode 100644 save-temps/471.omnetpp.tar.xz delete mode 100644 save-temps/473.astar.tar.xz delete mode 100644 save-temps/482.sphinx3.tar.xz delete mode 100644 save-temps/483.xalancbmk.tar.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (db3c5831f80 -> 0b2c1369d03)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from db3c5831f80 libstdc++: Remove problematic static_assert from src/c++20/tzdb.cc new 24a7980d0f4 PR target/106933: Limit TImode STV to SSA-like def-use chai [...] new 0b2c1369d03 PR target/107548: Handle vec_select in STV on x86. The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/i386/i386-features.cc | 68 ++++++++++++++++++++++++++++++ gcc/testsuite/gcc.target/i386/pr106933-1.c | 21 +++++++++ gcc/testsuite/gcc.target/i386/pr106933-2.c | 17 ++++++++ gcc/testsuite/gcc.target/i386/pr106959-1.c | 26 ++++++++++++ gcc/testsuite/gcc.target/i386/pr106959-2.c | 26 ++++++++++++ gcc/testsuite/gcc.target/i386/pr106959-3.c | 14 ++++++ gcc/testsuite/gcc.target/i386/pr107548-1.c | 25 +++++++++++ gcc/testsuite/gcc.target/i386/pr107548-2.c | 13 ++++++ 8 files changed, 210 insertions(+) create mode 100644 gcc/testsuite/gcc.target/i386/pr106933-1.c create mode 100644 gcc/testsuite/gcc.target/i386/pr106933-2.c create mode 100644 gcc/testsuite/gcc.target/i386/pr106959-1.c create mode 100644 gcc/testsuite/gcc.target/i386/pr106959-2.c create mode 100644 gcc/testsuite/gcc.target/i386/pr106959-3.c create mode 100644 gcc/testsuite/gcc.target/i386/pr107548-1.c create mode 100644 gcc/testsuite/gcc.target/i386/pr107548-2.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (dfdba08093 -> 030fc71935)

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 dfdba08093 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 470e008c1c 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 08695529f0 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 2fc1de55d8 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 365c509f00 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards a9630b922c 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards a7f68c234e 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards f75f1c07f0 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards b2daa1b33a 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards cdd9200aa0 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 069c6eb368 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards dcf26f1eb6 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 4ab6d87fad 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards f0183a024a 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 2cd1f7cfee 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 4482be90f6 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards f269689189 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 9bde568d58 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 437370eddd 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards 5af283e600 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards dbfecc8a66 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 8433467cd3 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 09d2f1929d 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 242cc478b3 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards c2adab7c29 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards 695ed240b0 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 7aa1020e13 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 210a419055 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards c831a4f1f3 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards a0a89ea2b5 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 504f523528 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards 6a728ff21a 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 2584972056 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 911e276fcf 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards dd57751bcd 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 70fbfc9cc2 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 91074e12f3 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 86148c9748 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards a6d01ec7df 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 8e47d9b618 229: force: #1926: 7: Success after gcc: 7 commits discards e1debec0cd 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards bf2ecf7020 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 947c294680 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 39b65e3d9a 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards 8fe17fc9f9 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 04abcb1bdd 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards d03b83c339 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards 8ca9bb5954 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 29da1bcb05 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 5fe844d91c 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards f32b7b7e13 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 68945d8a60 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 95363fc64c 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards c8523fe4ca 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 32b85ac5be 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards 4b732dbafa 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards aa84cc7df9 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards f226e6948f 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards 7006abb6de 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards d2b3a58918 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 4ed53fe9b2 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 4940beb4e0 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 55214c0e93 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards b9af1a73eb 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 74c4a1990d 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] discards 1d792aafb9 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits discards 3e49883751 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 3848c9e102 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] discards 2e41b06576 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards c9cb7cc587 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] discards 4bba072274 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 8897d52c54 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] discards 45b9859733 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] discards 405c2d19ab 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] discards dd8ee93e21 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] discards 2854ee280b 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] discards 1c3766831d 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] discards 624c6e6a59 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] discards 3e42e55349 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 310f0f84ba 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards 9e7b081f92 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards 0621170b6b 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] discards f299d438a2 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] discards 92dddb3856 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards 9df988ee6f 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] discards bb7c39b6ef 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] discards ea86aa3d22 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards 21f472ecee 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards fd1623119f 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards f37f6ed581 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards 651fb27f0b 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards 6cb777608d 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 18cd42f766 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards e333f3f848 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards 3b0aeeb4ce 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards b999817788 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 64e2d9cee7 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards 34b891e21f 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards 958f052324 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards f078d72877 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards 1f9624089a 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new 431e41009f 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new dd83afc19d 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new 6485180033 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 753ddc7bd1 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new c27e49f96a 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new d9790475ce 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 221a1b8041 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new d22f5e0429 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new 7c17443cb2 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new 7de15ddb12 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 4f4ca6a334 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new 865421521c 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new ef76321c0e 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 0233f22236 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new a8caecfc77 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new a2a1da3d5c 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] new cffea7a474 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] new 9ab97ff01f 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new b1fce845a7 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] new 5176b05670 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new abf8c907ad 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new ec254e9569 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new 4c96353fcf 190: onsuccess: #1774: 7: Success after binutils: 10 commits new 0a0080e350 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] new ab67152028 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] new 0051df894e 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] new 04fee98e5a 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] new 4c915f5536 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] new 5d4d374afd 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] new 0e35db3dd2 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] new 29f34e634f 198: onsuccess: #1852: 7: Success after gcc: 5 commits new d733c8f455 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] new fddaf98f34 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new b8963e9a6a 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] new dd31a8ddff 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 7de19d4523 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits new 2a418a1825 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new 1b3916158d 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 899ba916b6 206: onsuccess: #1860: 7: Success after gcc: 2 commits new afdcdd2661 207: onsuccess: #1862: 7: Success after binutils: 4 commits new ef24a71840 208: onsuccess: #1865: 7: Success after linux: 12 commits new 824cf8b79a 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new bbe203ff5b 210: onsuccess: #1868: 7: Success after binutils: 7 commits new ddd87c9382 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new cea0fca9c9 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new c5f9a78eed 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 78915a2526 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 937532a36b 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 1b7e9fdb79 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new 8926ceebb8 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new c9918b6e71 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new 45736392ad 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new 310a2220be 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new d676d1b554 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 075414c0fe 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 8ac9e84658 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new a520ae81d3 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new a922b86a41 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new f7fc754de4 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new 415db02aa9 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 0d0a3ae8ae 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 107e66864b 229: force: #1926: 7: Success after gcc: 7 commits new 4578003e29 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 976aef8eae 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 2f7dc32596 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 38b965787b 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 702cf8c772 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new cc9a94b28c 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 5129b6a5d6 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new b9cc1690c8 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 099e9599df 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 000ee4c586 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new c91c4d1a6c 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 31f84df5a2 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 69275d53cc 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new c1c48cbf4d 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 7d1125c6ef 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 9232f92daf 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 81e6990fe2 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 2b3c04c19c 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 293efbc81c 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 489fc42d38 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 4a93513590 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 6223e22a70 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 1e19b180eb 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 5e0028be22 253: onsuccess: #1950: 7: Success after glibc: 2 commits new 3420ccf3cb 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new abbdd89dc1 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 2b38fa7615 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 52afef1170 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new d6ac5b5e50 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new a054249dc8 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 7444e3a0fb 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new e9d7aec131 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 165cb7aec0 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 2c07c2c672 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 7f0b9b598a 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 829eb39c72 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 6c92e98933 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 5e30e2d161 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 9e9affea64 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 030fc71935 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] 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 (dfdba08093) \ 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 1700 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 32328 -> 32104 bytes 05-build_abe-stage1/console.log.xz | Bin 74724 -> 73764 bytes 07-build_abe-linux/console.log.xz | Bin 8812 -> 8804 bytes 08-build_abe-glibc/console.log.xz | Bin 245548 -> 245972 bytes 09-build_abe-stage2/console.log.xz | Bin 205688 -> 205240 bytes 10-build_abe-gdb/console.log.xz | Bin 39492 -> 39504 bytes 11-build_abe-qemu/console.log.xz | Bin 32144 -> 32008 bytes 12-check_regression/console.log.xz | Bin 4704 -> 3780 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 ++++++++--------- 19 files changed, 59 insertions(+), 59 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allmodconfig updated (57413d67df -> eba5963855)

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-release-arm-stable-allmodconfig in repository toolchain/ci/base-artifacts. from 57413d67df 37: onsuccess: #284: 22859: Success after binutils/qemu: 213 [...] new eba5963855 38: onsuccess: #285: 22859: Success after binutils/linux/qem [...] 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 1788 -> 1988 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2800 bytes 03-build_abe-binutils/console.log.xz | Bin 30680 -> 30616 bytes 04-build_kernel_llvm/console.log.xz | Bin 64348 -> 64844 bytes 05-build_abe-qemu/console.log.xz | Bin 31460 -> 31596 bytes 06-build_linux/console.log.xz | Bin 3972 -> 3976 bytes 08-check_regression/console.log.xz | Bin 3424 -> 3792 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 15 files changed, 20 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (a846817739c -> db3c5831f80)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from a846817739c c++, driver: Fix -static-libstdc++ for targets without Bsta [...] new db3c5831f80 libstdc++: Remove problematic static_assert from src/c++20/tzdb.cc 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: libstdc++-v3/src/c++20/tzdb.cc | 1 - 1 file changed, 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022