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 (9e16e3d517 -> 6f55f1fda7)

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 9e16e3d517 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] discards bfb083d83b 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] discards ecf9723ab1 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits discards 0433c7b4b9 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits discards 5110413b85 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] discards 802155062c 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] discards ce1192d087 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] discards 2c4c4fe8b2 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits discards ebcf96b2f5 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] discards e69fc5f76b 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] discards a2761f9f98 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] discards 907c010ecd 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits discards 187100099d 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] discards c05019008c 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] discards b8281f7b08 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] discards 3c330d8d75 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] discards 9bfe50f873 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits discards 2a1e758874 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] discards a07369411f 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits discards 42dd43c990 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits discards 6c544a9330 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] discards 20672512f1 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] discards 9b51fa64a3 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] discards 854148033e 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] discards c1f33efa89 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] discards 17542ed68e 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] discards 3abbb9bd89 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits discards 239db7fb87 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] discards 796568cc69 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] discards fa0d9dcde3 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] discards 64276af30e 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] discards 226a537ee7 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] discards 10cc1f29c6 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 8250bd4940 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] discards e1a475d357 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] discards 04cb74e476 305: force: #2006: 7: Success after gdb: 2 commits discards ed69ceafaa 304: onsuccess: #2002: 7: Success after gcc: 4 commits discards 1199c02335 303: onsuccess: #2001: 7: Success after binutils: 4 commits discards ff3de00189 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] discards 9b630c78e9 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits discards 3d7392c823 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] discards 5a2824831f 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] discards 5ab772b648 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits discards 8cfd16a4c4 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits discards 062c285e51 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] discards 66400c1581 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits discards afe214fa8e 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits discards 128ead6aad 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] discards c7c96dc996 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits discards 9357cd16ae 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits discards 6b5efbad28 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits discards a30e65c798 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 5c79ff76e5 288: onsuccess: #1985: 7: Success after gcc: 17 commits discards 57e1d0cda1 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits discards e0b3a7c766 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits discards 264028c048 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits discards 480fe9e06e 284: onsuccess: #1981: 7: Success after gcc: 2 commits discards a6b8a425df 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits discards 4e68ef5958 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] discards a0119172ba 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] discards ce71cc2fc6 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits discards cb514fe799 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits discards 3040df37ad 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] discards 216b40d7b1 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits discards a6596888df 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 00f0fe0cc0 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] discards db86aac0d7 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] discards a068719bde 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits discards 6c743e7c9f 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] discards 47304f0c31 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] discards d6523e21db 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] discards d9149d3ddf 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] discards 30cbfd9999 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] discards 160b0fd47b 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] discards d8c7e77e0f 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards c6d790921d 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 1906a4bbc5 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards 55600b3b97 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards d819fe02c9 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards a2f2703d3d 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 639a44e3e3 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 1595c0ee19 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 92a3b07b31 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 36083d384d 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 78913e127c 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 823cfd0246 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards 67bfd32ee5 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards b1f27673ec 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 346bbe476c 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 1aa8aba96a 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards a337a7ca96 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards ed2dda9370 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards bf236c8609 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 6a4957317f 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 244206a031 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 15ffd607dd 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards 052e5cf737 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards db26ec1c35 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards 7f20576364 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 9e041fd20d 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 701d89b4e3 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new 1e55c52bda 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new f5bd9da88d 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 8231bca9ba 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 988915ffe9 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new f4e8e40eab 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 02792863a9 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new c41755194b 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 1475a3c1e1 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 276d55bac7 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new dbbfab5fc7 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 2b19fef24b 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 2d8315d299 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 31ecd27269 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 9d445c810c 253: onsuccess: #1950: 7: Success after glibc: 2 commits new dc003484c6 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new 7223359a74 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 042fbac82c 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new c78f28d00f 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new 407a879e7e 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 8b4ea17414 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new df0bd24a60 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new 6d4e9dbfdd 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new 082d473826 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new 622ec947ce 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new fd483361d3 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new a0ede07f1b 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new 857af9df7f 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new 796071c9ef 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] new d63db79439 268: onsuccess: #1965: 7: Success after binutils/gcc/linux/g [...] new 4a190cfa1e 269: onsuccess: #1966: 7: Success after binutils/gcc/gdb: 43 [...] new 4a139f5b84 270: onsuccess: #1967: 7: Success after binutils/gcc/gdb: 71 [...] new 2c2fecd666 271: onsuccess: #1968: 7: Success after binutils/gcc/linux/g [...] new d1b42a2dd3 272: onsuccess: #1969: 7: Success after binutils/gcc/linux/g [...] new 259335100f 273: onsuccess: #1970: 7: Success after binutils/gcc/gdb: 5 commits new 775248ae61 274: onsuccess: #1971: 7: Success after binutils/gcc/gdb: 21 [...] new 03ab4c276d 275: onsuccess: #1972: 7: Success after binutils/gcc/gdb: 23 [...] new 79fba2041a 276: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new 13784146a8 277: onsuccess: #1974: 7: Success after binutils/gdb: 4 commits new 1c366b2ac1 278: onsuccess: #1975: 7: Success after basepoints/gcc-13-48 [...] new 3b83a01b39 279: onsuccess: #1976: 7: Success after binutils/gcc/gdb: 5 commits new 9ccc64621e 280: onsuccess: #1977: 7: Success after binutils/gdb: 18 commits new ced6e015a1 281: onsuccess: #1978: 7: Success after basepoints/gcc-13-48 [...] new 4542f38727 282: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 18 [...] new 30d9013e9e 283: onsuccess: #1980: 7: Success after binutils/gcc/gdb: 6 commits new 19442b57e8 284: onsuccess: #1981: 7: Success after gcc: 2 commits new ca5e73fe61 285: onsuccess: #1982: 7: Success after binutils/gcc/gdb: 6 commits new 37e1ac5b8b 286: onsuccess: #1983: 7: Success after binutils/gcc/gdb: 3 commits new f04fba42b5 287: onsuccess: #1984: 7: Success after binutils/gdb: 2 commits new 085e0b5eae 288: onsuccess: #1985: 7: Success after gcc: 17 commits new edf6bcc5c7 289: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new a04138f115 290: onsuccess: #1987: 7: Success after gcc/linux: 26 commits new b0de4a9d9f 291: onsuccess: #1988: 7: Success after binutils/gcc/gdb: 5 commits new b2bbcf4894 292: onsuccess: #1989: 7: Success after binutils/gcc/gdb: 8 commits new 12370ea032 293: onsuccess: #1990: 7: Success after binutils/gcc/linux/g [...] new 80daa6d9dd 294: onsuccess: #1991: 7: Success after binutils/gdb: 6 commits new 6f4a59e6fd 295: onsuccess: #1992: 7: Success after binutils/gdb: 18 commits new 63d55880b8 296: onsuccess: #1993: 7: Success after binutils/gcc/linux/g [...] new 9a891a0ccb 297: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 4 commits new 4713f651d2 298: onsuccess: #1995: 7: Success after binutils/gcc/gdb: 7 commits new 9e0b63809e 299: onsuccess: #1996: 7: Success after binutils/gcc/gdb: 10 [...] new aa26b6bca0 300: onsuccess: #1997: 7: Success after binutils/gcc/linux/g [...] new 32786a30c4 301: onsuccess: #1998: 7: Success after binutils/gdb: 6 commits new bd6b2ba151 302: onsuccess: #1999: 7: Success after binutils/gcc/glibc/g [...] new 9cb84c55eb 303: onsuccess: #2001: 7: Success after binutils: 4 commits new 4004dd6321 304: onsuccess: #2002: 7: Success after gcc: 4 commits new 12a6aeb355 305: force: #2006: 7: Success after gdb: 2 commits new 90e41ab6e5 306: force: #2007: 5: Failure after gdb-13-branchpoint-245-g [...] new 1c333b56a5 307: onsuccess: #2008: 5: Success after gdb-13-branchpoint-2 [...] new de82b2b5e7 308: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new f0b87f1d29 309: onsuccess: #2010: 7: Success after binutils/gcc/glibc/g [...] new f7e7600a13 310: onsuccess: #2011: 7: Success after binutils/gcc/gdb: 21 [...] new a11043a359 311: onsuccess: #2012: 7: Success after binutils/gcc/linux/g [...] new 4c522d42fb 312: onsuccess: #2013: 7: Success after binutils/gcc/glibc/g [...] new 94e9df41bc 313: onsuccess: #2014: 7: Success after binutils/gcc/linux/g [...] new e66f57706d 314: onsuccess: #2015: 7: Success after binutils/gcc/gdb: 6 commits new d729f8d12e 315: onsuccess: #2016: 7: Success after binutils/gcc/linux/g [...] new 40f9384d03 316: onsuccess: #2017: 7: Success after binutils/gcc/linux/g [...] new 679d5edffb 317: onsuccess: #2018: 7: Success after basepoints/gcc-13-50 [...] new b79a3d79be 318: onsuccess: #2019: 7: Success after binutils/gcc/gdb/qem [...] new bfcbc16f3b 319: onsuccess: #2020: 7: Success after binutils/gcc/glibc/g [...] new cd29a8c498 320: onsuccess: #2021: 7: Success after binutils/gcc/linux/g [...] new dddbb4b74b 321: onsuccess: #2022: 7: Success after gcc/qemu: 45 commits new f0259c0a84 322: onsuccess: #2023: 7: Success after gcc/linux: 34 commits new 5868be3084 323: onsuccess: #2024: 7: Success after binutils/gcc/gdb/qem [...] new 8d3873e252 324: onsuccess: #2025: 7: Success after linux/qemu: 35 commits new 1dec541142 325: onsuccess: #2026: 7: Success after binutils/gcc/linux/g [...] new 8ffc7b4080 326: onsuccess: #2027: 7: Success after binutils/gcc/gdb/qem [...] new eb46490086 327: onsuccess: #2028: 7: Success after binutils/gcc/gdb/qem [...] new 25b0633d7b 328: onsuccess: #2029: 7: Success after binutils/gcc/linux/g [...] new a535349a66 329: onsuccess: #2030: 7: Success after binutils/gdb: 146 commits new 025ff98bef 330: onsuccess: #2031: 7: Success after binutils/gcc/linux/g [...] new 5f32bcb6cb 331: onsuccess: #2032: 7: Success after binutils/gcc/glibc/g [...] new 4791017278 332: onsuccess: #2033: 7: Success after binutils/gcc/linux/g [...] new 82f5a0612e 333: onsuccess: #2034: 7: Success after binutils/gcc/gdb: 3 commits new cc76e17a36 334: onsuccess: #2035: 7: Success after binutils/gcc/gdb: 16 [...] new fa5772a2c0 335: onsuccess: #2036: 7: Success after binutils/gcc/gdb: 11 [...] new f3b1b54aa1 336: onsuccess: #2037: 7: Success after binutils/gcc/linux/g [...] new 970510e908 337: onsuccess: #2038: 7: Success after binutils/gcc/gdb: 7 commits new e411cc46a8 338: onsuccess: #2039: 7: Success after gcc/linux/glibc: 37 commits new dcff35f04a 339: onsuccess: #2040: 7: Success after binutils/gcc/glibc/g [...] new 6ca83edc1e 340: onsuccess: #2041: 7: Success after binutils/gcc/linux/g [...] new 6f55f1fda7 341: onsuccess: #2042: 7: Success after basepoints/gcc-13-51 [...] 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 (9e16e3d517) \ 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 1760 -> 1712 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2792 bytes 04-build_abe-binutils/console.log.xz | Bin 32256 -> 32264 bytes 05-build_abe-stage1/console.log.xz | Bin 73400 -> 74028 bytes 07-build_abe-linux/console.log.xz | Bin 9512 -> 9432 bytes 08-build_abe-glibc/console.log.xz | Bin 247784 -> 246760 bytes 09-build_abe-stage2/console.log.xz | Bin 206016 -> 207696 bytes 10-build_abe-gdb/console.log.xz | Bin 39636 -> 39756 bytes 11-build_abe-qemu/console.log.xz | Bin 32148 -> 32876 bytes 12-check_regression/console.log.xz | Bin 4048 -> 3224 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 ++++++------- 17 files changed, 53 insertions(+), 53 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch master updated (66e97803490 -> 9b6c6248200)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 66e97803490 testsuite: extend timeout into all gm2 tests new 9b6c6248200 Sync LTO type_for_mode with c-family/ The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/lto/lto-lang.cc | 20 +++++++++++++++++--- 1 file changed, 17 insertions(+), 3 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-arm-stable-allyesconfig updated (163fe7a42e -> 68d412ab8d)

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 163fe7a42e 43: onsuccess: #298: 20699: Success after llvm/linux/qemu: 3 [...] new 68d412ab8d 44: onsuccess: #299: all: Success after binutils/llvm/linux/ [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1800 -> 1808 bytes 02-prepare_abe/console.log.xz | Bin 2812 -> 2804 bytes 03-build_abe-binutils/console.log.xz | Bin 30756 -> 31192 bytes 04-build_kernel_llvm/console.log.xz | Bin 63944 -> 64236 bytes 05-build_abe-qemu/console.log.xz | Bin 31552 -> 31912 bytes 06-build_linux/console.log.xz | Bin 4048 -> 3784 bytes 07-boot_linux/console.log.xz | Bin 0 -> 496 bytes 08-check_regression/console.log.xz | Bin 3636 -> 4460 bytes 08-check_regression/mail-body.txt | 4 +++- 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 | 6 ++++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 4 +++- 19 files changed, 33 insertions(+), 27 deletions(-) create mode 100644 07-boot_linux/console.log.xz -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[gcc] branch devel/rust/master updated (0030bead12e -> 2f9f77f9dd6)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch devel/rust/master in repository gcc. from 0030bead12e Merge #1734 new 68839a57ea5 diagnostics: Add underline for tokens in diagnostics. new 2f9f77f9dd6 Merge #1733 The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/rust/lex/rust-lex.cc | 57 ++++++++++++++++++++++ gcc/testsuite/rust/compile/diagnostic_underline.rs | 15 ++++++ 2 files changed, 72 insertions(+) create mode 100644 gcc/testsuite/rust/compile/diagnostic_underline.rs -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig updated (6a475d6db5 -> cafd0baa61)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-master-aarch64-lts-allmodconfig in repository toolchain/ci/base-artifacts. from 6a475d6db5 45: onsuccess: #527: boot: Success after binutils/llvm/qemu: [...] new cafd0baa61 46: onsuccess: #529: boot: Success after binutils/llvm/linux [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1760 -> 1780 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 32076 -> 32048 bytes 04-build_kernel_llvm/console.log.xz | Bin 64004 -> 63648 bytes 05-build_abe-qemu/console.log.xz | Bin 31080 -> 32404 bytes 06-build_linux/console.log.xz | Bin 3508 -> 3916 bytes 07-boot_linux/console.log.xz | Bin 508 -> 508 bytes 08-check_regression/console.log.xz | Bin 3984 -> 4372 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/linux_rev | 2 +- git/llvm_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 17 files changed, 24 insertions(+), 24 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allyesconfig updated (bdcef7ee21 -> 121c19ee12)

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 bdcef7ee21 47: onsuccess: #523: 21032: Success after binutils/llvm/linu [...] new 121c19ee12 48: onsuccess: #524: 21032: 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 1780 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2792 bytes 03-build_abe-binutils/console.log.xz | Bin 32308 -> 32120 bytes 04-build_kernel_llvm/console.log.xz | Bin 64816 -> 64804 bytes 05-build_abe-qemu/console.log.xz | Bin 31376 -> 32408 bytes 06-build_linux/console.log.xz | Bin 3768 -> 3732 bytes 08-check_regression/console.log.xz | Bin 4356 -> 4592 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 16 ++++++++-------- 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 | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- 18 files changed, 34 insertions(+), 34 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-defconfig updated (2a4ea73dda -> 493b494b22)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/llvm-release-aarch64-next-defconfig in repository toolchain/ci/base-artifacts. from 2a4ea73dda 39: onsuccess: #507: boot: Success after binutils/llvm/qemu: [...] new 493b494b22 40: force: #509: boot: Success after linux: 65 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 1756 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2776 -> 2772 bytes 03-build_abe-binutils/console.log.xz | Bin 30572 -> 30780 bytes 04-build_kernel_llvm/console.log.xz | Bin 65180 -> 62980 bytes 05-build_abe-qemu/console.log.xz | Bin 31416 -> 31636 bytes 06-build_linux/console.log.xz | Bin 3212 -> 3092 bytes 07-boot_linux/console.log.xz | Bin 6148 -> 6156 bytes 08-check_regression/console.log.xz | Bin 3500 -> 2860 bytes 08-check_regression/mail-body.txt | 2 +- 09-update_baseline/console.log | 10 +++++----- dashboard/dashboard-generate.sh | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 4 ++-- mail/mail-subject.txt | 2 +- manifest.sh | 24 +++++++++++------------- results | 2 +- 17 files changed, 24 insertions(+), 26 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-next-allyesconfig updated (f16a2e7ace -> c69d1e663b)

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-next-allyesconfig in repository toolchain/ci/base-artifacts. from f16a2e7ace 38: onsuccess: #572: 33: Success after binutils/gcc/linux/qe [...] new c69d1e663b 39: onsuccess: #573: 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 1764 -> 1776 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 32152 -> 31564 bytes 04-build_abe-stage1/console.log.xz | Bin 92392 -> 91352 bytes 05-build_abe-qemu/console.log.xz | Bin 30856 -> 32100 bytes 06-build_linux/console.log.xz | Bin 4920 -> 4732 bytes 08-check_regression/console.log.xz | Bin 4356 -> 4344 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 ++++++++++++++++---------------- 17 files changed, 28 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_bmk-code_size-coremark/gnu_eabi-arm_eabi-master-Os_LTO created (now 4043193842)

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_bmk-code_size-coremark/gnu_eabi-arm_eabi-master-Os_LTO in repository toolchain/ci/base-artifacts. at 4043193842 46: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] This branch includes the following new commits: new 4043193842 46: onsuccess: #1: 1: [TCWG CI] No change after binutils/gcc [...] 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. -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/llvm-master-arm-mainline-allmodconfig updated (9b6c0e46af -> 365503b1a6)

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 9b6c0e46af 46: onsuccess: #528: 23233: Success after binutils/llvm/linu [...] new 365503b1a6 47: onsuccess: #529: 23234: 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 1800 -> 2028 bytes 02-prepare_abe/console.log.xz | Bin 2816 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32264 -> 31756 bytes 04-build_kernel_llvm/console.log.xz | Bin 64760 -> 65256 bytes 05-build_abe-qemu/console.log.xz | Bin 30912 -> 31432 bytes 06-build_linux/console.log.xz | Bin 3728 -> 3704 bytes 08-check_regression/console.log.xz | Bin 4516 -> 4316 bytes 08-check_regression/mail-body.txt | 4 ++-- 09-update_baseline/console.log | 8 ++++---- 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 | 6 +++--- mail/mail-subject.txt | 2 +- manifest.sh | 32 ++++++++++++++++---------------- results | 2 +- 19 files changed, 33 insertions(+), 33 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page: