Tcwg-commits February 2023

tcwg-commits@lists.linaro.org

5 participants
3393 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (08f6d766c4 -> c76c5be6ed)

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 08f6d766c4 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] discards bc9f891f9a 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] discards b323f46f3f 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits discards ecfc3a8cb8 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] discards ae185fb58a 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] discards d9d0a351cc 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] discards 0c17b1c4da 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] discards 509798919b 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits discards a8853e83b3 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] discards acd137a8ec 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] discards cb3093d2d1 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] discards 8b3fbeb529 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] discards 730a0f9355 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits discards cf9409bb6f 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits discards 0e513ab4b0 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] discards b86c02e4c5 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] discards ebb3125f1b 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] discards 6f8683333a 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] discards b658e24b0f 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] discards 3930a2ee70 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] discards dfecc4baa8 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] discards fccb32e2b8 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] discards 66528897d3 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] discards c764b7eeae 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] discards 8ffaeafed4 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] discards 0864da249f 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] discards 305ff67768 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] discards be5907183a 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] discards 9689dbc844 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] discards ea1a97c630 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] discards ba52638ae7 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] discards 0a8ad0ffdf 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] discards b7cfecb6ee 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] discards 75d8504a9c 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] discards 8c6b002018 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] discards 591fabef4a 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] discards 15fa7245bb 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] discards 262887cfdb 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits discards ae6261dac8 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] discards 1273c5062c 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] discards ba753be7da 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] discards 8040619f36 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] discards db691b7ad9 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] discards 4d54aef963 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits discards e22ba95191 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] discards 343de5ba86 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards b9f94dfe97 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards 18530ffc53 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards beab172d7e 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 587b7ceac8 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 931f20c3bf 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards bb12b698f1 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 1311103310 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards 7447d694dc 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards 6443d9a616 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards de0f497f05 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 436a660b08 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards dd7e94b93a 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards 786a998641 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 6b5680f2f6 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 7c06506105 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards b394641dbe 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards eb46fbdadd 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 3686c150af 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 2bed22e24c 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards da748934c4 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 5dbd5391b3 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 81a03848a1 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 6830fc2bba 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards 3b901c5141 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 6e1b97f04e 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards e650f82b48 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards a186d29355 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 7edfaa5252 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 1a16d2b50b 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards a3647f7479 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards dd4b56f58a 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 0cded9fe15 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards c8c06252ab 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 9c4d82a4e9 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 271dfd012c 305: force: #2006: 7: Success after gdb: 2 commits discards 9ecba3fbe7 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 2b90fc748b 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 15e4dd128a 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards fc6d56ca45 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 1cda628faf 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards f97de4e270 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 2f994d620f 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 65ca3366fc 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards c3a50024a7 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards f98b55e5a6 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 402c48be9e 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 98326f59a5 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards f63527b302 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards ebae506b54 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards d473a249f2 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 719f12c8ef 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards a4e859e23a 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 07686428ca 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards 2242936c8d 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards bf0cc67c5a 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 2cab226fc0 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new c950b7deb9 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new 41505d15b3 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 751e555fef 288: onsuccess: #1985: 7: Success after gcc: 17 commits new a565c519d9 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new bc47ea0efa 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 68fc3fb693 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new fbcee213a1 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 32d01030f7 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new b436ba3138 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 637539a224 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 112cf2a33c 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new ef2e3b5eef 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new f267984b57 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new bde288f298 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 5867033f51 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 1dccffe8f3 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 23e4f24a36 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 6993af6261 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 2677bd349e 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 9613ef33a4 305: force: #2006: 7: Success after gdb: 2 commits new fa48868635 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new e4e3690831 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new 4701675b0a 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 4c8341052f 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new b6984f5b75 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 2ec4d885ea 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new e55120927e 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new a8f5609851 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new e0683ea010 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 29101204b1 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 7f4125504b 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 70e633b946 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new ea1e54a737 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 36bd87569d 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 08f4de3f52 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new d2941cdc5f 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new a94ff3cef2 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new c236e3a1c4 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new a988857b22 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new b0d1cfae68 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new b5d56eba17 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new f87917f07c 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new dcfe3dcc6a 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 85b030373f 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 9e01543fa3 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 996c8abf86 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new a91b543e00 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 1ee1d15e78 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new b281710867 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new a5170c6ed9 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new f656fe33b4 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 0f4f6ee882 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new 31a9b94e24 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new b7e578db92 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 6296796af4 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 103284296b 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] new 27b82087ef 342: onsuccess: #2043: 7: Success after binutils/gcc/gdb: 9 commits new 4a0fd7edd7 343: onsuccess: #2044: 7: Success after binutils/gcc/linux/g [...] new 2839a73310 344: onsuccess: #2045: 7: Success after binutils/gcc/linux/g [...] new 110a8e9e8b 345: onsuccess: #2046: 7: Success after basepoints/gcc-13-51 [...] new 5f215f6b44 346: onsuccess: #2047: 7: Success after binutils/gcc/linux/g [...] new b95547a7c2 347: onsuccess: #2048: 7: Success after binutils/gcc/gdb: 27 [...] new 332a0a4434 348: onsuccess: #2049: 7: Success after binutils/gcc/gdb: 5 commits new 4637d4362e 349: onsuccess: #2050: 7: Success after binutils/gcc/linux/g [...] new 194819583d 350: onsuccess: #2051: 7: Success after binutils/gcc/gdb: 35 [...] new a2c59a40e2 351: onsuccess: #2052: 7: Success after binutils/gcc/linux/g [...] new 43b970d12d 352: onsuccess: #2053: 7: Success after binutils/gcc/linux/g [...] new f24c07f764 353: onsuccess: #2054: 7: Success after binutils/gcc/glibc/g [...] new 5db34bbc1e 354: onsuccess: #2055: 7: Success after binutils/gcc/linux/g [...] new 3d4f006ebd 355: onsuccess: #2056: 7: Success after binutils/gcc/linux/g [...] new 3ccf6551a2 356: onsuccess: #2057: 7: Success after binutils/gcc/linux/g [...] new 1dda805f78 357: onsuccess: #2058: 7: Success after binutils/gcc/linux/g [...] new 6261099e7e 358: onsuccess: #2059: 7: Success after binutils/gcc/linux/g [...] new b140834206 359: onsuccess: #2060: 7: Success after binutils/gcc/linux/g [...] new 8dcf9c6c2c 360: onsuccess: #2061: 7: Success after binutils/gcc/linux/g [...] new 4c68bc5c99 361: onsuccess: #2062: 7: Success after binutils/gcc/linux/g [...] new 1abdcdf0db 362: onsuccess: #2063: 7: Success after binutils/gcc/linux/g [...] new 83ae80007b 363: onsuccess: #2064: 7: Success after binutils/gcc/linux/g [...] new db3871f5fd 364: onsuccess: #2065: 7: Success after binutils/gcc/linux/g [...] new d4d0bfcfba 365: onsuccess: #2066: 7: Success after binutils/gcc/gdb: 71 [...] new 548c7c9887 366: onsuccess: #2067: 7: Success after binutils/gcc/linux/g [...] new 3ac2206684 367: onsuccess: #2068: 7: Success after binutils/gcc/linux/g [...] new 628d19f81e 368: onsuccess: #2069: 7: Success after binutils/gcc/linux/g [...] new f91797e399 369: onsuccess: #2070: 7: Success after binutils/gcc/glibc/g [...] new 76e93edbd1 370: onsuccess: #2071: 7: Success after binutils/gcc/gdb/qem [...] new 060ecfd245 371: onsuccess: #2072: 7: Success after binutils/gcc/linux/g [...] new 6565905b05 372: onsuccess: #2073: 7: Success after binutils/gcc/gdb: 3 commits new 77cc2bf0fd 373: onsuccess: #2074: 7: Success after binutils/gdb: 4 commits new 5aaa8da08b 374: onsuccess: #2075: 7: Success after binutils/gcc/gdb/qem [...] new 21632e87b4 375: onsuccess: #2076: 7: Success after binutils/gcc/linux/g [...] new f9bd1aede1 376: onsuccess: #2077: 7: Success after v6.2-rc6-273-g837c07 [...] new babe3aaef1 377: onsuccess: #2078: 7: Success after glibc-2.37.9000-17-g [...] new 2c93f1d7b9 378: onsuccess: #2079: 7: Success after gcc/qemu: 42 commits new a088ac6ce0 379: onsuccess: #2080: 7: Success after binutils/gcc/linux/g [...] new eb4c5ff2d7 380: onsuccess: #2081: 7: Success after basepoints/gcc-13-57 [...] new 95032d4465 381: onsuccess: #2082: 7: Success after binutils/gcc/gdb/qem [...] new 67a0c36215 382: onsuccess: #2083: 7: Success after binutils/gcc/linux/g [...] new 778bb4c5d8 383: onsuccess: #2084: 7: Success after binutils/gcc/gdb: 4 commits new 4eaa322cea 384: onsuccess: #2085: 7: Success after binutils/gcc/glibc/g [...] new 538ab83a42 385: onsuccess: #2086: 7: Success after binutils/gcc/linux/g [...] new c76c5be6ed 386: onsuccess: #2087: 7: 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 (08f6d766c4) \ 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 1780 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 04-build_abe-binutils/console.log.xz | Bin 32308 -> 30984 bytes 05-build_abe-stage1/console.log.xz | Bin 73428 -> 72644 bytes 07-build_abe-linux/console.log.xz | Bin 8680 -> 8660 bytes 08-build_abe-glibc/console.log.xz | Bin 245072 -> 244428 bytes 09-build_abe-stage2/console.log.xz | Bin 204588 -> 203500 bytes 10-build_abe-gdb/console.log.xz | Bin 39692 -> 38336 bytes 11-build_abe-qemu/console.log.xz | Bin 32476 -> 32472 bytes 12-check_regression/console.log.xz | Bin 4260 -> 4572 bytes 13-update_baseline/console.log | 40 +++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 46 +++++++++++++++++------------------ 22 files changed, 53 insertions(+), 53 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch master updated (c9245f0df5a -> 4170bc7ea84)

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 c9245f0df5a Automatic date update in version.in new 4170bc7ea84 Re: Resetting section vma after _bfd_dwarf2_find_nearest_line 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/dwarf2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (3a4ba3286d -> e1b124fdf9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 3a4ba3286d 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] discards 565ed408f9 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] discards 358415b291 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] discards 76ca7ae149 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] discards 096e3364c1 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] discards e04a25c24d 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] discards 321ca7dce3 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] discards 89e8142a2a 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] discards 82e863b267 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] discards c1f38a25ad 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] discards ca1be3d808 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] discards ba3ffaf26d 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] discards 59b58f2458 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits discards aa45f46948 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] discards 4fb4a4ccde 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] discards 6c1406bdad 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] discards d53245db61 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] discards 50a7e43746 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] discards dc2f557f9e 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] discards 93fc55dc3f 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] discards c29b7c1387 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] discards 2f72f67ce7 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] discards c959474c10 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] discards d45cd934ba 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] discards aac8d4ded8 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] discards 3881b33829 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] discards 713f075059 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] discards 3bd0b2f9e9 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] discards 495f5ce3c0 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] discards 9a880d6754 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] discards b93e0ec421 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] discards ea30d2e851 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] discards 116f00f03c 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits discards 3345dad698 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits discards 8be9365a6e 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits discards 74bcd6ec58 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] discards 053fb47850 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits discards 5912e1bfed 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] discards 12d2394e2d 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] discards 46e93da1cc 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] discards a559700e4e 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] discards 7fcf16fa7f 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] discards d96545cd2c 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] discards 9a7549f65e 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] discards 5afb1b897d 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] discards 2ad891f9e7 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] discards bf7b2c67e6 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] discards 43c7e387c7 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] discards 8fec4a5fe4 122: onsuccess: #909: 1: Success after linux: 2753 commits discards cea5bb2510 121: onsuccess: #908: 1: Success after glibc: 2 commits discards 1b736a3f91 120: onsuccess: #906: 1: Success after binutils: 29 commits discards d81386facb 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] discards 1f168f8b71 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] discards 522bd830d1 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] discards 0648bbdec6 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] discards 59ef81e4ae 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] discards 5dafb6c11f 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] discards 68f4912e5e 113: onsuccess: #898: 1: Success after linux: 3 commits discards eebb324897 112: onsuccess: #896: 1: Success after binutils: 24 commits discards 7fe83776ca 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] discards 58bf2aa830 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards b7fff3e916 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] discards 92ad5e4a3f 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 359bbdbb1d 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] discards 2665b55eaa 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 33aaac5e2f 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 618207bb71 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 8bcca0c9ab 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards a6a51b3b8a 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 7447f9cf98 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 17b0fa61b1 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards f59accd4cc 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 6d2a385134 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards b2561ee7ad 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 520b483b2c 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 2504ca9086 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 806f524c37 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards de4a1ac978 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 255620fff2 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards e23146f17c 91: onsuccess: #870: 1: Success after binutils: 5 commits discards f62540aa3c 90: onsuccess: #867: 1: Success after binutils: 4 commits discards e4789b7dd4 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 8f4b1433e3 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards da085a5ea1 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards f0e1e469ed 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards 5c663949dc 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards ce21ef4674 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards a956263448 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards e07422c0a7 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards e6235b54b1 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards efefe7e519 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards 1cde08022b 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards b8d23f4aa4 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards 8d9a032e1e 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 0df3843b62 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards cf6273e7c6 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards 37cf9381dd 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards ce31cf5b90 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 93592bfa8a 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 71632caffb 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 776c71a9c3 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new d29aab3649 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new baf63f9374 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 8e45cf8318 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new 8a349fce16 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new f66d34b5e9 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new da982363a0 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new f2a4b01495 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 6f74782a11 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new b9bacb53e4 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 4891abdbd1 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new fd3ab69275 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 4603c4f4cd 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 4198f254d9 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new b1c7663439 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new ed204a8f47 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new 918bd0b513 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 54807bb6c4 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new 62d3eb47af 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new c9f319d134 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 620a4d9a6a 89: onsuccess: #864: 1: Success after binutils: 25 commits new 208c2e1a33 90: onsuccess: #867: 1: Success after binutils: 4 commits new ad136f1e74 91: onsuccess: #870: 1: Success after binutils: 5 commits new 2bec6111b6 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new b07f453db5 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new b1be9cd75d 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 5f873be54d 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 07ce3e5573 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new f0542f65c1 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new ee3178ab39 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new c037ff2663 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new a85539a1e2 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new 7d0266a307 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 24adb244df 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 8f98462001 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new af96f83d4b 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 7addba83ce 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 8d92983a97 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new e1dab45d2c 107: onsuccess: #888: 1: Success after binutils/gcc/linux/gd [...] new d108c28582 108: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new a31c4642a1 109: onsuccess: #890: 1: Success after binutils/gcc/linux/gl [...] new 35ad4cc377 110: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new 913f25bdea 111: onsuccess: #893: 1: Success after binutils/gcc/linux: 2 [...] new 1d8dc159c2 112: onsuccess: #896: 1: Success after binutils: 24 commits new 583a3f6262 113: onsuccess: #898: 1: Success after linux: 3 commits new 2d736bde24 114: onsuccess: #899: 1: Success after binutils/gcc/linux/gl [...] new c65a62eb09 115: onsuccess: #900: 1: Success after binutils/gcc/linux/gl [...] new a2baadf393 116: onsuccess: #901: 1: Success after binutils/gcc/linux/gl [...] new 336ae52467 117: onsuccess: #902: 1: Success after binutils/gcc/linux/gl [...] new 0c78c7da23 118: onsuccess: #903: 1: Success after binutils/gcc/linux/gd [...] new 7fcc5a95dc 119: onsuccess: #904: 1: Success after binutils/gcc/linux/gd [...] new 717bb4100a 120: onsuccess: #906: 1: Success after binutils: 29 commits new b72d9f35b4 121: onsuccess: #908: 1: Success after glibc: 2 commits new b920d83ffa 122: onsuccess: #909: 1: Success after linux: 2753 commits new 3ea34c6db1 123: onsuccess: #910: 1: Success after binutils/gcc/linux/gl [...] new 667ef1db2e 124: onsuccess: #911: 1: Success after binutils/gcc/linux/gd [...] new b8784513b7 125: onsuccess: #912: 1: Success after binutils/gcc/linux/gl [...] new 1438d4a4a2 126: onsuccess: #913: 1: Success after binutils/gcc/linux/gd [...] new 5887e9a626 127: onsuccess: #914: 1: Success after binutils/gcc/linux/gd [...] new be62ee8eb3 128: onsuccess: #915: 1: Success after binutils/gcc/glibc/gd [...] new 00c3c336d5 129: onsuccess: #916: 1: Success after binutils/gcc/linux/gl [...] new f4ab346e6b 130: onsuccess: #917: 1: Success after binutils/gcc/linux/gl [...] new 4eefa3e271 131: onsuccess: #918: 1: Success after binutils/gcc/linux/gl [...] new 91c019165f 132: onsuccess: #919: 1: Success after binutils/gcc/linux/gl [...] new dfdfe6ab83 133: onsuccess: #920: 1: Success after binutils/gcc/linux/gd [...] new 811a945b8b 134: onsuccess: #921: 1: Success after binutils/gcc/gdb: 26 commits new 18291a296d 135: onsuccess: #922: 1: Success after binutils/gcc/linux/gd [...] new f8118c5215 136: onsuccess: #923: 1: Success after binutils/gcc/gdb: 10 commits new 676f826649 137: onsuccess: #924: 1: Success after binutils/gcc/gdb: 43 commits new db0f4420de 138: onsuccess: #925: 1: Success after binutils/gcc/gdb: 11 commits new 8a0dad98a8 139: onsuccess: #926: 1: Success after binutils/gcc/linux/gl [...] new 9d026625df 140: onsuccess: #927: 1: Success after binutils/gcc/linux/gd [...] new 105737eeb1 141: onsuccess: #928: 1: Success after binutils/gcc/linux/gd [...] new 4b6b91aaeb 142: onsuccess: #929: 1: Success after binutils/gcc/linux/gd [...] new 24d2171f86 143: onsuccess: #931: 1: Success after binutils/gcc/linux/gl [...] new 448c1f5262 144: onsuccess: #933: 1: Success after binutils/gcc/glibc/gd [...] new 70579854b3 145: onsuccess: #934: 1: Success after binutils/gcc/linux/gl [...] new d936a9779b 146: onsuccess: #939: 1: Success after binutils/gcc/linux/gl [...] new 775ad162c7 147: onsuccess: #940: 1: Success after binutils/gcc/linux/gd [...] new 9bbfc6b89f 148: onsuccess: #941: 1: Success after binutils/gcc/linux/gd [...] new f9cd5e9de1 149: onsuccess: #942: 1: Success after binutils/gcc/linux/gl [...] new e0482a6222 150: onsuccess: #943: 1: Success after binutils/gcc/linux/gl [...] new e3d65a7304 151: onsuccess: #944: 1: Success after binutils/gcc/linux/gl [...] new c7cb81bc87 152: onsuccess: #945: 1: Success after binutils/gcc/linux/gd [...] new 73b7a567d4 153: onsuccess: #946: 1: Success after binutils/gcc/linux/gl [...] new 5a971abafc 154: onsuccess: #947: 1: Success after binutils/gcc/linux/gl [...] new d6182b087f 155: onsuccess: #948: 1: Success after binutils/gcc/linux/gl [...] new c11350b760 156: onsuccess: #949: 1: Success after binutils/gcc/linux/gd [...] new b4329c0c2b 157: onsuccess: #950: 1: Success after binutils/gcc/linux/gd [...] new c5aa6f8178 158: onsuccess: #951: 1: Success after gcc/linux: 19 commits new 4a30fcea8d 159: onsuccess: #952: 1: Success after binutils/gcc/linux/gl [...] new c00809500f 160: onsuccess: #953: 1: Success after binutils/gcc/linux/gl [...] new 15d72a0d24 161: onsuccess: #954: 1: Success after binutils/gcc/linux/gl [...] new 3a6013ad33 162: onsuccess: #955: 1: Success after binutils/gcc/linux/gl [...] new fea8394455 163: onsuccess: #956: 1: Success after binutils/gcc/linux/gd [...] new ab440dd6a6 164: onsuccess: #957: 1: Success after binutils/gcc/glibc/gd [...] new fed1c7b92e 165: onsuccess: #958: 1: Success after binutils/gcc/linux/gd [...] new c36dec4b99 166: onsuccess: #959: 1: Success after binutils/gcc/linux/gl [...] new d4137ef51c 167: onsuccess: #960: 1: Success after binutils/gcc/linux/gl [...] new db5ee4c1f8 168: onsuccess: #961: 1: Success after binutils/gcc/linux/gl [...] new 85d3dab980 169: onsuccess: #962: 1: Success after binutils/gcc/linux/gl [...] new 689a2771e8 170: onsuccess: #963: 1: Success after binutils/gcc/linux/gl [...] new e1b124fdf9 171: onsuccess: #964: 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 (3a4ba3286d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gdb/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1764 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 38748 -> 39840 bytes 04-build_abe-gcc/console.log.xz | Bin 213556 -> 214660 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8520 -> 8652 bytes 07-build_abe-glibc/console.log.xz | Bin 244004 -> 244548 bytes 08-build_abe-gdb/console.log.xz | Bin 38528 -> 39676 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3840 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2140 -> 3324 bytes 11-check_regression/console.log.xz | Bin 9264 -> 9088 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 41 +- 11-check_regression/mail-body.txt | 165 +- 11-check_regression/results.compare | 84 +- 11-check_regression/results.compare2 | 575 ++-- 11-check_regression/results.regressions | 84 +- 12-update_baseline/console.log | 30 +- 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 | 167 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- results | 84 +- sumfiles/gdb.log.xz | Bin 1986104 -> 2000192 bytes sumfiles/gdb.sum | 4651 +++++++++++++++---------------- 31 files changed, 2792 insertions(+), 3145 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig updated (432d860340 -> 463e75c7ae)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-arm-lts-defconfig in repository toolchain/ci/base-artifacts. from 432d860340 47: onsuccess: #464: boot: Success after binutils/llvm/linux [...] new 463e75c7ae 48: onsuccess: #465: boot: Success after binutils/llvm/linux [...] 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 1768 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30608 -> 31884 bytes 04-build_kernel_llvm/console.log.xz | Bin 64752 -> 64408 bytes 05-build_abe-qemu/console.log.xz | Bin 31672 -> 31868 bytes 06-build_linux/console.log.xz | Bin 3484 -> 3484 bytes 07-boot_linux/console.log.xz | Bin 5808 -> 5804 bytes 08-check_regression/console.log.xz | Bin 4296 -> 4300 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-12 updated (6f23c9077fe -> 6bd330777a3)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch releases/gcc-12 in repository gcc. from 6f23c9077fe Fix PR 108582: ICE due to PHI-OPT removing a still in use s [...] new 6bd330777a3 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 28 ++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 34 ++++++++++++++++++++++++++++++++++ 3 files changed, 63 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-11 updated (5125737077a -> f18f568caf2)

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 5125737077a tree-optimization/106809 - compile time hog in VN new f18f568caf2 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch master updated (7ab75a6e6df -> 8f3b85efbf5)

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 7ab75a6e6df Fix 'libgomp.fortran/reverse-offload-6.f90' nvptx offloadin [...] new 8f3b85efbf5 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 38 ++++++++++++++++++++++++++++++++++++++ gcc/DATESTAMP | 2 +- gcc/analyzer/ChangeLog | 7 +++++++ gcc/fortran/ChangeLog | 6 ++++++ gcc/testsuite/ChangeLog | 30 ++++++++++++++++++++++++++++++ libgomp/ChangeLog | 5 +++++ 6 files changed, 87 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[gcc] branch releases/gcc-10 updated (051f78a5c1d -> feb7d31d322)

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 051f78a5c1d tree-optimization/106809 - compile time hog in VN new feb7d31d322 Daily bump. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/ChangeLog | 9 +++++++++ gcc/DATESTAMP | 2 +- gcc/testsuite/ChangeLog | 8 ++++++++ 3 files changed, 18 insertions(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 9 months

[binutils-gdb] branch binutils-2_40-branch updated (5d13759a681 -> cd1edf4e735)

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_40-branch in repository binutils-gdb. from 5d13759a681 Automatic date update in version.in new cd1edf4e735 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.

1 year, 9 months

[binutils-gdb] branch gdb-13-branch updated (e045e0fa775 -> 257660c3def)

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-13-branch in repository binutils-gdb. from e045e0fa775 Automatic date update in version.in new 257660c3def 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.

1 year, 9 months

Jump to page: