Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/master-arm updated (4d9e551193 -> a42894355d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/master-arm in repository toolchain/ci/base-artifacts. discards 4d9e551193 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits discards 7a64c87e3b 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits discards 5676d2b328 364: onsuccess: #2000: 1: Success after gcc: 5 commits discards 8fe0e8a560 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits discards 30fec08be4 362: onsuccess: #1998: 1: Success after binutils/gcc: 39 commits discards 41ac759395 361: onsuccess: #1997: 1: Success after binutils/gcc: 24 commits discards 96df16ba40 360: onsuccess: #1996: 1: Success after binutils/gcc: 47 commits discards 7113254396 359: onsuccess: #1995: 1: Success after binutils/gcc: 8 commits discards 84c8a98ef1 358: onsuccess: #1994: 1: Success after binutils: 3 commits discards 6640be45ac 357: onsuccess: #1993: 1: Success after gdb-12-branchpoint-2 [...] discards a753a77f9b 356: onsuccess: #1992: 1: Success after binutils/gcc: 2 commits discards 9f70894b94 355: onsuccess: #1991: 1: Success after basepoints/gcc-13-43 [...] discards 9c21410060 354: onsuccess: #1990: 1: Success after binutils: 4 commits discards fb76a0a8ea 353: onsuccess: #1989: 1: Success after binutils/gcc: 2 commits discards 0c4b136d1e 352: onsuccess: #1988: 1: Success after basepoints/gcc-13-43 [...] discards a30f355eae 351: onsuccess: #1987: 1: Success after binutils/gcc: 9 commits discards 68d9879a83 350: onsuccess: #1986: 1: Success after gcc: 6 commits discards 2ac9df252f 349: onsuccess: #1985: 1: Success after binutils/gcc: 5 commits discards a3e5d3da04 348: onsuccess: #1984: 1: Success after gdb-12-branchpoint-2 [...] discards d89c15a2bd 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 commits discards 4d16cee542 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits discards af75a46aaa 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits discards 8d64eb902e 344: onsuccess: #1980: 1: Success after gcc: 3 commits discards 7a7b3a79a0 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits discards 79e0dda8f1 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits discards d778cc3aa3 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits discards e965a178b2 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits discards 0e34aadf86 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits discards d8037a22b4 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits discards 4fd4ba433a 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits discards 7882005136 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits discards dd505ff229 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits discards 477653433e 334: onsuccess: #1970: 1: Success after gcc: 20 commits discards daf3cf34ae 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits discards 828480d501 332: onsuccess: #1968: 1: Success after gcc: 3 commits discards b22d66a033 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits discards 4448190335 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits discards 5ba1f49036 329: onsuccess: #1965: 1: Success after gcc: 2 commits discards 1fa76916fa 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits discards d435ae71cb 327: onsuccess: #1963: 1: Success after gcc: 3 commits discards 5e5d81852e 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits discards 52b507548f 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits discards 8b9f72d6bb 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits discards ff916eba53 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits discards 374e6ed76b 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits discards 931e5b5b28 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits discards ae039422a1 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits discards 9ac9f64671 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits discards db1a55c9a9 318: onsuccess: #1953: 1: Success after gcc: 11 commits discards 912fdde364 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits discards bd88499b06 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits discards 4ed741a729 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-40 [...] discards fffbf9ca2d 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits discards 385a82e88d 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits discards dbd0f6c12a 312: onsuccess: #1947: 1: Success after gcc: 87 commits discards 921d86d100 311: onsuccess: #1945: 1: Success after binutils: 3 commits discards c414dd4638 310: onsuccess: #1941: 1: Success after binutils: 2 commits discards b780f85c69 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint-2 [...] discards d1207f2afa 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint-2 [...] discards f8693ae9e7 307: onsuccess: #1931: 1: Success after binutils: 2 commits discards dc1be08adb 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint-2 [...] discards dfd670ebd3 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits discards 1ef9bfac56 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits discards eee020eec3 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits discards b908efd79a 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits discards ae36416118 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits discards 7081a040e8 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits discards a6e69d1a1e 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits discards a148760901 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits discards e4188dcbcb 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits discards ab367c2e4b 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits discards 41e7fb1859 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits discards 31e14f2a7a 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits discards dea30b4e70 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits discards 037b48950d 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits discards b7c1df338f 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits discards ea36aaa47c 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits discards ddff6ae5d7 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits discards 0e8aad2c06 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits discards f1b87ec6bf 287: onsuccess: #1908: 1: Success after gcc: 36 commits discards f0cf7159cd 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits discards 05497e8e18 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-37 [...] discards 6eb979ec1a 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits discards a5e06fbf6e 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-37 [...] discards 5785d1493a 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits discards ff2dc7774e 281: onsuccess: #1902: 1: Success after gcc: 2 commits discards 05180d7f80 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits discards fab25d77bc 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-36 [...] discards d0e24449fc 278: onsuccess: #1899: 1: Success after binutils: 9 commits discards 246ad7d563 277: onsuccess: #1898: 1: Success after gcc: 4 commits discards 0d4927113c 276: onsuccess: #1897: 1: Success after binutils/gcc: 42 commits discards 5734adb101 275: onsuccess: #1896: 1: Success after binutils/gcc: 12 commits discards b0507d25ba 274: onsuccess: #1895: 1: Success after binutils/gcc: 13 commits discards 03ce649245 273: onsuccess: #1894: 1: Success after binutils/gcc: 20 commits discards e006072bc5 272: onsuccess: #1893: 1: Success after binutils/gcc: 12 commits discards 94b93f2192 271: onsuccess: #1892: 1: Success after binutils/gcc: 7 commits discards 492063555f 270: onsuccess: #1891: 1: Success after binutils/gcc: 3 commits discards 1d1f15cc4f 269: onsuccess: #1890: 1: Success after binutils/gcc: 8 commits discards 33441ebb65 268: onsuccess: #1889: 1: Success after binutils/gcc: 11 commits discards b096882462 267: onsuccess: #1888: 1: Success after binutils/gcc: 6 commits discards 1bd8db03b0 266: onsuccess: #1887: 1: Success after binutils/gcc: 8 commits new 749a89f695 266: onsuccess: #1887: 1: Success after binutils/gcc: 8 commits new 2f810a6dee 267: onsuccess: #1888: 1: Success after binutils/gcc: 6 commits new f6a8ac7983 268: onsuccess: #1889: 1: Success after binutils/gcc: 11 commits new 47c5d63b24 269: onsuccess: #1890: 1: Success after binutils/gcc: 8 commits new aa496dd1f9 270: onsuccess: #1891: 1: Success after binutils/gcc: 3 commits new c791d2babb 271: onsuccess: #1892: 1: Success after binutils/gcc: 7 commits new 15b1e143d8 272: onsuccess: #1893: 1: Success after binutils/gcc: 12 commits new 68a639943e 273: onsuccess: #1894: 1: Success after binutils/gcc: 20 commits new 1a7e95b5c9 274: onsuccess: #1895: 1: Success after binutils/gcc: 13 commits new a57fec3488 275: onsuccess: #1896: 1: Success after binutils/gcc: 12 commits new fcf3e261d7 276: onsuccess: #1897: 1: Success after binutils/gcc: 42 commits new 03c2e0df38 277: onsuccess: #1898: 1: Success after gcc: 4 commits new 1cbfc524b4 278: onsuccess: #1899: 1: Success after binutils: 9 commits new 192b5f651f 279: onsuccess: #1900: 1: Success after basepoints/gcc-13-36 [...] new 868d748e8e 280: onsuccess: #1901: 1: Success after binutils/gcc: 10 commits new 2a31fba452 281: onsuccess: #1902: 1: Success after gcc: 2 commits new b76963a588 282: onsuccess: #1903: 1: Success after binutils/gcc: 4 commits new e4198c1f48 283: onsuccess: #1904: 1: Success after basepoints/gcc-13-37 [...] new 8315446111 284: onsuccess: #1905: 1: Success after binutils/gcc: 8 commits new 69ad82e013 285: onsuccess: #1906: 1: Success after basepoints/gcc-13-37 [...] new 184ab51020 286: onsuccess: #1907: 1: Success after binutils/gcc: 8 commits new b9ad68b013 287: onsuccess: #1908: 1: Success after gcc: 36 commits new 55478ad82a 288: onsuccess: #1909: 1: Success after binutils/gcc: 18 commits new a73bfcaea6 289: onsuccess: #1910: 1: Success after binutils/gcc: 8 commits new d5d4419ceb 290: onsuccess: #1911: 1: Success after binutils/gcc: 15 commits new a0dc774c03 291: onsuccess: #1912: 1: Success after binutils/gcc: 30 commits new 61998eea68 292: onsuccess: #1913: 1: Success after binutils/gcc: 11 commits new c7914fcb78 293: onsuccess: #1914: 1: Success after binutils/gcc: 12 commits new 60713541c9 294: onsuccess: #1915: 1: Success after binutils/gcc: 6 commits new 5a4decfaa4 295: onsuccess: #1916: 1: Success after binutils/gcc: 29 commits new 312bfe1180 296: onsuccess: #1917: 1: Success after binutils/gcc: 14 commits new e80f5e0566 297: onsuccess: #1918: 1: Success after binutils/gcc: 12 commits new 1a97f3bdd4 298: onsuccess: #1919: 1: Success after binutils/gcc: 7 commits new 51c3af8471 299: onsuccess: #1920: 1: Success after binutils/gcc: 12 commits new 5bcfa3d0dc 300: onsuccess: #1921: 1: Success after binutils/gcc: 18 commits new 805432e85d 301: onsuccess: #1922: 1: Success after binutils/gcc: 13 commits new 8521c204f5 302: onsuccess: #1923: 1: Success after binutils/gcc: 6 commits new 1b6f9e966a 303: onsuccess: #1924: 1: Success after binutils/gcc: 23 commits new bd2d7b52f1 304: onsuccess: #1925: 1: Success after binutils/gcc: 21 commits new c61e35dfa5 305: onsuccess: #1926: 1: Success after binutils/gcc: 8 commits new a162917b84 306: onsuccess: #1928: 1: Success after gdb-12-branchpoint-2 [...] new 40dc7e8d1b 307: onsuccess: #1931: 1: Success after binutils: 2 commits new 549b8eb3e6 308: onsuccess: #1934: 1: Success after gdb-12-branchpoint-2 [...] new 4ecd234af0 309: onsuccess: #1938: 1: Success after gdb-12-branchpoint-2 [...] new 374b61c2d6 310: onsuccess: #1941: 1: Success after binutils: 2 commits new 167c3079a3 311: onsuccess: #1945: 1: Success after binutils: 3 commits new c25a1e2b26 312: onsuccess: #1947: 1: Success after gcc: 87 commits new cc1c294bb4 313: onsuccess: #1948: 1: Success after binutils/gcc: 105 commits new f1c37ea4d8 314: onsuccess: #1949: 1: Success after binutils/gcc: 17 commits new 51fd539ea7 315: onsuccess: #1950: 1: Success after basepoints/gcc-13-40 [...] new 8e243b0aca 316: onsuccess: #1951: 1: Success after binutils/gcc: 8 commits new 2f1ec58d2a 317: onsuccess: #1952: 1: Success after binutils/gcc: 22 commits new 210cbba6ac 318: onsuccess: #1953: 1: Success after gcc: 11 commits new 710c43269b 319: onsuccess: #1954: 1: Success after binutils/gcc: 9 commits new 08abcfd119 320: onsuccess: #1955: 1: Success after binutils/gcc: 11 commits new 71942971c7 321: onsuccess: #1956: 1: Success after binutils/gcc: 12 commits new 1b2e927922 322: onsuccess: #1957: 1: Success after binutils/gcc: 9 commits new 1aad0c029e 323: onsuccess: #1959: 1: Success after binutils/gcc: 11 commits new 29d9c5196c 324: onsuccess: #1960: 1: Success after binutils/gcc: 14 commits new fa97ba25f3 325: onsuccess: #1961: 1: Success after binutils/gcc: 16 commits new 0bc2a9642a 326: onsuccess: #1962: 1: Success after binutils/gcc: 5 commits new 299d754d4f 327: onsuccess: #1963: 1: Success after gcc: 3 commits new 4f329acf0a 328: onsuccess: #1964: 1: Success after binutils/gcc: 8 commits new 54162d2ecb 329: onsuccess: #1965: 1: Success after gcc: 2 commits new 9daf33db88 330: onsuccess: #1966: 1: Success after binutils/gcc: 3 commits new 808f561b10 331: onsuccess: #1967: 1: Success after binutils/gcc: 4 commits new 8aa1c49f1f 332: onsuccess: #1968: 1: Success after gcc: 3 commits new 9b35cd01c2 333: onsuccess: #1969: 1: Success after binutils/gcc: 5 commits new 60cbb137e0 334: onsuccess: #1970: 1: Success after gcc: 20 commits new 816a2d6c4c 335: onsuccess: #1971: 1: Success after binutils/gcc: 14 commits new 24f4493548 336: onsuccess: #1972: 1: Success after binutils/gcc: 11 commits new 10153f54da 337: onsuccess: #1973: 1: Success after binutils/gcc: 10 commits new 0eee5ae6df 338: onsuccess: #1974: 1: Success after binutils/gcc: 5 commits new ef41657bab 339: onsuccess: #1975: 1: Success after binutils/gcc: 10 commits new aa63346fe3 340: onsuccess: #1976: 1: Success after binutils/gcc: 22 commits new 18d552394e 341: onsuccess: #1977: 1: Success after binutils/gcc: 14 commits new df0abcca30 342: onsuccess: #1978: 1: Success after binutils/gcc: 6 commits new d6269379fb 343: onsuccess: #1979: 1: Success after binutils/gcc: 8 commits new d2db301eed 344: onsuccess: #1980: 1: Success after gcc: 3 commits new 779e5b8940 345: onsuccess: #1981: 1: Success after binutils/gcc: 8 commits new 54184e946e 346: onsuccess: #1982: 1: Success after binutils/gcc: 19 commits new eeac8fe281 347: onsuccess: #1983: 1: Success after binutils/gcc: 19 commits new ef465033f6 348: onsuccess: #1984: 1: Success after gdb-12-branchpoint-2 [...] new 4bc3d4b8c5 349: onsuccess: #1985: 1: Success after binutils/gcc: 5 commits new e9ddfc836e 350: onsuccess: #1986: 1: Success after gcc: 6 commits new a8df08d08c 351: onsuccess: #1987: 1: Success after binutils/gcc: 9 commits new 329fa9eebc 352: onsuccess: #1988: 1: Success after basepoints/gcc-13-43 [...] new 978e823bba 353: onsuccess: #1989: 1: Success after binutils/gcc: 2 commits new 952c441fa7 354: onsuccess: #1990: 1: Success after binutils: 4 commits new e100f09935 355: onsuccess: #1991: 1: Success after basepoints/gcc-13-43 [...] new e21bc0aa39 356: onsuccess: #1992: 1: Success after binutils/gcc: 2 commits new ba9f88e5cf 357: onsuccess: #1993: 1: Success after gdb-12-branchpoint-2 [...] new 0c441eb9ec 358: onsuccess: #1994: 1: Success after binutils: 3 commits new 9e4fcde1bc 359: onsuccess: #1995: 1: Success after binutils/gcc: 8 commits new c7bdb5f962 360: onsuccess: #1996: 1: Success after binutils/gcc: 47 commits new 02c78e59ab 361: onsuccess: #1997: 1: Success after binutils/gcc: 24 commits new 86c67e8b4a 362: onsuccess: #1998: 1: Success after binutils/gcc: 39 commits new a2ceb6879e 363: onsuccess: #1999: 1: Success after binutils/gcc: 5 commits new 964f4ba8b2 364: onsuccess: #2000: 1: Success after gcc: 5 commits new f11316b0a6 365: onsuccess: #2005: 1: Success after binutils/gcc: 45 commits new b627bdfe9c 366: onsuccess: #2006: 1: Success after binutils/gcc: 11 commits new a42894355d 367: onsuccess: #2007: 1: Success after binutils/gcc: 13 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 (4d9e551193) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-arm (a4 [...] 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 1724 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2732 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 52148 -> 52264 bytes 04-build_abe-gcc/console.log.xz | Bin 233944 -> 234528 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3836 -> 3884 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2516 -> 2620 bytes 07-check_regression/console.log.xz | Bin 5108 -> 7032 bytes 07-check_regression/mail-body.txt | 46 - 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 442 ++- 08-update_baseline/console.log | 64 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 48 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +- sumfiles/g++.log.xz | Bin 2845484 -> 2848116 bytes sumfiles/g++.sum | 112 +- sumfiles/gcc.log.xz | Bin 2435168 -> 2441884 bytes sumfiles/gcc.sum | 5039 +++++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 918676 -> 911388 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 216332 -> 216368 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2532 -> 2532 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 466660 -> 474316 bytes sumfiles/libstdc++.sum | 10 +- 32 files changed, 3157 insertions(+), 2733 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allyesconfig updated (a524e4318e -> 2feafab00f)

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-mainline-allyesconfig in repository toolchain/ci/base-artifacts. from a524e4318e 34: onsuccess: #504: 21020: Success after binutils/llvm/linu [...] new 2feafab00f 35: onsuccess: #505: 21020: 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 1700 -> 1920 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 31892 -> 31492 bytes 04-build_kernel_llvm/console.log.xz | Bin 65456 -> 65392 bytes 05-build_abe-qemu/console.log.xz | Bin 31524 -> 30204 bytes 06-build_linux/console.log.xz | Bin 5020 -> 4976 bytes 08-check_regression/console.log.xz | Bin 4508 -> 4476 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, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allmodconfig updated (8516971499 -> e3007533b0)

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-mainline-allmodconfig in repository toolchain/ci/base-artifacts. from 8516971499 34: onsuccess: #509: 23187: Success after binutils/llvm/linu [...] new e3007533b0 35: onsuccess: #510: 23187: 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 1692 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31784 -> 31556 bytes 04-build_kernel_llvm/console.log.xz | Bin 65052 -> 65632 bytes 05-build_abe-qemu/console.log.xz | Bin 31612 -> 30468 bytes 06-build_linux/console.log.xz | Bin 5020 -> 4972 bytes 08-check_regression/console.log.xz | Bin 4468 -> 4472 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, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 updated (5e55c844b7 -> b783bb2990)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-aarch64 in repository toolchain/ci/base-artifacts. discards 5e55c844b7 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 60cc7ac203 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards eb3e435c15 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] discards 65ea87532e 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] discards ba1088e2d3 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] discards 78fdc24161 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 3d9931332b 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] discards 05c0210e94 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits discards 516e9177eb 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] discards e87991fd67 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] discards 21242955dd 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] discards 0bbe52f740 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] discards 14a2d83bdc 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] discards b04951e510 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] discards 184ffdab5a 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] discards 2ebaf30772 91: onsuccess: #870: 1: Success after binutils: 5 commits discards 19adbec431 90: onsuccess: #867: 1: Success after binutils: 4 commits discards c0364d35b9 89: onsuccess: #864: 1: Success after binutils: 25 commits discards 637fe972da 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] discards c36d838f7b 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] discards 04c34843c6 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] discards e7bd6298a4 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] discards 6fba97daec 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] discards c3d8854c20 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] discards 0b5e105e3f 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] discards 2cfb77adea 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] discards 65868ec242 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] discards eae9fcef49 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] discards 159478fdd7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] discards c606f832aa 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] discards 2e45a7181c 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] discards 867e5c7a65 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] discards f780fe86ff 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] discards 4c3e829c1d 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] discards 38c2b7c61e 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] discards 18e18c28d3 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] discards 7c474c6b68 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] discards afa2d15a04 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] discards 790a024f13 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] discards 7520d0bc26 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] discards 13d9eb8fc1 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] discards f1de64f557 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards 9c8d9ad2e0 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] discards e076369ddf 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] discards ffa0327c37 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] discards 82a590a648 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] discards b1dc27891e 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] discards a814e2d11d 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] discards 3e59b2b183 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] discards ea1a09ca5f 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] discards 5956db3354 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 0408a6702a 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards bce2f84b3b 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 647b5b138a 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards a9b158b556 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9c09ca5570 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 5a7c8bbc7f 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] discards d5522283d6 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 1ef3593e71 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 3fd4ca616d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards e29cd10848 46: onsuccess: #818: 1: Success after binutils: 10 commits discards d39c41347d 45: onsuccess: #815: 1: Success after binutils: 6 commits discards 111db10005 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards d5d6ad7f1d 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] discards d851f9520a 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards 619e377dab 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] discards aabdf310a6 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] discards 8229bcae28 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 4c5c471697 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] discards 06db1fbc99 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] discards d42325bcb0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] discards 3c759b4229 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 9e5bea651c 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] discards a98b72040c 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 5667da1f02 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards affa3e9d89 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] discards c6f78aca5b 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 0903cb8543 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] discards a79beeabd9 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 78a6e2cf08 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] discards 36b936cec2 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] discards c90f97d488 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 4f2cca5c8a 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 1c97c3883b 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] discards ff3baa4769 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits discards 48a7575162 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits discards 03c43fb06d 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 7c3ab5bc95 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 079be35533 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 57ac660c55 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards b29a34231b 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] discards a2f46afd06 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1bd62370e1 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards a230034dc4 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 95fb8cc0ea 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 382812faa6 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards f46f49bc51 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 718e8f0404 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards b80978d34d 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] discards a16ff75ec0 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 discards 10f09ca276 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new cb118498ac 6: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new d2caa214e3 7: onsuccess: binutils-gcc-linux-glibc-gdb: 1 new 4de03b3819 8: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 7777547def 9: onsuccess: 1: Successful build after binutils/gcc/linux/g [...] new 136c351327 10: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1304302254 11: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4ad987d3ad 12: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 2580d3129c 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 4bca88925a 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d4a559f294 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 0d043b72d0 16: onsuccess: 1: Successful build after binutils/gcc/glibc/ [...] new 022194a730 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6e2d82c28a 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new cc424f9094 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new d680f54bc6 20: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new b29aa21fd7 21: onsuccess: 1: Success after binutils/gcc/linux/gdb: 114 commits new bff4f5c692 22: onsuccess: 1: Success after binutils/gcc/linux/gdb: 234 commits new ea14dc32d2 23: onsuccess: #790: 1: Success after binutils/gcc/linux/gdb [...] new ab01f4cddb 24: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new 23456b06db 25: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new deabb5d711 26: onsuccess: #794: 1: Success after binutils/gcc/glibc/gdb [...] new abd9997b9b 27: onsuccess: #795: 1: Success after binutils/gcc/linux/gli [...] new 22216f2875 28: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 314fe13ca4 29: onsuccess: #797: 1: Success after binutils/gcc/linux/gdb [...] new b489a3b36c 30: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new ebb3443c3f 31: onsuccess: #799: 1: Success after binutils/gcc/linux/gli [...] new b273ed8bc7 32: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new e504378141 33: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 9b75e05df0 34: onsuccess: #802: 1: Success after binutils/gcc/glibc/gdb [...] new 28e5ab9b12 35: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new 5a8b25cdc0 36: onsuccess: #804: 1: Success after binutils/gcc/glibc/gdb [...] new c84d83c352 37: onsuccess: #805: 1: Success after binutils/gcc/linux/gdb [...] new ed38a9a0dc 38: onsuccess: #806: 1: Success after binutils/gcc/glibc/gdb [...] new ea77e5ca0f 39: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new 72cdc55e4d 40: onsuccess: #808: 1: Success after binutils/gcc/linux/gli [...] new 7227df7482 41: onsuccess: #810: 1: Success after binutils/gcc/linux/gli [...] new 2267ec191d 42: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new 76549875b1 43: onsuccess: #812: 1: Success after binutils/gcc/linux/gdb [...] new 636427ebc9 44: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new 0c53adc8f6 45: onsuccess: #815: 1: Success after binutils: 6 commits new 17b4ccbfc6 46: onsuccess: #818: 1: Success after binutils: 10 commits new 7095f1930d 47: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new ab05792c58 48: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new ee4602f52d 49: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new a80c1214da 50: onsuccess: #823: 1: Success after binutils/gcc/linux/gdb [...] new 48b5fd63b3 51: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 312c2e7090 52: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 94604a760d 53: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new 30558656b2 54: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 5d4515b504 55: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new deb945a077 56: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new b291fc1e75 57: onsuccess: #831: 1: Success after binutils/gcc/linux/gli [...] new 479e841216 58: onsuccess: #832: 1: Success after binutils/gcc/linux/gdb [...] new 3dd576168b 59: onsuccess: #833: 1: Success after binutils/gcc/linux/gli [...] new 0fc3d7a3f5 60: onsuccess: #834: 1: Success after binutils/gcc/linux/gdb [...] new 5070d144e9 61: onsuccess: #835: 1: Success after binutils/gcc/linux/gli [...] new 42cc43f418 62: onsuccess: #836: 1: Success after binutils/gcc/linux/gli [...] new 754ce92ba4 63: onsuccess: #837: 1: Success after binutils/gcc/linux/gdb [...] new 505f883892 64: onsuccess: #838: 1: Success after binutils/gcc/linux/gli [...] new eb65861598 65: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 535592bf9e 66: onsuccess: #840: 1: Success after binutils/gcc/glibc/gdb [...] new ecd880d924 67: onsuccess: #841: 1: Success after binutils/gcc/linux/gli [...] new 1c9ea48226 68: onsuccess: #842: 1: Success after binutils/gcc/linux/gdb [...] new 828723d4b4 69: onsuccess: #843: 1: Success after binutils/gcc/linux/gdb [...] new 4194ed6f8d 70: onsuccess: #844: 1: Success after binutils/gcc/linux/gdb [...] new b756b850b2 71: onsuccess: #845: 1: Success after binutils/gcc/linux/gli [...] new 9f7d5e1790 72: onsuccess: #846: 1: Success after binutils/gcc/linux/gli [...] new d634edc348 73: onsuccess: #847: 1: Success after binutils/gcc/linux/gli [...] new 68e83a3ccf 74: onsuccess: #848: 1: Success after binutils/gcc/linux/gli [...] new a53eacd219 75: onsuccess: #849: 1: Success after binutils/gcc/linux/gli [...] new 5959de1333 76: onsuccess: #850: 1: Success after binutils/gcc/linux/gdb [...] new 9c4f01bb85 77: onsuccess: #851: 1: Success after binutils/gcc/linux/gli [...] new 3d5ecbe4d7 78: onsuccess: #852: 1: Success after binutils/gcc/linux/gli [...] new 685ed993ab 79: onsuccess: #853: 1: Success after binutils/gcc/linux/gli [...] new 903dd4fbd7 80: onsuccess: #854: 1: Success after binutils/gcc/linux/gli [...] new 313c0bc66d 81: onsuccess: #855: 1: Success after binutils/gcc/linux/gli [...] new 59cc4fe408 82: onsuccess: #856: 1: Success after binutils/gcc/linux/gli [...] new b4fb8fa593 83: onsuccess: #857: 1: Success after binutils/gcc/linux/gdb [...] new 6b0476a72c 84: onsuccess: #858: 1: Success after binutils/gcc/linux/gdb [...] new b37d67ff1a 85: onsuccess: #859: 1: Success after binutils/gcc/linux/gli [...] new 44463a661c 86: onsuccess: #860: 1: Success after binutils/gcc/linux/gli [...] new ca0ed74c47 87: onsuccess: #861: 1: Success after binutils/gcc/linux/gli [...] new 01a6f6a615 88: onsuccess: #862: 1: Success after binutils/gcc/linux/gli [...] new 471f71fe3c 89: onsuccess: #864: 1: Success after binutils: 25 commits new bf7847a057 90: onsuccess: #867: 1: Success after binutils: 4 commits new 0e6d3fa84d 91: onsuccess: #870: 1: Success after binutils: 5 commits new 9fb7dafae5 92: onsuccess: #872: 1: Success after binutils/gcc/linux/gli [...] new 7611195a4a 93: onsuccess: #873: 1: Success after binutils/gcc/linux/gdb [...] new 814bbfd657 94: onsuccess: #874: 1: Success after binutils/gcc/linux/gdb [...] new 91a521cc1b 95: onsuccess: #876: 1: Success after binutils/gcc/linux/gli [...] new 81e1cedcf1 96: onsuccess: #877: 1: Success after binutils/gcc/linux/gdb [...] new 73eb5c691f 97: onsuccess: #878: 1: Success after binutils/gcc/linux/gdb [...] new 56da772439 98: onsuccess: #879: 1: Success after binutils/gcc/glibc/gdb [...] new e309ba43b9 99: onsuccess: #880: 1: Success after binutils/gcc/gdb: 70 commits new aa275fb812 100: onsuccess: #881: 1: Success after binutils/gcc/linux/gd [...] new fa6cc66b2b 101: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 03e18a364e 102: onsuccess: #883: 1: Success after binutils/gcc/linux/gd [...] new 2bff7ea3b4 103: onsuccess: #884: 1: Success after binutils/gcc/linux/gd [...] new a769e77959 104: onsuccess: #885: 1: Success after binutils/gcc/linux/gd [...] new 4b10fc542c 105: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new b640a6f5a8 106: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new b783bb2990 107: onsuccess: #888: 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 (5e55c844b7) \ 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 1712 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2720 bytes 03-build_abe-binutils/console.log.xz | Bin 39464 -> 40100 bytes 04-build_abe-gcc/console.log.xz | Bin 214864 -> 213100 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 9460 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 244840 -> 244296 bytes 08-build_abe-gdb/console.log.xz | Bin 39376 -> 38532 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3840 -> 3860 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2428 -> 2032 bytes 11-check_regression/console.log.xz | Bin 16428 -> 13276 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 56 +- 11-check_regression/mail-body.txt | 154 +- 11-check_regression/results.compare | 92 +- 11-check_regression/results.compare2 | 7277 +++++++++++++----------------- 11-check_regression/results.regressions | 92 +- 12-update_baseline/console.log | 62 +- 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 | 156 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 92 +- sumfiles/gdb.log.xz | Bin 1939844 -> 1886188 bytes sumfiles/gdb.sum | 7470 +++++++++---------------------- 30 files changed, 5872 insertions(+), 9627 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allyesconfig updated (3f32628977 -> 6281e25107)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allyesconfig in repository toolchain/ci/base-artifacts. from 3f32628977 30: onsuccess: #283: 20869: Success after binutils/llvm/qemu [...] new 6281e25107 31: onsuccess: #284: 20869: 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 1724 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2740 bytes 03-build_abe-binutils/console.log.xz | Bin 30088 -> 30108 bytes 04-build_kernel_llvm/console.log.xz | Bin 65472 -> 64680 bytes 05-build_abe-qemu/console.log.xz | Bin 31512 -> 30584 bytes 06-build_linux/console.log.xz | Bin 5064 -> 5064 bytes 08-check_regression/console.log.xz | Bin 3632 -> 4012 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, 5 months

[dejagnu] branch topic-improved-unit-test updated (1757c1e -> dedbb52)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch topic-improved-unit-test in repository dejagnu. from 1757c1e Document the dejagnu.h functions for the UNSUPPORTED status new b1a3781 Fix incorrect documentation new 9e26e77 Add NOTE function to C++ unit test API new ebcfc94 Align C++ TestState::totals() with C totals() new dfd3174 Add tests for C++ unit test library new 93b2a2b Remove old unit test program new 907d26d Add comment in libdejagnu test driver that the framework test [...] new 5b0b2df Add tests for mixed C/C++ unit test library usage new ee140a3 Document use of "DG_" and "DG__" prefixes in dejagnu.h new a90a46c Move unit test summary counters into global struct in dejagnu.h new ccb3c51 Eliminate global buffer in dejagnu.h new 25c50aa Move C++ internals to prefixed names in dejagnu.h new cc2dcde Revise generation of "END" messages in dejagnu.h new ac0996c Avoid spurious reinitialization in TestState new ad376ed Add global TestState object in dejagnu.h new c999134 Document the recent C++ API improvements and the rest of the C++ API new dedbb52 Rename libdejagnu test driver The 16 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: ChangeLog | 86 ++++++++ Makefile.am | 9 +- Makefile.in | 52 +++-- dejagnu.h | 286 ++++++++++++++++--------- doc/dejagnu.texi | 98 +++++++-- testsuite/libdejagnu/{unit.exp => harness.exp} | 18 +- testsuite/libdejagnu/tunit.exp | 24 --- testsuite/libdejagnu/unit-ccxxmix.cxx | 78 +++++++ testsuite/libdejagnu/unit-cxx.cxx | 57 +++++ testsuite/libdejagnu/unit.cc | 139 ------------ 10 files changed, 540 insertions(+), 307 deletions(-) rename testsuite/libdejagnu/{unit.exp => harness.exp} (84%) delete mode 100644 testsuite/libdejagnu/tunit.exp create mode 100644 testsuite/libdejagnu/unit-ccxxmix.cxx create mode 100644 testsuite/libdejagnu/unit-cxx.cxx delete mode 100644 testsuite/libdejagnu/unit.cc -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (fb8ee3cd6e -> bbba426276)

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-arm in repository toolchain/ci/base-artifacts. discards fb8ee3cd6e 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 65abd90eba 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits discards 03d7932552 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] discards 3645552889 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] discards 8ac1a35fa4 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] discards 4e1dc80deb 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits discards 867a08dbdf 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] discards 03e7601094 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] discards fb020efdab 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] discards 203ffe4b8a 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] discards cdbee36d94 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] discards 888d122b4d 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] discards f0a20159b4 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] discards 1600bf4677 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] discards d5180928c4 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] discards 8dca16cf8f 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] discards 796258692b 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] discards 513fdaf733 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] discards 49b4cd156b 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] discards d1668e3f23 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] discards 41e67680e1 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] discards c0c0b4dafe 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] discards f86bc94396 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] discards 93bba83d69 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] discards b036fa53e8 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] discards 07bb7a128b 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] discards 1982af377d 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] discards 8f4e0ef711 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] discards dc7d633b17 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] discards 5ac43c1af0 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] discards 309833f0a3 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards c7372346f0 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] discards fca4846aca 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] discards 18adc32340 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] discards 6bfef6a2dc 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits discards 586ac36e64 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] discards c9500be00c 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] discards 81a794b40f 156: onsuccess: #1757: 1: Success after gcc: 4 commits discards 815aedfbb6 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] discards 9b70e3caa2 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits discards e80adcbcf8 153: onsuccess: #1754: 1: Success after gcc: 2 commits discards bbc4445662 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] discards 9b995f7438 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] discards a7742f2cb3 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] discards 705406c299 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] discards e926b292a1 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] discards 2f1872aa9e 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] discards 3bcaa22014 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] discards e14a15cb9f 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] discards fdc92b7cb3 144: onsuccess: #1743: 1: Success after glibc: 2 commits discards 7bb436dd48 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] discards 529d91a678 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] discards b70a94e821 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits discards 5d25d57ce0 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits discards 03988eaeb7 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] discards 3826b1e1dc 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] discards ae600e2b67 137: onsuccess: #1736: 1: Success after gcc: 5 commits discards d9fcd4ae76 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] discards 2baa2d7d19 135: onsuccess: #1733: 1: Success after binutils: 5 commits discards d76a487ab9 134: onsuccess: #1730: 1: Success after binutils: 2 commits discards 5c8022b71b 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] discards 827c622205 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] discards ba288063d0 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] discards 9386355952 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits discards d928f81a43 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] discards 6931e590e9 128: onsuccess: #1723: 1: Success after linux: 12 commits discards 284b5f01e8 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits discards f84b8b3564 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits discards 38e7365e62 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits discards 32a4fc914d 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits discards cd3eee61cf 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] discards ffc9388cef 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] discards 397eb9d276 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] discards dbda9ac7a3 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] discards 9fb355060a 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] discards c04851cc0f 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits discards fa3ff10c94 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] discards 1b82de7aa4 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] discards 4e056c8424 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] discards 24702c0528 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] discards ce7ef20de2 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] discards f8aef3600f 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] discards 9705fbedb1 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] discards 3557348a9d 110: onsuccess: #1703: 1: Success after gcc: 6 commits discards 66c51d02b6 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits discards cac2512e3e 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits discards f802b58fb1 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] discards 7c05b0934a 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] discards 9339f88882 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] discards b1b1363c50 104: onsuccess: #1697: 1: Success after gcc: 4 commits discards 4909c8cb2d 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] discards 6254037997 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] discards 4be93ca602 101: onsuccess: #1693: 1: Success after glibc: 14 commits discards 8d86c7acfb 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] discards 0adfc5d46f 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] discards fc1a56dbf6 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] discards b874839314 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] discards 4348b5da99 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits discards 636bb65fe6 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] discards a155a24870 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] discards fe1a75b0ee 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new a4f8ad6e56 93: onsuccess: #1613: 1: Success after gcc/linux: 11 commits new 9d16ef23e9 94: onsuccess: #1616: 1: Success after binutils/gcc/linux/gd [...] new badf0b5424 95: onsuccess: #1617: 1: Success after binutils/gcc/glibc/gd [...] new 4689092985 96: onsuccess: #1618: 1: Success after gcc/glibc: 18 commits new 0be8549fc2 97: onsuccess: #1619: 1: Success after binutils/gcc/linux/gd [...] new c964fd6074 98: onsuccess: #1620: 1: Success after binutils/gcc/glibc/gd [...] new 814f6b5864 99: onsuccess: #1621: 1: Success after binutils/gcc/glibc/gd [...] new abde9cc64b 100: onsuccess: #1622: 1: Success after binutils/gcc/linux/g [...] new aa3916e1d9 101: onsuccess: #1693: 1: Success after glibc: 14 commits new ccabbbe42b 102: onsuccess: #1695: 1: Success after binutils/gcc/linux/g [...] new 95fdfb53b6 103: onsuccess: #1696: 1: Success after binutils/gcc/glibc/g [...] new 6a09cdd925 104: onsuccess: #1697: 1: Success after gcc: 4 commits new 1c0341c009 105: onsuccess: #1698: 1: Success after v6.0-rc5-97-g38eddee [...] new 22fcfe23fc 106: onsuccess: #1699: 1: Success after binutils/gcc/linux/g [...] new f325bbd5ad 107: onsuccess: #1700: 1: Success after binutils/gcc/glibc/g [...] new 28c35691ae 108: onsuccess: #1701: 1: Success after binutils/gcc/gdb: 3 commits new d68f12d969 109: onsuccess: #1702: 1: Success after binutils/gcc/gdb: 3 commits new f234be03a1 110: onsuccess: #1703: 1: Success after gcc: 6 commits new bb874be24c 111: onsuccess: #1704: 1: Success after binutils/gcc/glibc/g [...] new 06b3e86e67 112: onsuccess: #1705: 1: Success after binutils/gcc/linux/g [...] new afaa88f230 113: onsuccess: #1706: 1: Success after binutils/gcc/glibc/g [...] new f2e2b272c3 114: onsuccess: #1707: 1: Success after binutils/glibc/gdb: [...] new ad29fd42a3 115: onsuccess: #1708: 1: Success after binutils/gcc/gdb: 16 [...] new 5178a92bd5 116: onsuccess: #1709: 1: Success after binutils/gcc/linux/g [...] new 245a012446 117: onsuccess: #1710: 1: Success after binutils/gcc/gdb/qem [...] new 89a2ef1eb3 118: onsuccess: #1711: 1: Success after binutils/gcc/gdb: 4 commits new ac8059e3da 119: onsuccess: #1712: 1: Success after binutils/gcc/glibc/g [...] new fad3ed9a38 120: onsuccess: #1713: 1: Success after binutils/gcc/linux/g [...] new a478c26c9c 121: onsuccess: #1716: 1: Success after binutils/gcc/linux/g [...] new d7a5a9a240 122: onsuccess: #1717: 1: Success after binutils/gcc/linux/g [...] new e143e67b60 123: onsuccess: #1718: 1: Success after binutils/gcc/linux/g [...] new 81962520ca 124: onsuccess: #1719: 1: Success after binutils/gdb: 6 commits new 435f5fa1dc 125: onsuccess: #1720: 1: Success after binutils/gcc/gdb: 4 commits new b5b7b2f4f1 126: onsuccess: #1721: 1: Success after gcc/linux: 24 commits new 1747782b09 127: onsuccess: #1722: 1: Success after binutils/gcc/gdb: 3 commits new 58a6e3e9db 128: onsuccess: #1723: 1: Success after linux: 12 commits new 0f5e0f887d 129: onsuccess: #1724: 1: Success after basepoints/gcc-13-28 [...] new 4754c5ecd1 130: onsuccess: #1725: 1: Success after gcc/linux: 32 commits new da209a0391 131: onsuccess: #1726: 1: Success after binutils/gcc/linux/g [...] new 2091fdf66c 132: onsuccess: #1727: 1: Success after binutils/gcc/gdb: 10 [...] new 98b060d810 133: onsuccess: #1728: 1: Success after binutils/gcc/gdb: 26 [...] new 9f502bd5a1 134: onsuccess: #1730: 1: Success after binutils: 2 commits new f9764bd14f 135: onsuccess: #1733: 1: Success after binutils: 5 commits new ce5c1c5600 136: onsuccess: #1735: 1: Success after binutils/gcc/linux/g [...] new 6dfb4b41bb 137: onsuccess: #1736: 1: Success after gcc: 5 commits new b6f4fb2a69 138: onsuccess: #1737: 1: Success after binutils/gcc/linux/g [...] new a9bb9023ec 139: onsuccess: #1738: 1: Success after binutils/gcc/linux/g [...] new 76d30e8b5c 140: onsuccess: #1739: 1: Success after binutils/gcc/gdb: 3 commits new 8c1d6bc354 141: onsuccess: #1740: 1: Success after binutils/gcc/gdb: 9 commits new 29cee821ea 142: onsuccess: #1741: 1: Success after binutils/gcc/glibc/g [...] new b2ab9124b7 143: onsuccess: #1742: 1: Success after binutils/gcc/linux/g [...] new 28cc853636 144: onsuccess: #1743: 1: Success after glibc: 2 commits new c80282ac5d 145: onsuccess: #1744: 1: Success after binutils/gcc/gdb: 32 [...] new 46e7c2a102 146: onsuccess: #1745: 1: Success after binutils/gcc/linux/g [...] new d2e5a7d5d4 147: onsuccess: #1746: 1: Success after binutils/gcc/linux/g [...] new 5a82ce0a50 148: onsuccess: #1747: 1: Success after binutils/gcc/glibc/g [...] new d1a54422f3 149: onsuccess: #1748: 1: Success after binutils/gcc/gdb: 22 [...] new 56bcacd8d8 150: onsuccess: #1749: 1: Success after binutils/gcc/linux/g [...] new 5f3d750681 151: onsuccess: #1751: 1: Success after gdb-12-branchpoint-2 [...] new 56641e4fd7 152: onsuccess: #1753: 1: Success after gcc/linux/glibc/gdb: [...] new a89d04040c 153: onsuccess: #1754: 1: Success after gcc: 2 commits new f90e181169 154: onsuccess: #1755: 1: Success after gcc/linux: 21 commits new 3c07880487 155: onsuccess: #1756: 1: Success after binutils/gcc/glibc/g [...] new 0c616d29a8 156: onsuccess: #1757: 1: Success after gcc: 4 commits new a697590cd1 157: onsuccess: #1758: 1: Success after binutils/gcc/linux/g [...] new 088fbd4e5d 158: onsuccess: #1759: 1: Success after binutils/gcc/linux/g [...] new 608f1e5a32 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: 5 commits new a68dae9c68 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: 12 [...] new 4aec9ac006 161: onsuccess: #1762: 1: Success after binutils/gcc/linux/g [...] new 6194c3da65 162: onsuccess: #1763: 1: Success after binutils/gcc/linux/g [...] new ad37bfd3b6 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 2b5e317785 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: 28 [...] new 9ea462abb9 165: onsuccess: #1766: 1: Success after binutils/gcc/linux/g [...] new 0c5942ece5 166: onsuccess: #1767: 1: Success after binutils/gcc/linux/g [...] new f46fdea95f 167: onsuccess: #1768: 1: Success after binutils/gcc/linux/g [...] new fd92c2b0fa 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: 14 [...] new 45db8c14ee 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qemu [...] new 91d7f56fc0 170: onsuccess: #1771: 1: Success after binutils/gcc/linux/g [...] new e713b2a13b 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: 15 [...] new ad2fa287e6 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc/g [...] new 4c91e5708e 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc/g [...] new 9cdab326cf 174: onsuccess: #1775: 1: Success after binutils/gcc/linux/g [...] new ff668282c9 175: onsuccess: #1776: 1: Success after binutils/gcc/linux/g [...] new db8980b0e7 176: onsuccess: #1791: 1: Success after binutils/gcc/linux/g [...] new 2c341d9410 177: onsuccess: #1793: 1: Success after binutils/gcc/linux/g [...] new 6bc30fdc78 178: onsuccess: #1799: 1: Success after binutils/gcc/linux/g [...] new 23f11ac8a7 179: onsuccess: #1810: 1: Success after binutils/gcc/linux/g [...] new f9a6a40243 180: onsuccess: #1831: 1: Success after binutils/gcc/linux/g [...] new 8d96128ad4 181: onsuccess: #1857: 1: Success after binutils/gcc/linux/g [...] new 006a46e5ac 182: onsuccess: #1860: 1: Success after binutils/gcc/linux/g [...] new df3da11e87 183: onsuccess: #1897: 1: Success after binutils/gcc/linux/g [...] new 8c05567879 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: 13 [...] new b6be351d37 185: onsuccess: #1906: 1: Success after binutils/gcc/linux/g [...] new ceb35c2437 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: 22 [...] new 2a881d7ebc 187: onsuccess: #1908: 1: Success after binutils/gcc/linux/g [...] new 608b491186 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: 5 commits new 1471c254ff 189: onsuccess: #1912: 1: Success after binutils/gcc/linux/g [...] new 00852a5302 190: onsuccess: #1913: 1: Success after binutils/gcc/linux/g [...] new ae37227739 191: onsuccess: #1949: 1: Success after binutils/gcc/linux/g [...] new 4f567c9c65 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: 8 commits new c7c2122a32 193: onsuccess: #1992: 1: Success after binutils: 151 commits new bbba426276 194: onsuccess: #1995: 1: Success after linux: 517 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 (fb8ee3cd6e) \ 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 1736 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 31096 -> 31376 bytes 04-build_abe-stage1/console.log.xz | Bin 91880 -> 91692 bytes 06-build_abe-linux/console.log.xz | Bin 8804 -> 8568 bytes 07-build_abe-glibc/console.log.xz | Bin 235780 -> 235336 bytes 08-build_abe-stage2/console.log.xz | Bin 225128 -> 224236 bytes 09-build_abe-gdb/console.log.xz | Bin 39216 -> 39012 bytes 10-build_abe-qemu/console.log.xz | Bin 30888 -> 31328 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3864 bytes 12-build_abe-check_gcc/console.log.xz | Bin 3152 -> 3168 bytes 13-check_regression/console.log.xz | Bin 5328 -> 5348 bytes 13-check_regression/extra-bisect-params | 1 + 13-check_regression/fails.sum | 6 + 13-check_regression/mail-body.txt | 26 + 13-check_regression/results.compare | 9 +- 13-check_regression/results.compare2 | 34 +- 13-check_regression/results.regressions | 26 + 14-update_baseline/console.log | 40 +- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 26 + sumfiles/g++.log.xz | Bin 2705292 -> 2723764 bytes sumfiles/g++.sum | 36 +- sumfiles/gcc.log.xz | Bin 2238396 -> 2270540 bytes sumfiles/gcc.sum | 2410 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 892756 -> 891784 bytes sumfiles/gfortran.sum | 4 +- sumfiles/libatomic.log.xz | Bin 2264 -> 2260 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 212868 -> 212812 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 432932 -> 428940 bytes sumfiles/libstdc++.sum | 8 +- 40 files changed, 1393 insertions(+), 1289 deletions(-) create mode 100644 13-check_regression/extra-bisect-params create mode 100644 13-check_regression/fails.sum create mode 100644 13-check_regression/results.regressions -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_native_build/release-arm updated (eee6e17e19 -> 63f63ba584)

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_build/release-arm in repository toolchain/ci/base-artifacts. from eee6e17e19 37: onsuccess: #145: 6: Success after binutils/gcc/linux/gdb [...] new 63f63ba584 38: onsuccess: #146: 6: Success after binutils/gcc/glibc/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 1668 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2712 bytes 04-build_abe-binutils/console.log.xz | Bin 51740 -> 51752 bytes 05-build_abe-gcc/console.log.xz | Bin 230096 -> 230232 bytes 06-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 07-build_abe-linux/console.log.xz | Bin 8656 -> 8736 bytes 08-build_abe-glibc/console.log.xz | Bin 234060 -> 233696 bytes 09-build_abe-gdb/console.log.xz | Bin 46904 -> 46840 bytes 10-check_regression/console.log.xz | Bin 3752 -> 3796 bytes 11-update_baseline/console.log | 2 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++++++++----------------- 19 files changed, 26 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-allnoconfig updated (4a284d595c -> 0bdc9ae0fa)

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-arm-mainline-allnoconfig in repository toolchain/ci/base-artifacts. from 4a284d595c 24: onsuccess: #412: all: Success after binutils/gcc/linux/q [...] new 0bdc9ae0fa 25: onsuccess: #413: all: Success after binutils/gcc/linux/q [...] 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 1692 -> 1704 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2748 bytes 03-build_abe-binutils/console.log.xz | Bin 31944 -> 31412 bytes 04-build_abe-stage1/console.log.xz | Bin 91308 -> 91404 bytes 05-build_abe-qemu/console.log.xz | Bin 32032 -> 30236 bytes 06-build_linux/console.log.xz | Bin 3808 -> 3780 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 4376 -> 4452 bytes 09-update_baseline/console.log | 8 ++++---- 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 ++++++++++++++++---------------- 18 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check/release-arm updated (7dc144b470 -> b98931057a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_check/release-arm in repository toolchain/ci/base-artifacts. from 7dc144b470 37: onsuccess: #200: 1: Success after binutils/gcc: 10 commits new b98931057a 38: onsuccess: #201: 1: Success after binutils/gcc: 12 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 1664 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2716 -> 2724 bytes 03-build_abe-binutils/console.log.xz | Bin 52076 -> 51840 bytes 04-build_abe-gcc/console.log.xz | Bin 229080 -> 229512 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3832 bytes 06-build_abe-check_gcc/console.log.xz | Bin 2400 -> 2700 bytes 07-check_regression/console.log.xz | Bin 5512 -> 4716 bytes 07-check_regression/mail-body.txt | 31 - 07-check_regression/results.compare | 35 +- 07-check_regression/results.compare2 | 45 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 33 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- sumfiles/g++.log.xz | Bin 2760672 -> 2787568 bytes sumfiles/g++.sum | 134 +- sumfiles/gcc.log.xz | Bin 2344312 -> 2340088 bytes sumfiles/gcc.sum | 4524 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 901352 -> 903940 bytes sumfiles/gfortran.sum | 92 +- sumfiles/libatomic.log.xz | Bin 2180 -> 2172 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 200024 -> 200124 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2544 -> 2544 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 459740 -> 458392 bytes sumfiles/libstdc++.sum | 10 +- 31 files changed, 2424 insertions(+), 2536 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 5 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022