Tcwg-commits January 2023

tcwg-commits@lists.linaro.org

5 participants
4127 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (4f2fd8db73 -> 98b7637fbe)

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 4f2fd8db73 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards dcc52ef4ba 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards 7eb8fa3f6d 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards ae6278680e 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 8251296d00 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 264bed0af7 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards 0abce7cd89 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 31f0a51e96 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 3d1462a746 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards ce90f4109b 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards abfcf59ef4 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 7a64c8e1d4 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards da149aae39 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 2209c6085a 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 2f945701f0 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 405c07814d 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards a4a872f193 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 650f7c19bc 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 5b194eca14 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards ab128015e9 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards c5ac90b7bd 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards ad23adaa1f 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards fee427a855 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards f79da1ad9c 305: force: #2006: 7: Success after gdb: 2 commits discards 8f9e4bc449 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 2d44ca2863 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 3da8496248 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards d3c48e1520 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards dd2a74ff04 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 1cbc90b2bd 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards f916923b73 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards e4a14b019b 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards a6e814eb94 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards ee72fd8116 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards f2751e9325 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 0971bd0edb 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 8cdf06a464 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 8ce8235ed9 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 3930114bae 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards c7aa838cbe 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards bbedae8307 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 12c5e716b9 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards ef60074bda 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 0c5d8356ea 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 760db79870 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards b47be385ab 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 4f32ec1e30 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards a6c1578abf 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 158442e30a 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 7812adf677 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards a030cfb75b 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 12da21fb1b 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards b6d563df04 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards d521cc8eb5 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 98b9ec38d0 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 8a2181b7ef 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards aa3b69fac1 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 3fd625c100 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards ae6abc9203 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards 212c01e5e0 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 4c160af205 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 28d7168a24 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 8253baa431 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 2b633239d0 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards b4bed0fd1c 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 2407e4f98e 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 539a6d538e 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards abad1161c3 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards a1bf808e47 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 2633e04c03 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 887a3f3821 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 619467e193 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 976cdb4bc1 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 1a48b52378 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 3ed9432107 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 8fe23ed32e 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 2d459a4345 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards e6d21af7c7 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 951d8f82f3 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards e208f9b38b 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards a82447a094 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 17cba21a15 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards e1f50e85fd 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards bbe8bd5746 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards f2a242bbef 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards d13b2bdaee 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards d08d36489b 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 6c7dcdc9d7 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 04e2cb6a8b 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards b00d17aef5 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards b74783dea9 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards e65e8b46d6 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards f6be790d7f 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 119bae8fe6 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards 62c2ead642 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 79e7d85d0b 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 23558e50a9 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 378767ccc7 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards da0a73747b 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards d1dd784590 229: force: #1926: 7: Success after gcc: 7 commits discards 9c2f2fe37d 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 9d794c5e2c 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new ac87225851 229: force: #1926: 7: Success after gcc: 7 commits new 2cbf5a1e23 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 0db57a8708 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 9ac9877a79 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new c481b3c84f 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 20a15a0ead 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 0b87198939 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 8590f78eeb 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new d1c72afdff 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new d46e9bdff2 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new b920b20e92 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new 5952396eaf 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 3e44a55292 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 2a41679efc 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new b7118f4bc3 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new b0b7495be4 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new fda19913a8 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 6d8cd09588 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 781f35315a 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 09f7b3d4a1 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 768b53c757 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 5fd1181bba 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 0bcdaffe1a 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 0a2bf33867 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new a2371c859c 253: onsuccess: #1950: 7: Success after glibc: 2 commits new c5d4696b67 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new b53d1c6348 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 528dc81403 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new 14cf33d85a 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 0a6d52beaf 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 27cfdcc87b 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 1f488fe73e 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 5c48810674 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 108afec37d 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 3412bedb13 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 228e108982 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 67a7bfe24a 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new bfcc9b9e7d 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 060e98e564 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new 1f7097d973 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 6a44f0d24c 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new 788e6d27b3 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 69851f5577 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new 0eb8fbf288 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 4cdb2d9546 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 3121b3003f 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 51ef11537b 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new d8a1045432 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new ba455d91dd 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 9df8f321a6 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 549d466b95 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 844a5a7ce9 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 3fa051b417 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 52b6dc565f 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new a82b56f86d 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 922970be4a 284: onsuccess: #1981: 7: Success after gcc: 2 commits new c1d238ef4e 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 0b9b392f58 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new ed0bbef64a 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new d0dfa7e6d0 288: onsuccess: #1985: 7: Success after gcc: 17 commits new e3571dd434 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 1edc8e7be7 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new 5cbf7ab0af 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 246f0df2bc 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 290d85fc59 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new a4df5a9b4a 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new a3f42b2ccd 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new ab651e185b 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 3a7aa29acf 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new bd6138c175 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 6a17a975ce 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 953087555c 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new a7a56e83a4 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 6df462b888 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 157ba8bffe 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 8f12c8d2f8 304: onsuccess: #2002: 7: Success after gcc: 4 commits new f1dcc9727a 305: force: #2006: 7: Success after gdb: 2 commits new c3fe529a81 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new bd98963ecd 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new f2b7287f69 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 64d53cfa27 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new a903a25fa9 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new 10816ee88b 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 85adc33f78 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new c4afc06c05 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 1607010f3e 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new 070f0b2454 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new b1fd6999f4 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new c023e2d16b 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 2ef70d4e12 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 90e394391c 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 9b9f36e7c3 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 4688d9b4f9 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 01880dec23 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 80daf93c37 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 890ee761d5 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new e5e662da48 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new b74c45a38e 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 5d4e5322b1 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 6f6d78b94b 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new 98b7637fbe 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 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 (4f2fd8db73) \ 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 1704 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2788 bytes 04-build_abe-binutils/console.log.xz | Bin 32048 -> 32728 bytes 05-build_abe-stage1/console.log.xz | Bin 73020 -> 74112 bytes 07-build_abe-linux/console.log.xz | Bin 8744 -> 8876 bytes 08-build_abe-glibc/console.log.xz | Bin 244688 -> 247472 bytes 09-build_abe-stage2/console.log.xz | Bin 203976 -> 208160 bytes 10-build_abe-gdb/console.log.xz | Bin 39396 -> 40068 bytes 11-build_abe-qemu/console.log.xz | Bin 31900 -> 31840 bytes 12-check_regression/console.log.xz | Bin 3888 -> 3488 bytes 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 18 files changed, 52 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig updated (cb0da056dd -> e195a6f5a8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from cb0da056dd 35: onsuccess: #496: boot: Success after binutils/llvm/linux [...] new e195a6f5a8 36: onsuccess: #497: 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 1748 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32456 -> 32180 bytes 04-build_kernel_llvm/console.log.xz | Bin 65052 -> 63748 bytes 05-build_abe-qemu/console.log.xz | Bin 31168 -> 32012 bytes 06-build_linux/console.log.xz | Bin 3104 -> 3060 bytes 08-check_regression/console.log.xz | Bin 4300 -> 4256 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 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/release-arm updated (02d15eb1cc -> 4005aaf022)

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/release-arm in repository toolchain/ci/base-artifacts. from 02d15eb1cc 35: onsuccess: #210: 1: Success after gcc/linux/qemu: 379 commits new 4005aaf022 36: onsuccess: #211: 1: Success after gcc/qemu: 172 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 1744 -> 1792 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30436 -> 30152 bytes 04-build_abe-stage1/console.log.xz | Bin 87048 -> 86740 bytes 06-build_abe-linux/console.log.xz | Bin 8740 -> 8716 bytes 07-build_abe-glibc/console.log.xz | Bin 230084 -> 228972 bytes 08-build_abe-stage2/console.log.xz | Bin 221000 -> 221036 bytes 09-build_abe-gdb/console.log.xz | Bin 37020 -> 36784 bytes 10-build_abe-qemu/console.log.xz | Bin 31412 -> 31416 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3892 -> 3880 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2524 -> 2480 bytes 13-check_regression/console.log.xz | Bin 6656 -> 5728 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/mail-body.txt | 48 +- 13-check_regression/results.compare | 17 +- 13-check_regression/results.compare2 | 47 +- 13-check_regression/results.regressions | 26 - 14-update_baseline/console.log | 8 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 50 +- mail/mail-subject.txt | 2 +- manifest.sh | 28 +- results | 26 - sumfiles/g++.log.xz | Bin 2617392 -> 2591668 bytes sumfiles/g++.sum | 38 +- sumfiles/gcc.log.xz | Bin 2136432 -> 2146156 bytes sumfiles/gcc.sum | 2214 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 878068 -> 899904 bytes sumfiles/gfortran.sum | 9 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 196376 -> 196396 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 420532 -> 424144 bytes sumfiles/libstdc++.sum | 2 +- 41 files changed, 1207 insertions(+), 1329 deletions(-) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (e3a97b289d -> e3f6aa79e1)

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 e3a97b289d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] discards 888e6c4628 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 679ae0f468 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards df63cb11ef 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards 347b8dfcd5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards f29dffaaab 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 60bee4ea61 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 8de3c9a8e1 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 820c1fc646 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards 162bad64d9 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards 977c9e44b5 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards 83c88713d2 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards da86f3fec5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 1615fc9d5a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 164a4b8df1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards f37b50204a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards ea542fc42b 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards 50d9bae6e5 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards c5ee44c417 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards 13bf466705 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 156df7e07f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards 274ec0ecd0 295: onsuccess: #2545: 1: Success after linux: 10 commits discards eae522c6c2 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 625975f40c 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards 9781ba2304 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards 5816b5eaac 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards 7d879b2e75 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 273dd7196e 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards de6b57b285 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards a8a4042f6f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards 26928c451b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards 591e9e128e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 92fa56e3f7 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards e16d040b9b 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 890be2fdd8 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards a55e79aee4 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 188bda3878 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards f7ba85f439 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards 5b78303d36 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 81c83c1a03 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards f78956e8dd 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 850e7409a9 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards a873ef41bd 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards beda0c40f5 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards 82c68b2389 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 1acb96b14a 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards a2604a497f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards 5367a29d77 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 2c532fc02c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 7398163e7d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards e8fd7ad815 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards d9d81a15bc 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 40bd243076 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 304b46a9f0 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards b0e044721f 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards dd31de88a9 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 32172a84cc 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards f3162aa167 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 8f157bcbae 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards 16362046ed 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards cddfe3bfa5 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 4f46c4330f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards 90dab0e7a2 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 7b5e812917 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards 41e1d70905 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards a5bc396d55 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards ecd89056b0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 10161dc0cd 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 7df3532dc2 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 7918959151 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards b769bc5802 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards 6ab47eba03 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards bd0b6eb4d9 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards f309e2e756 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards 517171f479 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 5db8ea1f8a 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 0ec780f954 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards 52370e6ff8 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 478771b7a6 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 5794d43ea3 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 0a48b61f2f 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards d8f0d9ad8b 235: onsuccess: #2483: 1: Success after linux: 108 commits discards b023126a1b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 5503654859 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards d7802538ec 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards 0e31796c1e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards 6479b517ff 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 851fa402ac 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards 5c5f45eea2 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards bcd50a6c3c 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards aaf972ede1 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 4e5a073acc 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 6263fced66 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 536147eb06 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 105301bd9a 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards f4e096f83f 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards d293a6d9eb 220: onsuccess: #2465: 1: Success after linux: 572 commits discards d926fecb7b 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 26132d8728 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 5828f242a7 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards d0d8170ee9 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 8cf3015d0b 216: onsuccess: #2457: 1: Success after linux: 1736 commits new f0c67dc9eb 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 1b74584d0e 218: onsuccess: #2461: 1: Success after linux: 916 commits new 9ff00705fa 219: onsuccess: #2463: 1: Success after binutils: 3 commits new 596c4ded33 220: onsuccess: #2465: 1: Success after linux: 572 commits new 595a3c6093 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 1313447eb2 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 1de84a2478 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 0e8f8a99d1 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new c880aeff5b 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new 4116582cca 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new 0793e6b0f3 227: onsuccess: #2474: 1: Success after gcc: 2 commits new d1083b5292 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 1517b4ec49 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 04d4197695 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new f1fb4f28be 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new 8f0246f908 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 025aaecb02 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new 835f8163ab 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new dde718d501 235: onsuccess: #2483: 1: Success after linux: 108 commits new abe82409bf 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 67b7ebdfc1 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new a531dd2b0c 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 8666c3ab0a 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new f30e890171 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 8a28d1b1b3 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 98cc4fd0a6 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new e46b2c6291 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new 0eb6352290 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new ca334ef0ff 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new 0b378bad99 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 88d37c65bc 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new a136240d5e 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 5e9d2a69d0 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new 6393a90ab2 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new 414ed57e92 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 0782fa1670 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 77b7a1aa4c 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new a1c17c7b9d 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 0e61638df5 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new 4522a12f58 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 05a77a704d 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new b52f5143fb 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new d434e5ac49 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new dce1530b12 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new f8fad941db 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new 654319781b 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 4d0025aad4 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 1b5690c6ad 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new 6d6060eafd 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new 5d5b21cc5b 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 6b791eee99 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 6e17f5c20b 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new fb8f3dbf2e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new 20cbe0bb75 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new d3d908efbc 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new b21f2630c6 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new 61c9007d7d 273: onsuccess: #2521: 1: Success after gcc: 2 commits new 9670138d90 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 1b89ae3f1c 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new d5b09f7844 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 94cafedc9b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 70bde98810 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new 417abf3a95 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 14939aced7 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new e62b00fa57 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 19a13b5052 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new 6cf676cd44 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 5c7f5946ee 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new a0aaed462d 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 7cdbaaa16a 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new 6a7753ed59 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new 73a19988f6 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 03d9174bc8 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 115974da15 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 249e59e3ee 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new cafadabb15 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 892ca8dd23 293: onsuccess: #2542: 1: Success after gcc: 5 commits new 646fce9d42 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new ddff857d34 295: onsuccess: #2545: 1: Success after linux: 10 commits new 97f398f6d9 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 08619f0dad 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new ea290d4842 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new ae84a265f9 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new d58d325116 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new 22849325b1 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 76f573362c 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 829824b153 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new 51eaee63fa 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new d65d6dd86e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new d4be020b30 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 539e2a1b55 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 96003f0a66 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new df89c4c7db 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 54974a6355 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new 6c7f13f1fe 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 5055723747 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new 0fec9e6385 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new bc703a8419 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 68745a2062 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new 3c2445b6a6 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] new e3f6aa79e1 317: onsuccess: #2567: 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 (e3a97b289d) \ 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 1844 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 32412 -> 32796 bytes 04-build_abe-stage1/console.log.xz | Bin 73808 -> 73844 bytes 06-build_abe-linux/console.log.xz | Bin 8876 -> 8804 bytes 07-build_abe-glibc/console.log.xz | Bin 245984 -> 245588 bytes 08-build_abe-stage2/console.log.xz | Bin 206480 -> 205364 bytes 09-build_abe-gdb/console.log.xz | Bin 40220 -> 40092 bytes 10-build_abe-qemu/console.log.xz | Bin 31800 -> 31688 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3896 -> 3900 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2944 -> 2692 bytes 13-check_regression/console.log.xz | Bin 7956 -> 7164 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 24 +- 13-check_regression/mail-body.txt | 149 +- 13-check_regression/results.compare | 71 +- 13-check_regression/results.compare2 | 136 +- 13-check_regression/results.regressions | 71 +- 14-update_baseline/console.log | 74 +- 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 | 151 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 71 +- sumfiles/g++.log.xz | Bin 3414308 -> 3409120 bytes sumfiles/g++.sum | 20 +- sumfiles/gcc.log.xz | Bin 3032756 -> 3039344 bytes sumfiles/gcc.sum | 4474 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1037252 -> 1042192 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2292 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214532 -> 214848 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2692 -> 2696 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432388 -> 427396 bytes sumfiles/libstdc++.sum | 258 +- 43 files changed, 2627 insertions(+), 2934 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[binutils-gdb] branch master updated (7dd38e31d67 -> fd95c73ef5a)

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 7dd38e31d67 gdb/linespec.c: Fix missing source file during breakpoint re-set new 437eeee95c1 sim: modules: trigger generation from top-level new 7a1e1f94636 sim: build: drop support for subdir extra deps new c58353b7862 sim: aarch64: move libsim.a creation to top-level new 6a8e18f0389 sim: arm: move libsim.a creation to top-level new c65b31b8681 sim: avr: move libsim.a creation to top-level new bc1dd618aca sim: bfin: move libsim.a creation to top-level new cdbb77e4dc1 sim: bpf: move libsim.a creation to top-level new 2cbdcc340ae sim: cr16: move libsim.a creation to top-level new eaa678ecc30 sim: cris: move libsim.a creation to top-level new faf177dff01 sim: d10v: move libsim.a creation to top-level new 3f6c63ac49a sim: erc32: move libsim.a creation to top-level new 16a6d5420ba sim: example-synacor: move libsim.a creation to top-level new c26946a4aa3 sim: frv: move libsim.a creation to top-level new 6fe4bd8cede sim: ft32: move libsim.a creation to top-level new 3e9c9407ff0 sim: h8300: move libsim.a creation to top-level new 1486f22b135 sim: iq2000: move libsim.a creation to top-level new 000f7bee9a5 sim: lm32: move libsim.a creation to top-level new ba3a8498992 sim: m32c: move libsim.a creation to top-level new 8136f0578d9 sim: m32r: move libsim.a creation to top-level new ccb680718a3 sim: m68hc11: move libsim.a creation to top-level new dfceaa0dc36 sim: mcore: move libsim.a creation to top-level new a6ead8401a3 sim: microblaze: move libsim.a creation to top-level new 1f1afa43f5e sim: mips: move libsim.a creation to top-level new 4c54f341f0c sim: mn10300: move libsim.a creation to top-level new 0754b625917 sim: moxie: move libsim.a creation to top-level new bff048f5873 sim: msp430: move libsim.a creation to top-level new 4d998e1559a sim: or1k: move libsim.a creation to top-level new 3373e27fe1b sim: pru: move libsim.a creation to top-level new 91344291e0c sim: riscv: move libsim.a creation to top-level new 91a335f9fd9 sim: rl78: move libsim.a creation to top-level new 15538f65117 sim: rx: move libsim.a creation to top-level new dd719fa642c sim: sh: move libsim.a creation to top-level new 7a59a0b92cb sim: v850: move libsim.a creation to top-level new e732fe9b4f9 sim: build: drop support for creating libsim.a in subdirs new 638a9300b51 sim: build: drop common/nrun.o subdir hack new 54e26255ca9 sim: modules.c: move generation to top-level new bc438b3e593 sim: build: add basic framework for compiling arch objects [...] new b3e1c5d43d7 sim: aarch64: move arch-specific file compilation to top-level new 688fba23d28 sim: arm: move arch-specific file compilation to top-level new 98331de7867 sim: avr: move arch-specific file compilation to top-level new 75015a129fe sim: bpf: move arch-specific file compilation to top-level new a8e175e5783 sim: bfin: move arch-specific file compilation to top-level new df4b07f4b79 sim: cr16: move arch-specific file compilation to top-level new 71fa8692930 sim: cris: move arch-specific file compilation to top-level new 2206990476c sim: d10v: move arch-specific file compilation to top-level new 304195bcf89 sim: erc32: move arch-specific file compilation to top-level new 8ba643c31e8 sim: example-synacor: move arch-specific file compilation t [...] new 5ea1eaea7a1 sim: frv: move arch-specific file compilation to top-level new abc4c2173c0 sim: ft32: move arch-specific file compilation to top-level new dced2faff5f sim: h8300: move arch-specific file compilation to top-level new d2c06f6bcd9 sim: iq2000: move arch-specific file compilation to top-level new 2d3b0c959d8 sim: lm32: move arch-specific file compilation to top-level new cd7aa21771c sim: m32c: move arch-specific file compilation to top-level new 9b5a17d2be5 sim: m32r: move arch-specific file compilation to top-level new 5a71cd470ff sim: m68hc11: move arch-specific file compilation to top-level new 28ae9bed3df sim: mcore: move arch-specific file compilation to top-level new b7375a2dda6 sim: microblaze: move arch-specific file compilation to top-level new 1546cb45407 sim: mips: move arch-specific file compilation to top-level new 63a9d59e884 sim: mn10300: move arch-specific file compilation to top-level new ae0411a4858 sim: moxie: move arch-specific file compilation to top-level new 4fff443a114 sim: msp430: move arch-specific file compilation to top-level new b7bd5fe99b5 sim: or1k: move arch-specific file compilation to top-level new 51bc8f3a16c sim: pru: move arch-specific file compilation to top-level new e7699de5022 sim: riscv: move arch-specific file compilation to top-level new 0db0b664a68 sim: rl78: move arch-specific file compilation to top-level new 3e3e7217b0d sim: rx: move arch-specific file compilation to top-level new d667f7b30ab sim: sh: move arch-specific file compilation to top-level new 8f5fc30fcf1 sim: v850: move arch-specific file compilation to top-level new b36a89d135a sim: move arch-specific file compilation of common/ files t [...] new b014c9b0872 sim: common: move test-hw-events to top-level build new fd95c73ef5a sim: disable recursive make in (most) subdirs The 71 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: sim/Makefile.am | 34 +- sim/Makefile.in | 2028 ++++++++++++++++++++++++++++++++------- sim/README-HACKING | 7 - sim/aarch64/Makefile.in | 10 - sim/aarch64/local.mk | 18 + sim/arch-subdir.mk.in | 3 - sim/arm/Makefile.in | 10 - sim/arm/local.mk | 20 + sim/avr/Makefile.in | 6 - sim/avr/local.mk | 15 + sim/bfin/Makefile.in | 11 - sim/bfin/local.mk | 22 + sim/bpf/Makefile.in | 36 - sim/bpf/local.mk | 41 + sim/common/Make-common.in | 82 +- sim/common/defs.h | 2 +- sim/common/hw-events.c | 2 + sim/common/local.mk | 48 +- sim/configure | 620 +----------- sim/configure.ac | 21 - sim/cr16/Makefile.in | 8 - sim/cr16/local.mk | 18 + sim/cris/Makefile.in | 12 - sim/cris/local.mk | 35 + sim/d10v/Makefile.in | 9 - sim/d10v/local.mk | 19 + sim/erc32/Makefile.in | 12 - sim/erc32/local.mk | 29 +- sim/example-synacor/Makefile.in | 7 - sim/example-synacor/local.mk | 16 + sim/frv/Makefile.in | 18 - sim/frv/local.mk | 51 + sim/ft32/Makefile.in | 7 - sim/ft32/local.mk | 15 + sim/h8300/Makefile.in | 5 - sim/h8300/local.mk | 15 + sim/iq2000/Makefile.in | 10 - sim/iq2000/local.mk | 29 + sim/lm32/Makefile.in | 9 - sim/lm32/local.mk | 32 + sim/m32c/Makefile.in | 18 - sim/m32c/local.mk | 29 +- sim/m32r/Makefile.in | 17 - sim/m32r/local.mk | 58 ++ sim/m68hc11/Makefile.in | 7 - sim/m68hc11/local.mk | 33 + sim/mcore/Makefile.in | 6 - sim/mcore/local.mk | 15 + sim/microblaze/Makefile.in | 6 - sim/microblaze/local.mk | 15 + sim/mips/Makefile.in | 44 - sim/mips/acinclude.m4 | 20 +- sim/mips/local.mk | 62 ++ sim/mn10300/Makefile.in | 8 - sim/mn10300/local.mk | 29 + sim/moxie/Makefile.in | 8 - sim/moxie/local.mk | 17 + sim/msp430/Makefile.in | 6 - sim/msp430/local.mk | 15 + sim/or1k/Makefile.in | 22 - sim/or1k/local.mk | 34 + sim/pru/Makefile.in | 6 - sim/pru/local.mk | 15 + sim/riscv/Makefile.in | 7 - sim/riscv/local.mk | 19 + sim/rl78/Makefile.in | 12 - sim/rl78/local.mk | 21 +- sim/rx/Makefile.in | 17 - sim/rx/local.mk | 27 +- sim/sh/Makefile.in | 6 - sim/sh/local.mk | 16 + sim/v850/Makefile.in | 6 - sim/v850/local.mk | 26 + 73 files changed, 2554 insertions(+), 1485 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allyesconfig updated (c679cad0e8 -> 16f86762fd)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-lts-allyesconfig in repository toolchain/ci/base-artifacts. from c679cad0e8 41: onsuccess: #277: 19771: Success after binutils/qemu: 26 commits new 16f86762fd 42: onsuccess: #278: 19771: Success after llvm/qemu: 261 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 1736 -> 1800 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 30220 -> 30420 bytes 04-build_kernel_llvm/console.log.xz | Bin 62836 -> 63672 bytes 05-build_abe-qemu/console.log.xz | Bin 30708 -> 31708 bytes 06-build_linux/console.log.xz | Bin 3772 -> 3808 bytes 08-check_regression/console.log.xz | Bin 3296 -> 3380 bytes dashboard/dashboard-generate.sh | 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 | 24 ++++++++++++------------ 14 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-stable-allyesconfig updated (3628c1477c -> 407071ea2b)

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-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 3628c1477c 53: onsuccess: #525: 20699: Success after binutils/llvm/linu [...] new 407071ea2b 54: onsuccess: #526: 20699: Success after binutils/llvm/linu [...] 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 1752 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 31828 -> 32088 bytes 04-build_kernel_llvm/console.log.xz | Bin 64936 -> 65056 bytes 05-build_abe-qemu/console.log.xz | Bin 30636 -> 30908 bytes 06-build_linux/console.log.xz | Bin 3976 -> 3928 bytes 08-check_regression/console.log.xz | Bin 4368 -> 4344 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 ++++++++++++++++---------------- 16 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allnoconfig updated (cbe04a8460 -> d03917e734)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allnoconfig in repository toolchain/ci/base-artifacts. from cbe04a8460 35: onsuccess: #281: boot: Success after binutils/qemu: 26 commits new d03917e734 36: onsuccess: #282: boot: Success after llvm/qemu: 261 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 1764 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 30776 -> 31076 bytes 04-build_kernel_llvm/console.log.xz | Bin 65068 -> 63464 bytes 05-build_abe-qemu/console.log.xz | Bin 31232 -> 31644 bytes 06-build_linux/console.log.xz | Bin 3360 -> 3436 bytes 07-boot_linux/console.log.xz | Bin 504 -> 504 bytes 08-check_regression/console.log.xz | Bin 3200 -> 3300 bytes dashboard/dashboard-generate.sh | 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 | 24 ++++++++++++------------ 15 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allyesconfig updated (7f312c7bc6 -> f24aad06d0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-lts-allyesconfig in repository toolchain/ci/base-artifacts. from 7f312c7bc6 35: onsuccess: #256: all: Success after binutils/qemu: 26 commits new f24aad06d0 36: onsuccess: #257: all: Success after llvm/qemu: 261 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 1772 -> 1772 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2764 bytes 03-build_abe-binutils/console.log.xz | Bin 30632 -> 30572 bytes 04-build_kernel_llvm/console.log.xz | Bin 63616 -> 63272 bytes 05-build_abe-qemu/console.log.xz | Bin 31544 -> 31276 bytes 06-build_linux/console.log.xz | Bin 3472 -> 3480 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 3284 -> 3404 bytes dashboard/dashboard-generate.sh | 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 | 24 ++++++++++++------------ 15 files changed, 18 insertions(+), 18 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-aarch64 updated (017d705895 -> e3a97b289d)

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 017d705895 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] discards 2a5d4ac103 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits discards 4c3aeba352 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits discards bf92c258ab 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits discards 97c65c26c1 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] discards 45d4b04f76 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] discards 6516358ce5 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] discards 35ae70cdda 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] discards c2bf1296ca 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] discards b113fe7ad4 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits discards e37061738e 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits discards 1efe1eb684 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] discards 9f657e72ee 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] discards 4b941110b5 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits discards 5c24a3d44f 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] discards a6422159cf 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] discards f25c6f1b7d 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] discards df6a062a96 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits discards da99938302 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] discards 8ecc891835 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] discards ade3625019 295: onsuccess: #2545: 1: Success after linux: 10 commits discards ff28a079d0 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] discards 19b38e28f5 293: onsuccess: #2542: 1: Success after gcc: 5 commits discards dbf45dfb4c 292: onsuccess: #2541: 1: Success after binutils: 13 commits discards d7bce65bc1 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] discards afeefc3fe9 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] discards 062a1a671c 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] discards ec7f50ba4d 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] discards 075d744502 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] discards e0a9e2308b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits discards cb8ed1df6a 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits discards 6aa1108e4f 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits discards b0759e1855 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits discards 16989b9446 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits discards 11b6d212e3 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] discards 9c1b68a091 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits discards 2a6396ab6d 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] discards a47659266b 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] discards 780bd80d8b 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits discards 02b5b07ca3 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits discards 4b9843b319 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] discards 8e1dd1b322 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits discards 00273d49f8 273: onsuccess: #2521: 1: Success after gcc: 2 commits discards fee017eb97 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] discards 15ba860b3b 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] discards e400a05145 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] discards a8ca6efb8e 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits discards 17ff593cc9 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits discards 2aea652389 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits discards 608151421a 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] discards 000a1a2448 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits discards 96d718747a 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] discards 3aed5968d0 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits discards 8e79c559fc 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] discards 924eb444c0 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits discards 9161d8baa4 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] discards 3b53aabc1d 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] discards 3082b16268 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] discards e0f699b1ff 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] discards 6a9bbdc824 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] discards 9b07cee383 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] discards f6bc5c575b 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] discards 2bc5a0e980 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] discards ec90ce3a81 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] discards b850251972 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] discards c6d4dd39a5 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] discards 6ff5c3a25b 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] discards 3f4decbe3d 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] discards 7406fadc70 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] discards 6dd58b91b2 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits discards c3c9443bea 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits discards c26e12e014 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] discards 4aefbdeb0e 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] discards ee64baad20 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] discards 02e09bcab2 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] discards 12a3b0391a 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits discards f262193e5e 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits discards 13206af14b 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits discards 02c6e94317 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] discards 76634c1324 236: onsuccess: #2484: 1: Success after gcc: 2 commits discards c671bd367e 235: onsuccess: #2483: 1: Success after linux: 108 commits discards 192d102d66 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits discards 13bfe10576 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] discards 6cd6c60a0f 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] discards e525c6b6ac 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] discards b802040604 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] discards 4ce7712d85 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] discards f67422b099 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] discards 0dbc5c250b 227: onsuccess: #2474: 1: Success after gcc: 2 commits discards 13ad295e2d 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] discards 0df7e628c2 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits discards 2aae5b610d 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] discards 62dea37701 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] discards 0ec60de0e5 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] discards e932113f07 221: onsuccess: #2467: 1: Success after binutils: 3 commits discards ff64439744 220: onsuccess: #2465: 1: Success after linux: 572 commits discards a0429b37c6 219: onsuccess: #2463: 1: Success after binutils: 3 commits discards 1809dac5bb 218: onsuccess: #2461: 1: Success after linux: 916 commits discards 2fc8db5954 217: onsuccess: #2459: 1: Success after binutils: 3 commits discards 614b75f389 216: onsuccess: #2457: 1: Success after linux: 1736 commits discards 406526da57 215: onsuccess: #2455: 1: Success after binutils: 3 commits new 829761ceb1 215: onsuccess: #2455: 1: Success after binutils: 3 commits new d0d8170ee9 216: onsuccess: #2457: 1: Success after linux: 1736 commits new 5828f242a7 217: onsuccess: #2459: 1: Success after binutils: 3 commits new 26132d8728 218: onsuccess: #2461: 1: Success after linux: 916 commits new d926fecb7b 219: onsuccess: #2463: 1: Success after binutils: 3 commits new d293a6d9eb 220: onsuccess: #2465: 1: Success after linux: 572 commits new f4e096f83f 221: onsuccess: #2467: 1: Success after binutils: 3 commits new 105301bd9a 222: onsuccess: #2469: 1: Success after binutils/gcc/linux/g [...] new 536147eb06 223: onsuccess: #2470: 1: Success after binutils/gcc/linux/g [...] new 6263fced66 224: onsuccess: #2471: 1: Success after binutils/gcc/gdb: 34 [...] new 4e5a073acc 225: onsuccess: #2472: 1: Success after gcc/linux: 532 commits new aaf972ede1 226: onsuccess: #2473: 1: Success after binutils/gcc/linux/g [...] new bcd50a6c3c 227: onsuccess: #2474: 1: Success after gcc: 2 commits new 5c5f45eea2 228: onsuccess: #2475: 1: Success after binutils/gcc/gdb/qem [...] new 851fa402ac 229: onsuccess: #2476: 1: Success after binutils/gcc/linux/g [...] new 6479b517ff 230: onsuccess: #2477: 1: Success after binutils/gcc/linux/g [...] new 0e31796c1e 231: onsuccess: #2479: 1: Success after binutils/gcc/gdb/qem [...] new d7802538ec 232: onsuccess: #2480: 1: Success after binutils/gcc/linux/g [...] new 5503654859 233: onsuccess: #2481: 1: Success after binutils/gcc/gdb/qem [...] new b023126a1b 234: onsuccess: #2482: 1: Success after binutils/gdb: 18 commits new d8f0d9ad8b 235: onsuccess: #2483: 1: Success after linux: 108 commits new 0a48b61f2f 236: onsuccess: #2484: 1: Success after gcc: 2 commits new 5794d43ea3 237: onsuccess: #2485: 1: Success after binutils/gcc/gdb/qem [...] new 478771b7a6 238: onsuccess: #2486: 1: Success after binutils/gcc/gdb: 5 commits new 52370e6ff8 239: onsuccess: #2487: 1: Success after binutils/gcc/gdb: 5 commits new 0ec780f954 240: onsuccess: #2488: 1: Success after gcc/qemu: 3 commits new 5db8ea1f8a 241: onsuccess: #2489: 1: Success after binutils/gcc/glibc/g [...] new 517171f479 242: onsuccess: #2490: 1: Success after binutils/gcc/gdb: 16 [...] new f309e2e756 243: onsuccess: #2491: 1: Success after binutils/gcc/linux/g [...] new bd0b6eb4d9 244: onsuccess: #2492: 1: Success after binutils/gcc/linux/g [...] new 6ab47eba03 245: onsuccess: #2493: 1: Success after binutils/gcc/gdb: 9 commits new b769bc5802 246: onsuccess: #2494: 1: Success after binutils/gcc/gdb: 6 commits new 7918959151 247: onsuccess: #2495: 1: Success after binutils/gcc/linux/g [...] new 7df3532dc2 248: onsuccess: #2496: 1: Success after binutils/gcc/glibc/g [...] new 10161dc0cd 249: onsuccess: #2497: 1: Success after binutils/gcc/gdb: 16 [...] new ecd89056b0 250: onsuccess: #2498: 1: Success after binutils/gcc/gdb: 68 [...] new a5bc396d55 251: onsuccess: #2499: 1: Success after binutils/gcc/gdb/qem [...] new 41e1d70905 252: onsuccess: #2500: 1: Success after binutils/gcc/linux/g [...] new 7b5e812917 253: onsuccess: #2501: 1: Success after binutils/gcc/linux/g [...] new 90dab0e7a2 254: onsuccess: #2502: 1: Success after binutils/gcc/gdb: 37 [...] new 4f46c4330f 255: onsuccess: #2503: 1: Success after binutils/gcc/glibc/g [...] new cddfe3bfa5 256: onsuccess: #2504: 1: Success after binutils/gcc/linux/g [...] new 16362046ed 257: onsuccess: #2505: 1: Success after binutils/gcc/gdb: 47 [...] new 8f157bcbae 258: onsuccess: #2506: 1: Success after binutils/gcc/gdb: 49 [...] new f3162aa167 259: onsuccess: #2507: 1: Success after binutils/gcc/gdb: 49 [...] new 32172a84cc 260: onsuccess: #2508: 1: Success after binutils/gcc/linux/g [...] new dd31de88a9 261: onsuccess: #2509: 1: Success after binutils/gcc/gdb: 3 commits new b0e044721f 262: onsuccess: #2510: 1: Success after binutils/gcc/gdb: 10 [...] new 304b46a9f0 263: onsuccess: #2511: 1: Success after binutils/gdb: 16 commits new 40bd243076 264: onsuccess: #2512: 1: Success after binutils/gcc/gdb: 21 [...] new d9d81a15bc 265: onsuccess: #2513: 1: Success after binutils/gdb: 4 commits new e8fd7ad815 266: onsuccess: #2514: 1: Success after binutils/gcc/linux/g [...] new 7398163e7d 267: onsuccess: #2515: 1: Success after binutils/gdb: 4 commits new 2c532fc02c 268: onsuccess: #2516: 1: Success after binutils/gcc/gdb: 3 commits new 5367a29d77 269: onsuccess: #2517: 1: Success after binutils/gcc/gdb: 3 commits new a2604a497f 270: onsuccess: #2518: 1: Success after binutils/gcc/gdb: 19 [...] new 1acb96b14a 271: onsuccess: #2519: 1: Success after binutils/gcc/gdb: 23 [...] new 82c68b2389 272: onsuccess: #2520: 1: Success after basepoints/gcc-13-49 [...] new beda0c40f5 273: onsuccess: #2521: 1: Success after gcc: 2 commits new a873ef41bd 274: onsuccess: #2522: 1: Success after binutils/gcc/gdb: 8 commits new 850e7409a9 275: onsuccess: #2523: 1: Success after basepoints/gcc-13-49 [...] new f78956e8dd 276: onsuccess: #2524: 1: Success after binutils/gdb: 2 commits new 81c83c1a03 277: onsuccess: #2525: 1: Success after gcc/linux: 60 commits new 5b78303d36 278: onsuccess: #2526: 1: Success after binutils/gcc/linux/g [...] new f7ba85f439 279: onsuccess: #2527: 1: Success after basepoints/gcc-13-49 [...] new 188bda3878 280: onsuccess: #2528: 1: Success after binutils/gcc/gdb: 7 commits new a55e79aee4 281: onsuccess: #2529: 1: Success after binutils/gcc/linux/g [...] new 890be2fdd8 282: onsuccess: #2530: 1: Success after binutils/gcc/gdb: 3 commits new e16d040b9b 283: onsuccess: #2531: 1: Success after binutils/gdb: 16 commits new 92fa56e3f7 284: onsuccess: #2532: 1: Success after binutils/gdb: 10 commits new 591e9e128e 285: onsuccess: #2533: 1: Success after gcc/linux: 13 commits new 26928c451b 286: onsuccess: #2534: 1: Success after binutils/gcc/gdb: 4 commits new a8a4042f6f 287: onsuccess: #2535: 1: Success after binutils/gcc/gdb: 15 [...] new de6b57b285 288: onsuccess: #2536: 1: Success after binutils/gcc/linux/g [...] new 273dd7196e 289: onsuccess: #2537: 1: Success after binutils/gcc/linux/g [...] new 7d879b2e75 290: onsuccess: #2538: 1: Success after binutils/gcc/glibc/g [...] new 5816b5eaac 291: onsuccess: #2539: 1: Success after binutils/gcc/glibc/g [...] new 9781ba2304 292: onsuccess: #2541: 1: Success after binutils: 13 commits new 625975f40c 293: onsuccess: #2542: 1: Success after gcc: 5 commits new eae522c6c2 294: onsuccess: #2544: 1: Success after glibc-2.36.9000-416- [...] new 274ec0ecd0 295: onsuccess: #2545: 1: Success after linux: 10 commits new 156df7e07f 296: onsuccess: #2546: 1: Success after binutils/gcc/gdb: 79 [...] new 13bf466705 297: onsuccess: #2547: 1: Success after binutils/gcc/glibc/g [...] new c5ee44c417 298: onsuccess: #2548: 1: Success after binutils/gdb: 6 commits new 50d9bae6e5 299: onsuccess: #2549: 1: Success after binutils/gcc/gdb/qem [...] new ea542fc42b 300: onsuccess: #2550: 1: Success after binutils/gcc/linux/g [...] new f37b50204a 301: onsuccess: #2551: 1: Success after binutils/gcc/linux/g [...] new 164a4b8df1 302: onsuccess: #2552: 1: Success after binutils/gcc/gdb: 8 commits new 1615fc9d5a 303: onsuccess: #2553: 1: Success after binutils/gcc/gdb/qem [...] new da86f3fec5 304: onsuccess: #2554: 1: Success after binutils/gcc/linux/g [...] new 83c88713d2 305: onsuccess: #2555: 1: Success after binutils/gcc/gdb: 3 commits new 977c9e44b5 306: onsuccess: #2556: 1: Success after binutils/gcc/gdb: 5 commits new 162bad64d9 307: onsuccess: #2557: 1: Success after binutils/gcc/gdb/qem [...] new 820c1fc646 308: onsuccess: #2558: 1: Success after binutils/gcc/linux/g [...] new 8de3c9a8e1 309: onsuccess: #2559: 1: Success after binutils/gcc/linux/g [...] new 60bee4ea61 310: onsuccess: #2560: 1: Success after v7.2.0-493-g052e6534 [...] new f29dffaaab 311: onsuccess: #2561: 1: Success after binutils/gcc/linux/g [...] new 347b8dfcd5 312: onsuccess: #2562: 1: Success after binutils/gdb: 2 commits new df63cb11ef 313: onsuccess: #2563: 1: Success after linux/qemu: 44 commits new 679ae0f468 314: onsuccess: #2564: 1: Success after binutils/gcc/gdb: 5 commits new 888e6c4628 315: onsuccess: #2565: 1: Success after binutils/gcc/gdb/qem [...] new e3a97b289d 316: onsuccess: #2566: 1: Success after binutils/gcc/gdb/qem [...] 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 (017d705895) \ 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 1784 -> 1844 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2796 bytes 03-build_abe-binutils/console.log.xz | Bin 32240 -> 32412 bytes 04-build_abe-stage1/console.log.xz | Bin 73164 -> 73808 bytes 06-build_abe-linux/console.log.xz | Bin 8828 -> 8876 bytes 07-build_abe-glibc/console.log.xz | Bin 244176 -> 245984 bytes 08-build_abe-stage2/console.log.xz | Bin 204292 -> 206480 bytes 09-build_abe-gdb/console.log.xz | Bin 39648 -> 40220 bytes 10-build_abe-qemu/console.log.xz | Bin 31540 -> 31800 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3912 -> 3896 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2800 -> 2944 bytes 13-check_regression/console.log.xz | Bin 7448 -> 7956 bytes 13-check_regression/extra-bisect-params | 2 +- 13-check_regression/fails.sum | 47 +- 13-check_regression/mail-body.txt | 137 +- 13-check_regression/results.compare | 78 +- 13-check_regression/results.compare2 | 216 +- 13-check_regression/results.regressions | 78 +- 14-update_baseline/console.log | 78 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 139 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 +- results | 78 +- sumfiles/g++.log.xz | Bin 3410480 -> 3414308 bytes sumfiles/g++.sum | 27 +- sumfiles/gcc.log.xz | Bin 3040424 -> 3032756 bytes sumfiles/gcc.sum | 4683 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1037072 -> 1037252 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2288 -> 2288 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 214784 -> 214532 bytes sumfiles/libgomp.sum | 7 +- sumfiles/libitm.log.xz | Bin 2692 -> 2692 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 436840 -> 432388 bytes sumfiles/libstdc++.sum | 256 +- 43 files changed, 3069 insertions(+), 2813 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page: