Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[gcc] branch releases/gcc-11 updated (40b5a2354b5 -> 3e62dea6c25)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-11 in repository gcc. from 40b5a2354b5 d: Fix internal compiler error: in visit, at d/imports.cc:7 [...] new 3e62dea6c25 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/DATESTAMP | 2 +- gcc/d/ChangeLog | 10 ++++++++++ gcc/testsuite/ChangeLog | 11 +++++++++++ 3 files changed, 22 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch releases/gcc-10 updated (9d18a4b98d9 -> 14d625453bf)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-10 in repository gcc. from 9d18a4b98d9 d: Fix internal compiler error: in visit, at d/imports.cc:7 [...] new 14d625453bf Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/DATESTAMP | 2 +- gcc/d/ChangeLog | 10 ++++++++++ gcc/testsuite/ChangeLog | 11 +++++++++++ 3 files changed, 22 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (8f72249ff4c -> 324e9953400)

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 8f72249ff4c Fortran: fix ICE on bad use of statement function [PR107995] new 324e9953400 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: contrib/ChangeLog | 11 +++++++++++ gcc/ChangeLog | 21 +++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/d/ChangeLog | 20 ++++++++++++++++++++ gcc/fortran/ChangeLog | 11 +++++++++++ gcc/testsuite/ChangeLog | 28 ++++++++++++++++++++++++++++ libphobos/ChangeLog | 5 +++++ 7 files changed, 97 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch master updated (f2f58a399cf -> b35abeab8d8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from f2f58a399cf PR29870, objdump SEGV in display_debug_lines_decoded dwarf.c:5524 new b35abeab8d8 Automatic date update in version.in The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch gdb-12-branch updated (0ac0e852435 -> e4594519f23)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch gdb-12-branch in repository binutils-gdb. from 0ac0e852435 Automatic date update in version.in new e4594519f23 Automatic date update in version.in The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[binutils-gdb] branch binutils-2_39-branch updated (6f53ae49d6c -> 0c0b1af3837)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch binutils-2_39-branch in repository binutils-gdb. from 6f53ae49d6c Automatic date update in version.in new 0c0b1af3837 Automatic date update in version.in The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: bfd/version.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_binutils/release-aarch64 updated (8d01d823dd1 -> 01b7ebb9e6a)

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/release-aarch64 in repository toolchain/ci/base-artifacts. from 8d01d823dd1 36: onsuccess: #135: 1: Success after binutils/gcc/linux/gd [...] new 01b7ebb9e6a 37: onsuccess: #136: 1: Success after binutils/gcc/gdb: 13 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1712 -> 1732 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 38160 -> 37856 bytes 04-build_abe-gcc/console.log.xz | Bin 207328 -> 206508 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8668 -> 8696 bytes 07-build_abe-glibc/console.log.xz | Bin 241064 -> 238952 bytes 08-build_abe-gdb/console.log.xz | Bin 37104 -> 36940 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3844 -> 3848 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2064 -> 2072 bytes 11-check_regression/console.log.xz | Bin 5596 -> 5152 bytes 11-check_regression/results.compare | 8 +- 11-check_regression/results.compare2 | 6 +- 12-update_baseline/console.log | 9 + 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 | 28 +-- sumfiles/binutils.log.xz | Bin 55308 -> 55292 bytes sumfiles/binutils.sum | 58 ++--- sumfiles/gas.log.xz | Bin 80376 -> 80384 bytes sumfiles/gas.sum | 270 +++++++++++------------ sumfiles/ld.log.xz | Bin 118792 -> 118844 bytes sumfiles/ld.sum | 332 ++++++++++++++--------------- 28 files changed, 367 insertions(+), 358 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (5e0a0f04e24 -> 6f676386cc1)

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_check/master-arm in repository toolchain/ci/base-artifacts. discards 5e0a0f04e24 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits discards 83f2077e6b0 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits discards 6673c81a8fa 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-4 [...] discards 56195aaace0 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits discards 1293dc7084e 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits discards da420513f71 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits discards 5a1745f1cd2 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits discards c5268555e9b 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits discards 4aeb14f03fc 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits discards 1b54bee7b3c 395: onsuccess: #2035: 1: Success after gcc: 4 commits discards d496379b4ec 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits discards 7918c4521a3 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits discards 4c068277cc6 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits discards 70a3a4142ef 391: onsuccess: #2031: 1: Success after binutils/gcc: 5 commits discards 27aec4e3548 390: onsuccess: #2030: 1: Success after binutils/gcc: 8 commits discards 690d0528348 389: onsuccess: #2029: 1: Success after binutils/gcc: 13 commits discards be43cf5c1cd 388: onsuccess: #2028: 1: Success after binutils/gcc: 15 commits discards ba3070f8305 387: onsuccess: #2027: 1: Success after binutils/gcc: 14 commits discards 8d4a8b34da1 386: onsuccess: #2026: 1: Success after binutils/gcc: 5 commits discards dc0cdbb0984 385: onsuccess: #2025: 1: Success after binutils: 8 commits discards dae183dabdc 384: onsuccess: #2024: 1: Success after binutils/gcc: 13 commits discards d32a5b561e1 383: onsuccess: #2023: 1: Success after binutils/gcc: 7 commits discards e4e82c2a3bc 382: onsuccess: #2022: 1: Success after binutils/gcc: 3 commits discards 1db54dc204c 381: onsuccess: #2021: 1: Success after binutils/gcc: 6 commits discards 3bfb5257ed8 380: onsuccess: #2020: 1: Success after gcc: 2 commits discards 62cad90b255 379: onsuccess: #2019: 1: Success after gcc: 3 commits discards 22be9f74a49 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits discards c160424ade5 377: onsuccess: #2017: 1: Success after binutils: 3 commits discards b838411ad02 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-4 [...] discards faa38f27fa9 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits discards c66de5c13ad 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits discards d0e959b8ff7 373: onsuccess: #2013: 1: Success after gcc: 6 commits discards eaadee03516 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits discards 543d5225233 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits discards fcbe7dfd930 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits discards 416bd94cd31 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits discards f600431fe39 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits discards 4a964c46d30 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits discards e0bd0e3aba7 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits discards 658e6394c35 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits discards 033ee45e9bf 364: onsuccess: #2000: 1: Success after gcc: 5 commits discards e5a14e980fb 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits discards 7214a660447 362: onsuccess: #1998: 1: Success after binutils/gcc: 39 commits discards e9dc0ab31d2 361: onsuccess: #1997: 1: Success after binutils/gcc: 24 commits discards 86191d33d72 360: onsuccess: #1996: 1: Success after binutils/gcc: 47 commits discards e9acb8a18cb 359: onsuccess: #1995: 1: Success after binutils/gcc: 8 commits discards d7944d562ef 358: onsuccess: #1994: 1: Success after binutils: 3 commits discards b2abfe31fe6 357: onsuccess: #1993: 1: Success after gdb-12-branchpoint- [...] discards 609042ad9cf 356: onsuccess: #1992: 1: Success after binutils/gcc: 2 commits discards 053436a78e1 355: onsuccess: #1991: 1: Success after basepoints/gcc-13-4 [...] discards 7e8cad4af0e 354: onsuccess: #1990: 1: Success after binutils: 4 commits discards c721e635aff 353: onsuccess: #1989: 1: Success after binutils/gcc: 2 commits discards b8fa343803b 352: onsuccess: #1988: 1: Success after basepoints/gcc-13-4 [...] discards 0dc6a984653 351: onsuccess: #1987: 1: Success after binutils/gcc: 9 commits discards 8eb87aa962c 350: onsuccess: #1986: 1: Success after gcc: 6 commits discards ecf1ef88bd6 349: onsuccess: #1985: 1: Success after binutils/gcc: 5 commits discards f6a493b39ad 348: onsuccess: #1984: 1: Success after gdb-12-branchpoint- [...] discards 876d334d5df 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 commits discards 57084487920 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits discards bb2de6f893b 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits discards ecd675be8d8 344: onsuccess: #1980: 1: Success after gcc: 3 commits discards afc382807f3 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits discards 89e5703d796 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits discards 28c900dbb49 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits discards 1460f7f667a 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits discards 999387b12eb 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits discards b9236c9f208 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits discards 260578a7f9c 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits discards 7cc848bdafb 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits discards b43eabad4b9 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits discards fab9f4da518 334: onsuccess: #1970: 1: Success after gcc: 20 commits discards 30a84d5fbe9 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits discards f2f1f84d5ee 332: onsuccess: #1968: 1: Success after gcc: 3 commits discards cf5a8bc9d02 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits discards 29ed13e6b1e 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits discards 72e2750fac9 329: onsuccess: #1965: 1: Success after gcc: 2 commits discards 0c4b19340a8 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits discards c98762522a9 327: onsuccess: #1963: 1: Success after gcc: 3 commits discards 818c0354d25 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits discards 09d084a6b5d 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits discards ff567c40a0e 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits discards b5464f21ddb 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits discards 8beba6cfda3 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits discards a43ba35cebe 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits discards dbdf5508366 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits discards 51024e99895 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits discards 4b2d1d545f5 318: onsuccess: #1953: 1: Success after gcc: 11 commits discards 34a3435d663 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits discards 388eaed0e09 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits discards 6fd9b1ad362 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-4 [...] discards fe455dbaa31 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits discards 61a24bf60f4 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits discards 6cd4d459e55 312: onsuccess: #1947: 1: Success after gcc: 87 commits discards 75e44bbec2f 311: onsuccess: #1945: 1: Success after binutils: 3 commits discards afa9a6a32e8 310: onsuccess: #1941: 1: Success after binutils: 2 commits discards e04bfc3d4c8 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint- [...] discards 50d2fc32ec8 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint- [...] discards 11809804c5e 307: onsuccess: #1931: 1: Success after binutils: 2 commits discards 4a3d3c78525 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint- [...] discards cf31168b51f 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits discards f8a206cc3e6 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits new 804afa2b8ae 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits new c366574a8cb 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits new 507cf6bbed0 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint- [...] new 6b929d2bb05 307: onsuccess: #1931: 1: Success after binutils: 2 commits new 3bc904d4050 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint- [...] new d35e16196b0 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint- [...] new c8c9634ca5c 310: onsuccess: #1941: 1: Success after binutils: 2 commits new e31d46ecd91 311: onsuccess: #1945: 1: Success after binutils: 3 commits new cd000bce829 312: onsuccess: #1947: 1: Success after gcc: 87 commits new 12a557935d1 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits new 892dd056ae9 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits new f674dbbea31 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-4 [...] new 7b2639d9421 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits new 7a2b68984ce 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits new 527760b305b 318: onsuccess: #1953: 1: Success after gcc: 11 commits new 731665efb72 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits new b10947be065 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits new a2635c42623 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits new 88a4c74d39a 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits new 735b5065803 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits new 990eb469263 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits new 4962aa42a72 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits new fca88affa47 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits new 8a8eaadb654 327: onsuccess: #1963: 1: Success after gcc: 3 commits new 85c5d06b905 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits new b6c98c64446 329: onsuccess: #1965: 1: Success after gcc: 2 commits new aed84e01eb0 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits new f4efded08aa 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits new d4d2bc76fa7 332: onsuccess: #1968: 1: Success after gcc: 3 commits new b43e8ef4252 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits new f28abbbb105 334: onsuccess: #1970: 1: Success after gcc: 20 commits new 66533e32e13 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits new 54e43f8108e 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits new 70d73f1bf53 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits new 930874c1b17 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits new 354026e19e1 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits new 5c8e78f6487 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits new 875dc54e109 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits new 007916af49e 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits new 3ef450675dc 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits new 6dabe6b5984 344: onsuccess: #1980: 1: Success after gcc: 3 commits new 87f141e0100 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits new b227246f2da 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits new ce4ff9a2e22 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 commits new f0cfed28742 348: onsuccess: #1984: 1: Success after gdb-12-branchpoint- [...] new 8b035a805d7 349: onsuccess: #1985: 1: Success after binutils/gcc: 5 commits new e5568f9cc31 350: onsuccess: #1986: 1: Success after gcc: 6 commits new 516f80566a8 351: onsuccess: #1987: 1: Success after binutils/gcc: 9 commits new 196a6fd9804 352: onsuccess: #1988: 1: Success after basepoints/gcc-13-4 [...] new 5b0f42a8c21 353: onsuccess: #1989: 1: Success after binutils/gcc: 2 commits new 5e13b00613b 354: onsuccess: #1990: 1: Success after binutils: 4 commits new b601bd8467e 355: onsuccess: #1991: 1: Success after basepoints/gcc-13-4 [...] new e1404ae6fb3 356: onsuccess: #1992: 1: Success after binutils/gcc: 2 commits new 57fee557e88 357: onsuccess: #1993: 1: Success after gdb-12-branchpoint- [...] new c57a01e7b42 358: onsuccess: #1994: 1: Success after binutils: 3 commits new 52ee18400ab 359: onsuccess: #1995: 1: Success after binutils/gcc: 8 commits new dc16ef996ce 360: onsuccess: #1996: 1: Success after binutils/gcc: 47 commits new d004da04c4a 361: onsuccess: #1997: 1: Success after binutils/gcc: 24 commits new a77df2fe47c 362: onsuccess: #1998: 1: Success after binutils/gcc: 39 commits new dff2ccf8aec 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits new 5112bdd8868 364: onsuccess: #2000: 1: Success after gcc: 5 commits new 3977e81d419 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits new c3414d2c0b4 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits new 33e1417f7ae 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 commits new 28483336de2 368: onsuccess: #2008: 1: Success after binutils/gcc: 10 commits new bd5f7debb7e 369: onsuccess: #2009: 1: Success after binutils/gcc: 21 commits new 5b88650904b 370: onsuccess: #2010: 1: Success after binutils/gcc: 8 commits new 45252a791e0 371: onsuccess: #2011: 1: Success after binutils/gcc: 6 commits new b72843c74cf 372: onsuccess: #2012: 1: Success after binutils/gcc: 10 commits new 4e7dd3374e2 373: onsuccess: #2013: 1: Success after gcc: 6 commits new 36eba7c2b81 374: onsuccess: #2014: 1: Success after binutils/gcc: 9 commits new 7b1351dc93c 375: onsuccess: #2015: 1: Success after binutils/gcc: 4 commits new ab88d4f0991 376: onsuccess: #2016: 1: Success after basepoints/gcc-13-4 [...] new 5cdc31c0be5 377: onsuccess: #2017: 1: Success after binutils: 3 commits new 4766390fb94 378: onsuccess: #2018: 1: Success after binutils/gcc: 2 commits new 5b5a9123199 379: onsuccess: #2019: 1: Success after gcc: 3 commits new c78432cc03b 380: onsuccess: #2020: 1: Success after gcc: 2 commits new 272980f9491 381: onsuccess: #2021: 1: Success after binutils/gcc: 6 commits new c906caac4e0 382: onsuccess: #2022: 1: Success after binutils/gcc: 3 commits new 6e164a435bc 383: onsuccess: #2023: 1: Success after binutils/gcc: 7 commits new 49b665a9ab4 384: onsuccess: #2024: 1: Success after binutils/gcc: 13 commits new fe5783a6b4b 385: onsuccess: #2025: 1: Success after binutils: 8 commits new 198e07cf67d 386: onsuccess: #2026: 1: Success after binutils/gcc: 5 commits new a4dd7c93de8 387: onsuccess: #2027: 1: Success after binutils/gcc: 14 commits new 9e5bd3f8b2d 388: onsuccess: #2028: 1: Success after binutils/gcc: 15 commits new 730be098c9d 389: onsuccess: #2029: 1: Success after binutils/gcc: 13 commits new 07acaa2f4dc 390: onsuccess: #2030: 1: Success after binutils/gcc: 8 commits new 87e1666d215 391: onsuccess: #2031: 1: Success after binutils/gcc: 5 commits new 47745d21868 392: onsuccess: #2032: 1: Success after binutils/gcc: 6 commits new f05a9bc5e45 393: onsuccess: #2033: 1: Success after binutils/gcc: 9 commits new 67bce6a58cb 394: onsuccess: #2034: 1: Success after binutils/gcc: 4 commits new 5fbc9c1e084 395: onsuccess: #2035: 1: Success after gcc: 4 commits new e6ceeedae8c 396: onsuccess: #2037: 1: Success after binutils/gcc: 22 commits new f69bc7565ce 397: onsuccess: #2038: 1: Success after binutils/gcc: 12 commits new 3a8973de416 398: onsuccess: #2039: 1: Success after binutils/gcc: 4 commits new 7381f5a051b 399: onsuccess: #2040: 1: Success after binutils/gcc: 3 commits new 14174c3a02d 400: onsuccess: #2041: 1: Success after binutils/gcc: 8 commits new 174b984cc54 401: onsuccess: #2042: 1: Success after binutils/gcc: 11 commits new 37ac81ea3db 402: onsuccess: #2043: 1: Success after basepoints/gcc-13-4 [...] new e9e6b088fed 403: onsuccess: #2044: 1: Success after binutils/gcc: 2 commits new 6ce5c49af47 404: onsuccess: #2045: 1: Success after binutils/gcc: 8 commits new 6f676386cc1 405: onsuccess: #2046: 1: Success after gcc: 2 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 (5e0a0f04e24) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (6f [...] 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 1820 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 53172 -> 52340 bytes 04-build_abe-gcc/console.log.xz | Bin 235628 -> 234732 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2492 bytes 07-check_regression/console.log.xz | Bin 5856 -> 4792 bytes 07-check_regression/extra-bisect-params | 1 - 07-check_regression/fails.sum | 7 - 07-check_regression/mail-body.txt | 49 +- 07-check_regression/results.compare | 43 +- 07-check_regression/results.compare2 | 87 +- 07-check_regression/results.regressions | 51 - 08-update_baseline/console.log | 58 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 51 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 51 - sumfiles/g++.log.xz | Bin 2866936 -> 2864732 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2451660 -> 2434668 bytes sumfiles/gcc.sum | 4706 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 915448 -> 916488 bytes sumfiles/gfortran.sum | 48 +- sumfiles/libatomic.log.xz | Bin 2168 -> 2164 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 216924 -> 217080 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 473708 -> 474220 bytes sumfiles/libstdc++.sum | 10 +- 35 files changed, 2556 insertions(+), 2774 deletions(-) delete mode 100644 07-check_regression/extra-bisect-params delete mode 100644 07-check_regression/fails.sum delete mode 100644 07-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (28dc2c9525f -> 65ff2046a47)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards 28dc2c9525f 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 [...] discards b8c2830c979 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/ [...] discards 3d6b927f660 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 1 [...] discards 5a98b113c8e 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] discards 25facce3a51 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] discards 670bef723fe 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] discards 3a59765bdcb 204: onsuccess: #2435: 1: Success after linux: 3 commits discards 93f0680a4f9 203: onsuccess: #2433: 1: Success after binutils: 27 commits discards 6c3f2c14905 202: onsuccess: #2431: 1: Success after linux: 944 commits discards 9b7735c3ac6 201: onsuccess: #2430: 1: Success after glibc: 26 commits discards 9fdf347d8da 200: onsuccess: #2427: 1: Success after binutils: 274 commits discards 149e586963d 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] discards 2dd00ec2160 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] discards 821aa0e1da1 197: onsuccess: #2348: 1: Success after linux: 190 commits discards 7f0d68b16cf 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] discards 30795865caf 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] discards a09f9aa1c03 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] discards 4c4c17d533f 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] discards 038963a45c8 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] discards 284ab4c5a71 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits discards 25f057f6551 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] discards c6f44d57743 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] discards 1a31cf11671 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] discards 463baa67678 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] discards 0a079ec6d79 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] discards 7f0f29a2724 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] discards 2fc83585382 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] discards a3ec6517107 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] discards b560a05c5e6 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] discards f0b665eeddb 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] discards cf7e28b545e 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] discards 1e3b7f34029 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] discards 6b2c1053b64 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] discards ffa675117ac 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits discards ff04e4a50a8 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] discards 9f357f6564c 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] discards 51ddeee936c 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] discards dfcdfa822e9 173: onsuccess: #2208: 1: Success after gcc: 10 commits discards bfb4666ba5e 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] discards a82c1b53c74 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] discards e2b3bae6b56 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] discards 2f9572451a9 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] discards e1c2db0897f 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] discards c23e28f70b4 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] discards 534b0a46bdc 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits discards 00612b1d4ab 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits discards 042bf9702ec 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] discards 1b5cbe9b094 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] discards ba1814e1aa2 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] discards b0524d97195 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] discards 993694be95e 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] discards c8e38b48ffe 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] discards d6baac4cf4c 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] discards f45cc6940f8 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] discards 43e18e73c3b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] discards 9aa941a568c 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] discards 21ff7fa532b 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] discards aa01beb0451 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] discards 1a790e70a22 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] discards 671ecc9af87 151: onsuccess: #2186: 1: Success after gcc: 2 commits discards 32a8b212f0a 150: onsuccess: #2185: 1: Success after gcc: 3 commits discards 10060ed6af5 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] discards 4ac4150861b 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] discards 56dcb257095 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] discards 520f2a707bd 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] discards 7e142c39a52 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] discards aa30d1e3eb5 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] discards 2ae68a21fc1 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] discards c2a2a28d207 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits discards af2e2fb02f2 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] discards c61966123d5 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] discards b29635488fe 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] discards 38d0c4e1cac 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] discards 62d4c3df62f 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] discards adb01828419 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] discards 918a442aabb 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits discards 5b9652b5625 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] discards f5064c4f1ca 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] discards 76fb48e1fd4 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] discards 07ca57aa97a 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] discards a61e0c8fa0a 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] discards 109d28073ba 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] discards 3646cc07779 128: onsuccess: #2163: 1: Success after linux: 23 commits discards 3161c28ba2f 127: onsuccess: #2162: 1: Success after gcc: 9 commits discards 30d6ce8e94f 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] discards c8530f0d253 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] discards 239577d56ce 124: onsuccess: #2159: 1: Success after linux: 23 commits discards 083c774d6c2 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] discards a006a6a1282 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] discards b4bb6a5a400 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] discards beed4e8a0cf 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] discards f90d22c0403 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] discards 1c0b2e6f48f 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] discards 88848fab4c9 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] discards 31a81fa29ff 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] discards f3e6a807e53 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] discards 13cebe52ef9 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] discards 9ca9e294064 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] discards 16bdb60ecce 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] discards fe54ee72661 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] discards 4cd31934666 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new f0136840180 110: onsuccess: #2142: 1: Success after binutils/gcc/glibc/ [...] new 21d7290bca6 111: onsuccess: #2143: 1: Success after binutils/gcc/linux/ [...] new 58f5a317fdd 112: onsuccess: #2144: 1: Success after binutils/gcc/glibc/ [...] new d47032cc0a6 113: onsuccess: #2145: 1: Success after binutils/gcc/glibc/ [...] new c6b53889f2d 114: onsuccess: #2146: 1: Success after binutils/gcc/glibc/ [...] new 4777ce02681 115: onsuccess: #2147: 1: Success after binutils/linux/glib [...] new b8bfcd18aa2 116: onsuccess: #2148: 1: Success after binutils/gcc/gdb: 7 [...] new 55bcc302163 117: onsuccess: #2150: 1: Success after binutils/gcc/glibc/ [...] new 48876d4b729 118: onsuccess: #2151: 1: Success after binutils/gcc/linux/ [...] new 44ded7ea0c3 119: onsuccess: #2154: 1: Success after binutils/gcc/linux/ [...] new 445a0be63b6 120: onsuccess: #2155: 1: Success after binutils/gcc/linux/ [...] new ac1e4505cec 121: onsuccess: #2156: 1: Success after binutils/gcc/linux/ [...] new fcd9d7a424e 122: onsuccess: #2157: 1: Success after binutils/gcc/gdb: 6 [...] new c0840d874a4 123: onsuccess: #2158: 1: Success after basepoints/gcc-13-2 [...] new fe3fec1d89a 124: onsuccess: #2159: 1: Success after linux: 23 commits new 5a87a777adc 125: onsuccess: #2160: 1: Success after binutils/gcc/linux/ [...] new d8d705dbf11 126: onsuccess: #2161: 1: Success after basepoints/gcc-13-2 [...] new 625cd35eaae 127: onsuccess: #2162: 1: Success after gcc: 9 commits new cd0ecd0884f 128: onsuccess: #2163: 1: Success after linux: 23 commits new ce18827cf94 129: onsuccess: #2164: 1: Success after binutils/gcc/linux/ [...] new 282465ea4aa 130: onsuccess: #2165: 1: Success after binutils/gcc/gdb: 3 [...] new cdbdffec69d 131: onsuccess: #2166: 1: Success after binutils/gcc/gdb: 1 [...] new 6c3353d2a2a 132: onsuccess: #2167: 1: Success after binutils/gcc/glibc/ [...] new 3c1f32fc1e9 133: onsuccess: #2168: 1: Success after binutils/gcc/linux/ [...] new 5bd7a7ae71c 134: onsuccess: #2169: 1: Success after binutils/gcc/gdb: 1 [...] new 9380efe3286 135: onsuccess: #2170: 1: Success after gcc/linux/qemu: 63 commits new e2c2b5c99b4 136: onsuccess: #2171: 1: Success after binutils/gcc/gdb/qe [...] new 21ee7325eaa 137: onsuccess: #2172: 1: Success after binutils/gcc/linux/ [...] new 8b5ad6c9c01 138: onsuccess: #2173: 1: Success after binutils/gcc/gdb: 5 [...] new 2ee08d31892 139: onsuccess: #2174: 1: Success after binutils/gcc/gdb: 1 [...] new e0c98f0e0b3 140: onsuccess: #2175: 1: Success after binutils/gcc/linux/ [...] new 66d00fe5220 141: onsuccess: #2176: 1: Success after binutils/gcc/gdb: 6 [...] new 86a81d39feb 142: onsuccess: #2177: 1: Success after gcc/glibc: 4 commits new 55fdb1e344e 143: onsuccess: #2178: 1: Success after binutils/gcc/gdb/qe [...] new 368c6114d0c 144: onsuccess: #2179: 1: Success after binutils/gcc/linux/ [...] new ebe483284b3 145: onsuccess: #2180: 1: Success after binutils/gcc/linux/ [...] new e1940b03024 146: onsuccess: #2181: 1: Success after binutils/glibc/gdb: [...] new 607cea92447 147: onsuccess: #2182: 1: Success after binutils/gcc/gdb: 1 [...] new 3a248fb4b11 148: onsuccess: #2183: 1: Success after gcc/linux/glibc: 64 [...] new 5f25cdabb33 149: onsuccess: #2184: 1: Success after binutils/gcc/linux/ [...] new f7f248e2c27 150: onsuccess: #2185: 1: Success after gcc: 3 commits new 0364b2a9778 151: onsuccess: #2186: 1: Success after gcc: 2 commits new b4ecf512da7 152: onsuccess: #2187: 1: Success after gcc/linux/glibc: 22 [...] new 68640d57ea1 153: onsuccess: #2188: 1: Success after binutils/gcc/gdb: 3 [...] new 08647b250ee 154: onsuccess: #2189: 1: Success after binutils/gcc/gdb: 1 [...] new fd35c5b8071 155: onsuccess: #2190: 1: Success after binutils/gcc/linux/ [...] new e004c9bab0b 156: onsuccess: #2191: 1: Success after binutils/gcc/linux/ [...] new 75594279953 157: onsuccess: #2192: 1: Success after binutils/gcc/gdb: 8 [...] new 124f744eb35 158: onsuccess: #2193: 1: Success after binutils/gcc/glibc/ [...] new 3161d40a344 159: onsuccess: #2194: 1: Success after gcc/linux/glibc: 19 [...] new caca07d568c 160: onsuccess: #2195: 1: Success after binutils/gcc/linux/ [...] new 0e83ba1effe 161: onsuccess: #2196: 1: Success after binutils/gcc/linux/ [...] new 6c25f3bd614 162: onsuccess: #2197: 1: Success after binutils/gcc/glibc/ [...] new ae868caef5e 163: onsuccess: #2198: 1: Success after binutils/gcc/linux/ [...] new ecec28d5f63 164: onsuccess: #2199: 1: Success after binutils/gcc/linux/ [...] new bd118a65902 165: onsuccess: #2200: 1: Success after binutils/gdb: 8 commits new cc15c4eaefd 166: onsuccess: #2201: 1: Success after gcc/glibc/qemu: 40 commits new b24136128fb 167: onsuccess: #2202: 1: Success after gcc/linux/glibc/qem [...] new fcf10e8da5b 168: onsuccess: #2203: 1: Success after binutils/gcc/glibc/ [...] new 5c5cf5f84fc 169: onsuccess: #2204: 1: Success after binutils/gcc/glibc/ [...] new 1eeb768ca04 170: onsuccess: #2205: 1: Success after binutils/gcc/glibc/ [...] new bfd2e2ea4db 171: onsuccess: #2206: 1: Success after binutils/gcc/linux/ [...] new fa1f922df76 172: onsuccess: #2207: 1: Success after binutils/gcc/linux/ [...] new a3242f12678 173: onsuccess: #2208: 1: Success after gcc: 10 commits new 44491fe972b 174: onsuccess: #2209: 1: Success after binutils/gcc/gdb: 2 [...] new c371bb4d799 175: onsuccess: #2210: 1: Success after binutils/gcc/linux/ [...] new 03f29bb8c1e 176: onsuccess: #2211: 1: Success after binutils/gcc/linux/ [...] new 7b23a719de8 177: onsuccess: #2212: 1: Success after binutils/gdb: 2 commits new 8dcf2717977 178: onsuccess: #2217: 1: Success after binutils/gcc/linux/ [...] new 1c5e808a605 179: onsuccess: #2230: 1: Success after binutils/gcc/linux/ [...] new b6c7977f93e 180: onsuccess: #2232: 1: Success after binutils/gcc/glibc/ [...] new 6ed56b7db82 181: onsuccess: #2239: 1: Success after binutils/gcc/linux/ [...] new 13231f8ce45 182: onsuccess: #2247: 1: Success after binutils/gcc/linux/ [...] new 9e713f3791a 183: onsuccess: #2270: 1: Success after binutils/gcc/linux/ [...] new 9c57a44cb21 184: onsuccess: #2288: 1: Success after binutils/gcc/linux/ [...] new 629f5d753aa 185: onsuccess: #2290: 1: Success after binutils/gcc/linux/ [...] new 9a44b07593c 186: onsuccess: #2291: 1: Success after binutils/gcc/linux/ [...] new 526033b2b90 187: onsuccess: #2294: 1: Success after binutils/gcc/linux/ [...] new 13f7d0fc765 188: onsuccess: #2295: 1: Success after binutils/gcc/linux/ [...] new fa915cabff6 189: onsuccess: #2299: 1: Success after binutils/gcc/linux/ [...] new 90436969fd4 190: onsuccess: #2330: 1: Success after binutils/gcc/linux/ [...] new da7cb91d92c 191: onsuccess: #2331: 1: Success after gcc/qemu: 90 commits new 53f5afd06a8 192: onsuccess: #2338: 1: Success after binutils/gcc/linux/ [...] new eef29db7f50 193: onsuccess: #2339: 1: Success after binutils/gcc/glibc/ [...] new 83194e91c09 194: onsuccess: #2340: 1: Success after binutils/gcc/linux/ [...] new 856597d8949 195: onsuccess: #2341: 1: Success after binutils/gcc/linux/ [...] new 3783c83d857 196: onsuccess: #2342: 1: Success after binutils/gcc/gdb: 4 [...] new 1674884c7ab 197: onsuccess: #2348: 1: Success after linux: 190 commits new 16d712737cf 198: onsuccess: #2360: 1: Success after binutils/gcc/linux/ [...] new a381283a353 199: onsuccess: #2363: 1: Success after binutils/gcc/linux/ [...] new cd06c500ecb 200: onsuccess: #2427: 1: Success after binutils: 274 commits new 563840260e5 201: onsuccess: #2430: 1: Success after glibc: 26 commits new d015492a602 202: onsuccess: #2431: 1: Success after linux: 944 commits new 948d284e637 203: onsuccess: #2433: 1: Success after binutils: 27 commits new 198136e11bb 204: onsuccess: #2435: 1: Success after linux: 3 commits new 504974904a9 205: onsuccess: #2444: 1: Success after binutils/gcc/linux/ [...] new 2c30698a92d 206: onsuccess: #2445: 1: Success after binutils/gcc/glibc/ [...] new 24219d74ca4 207: onsuccess: #2446: 1: Success after binutils/gcc/linux/ [...] new 82cb30794fc 208: onsuccess: #2447: 1: Success after binutils/gcc/gdb: 1 [...] new 46d7b47fb32 209: onsuccess: #2448: 1: Success after binutils/gcc/linux/ [...] new a896ead3fc3 210: onsuccess: #2449: 1: Success after binutils/gcc/gdb: 6 [...] new 65ff2046a47 211: onsuccess: #2450: 1: Success after gcc/linux: 7 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 (28dc2c9525f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31876 -> 31888 bytes 04-build_abe-stage1/console.log.xz | Bin 72984 -> 72880 bytes 05-clean_sysroot/console.log.xz | Bin 328 -> 328 bytes 06-build_abe-linux/console.log.xz | Bin 8788 -> 8532 bytes 07-build_abe-glibc/console.log.xz | Bin 243056 -> 244424 bytes 08-build_abe-stage2/console.log.xz | Bin 203968 -> 204336 bytes 09-build_abe-gdb/console.log.xz | Bin 38956 -> 38936 bytes 10-build_abe-qemu/console.log.xz | Bin 30648 -> 31364 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3888 -> 3888 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2904 -> 2784 bytes 13-check_regression/console.log.xz | Bin 6440 -> 20100 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 105 +- 13-check_regression/mail-body.txt | 192 +- 13-check_regression/results.compare | 173 +- 13-check_regression/results.compare2 | 3316 ++++++++++++++++- 13-check_regression/results.regressions | 121 +- 14-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 194 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +- results | 119 +- sumfiles/g++.log.xz | Bin 3406364 -> 3409640 bytes sumfiles/g++.sum | 2590 +++++++------- sumfiles/gcc.log.xz | Bin 3028408 -> 3029940 bytes sumfiles/gcc.sum | 5896 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1038452 -> 1040884 bytes sumfiles/gfortran.sum | 50 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 214720 -> 214716 bytes sumfiles/libgomp.sum | 21 +- sumfiles/libitm.log.xz | Bin 2700 -> 2692 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429920 -> 434284 bytes sumfiles/libstdc++.sum | 16 +- 42 files changed, 8215 insertions(+), 4690 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm updated (f63f94c1992 -> 809a4e16895)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards f63f94c1992 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] discards 048703eb35f 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] discards 1e545fafc41 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] discards 787e5fc7bf5 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] discards b1c9f8934f8 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] discards aae4b3f047b 129: onsuccess: #588: 1: Success after linux: 4 commits discards 992856614b3 128: onsuccess: #586: 1: Success after binutils: 22 commits discards b43544d89cb 127: onsuccess: #584: 1: Success after linux: 21 commits discards 9a542fe9ade 126: onsuccess: #582: 1: Success after gcc: 9 commits discards 5c650629f7f 125: onsuccess: #581: 1: Success after binutils: 4 commits discards a3546876bcf 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] discards 373a360f293 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] discards 640b237f2e6 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] discards f481a0864a6 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] discards 7d4b3f9ef59 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] discards bc0e120f8da 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] discards a2e28839886 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] discards ffaebf97bbe 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] discards ccff162f66b 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] discards 07678d7ffb8 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] discards 0cf5044fbdf 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] discards 0d7a9e1fbc7 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] discards a3fe8ea253c 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] discards baa5cb4db19 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] discards a91fea1c7b5 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] discards f0c42648373 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] discards bd90852e7a9 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] discards 329ad9fdf3b 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] discards 533ee0594d5 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] discards 74d063acb33 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] discards 5c8794df393 104: onsuccess: #558: 1: Success after binutils: 3 commits discards e90b27bdf4c 103: onsuccess: #555: 1: Success after binutils: 4 commits discards 2ab462d3bf1 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] discards 71d0853c32a 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] discards 71c624133ae 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] discards 3103382c530 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] discards 785255bfc9c 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] discards 07e43368148 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] discards 48d8eb6d8bf 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] discards f008a24ca95 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] discards 85598230677 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] discards 1bf807c4c42 93: onsuccess: #544: 1: Success after linux: 34 commits discards c677ac8788b 92: onsuccess: #543: 1: Success after glibc: 4 commits discards f032a475b12 91: onsuccess: #539: 1: Success after linux: 27 commits discards 1147a1c173d 90: onsuccess: #538: 1: Success after glibc: 10 commits discards b7919694540 89: onsuccess: #536: 1: Success after binutils: 27 commits discards 323c1a089c2 88: onsuccess: #534: 1: Success after linux: 12 commits discards 916aadca304 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] discards 4ed3b05d4b3 86: onsuccess: #532: 1: Success after gcc: 16 commits discards 9fcb4be9125 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] discards 1e52328b189 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] discards 42effaa1eef 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] discards 0a905a3d821 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] discards a4d61c4cd63 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] discards a243ae95bf6 80: onsuccess: #524: 1: Success after linux: 9 commits discards cef17bcf4f5 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 4b5c8607b7f 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 7320e1324d1 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] discards a9188c2139e 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] discards 1e42402ec69 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] discards fe298234302 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] discards 052316c3503 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] discards 2e12b4146c7 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards d1725bb2cc3 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] discards 3a5f6ce6ffd 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] discards 22c5013a0f1 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] discards 4c648aa8823 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] discards 1a884a31ade 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] discards c370c932296 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] discards 1202975eb8b 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] discards c19d559ece6 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] discards 262ab2d965e 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] discards 579c3fa58b3 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] discards f0a1a3b6c67 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] discards 669e12e79fd 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] discards f7eea3df147 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] discards c4ad44169de 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] discards 1fee95db1e1 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] discards d5d34e06c56 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] discards 6807180d7ac 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] discards 964d3c30ed6 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] discards fbe694483db 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] discards ea35a9cdfef 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] discards 40bb969e78e 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 1e50369fb4a 50: onsuccess: #490: 1: Success after binutils: 6 commits discards e79f069a578 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 9a906ab0268 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] discards eb0f28361f9 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] discards 082242b3d41 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] discards 586ce32fd1d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] discards 4d8b5accf23 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] discards ab1c9fab5eb 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] discards fc165fc1d88 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] discards 28983bff9a3 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] discards 9a7a330150f 40: onsuccess: #476: 1: Success after linux: 69 commits discards d5c9d7d3acb 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 7f8bafac4ca 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] discards b55c865c01b 37: onsuccess: #470: 1: Success after binutils: 3 commits discards c1ce0ac48d4 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] discards 38123909f3b 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 0e729d9f549 34: onsuccess: #465: 1: Success after binutils: 11 commits new 15cc4b7f3ab 34: onsuccess: #465: 1: Success after binutils: 11 commits new f0952a5feac 35: onsuccess: #467: 1: Success after glibc: 2 commits new bc2fa644234 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65 [...] new b3c0e10abd7 37: onsuccess: #470: 1: Success after binutils: 3 commits new 9f8003350f7 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g [...] new ebc051582e2 39: onsuccess: #474: 1: Success after binutils: 8 commits new ef048e7ff50 40: onsuccess: #476: 1: Success after linux: 69 commits new fd951eddfab 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gd [...] new 0c84461df8b 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gd [...] new 93dfadcbbb0 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gd [...] new 92478bce5f2 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gl [...] new 559cf2dc55a 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gl [...] new 32f2736b19b 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gl [...] new bc5a1692f92 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gd [...] new 66174102837 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gd [...] new db5896c3660 49: onsuccess: #487: 1: Success after binutils: 11 commits new 9194396410b 50: onsuccess: #490: 1: Success after binutils: 6 commits new af2ec3abbb0 51: onsuccess: #493: 1: Success after binutils: 13 commits new 554f5512fa9 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gl [...] new 9da409eb871 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gl [...] new cfaf29e7b5a 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gl [...] new 380ec411d89 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gd [...] new 8e0fd74a053 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gl [...] new cae5839c4bc 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gl [...] new 20eaae9df50 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gl [...] new b73307011c4 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gl [...] new ecbc917cc2c 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gl [...] new d6f3595077d 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gd [...] new f29ff95d1ba 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gl [...] new d47be7e2922 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gl [...] new 134bc13dc22 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gd [...] new e0e6d4bb186 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gl [...] new 6899b661635 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gl [...] new 9a5660dde78 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gl [...] new d9556f294dd 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gl [...] new fc08ed4a766 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gd [...] new ecf49e2496d 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gl [...] new a11a16615c9 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gl [...] new 4f12d4eea54 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new c3181edc363 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gd [...] new ef269be23a3 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gd [...] new 2c493d4af6d 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gd [...] new bfcde8a19ca 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gd [...] new 5404c004619 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gl [...] new f9f5c8de56b 78: onsuccess: #522: 1: Success after binutils: 10 commits new ee226d903d9 79: onsuccess: #523: 1: Success after gcc: 25 commits new ac42ee11820 80: onsuccess: #524: 1: Success after linux: 9 commits new 0bb023fcfbc 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gl [...] new 9a0329b3f53 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gl [...] new c6b943e231a 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gl [...] new a4440147718 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gl [...] new effa6cf4ce9 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gl [...] new c05320f45d5 86: onsuccess: #532: 1: Success after gcc: 16 commits new dd290911257 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-g [...] new 8ac5867370e 88: onsuccess: #534: 1: Success after linux: 12 commits new 78c84eea48d 89: onsuccess: #536: 1: Success after binutils: 27 commits new a9884253fc4 90: onsuccess: #538: 1: Success after glibc: 10 commits new 5db8574549f 91: onsuccess: #539: 1: Success after linux: 27 commits new 429bdb8bb50 92: onsuccess: #543: 1: Success after glibc: 4 commits new 499870614d4 93: onsuccess: #544: 1: Success after linux: 34 commits new bfb55148637 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gl [...] new 94ab3af6d1d 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gl [...] new c586b297a84 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gd [...] new f36b6ec72f1 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gd [...] new 5d264e7a1fe 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gl [...] new 033e7df5bdc 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gl [...] new eef0decd848 100: onsuccess: #551: 1: Success after binutils/gcc/linux/g [...] new 48de63536bf 101: onsuccess: #552: 1: Success after binutils/gcc/linux/g [...] new 99b0a498696 102: onsuccess: #553: 1: Success after binutils/gcc/linux/g [...] new 6c86fb2f223 103: onsuccess: #555: 1: Success after binutils: 4 commits new 807f52cd65f 104: onsuccess: #558: 1: Success after binutils: 3 commits new 0a73bf04e64 105: onsuccess: #560: 1: Success after binutils/gcc/linux/g [...] new 1810b14706f 106: onsuccess: #561: 1: Success after binutils/gcc/linux/g [...] new 5337dff4ccd 107: onsuccess: #562: 1: Success after binutils/gcc/linux/g [...] new eb12fca2a76 108: onsuccess: #563: 1: Success after binutils/gcc/linux/g [...] new 9ece62695d4 109: onsuccess: #564: 1: Success after binutils/gcc/linux/g [...] new 3cbd1feae00 110: onsuccess: #565: 1: Success after binutils/gcc/linux/g [...] new 42d4969d947 111: onsuccess: #566: 1: Success after binutils/gcc/linux/g [...] new 172d645007f 112: onsuccess: #567: 1: Success after binutils/gcc/linux/g [...] new d3d68732eb8 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 [...] new 5cb0ccc38eb 114: onsuccess: #569: 1: Success after binutils/gcc/linux/g [...] new a305a108497 115: onsuccess: #570: 1: Success after binutils/gcc/linux/g [...] new e3351bbe44f 116: onsuccess: #571: 1: Success after binutils/gcc/linux/g [...] new 73363fb1566 117: onsuccess: #572: 1: Success after binutils/gcc/linux/g [...] new ff1193adb76 118: onsuccess: #573: 1: Success after binutils/gcc/linux/g [...] new 172383d1097 119: onsuccess: #574: 1: Success after binutils/gcc/glibc/g [...] new 3f443ed42dd 120: onsuccess: #575: 1: Success after binutils/gcc/linux/g [...] new f4c526e8b8d 121: onsuccess: #576: 1: Success after binutils/gcc/linux/g [...] new 07354cb0815 122: onsuccess: #577: 1: Success after binutils/gcc/linux/g [...] new 746183346cc 123: onsuccess: #578: 1: Success after binutils/gcc/linux/g [...] new 1c5be6724bb 124: onsuccess: #579: 1: Success after binutils/gcc/linux/g [...] new c1b105d35c6 125: onsuccess: #581: 1: Success after binutils: 4 commits new 7232d2ae12d 126: onsuccess: #582: 1: Success after gcc: 9 commits new dc46050354b 127: onsuccess: #584: 1: Success after linux: 21 commits new fc00b92454d 128: onsuccess: #586: 1: Success after binutils: 22 commits new 90ac0f24ac2 129: onsuccess: #588: 1: Success after linux: 4 commits new 4f9df7af57e 130: onsuccess: #589: 1: Success after binutils/gcc/linux/g [...] new ab64253992c 131: onsuccess: #590: 1: Success after binutils/gcc/linux/g [...] new de19b4b2add 132: onsuccess: #591: 1: Success after binutils/gcc/linux/g [...] new f4a0e31bd1c 133: onsuccess: #592: 1: Success after binutils/gcc/linux/g [...] new 96fc988b0fa 134: onsuccess: #593: 1: Success after binutils/gcc/linux/g [...] new 809a4e16895 135: onsuccess: #594: 1: Success after binutils/gcc/linux/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (f63f94c1992) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1724 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 53524 -> 53256 bytes 04-build_abe-gcc/console.log.xz | Bin 234632 -> 235636 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8496 -> 8516 bytes 07-build_abe-glibc/console.log.xz | Bin 236360 -> 235084 bytes 08-build_abe-gdb/console.log.xz | Bin 51384 -> 51884 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2612 -> 2544 bytes 11-check_regression/console.log.xz | Bin 7080 -> 7284 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 29 +- 11-check_regression/mail-body.txt | 115 +- 11-check_regression/results.compare | 72 +- 11-check_regression/results.compare2 | 154 +- 11-check_regression/results.regressions | 72 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 117 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 72 +- sumfiles/g++.log.xz | Bin 2895548 -> 2891564 bytes sumfiles/g++.sum | 150 +- sumfiles/gcc.log.xz | Bin 2550696 -> 2579640 bytes sumfiles/gcc.sum | 5112 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 959620 -> 957776 bytes sumfiles/gfortran.sum | 64 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2256 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 230028 -> 230376 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2664 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 470556 -> 471316 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 3111 insertions(+), 2968 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page: