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 (50e80ae069 -> 656a8f1b99)

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 50e80ae069 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 591db053d5 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards edb7ab7ced 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards b6b553bc6d 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards b7c086ce52 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards f1a19e6ca1 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 6548b4af50 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 3d1bf52d19 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 91701bc6b9 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards ed429b22aa 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards d5f5753c5a 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards b212fd130d 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 8098282cc4 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards c3a2ff8a74 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards ea44ad1ef2 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards 6b05fb7102 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 51ace7893f 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 40d4afc9cb 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 240b59a2e1 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 28caa6e3b4 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards 3336d26ddd 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 9e51109025 305: force: #2006: 7: Success after gdb: 2 commits discards e4d8793014 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 93af7a188e 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards 74cf409324 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 6120a0a561 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 05ed2842d0 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards bb510c682a 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards ebb92c637e 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards a7a0a09ebd 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 29ee1b558b 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 81b4c2f9b1 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards 1ceb2c28cc 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 66f1e78953 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards 3e13cd2d82 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards a89fe65da1 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 29e13b67df 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards 74e84cc034 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards c3f1ab486a 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 7636ca440e 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards bed4ac094a 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards e18668a35d 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 1a7e897005 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards 999d4bf0fc 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards d22a1c6457 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards 918c4aa260 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards 806a4b54ca 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards 4633b0257d 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards fecfdd6e57 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards cf81e47e31 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards 1b59c91397 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 9895a649fb 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards 24aaaf67e0 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards 32fb52d588 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 21184904a1 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 0e94d898df 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards 5fd1de710b 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards db3672b6b5 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 1aa72d5dee 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 0d3c359868 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards 18e181599c 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 876b46931b 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 492ed0acad 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 92d4681682 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards 521021884d 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards e371681862 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 5f5731a595 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 8bc8a12c30 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards d59aa31058 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards a947a2f0a9 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards ba6045883d 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards ed79582d81 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards f5551d1e1b 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards e848577f69 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 7a127fb900 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards b097645c93 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 1b7fe6fef3 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards b9e9a2fc19 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards c1a8232956 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 94b16fdde6 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards b045ada7f6 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards e17d303d25 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards e0361ff42e 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards fd33eadb26 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards a83b26a030 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards c6f4695a35 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 9fce9c96a2 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards eec0a4bc83 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards cbf89bf9e3 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards d26c3bc03a 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 6fb274c734 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards b3a23b9e81 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards ec2cd8b0f7 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 89903c3ea2 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 3e1deb2502 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards 2787965291 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 1f62e5f3f7 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 424c5a3217 229: force: #1926: 7: Success after gcc: 7 commits discards b418b9084e 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards 9d465a4408 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards 4450d898a9 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new eb50ab1ea3 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new d59cd4ccbb 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 31a71287a8 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 86e810c632 229: force: #1926: 7: Success after gcc: 7 commits new 943b70c44e 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 873ca5bd68 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 2231aae97d 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 77e6854e23 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 8d53fdfad7 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 59f86e21fd 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 1a6713a6f9 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 6210e8983c 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new b8b17149b1 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 78c4132273 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new a5d5992cba 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 6aaba8ec24 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 72d469eb78 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new c8e69d292d 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new fcae8cb9a1 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new c1c3dccf42 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new fddf8572b6 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 1aca25a79f 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 7c74573a3f 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 3a3c817cb5 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new a53c1e690c 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 9145535783 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 934f23ac90 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 893068c664 253: onsuccess: #1950: 7: Success after glibc: 2 commits new d64506a07b 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new f9da59b74e 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new bc7ea2c472 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new dc4ec66cb2 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 08ab99f1a3 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new d344e3c434 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 5ae8fdc549 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new b168e76255 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 1f8268f14c 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new b57b8c58af 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new 28eabf32da 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 55eb0a46d5 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 2dc3de3fea 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 6f3cb42671 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new e2177b50ce 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 840933553f 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new 8f22192f76 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 7300afa454 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new 6c6c599919 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 269861b484 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new ca2cb25df1 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 870b1a65ef 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new fa190380e4 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new adb72b93b5 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 57247e7cb2 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 1784af3f59 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new a948acfe80 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new 12265903e7 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 6d8a0f6ffc 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 4d2882fb11 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 13d7f87942 284: onsuccess: #1981: 7: Success after gcc: 2 commits new 74cd3df1c3 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 0175db62cb 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new bff30fba55 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new d24e716558 288: onsuccess: #1985: 7: Success after gcc: 17 commits new 40f3a248ad 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 527fcc3d91 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new ad09350457 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new 996fdcd7b9 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 1b002f42cf 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new 74a83ee0ab 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 7e9bee9f3f 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 0e421ebe17 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 9ba8375198 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new bc4ac9a131 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 3096b8a398 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new 71b4d22d33 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 020006dac1 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new 9651d862e0 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new e12ce00590 303: onsuccess: #2001: 7: Success after binutils: 4 commits new ce877e4a6d 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 248ef650f9 305: force: #2006: 7: Success after gdb: 2 commits new a47fb857f9 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 1065e6aa85 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new e3bb11eb21 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 35b1c19088 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new 9975aecbd3 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new c5f77b9790 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 5f167b7a7b 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 5f9786765a 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new 6b101f7188 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new d58d2a49fb 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 300bb4c02b 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new dfa8c9b450 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new 027042cbca 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new 15c8967905 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new 6a0de9d24e 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new 724ed60c30 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new 9078940fa6 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 43b36c50c4 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new f5a81856de 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new c2d62a36ff 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new a33b025551 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new 656a8f1b99 327: onsuccess: #2028: 7: 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 (50e80ae069) \ 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 1788 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2784 -> 2760 bytes 04-build_abe-binutils/console.log.xz | Bin 32764 -> 32288 bytes 05-build_abe-stage1/console.log.xz | Bin 74564 -> 73140 bytes 07-build_abe-linux/console.log.xz | Bin 8956 -> 8840 bytes 08-build_abe-glibc/console.log.xz | Bin 247692 -> 244684 bytes 09-build_abe-stage2/console.log.xz | Bin 207252 -> 204504 bytes 10-build_abe-gdb/console.log.xz | Bin 39732 -> 39712 bytes 11-build_abe-qemu/console.log.xz | Bin 31600 -> 31552 bytes 12-check_regression/console.log.xz | Bin 4348 -> 4228 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 36 ++++++++++---------- 20 files changed, 58 insertions(+), 58 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_native_check_gcc/master-aarch64 updated (ca20ffa86c -> 3a7f213dad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gcc/master-aarch64 in repository toolchain/ci/base-artifacts. discards ca20ffa86c 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] discards 34bf0f6c1c 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] discards 12d1dd5abf 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] discards dc8b096d68 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] discards 1e97c74d0e 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] discards ea081b9422 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] discards 8451edf039 152: onsuccess: #903: 1: Success after linux: 22 commits discards a7b7991f47 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 828bd8108f 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 79c97a1148 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 5ce1bf8f1c 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] discards 58df207f66 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] discards b28441fd92 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] discards a46fcc696b 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards fc9fe679e2 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits discards 6c041b78c3 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits discards 1e22e7139c 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] discards 9254847ddb 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits discards 50837cc2a2 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards 97d1ad7375 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards 67dbee9faf 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 571267052a 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards a56fdee8f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 12f71f01d3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 1326050cd7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards f0f78a1482 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards f7922e2e84 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards d86fe65ca5 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards 7bdd977de0 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 5e14b080d0 129: onsuccess: #878: 1: Success after linux: 3008 commits discards b4b14752b1 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 58f7c746d2 127: onsuccess: #874: 1: Success after linux: 219 commits discards 2153d1d816 126: onsuccess: #873: 1: Success after glibc: 2 commits discards b921d73f89 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 6f37cb8f05 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards e6a71289e5 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards e3ef35171a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards a183d4a239 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards ccb2702a22 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards 41c02868c4 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 2f62cf6626 118: onsuccess: #863: 1: Success after linux: 12 commits discards 5728fc2690 117: onsuccess: #861: 1: Success after binutils: 18 commits discards cb52e787fc 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 32ab78759c 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 1d1a0dcae6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 32930f9379 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 445622230c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards c530f97249 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards d3c0255e9e 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards b1439aebc3 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 7af7543a81 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 4a98992bce 107: onsuccess: #849: 1: Success after binutils: 5 commits discards fdb3aca946 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards f05af8315a 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards f726184637 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 62cc949475 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards 74ebcc5a24 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards fd7655521e 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 1e512224a9 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards 6af3f4f8e6 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards d58ab3bd53 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards ae46d63fef 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards d5626a95fd 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards 031244154d 95: onsuccess: #835: 1: Success after binutils: 3 commits discards 54e7f8fca5 94: onsuccess: #832: 1: Success after binutils: 5 commits discards bb799c4cd2 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 1546b5b34f 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 5085772ef3 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 09b085bc31 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards 656f95d6cd 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 74d74d4ab3 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards 5cd22ff804 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards db391896f0 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards a3ec215a5b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 8390d85428 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 60bc26c86e 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards e85d037aa2 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards a823617fc7 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 84d9da20a9 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 6c0aae16bb 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 1e39524560 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards 3ba0919ac2 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards 7477af49c7 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards c30931edb0 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 98e6345cee 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 59ec1026eb 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards a83f5a4557 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards 7af19e07e1 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards e5d36ae38e 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 2558995dd0 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 24314a4669 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards ed92eab36c 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards ae99759983 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards edf38fdd06 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 6e751ea6aa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 3a14805787 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards 95e87f1546 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 54a4fff6c4 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards c5f0d3ccf2 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 98bd9109d3 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 1ffe945b11 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 1def3eecc8 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new 8f18d7c614 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new a91755f3e7 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new db5de082c9 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ad3badd2bd 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 7ff5e75f02 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new e604eacdfa 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new b3ff14c86b 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new bfefec0bc4 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 35cbb78f4b 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 8696d78bb9 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new d2faaafe14 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new cdb8b1f9ad 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 9a0ec6fb15 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new 9cf60b5977 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 51bf789a7c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 777ccf0643 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new cac51be6f5 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 59c0ba3d7c 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new d515dd22f9 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new c429fec0f4 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 1ad1f4c4d4 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 5563a490ba 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new c456b4d156 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new f8c3c58ecf 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 25db7464e4 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new b69f91d1bb 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new becfbefe38 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 8eb84e6e07 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new 75746c50d0 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new df4014ff81 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new 42f65e9a1c 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new f6d79076c4 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new ac40dd2265 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 54f2a4d962 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new b132823d65 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new ecb3e354e2 94: onsuccess: #832: 1: Success after binutils: 5 commits new 7d4e39cf3b 95: onsuccess: #835: 1: Success after binutils: 3 commits new 313392930f 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new d3ae7b0c81 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new c864654c56 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 6f3a16284b 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new d58a3f40c3 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new 75c1d6dffa 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 763d434d53 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 4da95252d0 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new a0f446f882 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 91ecb6e6ba 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 5410ecf872 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 6ebcb19510 107: onsuccess: #849: 1: Success after binutils: 5 commits new f722e65c3e 108: onsuccess: #850: 1: Success after gcc: 2 commits new b9ea68f20c 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 81ed3ee7dc 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new be0bcdbba1 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 152704c68c 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 9298cce3e3 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new d582b0c1ae 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new 4257cd0bb7 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 1eee3d9594 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 1c4285fc5e 117: onsuccess: #861: 1: Success after binutils: 18 commits new e35617401e 118: onsuccess: #863: 1: Success after linux: 12 commits new 78fbb3abaa 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 0d9f951afc 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 9c0d6fded7 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new ce9b1198ed 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 26693c5adf 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 8d81e4858c 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 298a627a1c 125: onsuccess: #871: 1: Success after binutils: 26 commits new b11c8e9ba9 126: onsuccess: #873: 1: Success after glibc: 2 commits new 5f9f50a511 127: onsuccess: #874: 1: Success after linux: 219 commits new 6074e27835 128: onsuccess: #876: 1: Success after binutils: 12 commits new 123f757f5a 129: onsuccess: #878: 1: Success after linux: 3008 commits new 02e583f706 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new 9a7748b807 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 10d6d9d721 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new d48044bb21 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 79ce8e89a7 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 92e8bc0f88 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new 6794148d18 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 84cee64215 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new e49236e1c4 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 53bb9422da 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new f11fa16b73 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new d1e4481346 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 commits new 6014b5448f 142: onsuccess: #891: 1: Success after binutils/gcc/linux/gd [...] new cf891b3091 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 commits new 3807ba9a7c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 commits new ca225e278d 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 2147b5ab66 146: onsuccess: #895: 1: Success after binutils/gcc/linux/gl [...] new 86d3ffbd04 147: onsuccess: #896: 1: Success after binutils/gcc/linux/gd [...] new aa315cc9ab 148: onsuccess: #897: 1: Success after binutils/gcc/linux/gd [...] new 64109a7982 149: onsuccess: #899: 1: Success after binutils: 15 commits new bd83a1583c 150: onsuccess: #900: 1: Success after gcc: 11 commits new 7664bbb29e 151: onsuccess: #902: 1: Success after glibc: 8 commits new f7bc9abe07 152: onsuccess: #903: 1: Success after linux: 22 commits new 949a2b1a04 153: onsuccess: #904: 1: Success after binutils/gcc/linux/gl [...] new 167d45328d 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/gd [...] new 1c0d7fc575 155: onsuccess: #906: 1: Success after binutils/gcc/linux/gl [...] new 899928e76a 156: onsuccess: #907: 1: Success after binutils/gcc/linux/gd [...] new e654f72e02 157: onsuccess: #908: 1: Success after binutils/gcc/linux/gl [...] new c8cb3cb3d3 158: onsuccess: #909: 1: Success after binutils/gcc/linux/gd [...] new 3a7f213dad 159: onsuccess: #910: 1: Success after binutils/gcc/linux/gd [...] 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 (ca20ffa86c) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1752 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39756 -> 40016 bytes 04-build_abe-gcc/console.log.xz | Bin 215296 -> 215032 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8548 -> 8796 bytes 07-build_abe-glibc/console.log.xz | Bin 244148 -> 244320 bytes 08-build_abe-gdb/console.log.xz | Bin 39564 -> 39336 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3884 -> 3876 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2364 -> 2628 bytes 11-check_regression/console.log.xz | Bin 6396 -> 6496 bytes 11-check_regression/extra-bisect-params | 1 - 11-check_regression/fails.sum | 7 - 11-check_regression/mail-body.txt | 57 +- 11-check_regression/results.compare | 32 +- 11-check_regression/results.compare2 | 56 +- 11-check_regression/results.regressions | 42 - 12-update_baseline/console.log | 34 +- 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 | 59 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 42 - sumfiles/g++.log.xz | Bin 3728756 -> 3754968 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 3297940 -> 3297304 bytes sumfiles/gcc.sum | 5182 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 1078372 -> 1084076 bytes sumfiles/gfortran.sum | 44 +- sumfiles/libatomic.log.xz | Bin 2276 -> 2268 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232200 -> 232364 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 455484 -> 458104 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2800 insertions(+), 2962 deletions(-) delete mode 100644 11-check_regression/extra-bisect-params delete mode 100644 11-check_regression/fails.sum delete mode 100644 11-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_native_fast_check_gdb/master-arm updated (0273ab270c -> d8f3353335)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from 0273ab270c 65: onsuccess: #74: 1: Success after binutils/gcc/linux/gdb: [...] new d8f3353335 66: onsuccess: #75: 1: Success after binutils/gcc/gdb: 30 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 1740 -> 1740 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52528 -> 53028 bytes 04-build_abe-gcc/console.log.xz | Bin 237908 -> 241136 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8832 -> 8964 bytes 07-build_abe-glibc/console.log.xz | Bin 236056 -> 238428 bytes 08-build_abe-gdb/console.log.xz | Bin 51204 -> 52952 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3876 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2548 -> 2668 bytes 11-check_regression/console.log.xz | Bin 5424 -> 5416 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- sumfiles/gdb.log.xz | Bin 14504 -> 14496 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 23 files changed, 44 insertions(+), 44 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/gnu-release-arm-mainline-allmodconfig updated (58b6ca5a40 -> 8e54f05a56)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 58b6ca5a40 42: onsuccess: #453: boot: Success after binutils/gcc/linux/ [...] new 8e54f05a56 43: onsuccess: #454: boot: Success after gcc/linux/qemu: 530 [...] 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 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30360 -> 30388 bytes 04-build_abe-stage1/console.log.xz | Bin 87692 -> 86524 bytes 05-build_abe-qemu/console.log.xz | Bin 31416 -> 31148 bytes 06-build_linux/console.log.xz | Bin 3328 -> 3292 bytes 07-boot_linux/console.log.xz | Bin 480 -> 480 bytes 08-check_regression/console.log.xz | Bin 4160 -> 3852 bytes 08-check_regression/mail-body.txt | 2 +- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 28 ++++++++++++++-------------- results | 2 +- 18 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/gnu-release-arm-stable-allyesconfig updated (0ea9998043 -> 26320da68b)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 0ea9998043 37: onsuccess: #403: 20882: Success after binutils/gcc/linux [...] new 26320da68b 38: onsuccess: #404: 20882: Success after gcc/linux/qemu: 45 [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1756 -> 1960 bytes 02-prepare_abe/console.log.xz | Bin 2780 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 30436 -> 30292 bytes 04-build_abe-stage1/console.log.xz | Bin 87228 -> 86496 bytes 05-build_abe-qemu/console.log.xz | Bin 30536 -> 31128 bytes 06-build_linux/console.log.xz | Bin 3884 -> 3884 bytes 08-check_regression/console.log.xz | Bin 4132 -> 3756 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_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 | 28 ++++++++++++++-------------- 15 files changed, 21 insertions(+), 21 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_native_fast_check_gdb/master-aarch64 updated (9933a6cdf0 -> 3b4e61c260)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. from 9933a6cdf0 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 3b4e61c260 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] 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 1732 -> 1924 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 39604 -> 39852 bytes 04-build_abe-gcc/console.log.xz | Bin 216020 -> 214332 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8380 -> 8812 bytes 07-build_abe-glibc/console.log.xz | Bin 246552 -> 245416 bytes 08-build_abe-gdb/console.log.xz | Bin 40032 -> 39516 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2556 -> 2728 bytes 11-check_regression/console.log.xz | Bin 5488 -> 5732 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- 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 | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14656 -> 14608 bytes sumfiles/gdb.sum | 34 +++++++++++++++++----------------- 24 files changed, 47 insertions(+), 47 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/gnu-master-aarch64-next-allyesconfig updated (c9e00b4153 -> 8b02c4e4cf)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-next-allyesconfig in repository toolchain/ci/base-artifacts. from c9e00b4153 39: onsuccess: #561: 33: Success after binutils/gcc/linux/qe [...] new 8b02c4e4cf 40: onsuccess: #562: 33: Success after binutils/gcc/linux/qe [...] 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 1776 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2772 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 32520 -> 32172 bytes 04-build_abe-stage1/console.log.xz | Bin 73624 -> 73336 bytes 05-build_abe-qemu/console.log.xz | Bin 31456 -> 31516 bytes 06-build_linux/console.log.xz | Bin 4680 -> 4788 bytes 08-check_regression/console.log.xz | Bin 4456 -> 4324 bytes 09-update_baseline/console.log | 9 --------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_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 | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 33 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/gnu-release-aarch64-stable-allyesconfig updated (d5bfc4643e -> e4e674e341)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-aarch64-stable-allyesconfig in repository toolchain/ci/base-artifacts. from d5bfc4643e 33: onsuccess: #387: all: Success after binutils/gcc/linux/q [...] new e4e674e341 34: onsuccess: #388: all: Success after gcc/linux/qemu: 453 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 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 30676 -> 30604 bytes 04-build_abe-stage1/console.log.xz | Bin 69112 -> 68476 bytes 05-build_abe-qemu/console.log.xz | Bin 31208 -> 31580 bytes 06-build_linux/console.log.xz | Bin 3340 -> 3336 bytes 07-boot_linux/console.log.xz | Bin 576 -> 576 bytes 08-check_regression/console.log.xz | Bin 4096 -> 3684 bytes dashboard/dashboard-generate.sh | 2 +- git/gcc_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 | 28 ++++++++++++++-------------- 16 files changed, 21 insertions(+), 21 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm updated (4f4b078198 -> f1f8140420)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 4f4b078198 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] discards 451a6e640a 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] discards eee30d10e2 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] discards 073ea9d837 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] discards 27e16d2511 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] discards 62f3e8126a 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] discards 6ed1b679a7 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] discards bc40cbac4a 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] discards 30c1cff544 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] discards fd126d840d 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] discards e4ac0bda4b 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits discards e5b03cc367 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits discards 68afd5e4b3 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits discards f40e81a78a 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] discards 187d4bf4f4 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits discards bce77df680 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] discards 0ec76b93fb 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] discards 4b8dbd4894 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] discards cca1db3309 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards 2bc9f9d3a3 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards 0464894aff 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards 06213c7c32 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 516e34a9f7 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 1696ee5748 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards a78cf922a5 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards 74ceb12058 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards fab23ed906 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 334359832b 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 67a9382f52 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 62314e83fc 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards c5fc9a30b6 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards 70ad50d6a4 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 6345a01541 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 6f7c12e384 125: onsuccess: #614: 1: Success after linux: 12 commits discards 92800b7753 124: onsuccess: #612: 1: Success after binutils: 18 commits discards 265d0a69e5 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards da370a6294 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 8442384c60 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 7524bff372 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards 19bfcd617b 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 2e79bc64c9 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 59eb1b6243 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 4bac94abf1 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards bc2049ba6f 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards a1ba8c4421 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards 677a1425ef 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards c19c06693b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards 23de232783 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards b7b8883a62 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards aa8549445a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards fc255eec67 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 38c207fbc2 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards ae03c7db6b 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards def2fb6cb7 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards d069c4ca57 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards da3e89376a 103: onsuccess: #589: 1: Success after binutils: 3 commits discards c7539f646d 102: onsuccess: #586: 1: Success after binutils: 5 commits discards 6c75477af8 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 3cea43d5ff 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards e6c51a5d58 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 0b2a16f802 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards bba4b5429b 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards 0f1e703fa4 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards fd67d2bf9d 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 81311c6390 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards bd7a3683f2 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards b2e23a812b 92: onsuccess: #575: 1: Success after linux: 34 commits discards acc490ef17 91: onsuccess: #574: 1: Success after glibc: 3 commits discards 98638c9beb 90: onsuccess: #572: 1: Success after binutils: 15 commits discards f60af8199c 89: onsuccess: #570: 1: Success after linux: 11 commits discards aa56c828b9 88: onsuccess: #569: 1: Success after glibc: 10 commits discards 40495f2c79 87: onsuccess: #567: 1: Success after binutils: 8 commits discards 587d1b65c8 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards f86184cd60 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 5210f033df 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards ebbc418d0b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 1f42c945a1 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards 9a8f1dce37 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 8d984e1a7c 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards 97b3c138bf 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards 98268be0ba 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 62c4449484 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards 3c0b93572c 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 31de458dee 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 81e4a32b1b 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards 5dc294bf8d 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards 3d4a26df70 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards b710e34893 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards e99961b78a 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards e3b509b3a8 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 15ff2e9c92 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards ca191f660c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards c904efcd53 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 87bc07e5e9 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards e97c7f8e4f 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 924cdc4e23 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards a34fe0ac89 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards 2149c283ba 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards 9a3089f777 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards a859185d90 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 0a3d3556e5 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 5240382458 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 644ee769ef 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new fcc7024bd7 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 4cace3286a 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new aaf30ff739 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 5f031e904a 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new fc3c3c8a4c 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new de89c73213 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new 72e3fe3013 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 4fd8f7898c 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new b448c56885 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new af6a01e38f 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new bf645e8dce 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 63b992c2af 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 72f819e577 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new d6a88554d0 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new fdddcdb58e 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 526f05ffd8 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new 669eda0837 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new 35ce56107f 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 05ffd95b4f 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 6a6850be44 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 07f4fe1f36 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new 4acc023499 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new f4c4de691f 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new b6d395c19b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 902070252e 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 55668c724b 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new b3b10be69a 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new 30a1c4d4f1 87: onsuccess: #567: 1: Success after binutils: 8 commits new de29466d02 88: onsuccess: #569: 1: Success after glibc: 10 commits new f2f539a7ed 89: onsuccess: #570: 1: Success after linux: 11 commits new 9f42bccfb8 90: onsuccess: #572: 1: Success after binutils: 15 commits new a8d28782bd 91: onsuccess: #574: 1: Success after glibc: 3 commits new 2e84e38d0e 92: onsuccess: #575: 1: Success after linux: 34 commits new 79f1bd2e3d 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 0d642e646a 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new ba6bf093da 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new 3c7c80a93c 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new a831225dec 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 81beff205e 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new 8746a137e9 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 3e143ee6f8 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new 85dfce6967 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 3728c545c3 102: onsuccess: #586: 1: Success after binutils: 5 commits new 83e096c3fb 103: onsuccess: #589: 1: Success after binutils: 3 commits new 81504fa8bc 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new 208790dd27 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new bd270bef44 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new ee65bdecd4 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 07e6cdbbf5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 9f100c2daa 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new 5752ea4231 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new f88e657352 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new a93143cf3e 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 39ceb92c1c 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new cbd71e8739 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 9759350679 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 73bf5ca3c0 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new a1f63ac669 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new ef3a1ab1b8 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new e51038cc64 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new cbad1b8829 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 10169dda27 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 3147291cbd 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 31a0d9ef4b 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new d9dc677ddf 124: onsuccess: #612: 1: Success after binutils: 18 commits new d1970cc678 125: onsuccess: #614: 1: Success after linux: 12 commits new 044ea8a328 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new 7d2c87469c 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 1f1faeb39a 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new 414a6a7e70 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new e9817bb517 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 553f8d69b8 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 9e1fcf76e6 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 11c4692787 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new fa96ed24eb 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new afeec2479f 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 6cddaa4a76 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new 450b1dd992 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 7c7a060eac 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 8c0ab3c12c 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 3bdcef4bd2 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new e41eed6fde 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] new 901a9f5ac8 142: onsuccess: #634: 1: Success after binutils/gcc/linux/gl [...] new 293660e2cb 143: onsuccess: #635: 1: Success after binutils/gcc/linux/gd [...] new edb66f3c79 144: onsuccess: #636: 1: Success after binutils/gcc/gdb: 47 commits new 35b7c01b97 145: onsuccess: #637: 1: Success after binutils/gcc/linux/gd [...] new ce50bd3ea7 146: onsuccess: #638: 1: Success after binutils/gcc/gdb: 35 commits new a810f7f316 147: onsuccess: #639: 1: Success after binutils/gcc/gdb: 19 commits new 9d9addeb59 148: onsuccess: #640: 1: Success after binutils/gcc/gdb: 7 commits new 284f46a3a9 149: onsuccess: #641: 1: Success after binutils/gcc/linux/gl [...] new cdc54f2e34 150: onsuccess: #642: 1: Success after binutils/gcc/linux/gd [...] new fab23cd8cb 151: onsuccess: #643: 1: Success after binutils/gcc/linux/gd [...] new e747c147b5 152: onsuccess: #645: 1: Success after binutils/gcc/linux/gl [...] new dc37328d50 153: onsuccess: #647: 1: Success after binutils/gcc/linux/gl [...] new 7045885851 154: onsuccess: #648: 1: Success after binutils/gcc/glibc/gd [...] new f35c4bf7a6 155: onsuccess: #649: 1: Success after binutils/gcc/linux/gl [...] new beff74b0ac 156: onsuccess: #650: 1: Success after binutils/gcc/linux/gl [...] new f4a1b084c3 157: onsuccess: #651: 1: Success after binutils/gcc/linux/gl [...] new 68532e43cc 158: onsuccess: #652: 1: Success after binutils/gcc/linux/gd [...] new f1f8140420 159: onsuccess: #653: 1: Success after binutils/gcc/linux/gd [...] 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 (4f4b078198) \ 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 1728 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2752 bytes 03-build_abe-binutils/console.log.xz | Bin 52828 -> 52612 bytes 04-build_abe-gcc/console.log.xz | Bin 237620 -> 238124 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8600 -> 8808 bytes 07-build_abe-glibc/console.log.xz | Bin 236032 -> 235992 bytes 08-build_abe-gdb/console.log.xz | Bin 51784 -> 52800 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3856 -> 3868 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2208 -> 2072 bytes 11-check_regression/console.log.xz | Bin 14724 -> 8064 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 37 +- 11-check_regression/mail-body.txt | 170 +- 11-check_regression/results.compare | 70 +- 11-check_regression/results.compare2 | 4047 +------------------------ 11-check_regression/results.regressions | 70 +- 12-update_baseline/console.log | 46 +- 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 | 172 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- results | 70 +- sumfiles/gdb.log.xz | Bin 1845144 -> 1802968 bytes sumfiles/gdb.sum | 5053 +++++++++++++++---------------- 30 files changed, 2960 insertions(+), 6825 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

[gcc] branch releases/gcc-12 updated (4494965932f -> 05fce806840)

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 4494965932f Daily bump. new 05fce806840 Update cpplib eo.po 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: libcpp/po/eo.po | 67 ++++++++++++++++++++++++--------------------------------- 1 file changed, 28 insertions(+), 39 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 10 months

Jump to page: