Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (7566507991 -> 15fefaa90d)

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-arm in repository toolchain/ci/base-artifacts. discards 7566507991 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] discards fbb196e740 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] discards 2ec86a3398 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] discards 1a06be1f91 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] discards 7504a86b30 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] discards 42582a3506 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] discards 5576f9f6d4 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits discards 00d31deeca 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] discards ece53ed58c 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] discards c8ba77d139 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] discards 47b414501a 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] discards 75a2012dda 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] discards 13368fdf44 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] discards a3a745a080 268: onsuccess: #1997: 7: Success after glibc: 2 commits discards ccf30c03f8 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] discards 36be1fcd5b 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] discards 4c72e385d1 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits discards 3a8acd01da 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits discards 4cbd755505 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] discards a28a46e4aa 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards 895386dd82 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] discards 5ea938e09f 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] discards 27de6f5cd6 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] discards 5940617f7f 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] discards 903fa6c46b 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] discards 10b2cf33f2 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] discards 7ad41d7f30 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] discards 5cdfacec38 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] discards b42bb7ebdb 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] discards b9c9084665 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] discards 1b6209e83f 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] discards 58909288c0 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] discards 7a2e79a251 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] discards 0ff420fc65 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] discards e29e2fac08 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] discards c24a52bb6e 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] discards 6cef90c78e 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] discards 1225754a12 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] discards 8fe21385b2 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] discards d64bcce087 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] discards 9ceac54c9b 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] discards 1b00bc73de 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards 5eb0886b16 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits discards d4ff2f51ad 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] discards f9334d3438 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards 1dbc99c987 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] discards 95e8a7a494 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] discards 4d760da520 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits discards c80a610490 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards 81bda9b7dc 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] discards 5908002c23 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] discards 99375458df 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] discards 963e0de332 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] discards e98849d7c4 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards 61012dee85 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 173cdb45c9 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] discards 178916ed2e 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards 08dd1ca83c 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] discards 9dbcfc5b7a 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] discards 21d7a4d14b 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] discards fc95de146a 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] discards 421d52bb52 220: force: #1948: 5: Success after gcc: 4 commits discards 92ec2410c2 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 4a47489764 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards d53f68c5c2 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] discards f1da8a3221 216: onsuccess: #1940: 7: Success after linux: 12 commits discards ac7e96d73d 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 1b9e134ee7 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 0c451fbbba 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 156f3ab958 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards dca18bea88 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 624eb27d9c 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits discards f4fb42e9c9 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] discards 45d0df6243 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 8e76045745 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] discards 2db4034bfb 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] discards f8a81e201f 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] discards 9321e6b60b 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] discards 5331ef41b9 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] discards 6d07863bd7 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/g [...] discards 56772d83e1 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/g [...] discards 5cfed0918e 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/g [...] discards dd897411fd 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] discards f3759850ec 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] discards 7127ab272f 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] discards 7be9e0095f 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards ac3888256f 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] discards 0e2c42faeb 194: force: #1853: 7: Success after gcc: 26 commits discards b4054679f8 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] discards 08a9383b85 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 960baa392f 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards 0fb79329c6 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 4c93662d58 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] discards 7f9948f5db 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] discards d49a789414 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] discards d492a6ce7b 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] discards b2bd5f485e 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] discards 628b7fb236 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] discards 871f902e4c 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] discards e08f7c4eac 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits discards 71e04d7482 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new f47919aa42 181: onsuccess: #1773: 7: Success after binutils/gcc/linux/g [...] new 83bdb541e6 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: 8 commits new 9e42be6793 183: onsuccess: #1776: 7: Success after binutils/gcc/linux/g [...] new 5a8c2c7b6c 184: onsuccess: #1777: 7: Success after binutils/gcc/linux/g [...] new dab5454b92 185: onsuccess: #1815: 7: Success after binutils/gcc/linux/g [...] new 60aa399c6f 186: onsuccess: #1825: 7: Success after binutils/gcc/linux/g [...] new 0228dc4aee 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc/g [...] new 48ebcb38c8 188: onsuccess: #1827: 7: Success after binutils/gcc/linux/g [...] new fe64c2cb54 189: onsuccess: #1829: 7: Success after binutils/gcc/linux/g [...] new 1e3366f2e8 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 389131e14b 191: onsuccess: #1846: 7: Success after binutils: 4 commits new b00e000738 192: onsuccess: #1848: 7: Success after linux: 213 commits new dd84e1aa6e 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint-2 [...] new 06566a65fd 194: force: #1853: 7: Success after gcc: 26 commits new 77a748e17e 195: force: #1854: 4: Failure after basepoints/gcc-13-3918-g [...] new e3d5b59205 196: onsuccess: #1855: 4: Success after gcc: 30 commits new 4355afb939 197: onsuccess: #1856: 4: Success after binutils/gcc/linux/g [...] new a9b86975e7 198: onsuccess: #1878: 7: Success after binutils/gcc/linux/g [...] new bd61f48170 199: onsuccess: #1881: 7: Success after binutils/gcc/linux/g [...] new c50ee40647 200: onsuccess: #1899: 7: Success after binutils/gcc/linux/g [...] new 3c49b0319b 201: onsuccess: #1905: 7: Success after binutils/gcc/linux/g [...] new 522625b099 202: onsuccess: #1923: 7: Success after binutils/gcc/linux/g [...] new 160a66f9d0 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: 16 [...] new 03fedc388a 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: 13 [...] new ce557ccb95 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: 40 [...] new 232a8f57b2 206: onsuccess: #1927: 7: Success after binutils/gcc/linux/g [...] new bce371ab43 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: 22 [...] new 9324ecda98 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new ab2343258d 209: onsuccess: #1931: 7: Success after binutils/gcc/linux/g [...] new 104e587132 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: 7 commits new b46e8447b9 211: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 431bdb2082 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 408aac9551 213: onsuccess: #1935: 7: Success after gcc: 2 commits new 2277ad22c2 214: onsuccess: #1937: 7: Success after binutils: 4 commits new c5c5b5488c 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 13ff33d9cd 216: onsuccess: #1940: 7: Success after linux: 12 commits new 5f74c19534 217: force: #1942: 5: Failure after gdb-12-branchpoint-2943- [...] new fea1ac18eb 218: onsuccess: #1943: 5: Success after gdb: 3 commits new b8dee8ff6c 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 2c02cd7bb5 220: force: #1948: 5: Success after gcc: 4 commits new 1a95689821 221: force: #1949: 3: Failure after basepoints/gcc-13-4492-g [...] new 3155ae55d6 222: onsuccess: #1950: 3: Success after basepoints/gcc-13-44 [...] new 7081df8bcf 223: onsuccess: #1951: 3: Success after binutils/gcc/linux: [...] new 5b70e7da8c 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/qem [...] new 8d175fc1cf 225: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new a57d79e280 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc/g [...] new 2d9adb8728 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 9b3ed22a08 228: onsuccess: #1956: 7: Success after gcc: 5 commits new eb220f57d3 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc/g [...] new 19be59bbce 230: onsuccess: #1958: 7: Success after binutils/gcc/linux/g [...] new 2b869a8326 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc/g [...] new 94f6e88080 232: onsuccess: #1961: 7: Success after binutils/gcc/linux/g [...] new 0c05953caa 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 635ac61535 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 7 commits new 8c02d88ef3 235: onsuccess: #1964: 7: Success after binutils/linux/glibc [...] new 272ed60485 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: 15 [...] new d2ef25ff48 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new 503a391ef8 238: onsuccess: #1967: 7: Success after binutils/gcc/linux/g [...] new 5816990d16 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: 3 commits new d3e5b59ace 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new baa8d410ad 241: onsuccess: #1970: 7: Success after binutils/gcc/linux/g [...] new 6bf048f173 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc/g [...] new 88630470d7 243: onsuccess: #1972: 7: Success after binutils/gcc/linux/g [...] new f292d2bbec 244: onsuccess: #1973: 7: Success after binutils/gcc/linux/g [...] new a19c33d957 245: onsuccess: #1974: 7: Success after binutils/linux/gdb: [...] new 2c88bd5f68 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: 53 [...] new a58134b3ec 247: onsuccess: #1976: 7: Success after binutils/gcc/linux/g [...] new ef12956336 248: onsuccess: #1977: 7: Success after binutils/gcc/linux/g [...] new 7343107f55 249: onsuccess: #1978: 7: Success after binutils/gcc/linux/g [...] new b1329505c5 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: 21 [...] new 300794bfbc 251: onsuccess: #1980: 7: Success after binutils/gcc/linux/g [...] new 53ab810819 252: onsuccess: #1981: 7: Success after binutils/gcc/linux/g [...] new 642dcdc2de 253: onsuccess: #1982: 7: Success after basepoints/gcc-13-47 [...] new c732c1ddeb 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/qem [...] new 5d165cfe53 255: onsuccess: #1984: 7: Success after binutils/gcc/linux/g [...] new 4af31067ae 256: onsuccess: #1985: 7: Success after binutils/gcc/linux/g [...] new 2fb74d1cd7 257: onsuccess: #1986: 7: Success after binutils/gcc/linux/g [...] new 81ea4ae28e 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/qem [...] new 4b533ccb21 259: onsuccess: #1988: 7: Success after binutils/gcc/linux/g [...] new 2e542d5084 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/qem [...] new 3672f5da1e 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: 19 [...] new a42878959a 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new be4d935ecc 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/qem [...] new 1c3ae0b538 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: 5 commits new 20618ade17 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: 5 commits new 10535607c9 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4af3 [...] new df3ac91eaf 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc/g [...] new 3a9d82d8a4 268: onsuccess: #1997: 7: Success after glibc: 2 commits new d7502aca68 269: onsuccess: #1998: 7: Success after binutils/gcc/glibc/g [...] new 4f42fa05e3 270: onsuccess: #1999: 7: Success after binutils/gcc/linux/g [...] new 3df9a8c176 271: onsuccess: #2000: 7: Success after binutils/gcc/gdb: 10 [...] new e949d9c71c 272: onsuccess: #2001: 7: Success after basepoints/gcc-13-48 [...] new 0697d0c134 273: onsuccess: #2002: 7: Success after binutils/gcc/gdb/qem [...] new 6b9f999d39 274: onsuccess: #2003: 7: Success after binutils/gcc/linux/g [...] new 80566994d5 275: onsuccess: #2004: 7: Success after binutils/gcc/gdb: 6 commits new 6eaa427ca8 276: onsuccess: #2005: 7: Success after binutils/gcc/gdb: 69 [...] new cf8f2ee11d 277: onsuccess: #2006: 7: Success after binutils/gcc/gdb/qem [...] new f7cbfc18cd 278: onsuccess: #2007: 7: Success after binutils/gcc/linux/g [...] new cd6a8e6f74 279: onsuccess: #2008: 7: Success after binutils/gcc/glibc/g [...] new 9b5b08b638 280: onsuccess: #2009: 7: Success after binutils/gcc/linux/g [...] new 8f99ccfee8 281: onsuccess: #2010: 7: Success after binutils/gcc/gdb: 30 [...] new 15fefaa90d 282: onsuccess: #2011: 7: Success after binutils/gcc/glibc/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (7566507991) \ 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 1784 -> 1744 bytes 02-prepare_abe/console.log.xz | Bin 2788 -> 2768 bytes 04-build_abe-binutils/console.log.xz | Bin 32316 -> 32132 bytes 05-build_abe-stage1/console.log.xz | Bin 92516 -> 91780 bytes 07-build_abe-linux/console.log.xz | Bin 8564 -> 8564 bytes 08-build_abe-glibc/console.log.xz | Bin 236608 -> 238468 bytes 09-build_abe-stage2/console.log.xz | Bin 225488 -> 225336 bytes 10-build_abe-gdb/console.log.xz | Bin 39380 -> 40064 bytes 11-build_abe-qemu/console.log.xz | Bin 31260 -> 31344 bytes 12-check_regression/console.log.xz | Bin 3832 -> 4220 bytes 13-update_baseline/console.log | 68 +++++++++++++++++------------------ 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 | 38 ++++++++++---------- 20 files changed, 61 insertions(+), 61 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_gnu_native_fast_check_gdb/master-arm updated (fb806b6bb8 -> da95f30dad)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_fast_check_gdb/master-arm in repository toolchain/ci/base-artifacts. from fb806b6bb8 47: onsuccess: #54: 1: Success after binutils/gcc/linux/glib [...] new da95f30dad 48: onsuccess: #55: 1: Success after binutils/gcc/linux/glib [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1768 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 52912 -> 52648 bytes 04-build_abe-gcc/console.log.xz | Bin 235304 -> 234480 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9412 -> 8732 bytes 07-build_abe-glibc/console.log.xz | Bin 236156 -> 236464 bytes 08-build_abe-gdb/console.log.xz | Bin 51768 -> 52216 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3828 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2612 -> 2532 bytes 11-check_regression/console.log.xz | Bin 6068 -> 6288 bytes 11-check_regression/results.compare | 4 ++-- 11-check_regression/results.compare2 | 6 +++--- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++++++++----------------- sumfiles/gdb.log.xz | Bin 14492 -> 14452 bytes sumfiles/gdb.sum | 34 +++++++++++++++--------------- 25 files changed, 50 insertions(+), 50 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_gnu_cross_build/master-aarch64 updated (fb4fd6ecb3 -> fc2793df75)

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 fb4fd6ecb3 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] discards 1d8b4bc5cf 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] discards 44440c0125 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] discards e7f02aec4a 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] discards ff0611598c 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] discards 29447a3b48 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] discards 89b641ccf7 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits discards 26a28a50dd 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] discards 91599d32ff 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits discards 063ce1b492 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits discards 9c57b51c3e 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] discards e3ca92d129 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] discards d708a11a97 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] discards 4ea4456700 253: onsuccess: #1950: 7: Success after glibc: 2 commits discards 5fe9c87b59 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] discards 9ce2115aff 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] discards 2b90bf33ea 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits discards e67eda9ceb 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits discards b529a8c9c7 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] discards 3986b27081 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 6a6495ddd5 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 02b2b97208 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] discards 4553ebeaee 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] discards f9fb119db3 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] discards b8f732e16e 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] discards 86a8b8ee80 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] discards 5d4a9b80db 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] discards ae0d843c2d 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] discards 4037661f32 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] discards e83b247980 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] discards 87962d03df 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] discards 3ccad07b53 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] discards b251110d43 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] discards 0aab2b0026 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] discards 18e0ff256b 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] discards f73358fc95 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 48b6065ebc 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] discards 8b9c2223b4 229: force: #1926: 7: Success after gcc: 7 commits discards 1e89b7f793 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] discards a88602c144 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards d342b50ca0 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] discards 59b5726bb5 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] discards cebe76eae9 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] discards 44e20d5113 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] discards 66d0bff0e6 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] discards f939c50345 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] discards 67e87a4933 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] discards 66595e760e 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits discards 9692403b3f 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] discards 47147edfe4 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] discards 1db8eff2ea 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 28e57d18ad 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] discards 32d0dbc749 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] discards a3bc463abf 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards 1971709a09 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] discards 1b7ed6d40b 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] discards bae5f28cdd 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards 37e0653d52 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] discards 1bf3283a75 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 45a29e831f 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards 383663c7df 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards 9aa7d42881 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards 2cf5f2b3b2 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] discards fe0e8b71c3 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits discards b89bda682d 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards 7209f2c47b 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] discards 7b11b28466 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards d8c6a204f7 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] discards 349f069bbb 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards f6f09f333b 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] discards 2df56c9980 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] discards c0437aa06e 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] discards 7feba97c40 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] discards eac9463c31 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] discards 81382501d4 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] discards c032c5ebf2 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] discards 893f719790 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 96cb74e32b 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] discards 059c8e073c 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] discards dbcf88f680 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] discards b838693248 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] discards 6d3812017a 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] discards ccfdcbd006 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] discards 209747b665 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] discards 3b5b1ba20e 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] discards 141328c8bd 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] discards aa2c292342 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] discards 6011b7561c 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards dc2f710546 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] discards 069900bb7f 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards eb3e4c4209 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] discards b22d346057 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] discards 8c201bc74e 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] discards 9602ae00ab 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 8aa2df2916 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] discards 6ef8c1da7a 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] discards 3ab136c043 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] discards 925111a91d 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] discards 63a125d12c 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] discards b056e604a7 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] discards 978b46bb7e 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 0340ffa3b9 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 82e00b0d37 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: 28 [...] new d3137dff3c 168: onsuccess: #1621: 7: Success after binutils/gcc/linux/g [...] new b8d0815ce2 169: onsuccess: #1622: 7: Success after binutils/gcc/linux/g [...] new 00ba6343e4 170: onsuccess: #1623: 7: Success after binutils/gcc/linux/g [...] new 36407ed58c 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: 12 [...] new e36dcbf60d 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qemu [...] new 38bd0d713d 173: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 6d49cb9b23 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: 15 [...] new e5d705852b 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc/g [...] new f81ff63972 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc/g [...] new 2af071de88 177: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 3684b8723f 178: onsuccess: #1631: 7: Success after binutils/gcc/linux/g [...] new 1e99154feb 179: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new febeefc350 180: onsuccess: #1636: 7: Success after binutils/linux/gdb: [...] new 25cdf32c15 181: onsuccess: #1700: 7: Success after binutils/gcc/linux/g [...] new 9e3661dd9f 182: onsuccess: #1711: 7: Success after binutils/gcc/linux/g [...] new 133a311a51 183: onsuccess: #1712: 7: Success after binutils/gcc/linux/g [...] new a655d9f8f1 184: onsuccess: #1715: 7: Success after binutils/gcc/linux/g [...] new cedc0108d4 185: onsuccess: #1716: 7: Success after binutils/linux/gdb: [...] new 4e2731fa4d 186: onsuccess: #1761: 7: Success after binutils/gcc/linux/g [...] new cfcbacd182 187: onsuccess: #1763: 7: Success after binutils/gcc/linux/g [...] new b955d68c80 188: onsuccess: #1765: 7: Success after binutils/gcc/linux/g [...] new 60f344afb3 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: 37 [...] new 43a5013d93 190: onsuccess: #1774: 7: Success after binutils: 10 commits new dc290110e1 191: onsuccess: #1808: 7: Success after binutils/gcc/linux/g [...] new 74c90fad7b 192: onsuccess: #1816: 7: Success after binutils/gcc/linux/g [...] new cb9c47b7c5 193: onsuccess: #1847: 7: Success after binutils/gcc/linux/g [...] new df847e2d7a 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: 16 [...] new 869fb659fd 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: 11 [...] new ce9991c81e 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: 42 [...] new 97195a9e5d 197: onsuccess: #1851: 7: Success after binutils/gcc/linux/g [...] new c4ad203b26 198: onsuccess: #1852: 7: Success after gcc: 5 commits new 8dcc8221f4 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: 18 [...] new c9aa39b1a7 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 94eb05515b 201: onsuccess: #1855: 7: Success after binutils/gcc/linux/g [...] new aa2dd5241a 202: onsuccess: #1856: 7: Success after gcc: 2 commits new 3ae44be144 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: 7 commits new 500decbe67 204: onsuccess: #1858: 7: Success after binutils/gcc/linux/g [...] new 9b64c5b243 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 1b3427b972 206: onsuccess: #1860: 7: Success after gcc: 2 commits new bbd481b829 207: onsuccess: #1862: 7: Success after binutils: 4 commits new bf67152630 208: onsuccess: #1865: 7: Success after linux: 12 commits new a07540224a 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/qem [...] new 98a7a711e0 210: onsuccess: #1868: 7: Success after binutils: 7 commits new addd35ad6d 211: onsuccess: #1887: 7: Success after binutils/gcc/linux/g [...] new 715891e663 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc/g [...] new d4c9e11793 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 021af26b00 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc/g [...] new 49665b977e 215: onsuccess: #1891: 7: Success after binutils/gcc/linux/g [...] new 1e6a523931 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new ff26e35821 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: 10 [...] new 5cf9ac9b3a 218: onsuccess: #1896: 7: Success after binutils/gcc/linux/g [...] new d42045bf68 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: 8 commits new a3522a4363 220: onsuccess: #1898: 7: Success after binutils/linux/glibc [...] new 9dbba3061d 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: 15 [...] new 95cbd64137 222: onsuccess: #1900: 7: Success after binutils/gcc/linux/g [...] new 3ea00966eb 223: onsuccess: #1901: 7: Success after basepoints/gcc-13-45 [...] new 93bd7cd01c 224: onsuccess: #1902: 7: Success after binutils/gcc/linux/g [...] new 162f0554d9 225: onsuccess: #1903: 7: Success after binutils/gcc/linux/g [...] new e664a63b94 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: 38 [...] new e2b4bc350f 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 4246221bad 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint-3 [...] new 45a314d4b1 229: force: #1926: 7: Success after gcc: 7 commits new 8b2aabba7d 230: force: #1927: 3: Failure after basepoints/gcc-13-4618-g [...] new 6b00314814 231: onsuccess: #1928: 3: Success after gcc: 8 commits new d00b3b7297 232: onsuccess: #1929: 7: Success after binutils/gcc/linux/g [...] new 38edad3cec 233: onsuccess: #1930: 7: Success after binutils/gcc/linux/g [...] new 9da5e5b416 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: 22 [...] new 9fc5a9d759 235: onsuccess: #1932: 7: Success after binutils/gcc/linux/g [...] new 7a068f5b0b 236: onsuccess: #1933: 7: Success after binutils/gcc/linux/g [...] new 062a827d00 237: onsuccess: #1934: 7: Success after basepoints/gcc-13-47 [...] new 30c094024b 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/qem [...] new 7d5dfcc9c4 239: onsuccess: #1936: 7: Success after binutils/gcc/linux/g [...] new e1024bd3f7 240: onsuccess: #1937: 7: Success after binutils/gcc/linux/g [...] new a60fed6eda 241: onsuccess: #1938: 7: Success after binutils/gcc/linux/g [...] new 68b25f7c23 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/qem [...] new 937833cc7c 243: onsuccess: #1940: 7: Success after binutils/gcc/linux/g [...] new 2476632913 244: onsuccess: #1941: 7: Success after binutils/gcc/linux/g [...] new 052a244804 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: 13 [...] new 236648eb33 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new b8fc69b103 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new cd85754452 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/qem [...] new 86e7c1864d 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: 5 commits new 6891593c6c 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: 5 commits new 41202deb8f 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4af3 [...] new 2fecdf244c 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc/g [...] new 3950e11d7a 253: onsuccess: #1950: 7: Success after glibc: 2 commits new b8918659d4 254: onsuccess: #1951: 7: Success after binutils/gcc/glibc/g [...] new e17fd374f5 255: onsuccess: #1952: 7: Success after binutils/gcc/linux/g [...] new 9697f6b4d5 256: onsuccess: #1953: 7: Success after binutils/gcc/linux/g [...] new d3882991a8 257: onsuccess: #1954: 7: Success after binutils/gcc/gdb: 7 commits new aa7cdc4ec1 258: onsuccess: #1955: 7: Success after binutils/gcc/gdb: 7 commits new 360d8f2253 259: onsuccess: #1956: 7: Success after gcc/linux/glibc/qemu [...] new 647e619814 260: onsuccess: #1957: 7: Success after binutils/gcc/gdb: 8 commits new d569a9928d 261: onsuccess: #1958: 7: Success after binutils/gcc/gdb: 64 [...] new bd81284356 262: onsuccess: #1959: 7: Success after binutils/gcc/gdb/qem [...] new f42f7ad448 263: onsuccess: #1960: 7: Success after binutils/gcc/linux/g [...] new edb905dec9 264: onsuccess: #1961: 7: Success after binutils/gcc/glibc/g [...] new 3125920521 265: onsuccess: #1962: 7: Success after binutils/gcc/linux/g [...] new d093d87b88 266: onsuccess: #1963: 7: Success after binutils/gcc/gdb: 28 [...] new fc2793df75 267: onsuccess: #1964: 7: Success after binutils/gcc/glibc/g [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (fb4fd6ecb3) \ 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 1756 -> 1696 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2796 bytes 04-build_abe-binutils/console.log.xz | Bin 32516 -> 32740 bytes 05-build_abe-stage1/console.log.xz | Bin 74336 -> 73620 bytes 07-build_abe-linux/console.log.xz | Bin 8540 -> 8608 bytes 08-build_abe-glibc/console.log.xz | Bin 246000 -> 247216 bytes 09-build_abe-stage2/console.log.xz | Bin 206908 -> 207212 bytes 10-build_abe-gdb/console.log.xz | Bin 40024 -> 40296 bytes 11-build_abe-qemu/console.log.xz | Bin 31716 -> 32144 bytes 12-check_regression/console.log.xz | Bin 3924 -> 4356 bytes 13-update_baseline/console.log | 64 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 ++++++++++----------- 20 files changed, 59 insertions(+), 59 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-aarch64-stable-defconfig updated (22bca07530 -> 7f7c13bfea)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-aarch64-stable-defconfig in repository toolchain/ci/base-artifacts. from 22bca07530 35: onsuccess: #516: boot: Success after binutils/gcc/qemu: [...] new 7f7c13bfea 36: onsuccess: #517: boot: Success after binutils/gcc/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 1788 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2796 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 32500 -> 32136 bytes 04-build_abe-stage1/console.log.xz | Bin 74176 -> 73676 bytes 05-build_abe-qemu/console.log.xz | Bin 31356 -> 31632 bytes 06-build_linux/console.log.xz | Bin 6512 -> 6080 bytes 07-boot_linux/console.log.xz | Bin 6256 -> 6232 bytes 08-check_regression/console.log.xz | Bin 3924 -> 4284 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.

2 years, 5 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gcc_check_bootstrap/release-arm-check_bootstrap updated (99abc96c83 -> 90e84881d3)

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_bootstrap/release-arm-check_bootstrap in repository toolchain/ci/base-artifacts. from 99abc96c83 43: onsuccess: #166: 1: Success after binutils/gcc: 13 commits new 90e84881d3 44: onsuccess: #167: 1: Success after binutils/gcc: 14 commits The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1736 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2744 bytes 03-build_abe-binutils/console.log.xz | Bin 50940 -> 51344 bytes 04-build_abe-bootstrap/console.log.xz | Bin 465700 -> 462716 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3832 bytes 06-build_abe-check_bootstrap/console.log.xz | Bin 3052 -> 2700 bytes 07-check_regression/console.log.xz | Bin 5256 -> 5644 bytes 07-check_regression/extra-bisect-params | 1 + 07-check_regression/fails.sum | 7 + 07-check_regression/mail-body.txt | 27 + 07-check_regression/results.compare | 26 +- 07-check_regression/results.compare2 | 124 +- 07-check_regression/results.regressions | 27 + dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 29 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 27 + sumfiles/g++.log.xz | Bin 2811412 -> 2823360 bytes sumfiles/g++.sum | 126 +- sumfiles/gcc.log.xz | Bin 2467728 -> 2448528 bytes sumfiles/gcc.sum | 4734 +++++++++++++-------------- sumfiles/gfortran.log.xz | Bin 948412 -> 940544 bytes sumfiles/gfortran.sum | 42 +- sumfiles/libatomic.log.xz | Bin 2308 -> 2308 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 206664 -> 207172 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2736 -> 2724 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 468172 -> 467304 bytes sumfiles/libstdc++.sum | 13 +- 35 files changed, 2659 insertions(+), 2580 deletions(-) create mode 100644 07-check_regression/extra-bisect-params create mode 100644 07-check_regression/fails.sum create mode 100644 07-check_regression/results.regressions -- 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_gcc_check/master-aarch64 updated (82ab58419f -> bb2576de64)

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-aarch64 in repository toolchain/ci/base-artifacts. discards 82ab58419f 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits discards b365d15759 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits discards a7beb1b824 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits discards db682358d5 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits discards 86c5130918 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits discards e46378d5be 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits discards 3d4c59f35a 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits discards b0efffcbd4 441: onsuccess: #2403: 1: Success after gcc: 3 commits discards 107fd68628 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits discards 9c7ad98ab4 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits discards d85ceef183 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits discards ed153c5b83 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits discards c54b1cb21e 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits discards 9efdc410bd 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] discards 9ae6be67ea 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits discards 342272492a 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits discards 8743770074 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits discards ebf4712c4e 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits discards 0d8ec9aa6a 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] discards e9ae873e8f 429: onsuccess: #2391: 1: Success after binutils: 3 commits discards a90cb74734 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits discards cd841a98e2 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits discards b5a29ec1fa 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits discards a69e021644 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits discards bc05d2d039 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits discards 39e40ea013 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits discards 4cddaa2af8 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits discards 8fcab642c2 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits discards aafa177017 420: onsuccess: #2382: 1: Success after gcc: 2 commits discards 72d8206f08 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits discards 342d18ec16 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits discards 92e78a2da9 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits discards 7f4c86c243 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits discards 4c1e6f5271 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits discards 65bb2f427e 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits discards 34556e9048 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits discards e36981e508 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits discards 4546481d78 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits discards f9e5b9e438 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits discards cf36133771 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits discards f10ea006bd 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] discards 8ab20ee263 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits discards 23acc75e48 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits discards f3f2a39afe 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] discards 0dbb7fded2 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] discards 364f9fd87f 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits discards e0fe71b645 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits discards 1bcdc4dcdb 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] discards 2055098450 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits discards d2bb430ea8 399: onsuccess: #2361: 1: Success after gcc: 10 commits discards 6204b3bb24 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits discards 413248e35c 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits discards 420aeebd94 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits discards 39f9108909 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits discards 379ea55aac 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits discards ebd457b11c 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits discards 7ae3e359ac 392: onsuccess: #2354: 1: Success after gcc: 5 commits discards 52b752e939 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits discards 4acbb15fbf 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits discards 04e7709094 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits discards ef8f41edff 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits discards bff6a942df 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits discards b73ccfb9ba 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits discards 70df134b64 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits discards 12fc66e839 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits discards 6a9682f900 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits discards a97442cb71 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits discards 11d352c70f 381: onsuccess: #2343: 1: Success after gcc: 2 commits discards 90767d0444 380: onsuccess: #2342: 1: Success after gcc: 3 commits discards 0d47c5df33 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] discards 3090e8300a 378: onsuccess: #2340: 1: Success after binutils: 2 commits discards 7a88560239 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits discards d56e8218d1 376: onsuccess: #2338: 1: Success after gcc: 2 commits discards 08e62e158d 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits discards 5b04b062ec 374: onsuccess: #2336: 1: Success after gcc: 4 commits discards 989fe646e9 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits discards 1cf7eb383d 372: onsuccess: #2334: 1: Success after gcc: 5 commits discards 8d26434ac3 371: onsuccess: #2333: 1: Success after binutils: 5 commits discards 3f93c4d077 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits discards 762fdba612 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits discards 4140becd80 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits discards 7842957b4e 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits discards 1f11d61ec2 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits discards b2006813eb 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits discards cc263414d7 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits discards 0acb6612bd 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits discards 071dc83fba 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits discards 1dc253cb9f 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits discards 667cd4248f 360: onsuccess: #2317: 1: Success after binutils: 4 commits discards 4a6ddb0c73 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] discards 7b55026659 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits discards 985b7457da 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits discards 59bc61894f 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits discards b3dd914932 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits discards 908cdf8f09 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits discards 248d42e0fb 353: onsuccess: #2309: 1: Success after gcc: 7 commits discards df3e8e877d 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits discards 9b418fe573 351: onsuccess: #2307: 1: Success after binutils: 2 commits discards c41dceb4d2 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits discards d92c1805f3 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits discards 0a9b955005 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new 76c92a3454 348: onsuccess: #2304: 1: Success after binutils/gcc: 7 commits new c4276388d9 349: onsuccess: #2305: 1: Success after binutils/gcc: 21 commits new ecd2d7ddc1 350: onsuccess: #2306: 1: Success after binutils/gcc: 17 commits new 9d6cf75ed8 351: onsuccess: #2307: 1: Success after binutils: 2 commits new d41577e824 352: onsuccess: #2308: 1: Success after binutils/gcc: 4 commits new e6bfa5f488 353: onsuccess: #2309: 1: Success after gcc: 7 commits new 808cdf3e92 354: onsuccess: #2310: 1: Success after binutils/gcc: 8 commits new 1c013ff890 355: onsuccess: #2311: 1: Success after binutils/gcc: 2 commits new 1f08b13631 356: onsuccess: #2313: 1: Success after binutils/gcc: 3 commits new 9064813ec0 357: onsuccess: #2314: 1: Success after binutils/gcc: 3 commits new 93adffbe3d 358: onsuccess: #2315: 1: Success after binutils/gcc: 2 commits new d484f93670 359: onsuccess: #2316: 1: Success after gdb-12-branchpoint-2 [...] new 55704d1e74 360: onsuccess: #2317: 1: Success after binutils: 4 commits new ba94682332 361: onsuccess: #2318: 1: Success after binutils/gcc: 7 commits new d9bb57a351 362: onsuccess: #2319: 1: Success after binutils/gcc: 53 commits new 39c5a78a28 363: onsuccess: #2320: 1: Success after binutils/gcc: 25 commits new f9400e6ba4 364: onsuccess: #2321: 1: Success after binutils/gcc: 34 commits new 22070a2a93 365: onsuccess: #2322: 1: Success after binutils/gcc: 3 commits new 0caca684b1 366: onsuccess: #2328: 1: Success after binutils/gcc: 53 commits new bf4c1a9205 367: onsuccess: #2329: 1: Success after binutils/gcc: 9 commits new b71bb3beba 368: onsuccess: #2330: 1: Success after binutils/gcc: 15 commits new fded32841e 369: onsuccess: #2331: 1: Success after binutils/gcc: 7 commits new 336445bcdb 370: onsuccess: #2332: 1: Success after binutils/gcc: 25 commits new ec3ed18062 371: onsuccess: #2333: 1: Success after binutils: 5 commits new f4cfd65d49 372: onsuccess: #2334: 1: Success after gcc: 5 commits new a65c72de1e 373: onsuccess: #2335: 1: Success after binutils/gcc: 13 commits new 9385204e96 374: onsuccess: #2336: 1: Success after gcc: 4 commits new ae8f41d6c3 375: onsuccess: #2337: 1: Success after binutils/gcc: 10 commits new c1ed7ad8a5 376: onsuccess: #2338: 1: Success after gcc: 2 commits new 6350628e92 377: onsuccess: #2339: 1: Success after binutils/gcc: 3 commits new 4858da52cd 378: onsuccess: #2340: 1: Success after binutils: 2 commits new 0dccfa000c 379: onsuccess: #2341: 1: Success after basepoints/gcc-13-44 [...] new ee16e9e2c3 380: onsuccess: #2342: 1: Success after gcc: 3 commits new c8c660318a 381: onsuccess: #2343: 1: Success after gcc: 2 commits new 0cf180a1fc 382: onsuccess: #2344: 1: Success after binutils/gcc: 7 commits new c9fd3a5304 383: onsuccess: #2345: 1: Success after binutils/gcc: 3 commits new 9291353cb3 384: onsuccess: #2346: 1: Success after binutils/gcc: 8 commits new 9e2bc8ffc6 385: onsuccess: #2347: 1: Success after binutils/gcc: 12 commits new 7d47b013d3 386: onsuccess: #2348: 1: Success after binutils/gcc: 10 commits new 1fd7fe03cc 387: onsuccess: #2349: 1: Success after binutils/gcc: 6 commits new 25df8c6163 388: onsuccess: #2350: 1: Success after binutils/gcc: 13 commits new 671e6b6eb7 389: onsuccess: #2351: 1: Success after binutils/gcc: 12 commits new 12c1de9f7d 390: onsuccess: #2352: 1: Success after binutils/gcc: 15 commits new 3068a26cb4 391: onsuccess: #2353: 1: Success after binutils/gcc: 8 commits new 896dedae48 392: onsuccess: #2354: 1: Success after gcc: 5 commits new 754c7cd806 393: onsuccess: #2355: 1: Success after binutils/gcc: 8 commits new 6267eeac0b 394: onsuccess: #2356: 1: Success after binutils/gcc: 6 commits new 695a80bce8 395: onsuccess: #2357: 1: Success after binutils/gcc: 3 commits new 8f813354ab 396: onsuccess: #2358: 1: Success after binutils/gcc: 9 commits new aed70a9cf9 397: onsuccess: #2359: 1: Success after binutils/gcc: 10 commits new 6e86900a8b 398: onsuccess: #2360: 1: Success after binutils/gcc: 9 commits new 01fda7bf7d 399: onsuccess: #2361: 1: Success after gcc: 10 commits new 3f3110d9db 400: onsuccess: #2362: 1: Success after binutils/gcc: 6 commits new f2c66e1f64 401: onsuccess: #2363: 1: Success after gdb-12-branchpoint-3 [...] new 49be4ca49d 402: onsuccess: #2364: 1: Success after binutils/gcc: 19 commits new 72fdec85c5 403: onsuccess: #2365: 1: Success after binutils/gcc: 2 commits new 48dcb00f4c 404: onsuccess: #2366: 1: Success after basepoints/gcc-13-45 [...] new 4c8604a251 405: onsuccess: #2367: 1: Success after basepoints/gcc-13-45 [...] new 8936828a02 406: onsuccess: #2368: 1: Success after binutils/gcc: 8 commits new 8f2f9212c5 407: onsuccess: #2369: 1: Success after binutils/gcc: 2 commits new b3ebb315bd 408: onsuccess: #2370: 1: Success after basepoints/gcc-13-46 [...] new 4dbb7f10ec 409: onsuccess: #2371: 1: Success after binutils/gcc: 13 commits new 19c294349e 410: onsuccess: #2372: 1: Success after binutils/gcc: 27 commits new 481f1efb4a 411: onsuccess: #2373: 1: Success after binutils/gcc: 6 commits new dba6fefa8e 412: onsuccess: #2374: 1: Success after binutils/gcc: 4 commits new c822d164f0 413: onsuccess: #2375: 1: Success after binutils/gcc: 7 commits new 202c2c83ed 414: onsuccess: #2376: 1: Success after binutils/gcc: 55 commits new 0fda85b4b8 415: onsuccess: #2377: 1: Success after binutils/gcc: 15 commits new 305abc742f 416: onsuccess: #2378: 1: Success after binutils/gcc: 4 commits new 47d426eeda 417: onsuccess: #2379: 1: Success after binutils/gcc: 13 commits new 54511c0012 418: onsuccess: #2380: 1: Success after binutils/gcc: 14 commits new e3df54920f 419: onsuccess: #2381: 1: Success after binutils/gcc: 7 commits new cbd37eef0c 420: onsuccess: #2382: 1: Success after gcc: 2 commits new 8c26479119 421: onsuccess: #2383: 1: Success after binutils/gcc: 7 commits new 5556b4e84b 422: onsuccess: #2384: 1: Success after binutils/gcc: 12 commits new c706da728d 423: onsuccess: #2385: 1: Success after binutils/gcc: 14 commits new 308f386315 424: onsuccess: #2386: 1: Success after binutils/gcc: 3 commits new d42da83c80 425: onsuccess: #2387: 1: Success after binutils/gcc: 13 commits new ec7fcac110 426: onsuccess: #2388: 1: Success after binutils/gcc: 11 commits new 22fb62b394 427: onsuccess: #2389: 1: Success after binutils/gcc: 11 commits new 6fd66c22c9 428: onsuccess: #2390: 1: Success after binutils/gcc: 8 commits new 2846b884eb 429: onsuccess: #2391: 1: Success after binutils: 3 commits new 05c74afcea 430: onsuccess: #2392: 1: Success after basepoints/gcc-13-47 [...] new f2cfffb071 431: onsuccess: #2393: 1: Success after binutils/gcc: 3 commits new 2d282549c0 432: onsuccess: #2394: 1: Success after binutils/gcc: 3 commits new 338cc5e453 433: onsuccess: #2395: 1: Success after binutils/gcc: 3 commits new cc30c5e447 434: onsuccess: #2396: 1: Success after binutils/gcc: 2 commits new 18da3747b8 435: onsuccess: #2397: 1: Success after basepoints/gcc-13-47 [...] new 3ce887b98c 436: onsuccess: #2398: 1: Success after binutils/gcc: 20 commits new f2a970c028 437: onsuccess: #2399: 1: Success after binutils/gcc: 26 commits new 8ac675f7a6 438: onsuccess: #2400: 1: Success after binutils/gcc: 7 commits new b581e69725 439: onsuccess: #2401: 1: Success after binutils/gcc: 4 commits new 197305786e 440: onsuccess: #2402: 1: Success after binutils/gcc: 4 commits new ecf031c86f 441: onsuccess: #2403: 1: Success after gcc: 3 commits new 1b2765d2cc 442: onsuccess: #2404: 1: Success after binutils/gcc: 5 commits new 05bbe7f341 443: onsuccess: #2405: 1: Success after binutils/gcc: 36 commits new 237f5bf07a 444: onsuccess: #2406: 1: Success after binutils/gcc: 18 commits new c48f06b5ff 445: onsuccess: #2407: 1: Success after binutils/gcc: 8 commits new 42071fc054 446: onsuccess: #2408: 1: Success after binutils/gcc: 5 commits new 96a79f8bb9 447: onsuccess: #2409: 1: Success after binutils/gcc: 9 commits new 5841891e33 448: onsuccess: #2410: 1: Success after binutils/gcc: 18 commits new bb2576de64 449: onsuccess: #2411: 1: Success after binutils/gcc: 11 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 (82ab58419f) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_check/master-aarch64 [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1780 -> 1796 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 39748 -> 40772 bytes 04-build_abe-gcc/console.log.xz | Bin 215172 -> 217652 bytes 05-build_abe-dejagnu/console.log.xz | Bin 3876 -> 3844 bytes 06-build_abe-check_gcc/console.log.xz | Bin 3024 -> 2508 bytes 07-check_regression/console.log.xz | Bin 5960 -> 5608 bytes 07-check_regression/extra-bisect-params | 2 +- 07-check_regression/fails.sum | 6 +- 07-check_regression/mail-body.txt | 61 +- 07-check_regression/results.compare | 30 +- 07-check_regression/results.compare2 | 79 +- 07-check_regression/results.regressions | 30 +- 08-update_baseline/console.log | 36 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 63 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 +- results | 30 +- sumfiles/g++.log.xz | Bin 3616460 -> 3619460 bytes sumfiles/g++.sum | 138 +- sumfiles/gcc.log.xz | Bin 3147396 -> 3149948 bytes sumfiles/gcc.sum | 4578 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1054728 -> 1051384 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2184 -> 2188 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 220296 -> 220252 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2548 -> 2540 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 453164 -> 449020 bytes sumfiles/libstdc++.sum | 12 +- 36 files changed, 2571 insertions(+), 2590 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_gcc_bootstrap/release-arm-bootstrap_debug updated (f9107b2bd9 -> 2f9acb2f70)

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_bootstrap/release-arm-bootstrap_debug in repository toolchain/ci/base-artifacts. from f9107b2bd9 43: onsuccess: #166: 2: Success after binutils/gcc: 13 commits new 2f9acb2f70 44: onsuccess: #167: 2: Success after binutils/gcc: 14 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 -> 1736 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2756 bytes 04-build_abe-binutils/console.log.xz | Bin 53056 -> 53260 bytes 05-build_abe-bootstrap_debug/console.log.xz | Bin 462288 -> 462104 bytes 06-check_regression/console.log.xz | Bin 2828 -> 2836 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 20 ++++++++++---------- 12 files changed, 16 insertions(+), 16 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[glibc] branch master updated (3c66c9600e -> c923cd8c49)

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 glibc. from 3c66c9600e Linux: Pass size argument of epoll_create to the kernel new c923cd8c49 Avoid use of atoi in malloc 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: malloc/arena.c | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 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_gnu_native_check_gdb/master-arm updated (0b42063425 -> d6545f42d9)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_gdb/master-arm in repository toolchain/ci/base-artifacts. discards 0b42063425 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] discards e05c535c74 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] discards a3d9c775f8 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] discards ee8ce1d2b4 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits discards 55823a796f 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] discards 8c4a0a0ef2 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] discards 710ae600a2 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] discards f5090a0990 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] discards 174dda1ac6 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] discards 34c8ceb5ee 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] discards 8f5fc2a16a 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] discards 3ccade06f4 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] discards 7541c1b9b9 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] discards c25d0ac5ea 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] discards 8683849655 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] discards 6db50daede 125: onsuccess: #614: 1: Success after linux: 12 commits discards b754f2c3a2 124: onsuccess: #612: 1: Success after binutils: 18 commits discards efae546c00 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] discards ed0793ad23 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] discards 4bc0cb4a70 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] discards 1aff725078 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] discards f8dcc5f3b5 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] discards 8d6b087070 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] discards 326d6cc8cd 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] discards 87c40f6912 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] discards c28fe39fdd 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] discards ec96862620 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] discards d3f490a261 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] discards e5c16170ad 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits discards b55d473bd1 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits discards 660b4c3bda 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] discards df4ba9d74a 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] discards d52ffff3d5 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] discards 82788eb731 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] discards a9cf92b785 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] discards 6eee4c13a0 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] discards c128f963f4 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] discards 3ecdb4ff67 103: onsuccess: #589: 1: Success after binutils: 3 commits discards fd9d62ab55 102: onsuccess: #586: 1: Success after binutils: 5 commits discards ce30dd3afa 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] discards 9b62dde9fd 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] discards 7334b6fb74 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] discards 180e0a43d2 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] discards 12da62cce2 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] discards d9a7cdfb1d 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] discards 415f76110f 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] discards 9d443a59f3 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] discards 109f82100e 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] discards 57676e2879 92: onsuccess: #575: 1: Success after linux: 34 commits discards ca5b11bdc4 91: onsuccess: #574: 1: Success after glibc: 3 commits discards d85715678f 90: onsuccess: #572: 1: Success after binutils: 15 commits discards 74c30a12f2 89: onsuccess: #570: 1: Success after linux: 11 commits discards a12caf9b75 88: onsuccess: #569: 1: Success after glibc: 10 commits discards bd493ce41b 87: onsuccess: #567: 1: Success after binutils: 8 commits discards e7b2747504 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] discards 0719b78095 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] discards 2c5d3c16c6 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] discards 6bba09f2c5 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] discards 240303f589 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] discards e84b9985bf 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] discards 9d6ec45abc 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] discards b42a5c1a72 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] discards e5f9b8d99c 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] discards 179c1e29a8 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] discards f8713e08b8 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] discards 13e36a69f8 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] discards 376879dcca 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] discards a1a5ed6442 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] discards b8dc101b11 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] discards 66f31eff9f 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] discards 75b053a0e4 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards d8362768b0 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] discards 7c54dd3876 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] discards a6f0b35c07 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 16947bf0bd 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 572f51e24b 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] discards 4ccb4f1b85 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] discards 545fd6fbe4 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] discards a19f6f4219 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] discards cab55208e7 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] discards e1ad8993f7 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] discards 8115194ad7 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] discards 4dd6ab476a 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] discards fadde7f745 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] discards b65ab0794d 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] discards 0700ba89ea 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] discards 99c3b040dd 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] discards c2f217fe77 53: onsuccess: #531: 1: Success after binutils: 12 commits discards 60e4c1e421 52: onsuccess: #528: 1: Success after binutils: 8 commits discards efc425cb3d 51: onsuccess: #525: 1: Success after binutils: 8 commits discards 63d5093d86 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] discards 6fabf3ff2f 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] discards 58179a531e 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] discards bb0cb3ac97 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] discards ab05001a2c 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] discards f96668197e 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] discards 914a66e468 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] discards b74e2b4d29 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] discards b1118a35af 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] discards 5cee24afaa 41: onsuccess: #514: 1: Success after linux: 64 commits discards 74460a2bc8 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new 474bbaa9a1 40: onsuccess: #513: 1: Success after glibc-2.36.9000-121-g5 [...] new badadd1850 41: onsuccess: #514: 1: Success after linux: 64 commits new ea51c07a5d 42: onsuccess: #515: 1: Success after binutils/gcc/linux/gli [...] new 7605fd1fce 43: onsuccess: #516: 1: Success after binutils/gcc/linux/gli [...] new 6581b1b672 44: onsuccess: #517: 1: Success after binutils/gcc/linux/gli [...] new 937101d6c3 45: onsuccess: #518: 1: Success after binutils/gcc/glibc/gdb [...] new 2ea03174f1 46: onsuccess: #519: 1: Success after binutils/gcc/linux/gli [...] new c570d081b2 47: onsuccess: #520: 1: Success after binutils/gcc/glibc/gdb [...] new c9cac3b780 48: onsuccess: #521: 1: Success after binutils/gcc/linux/gli [...] new 5dc6a0e725 49: onsuccess: #522: 1: Success after binutils/gcc/linux/gli [...] new 06b6dfb37b 50: onsuccess: #523: 1: Success after binutils/gcc/linux/gdb [...] new 506e95cffd 51: onsuccess: #525: 1: Success after binutils: 8 commits new 1de617bd86 52: onsuccess: #528: 1: Success after binutils: 8 commits new 68c7542530 53: onsuccess: #531: 1: Success after binutils: 12 commits new d0c60f4195 54: onsuccess: #533: 1: Success after binutils/gcc/linux/gli [...] new c37814cbb7 55: onsuccess: #534: 1: Success after binutils/gcc/linux/gli [...] new 7681cb2227 56: onsuccess: #535: 1: Success after binutils/gcc/linux/gli [...] new 3257eae6cd 57: onsuccess: #536: 1: Success after binutils/gcc/linux/gli [...] new eafc270abc 58: onsuccess: #537: 1: Success after binutils/gcc/linux/gli [...] new 50c97142ba 59: onsuccess: #538: 1: Success after binutils/gcc/linux/gli [...] new b5749e00f2 60: onsuccess: #539: 1: Success after binutils/gcc/linux/gli [...] new 1622ca53d0 61: onsuccess: #540: 1: Success after binutils/gcc/linux/gli [...] new 6c05abf72b 62: onsuccess: #541: 1: Success after binutils/gcc/linux/gli [...] new 40d1815498 63: onsuccess: #542: 1: Success after binutils/gcc/linux/gli [...] new e523007b26 64: onsuccess: #543: 1: Success after binutils/gcc/linux/gli [...] new be98b23023 65: onsuccess: #544: 1: Success after binutils/gcc/linux/gli [...] new ced58409ec 66: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new 116387c448 67: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new c48b4b519e 68: onsuccess: #547: 1: Success after binutils/gcc/linux/gli [...] new eb886001d4 69: onsuccess: #548: 1: Success after binutils/gcc/linux/gli [...] new 951af94da3 70: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new 5971f893ca 71: onsuccess: #550: 1: Success after binutils/gcc/linux/gdb [...] new 0a6004a23f 72: onsuccess: #551: 1: Success after binutils/gcc/linux/gli [...] new b4f9183c9b 73: onsuccess: #552: 1: Success after binutils/gcc/linux/gli [...] new 67ef6fadaa 74: onsuccess: #553: 1: Success after binutils/gcc/linux/gli [...] new 9a5547c1b6 75: onsuccess: #554: 1: Success after binutils/gcc/glibc/gdb [...] new f018ad147f 76: onsuccess: #555: 1: Success after binutils/gcc/linux/gli [...] new d84a3277dc 77: onsuccess: #556: 1: Success after binutils/gcc/linux/gdb [...] new 1dfd6171f0 78: onsuccess: #557: 1: Success after binutils/gcc/linux/gdb [...] new 1dafd5d142 79: onsuccess: #558: 1: Success after binutils/gcc/linux/gli [...] new 8cc3f32ba2 80: onsuccess: #559: 1: Success after binutils/gcc/linux/gli [...] new d3851d664b 81: onsuccess: #560: 1: Success after binutils/gcc/linux/gli [...] new fdef66e78a 82: onsuccess: #561: 1: Success after binutils/gcc/linux/gli [...] new 0e97f85c7b 83: onsuccess: #562: 1: Success after binutils/gcc/linux/gli [...] new 0d05676e8c 84: onsuccess: #563: 1: Success after binutils/gcc/linux/gli [...] new 092e3440b9 85: onsuccess: #564: 1: Success after binutils/gcc/linux/gdb [...] new d6502a1e44 86: onsuccess: #565: 1: Success after binutils/gcc/linux/gli [...] new f4f1f57a09 87: onsuccess: #567: 1: Success after binutils: 8 commits new 822a863944 88: onsuccess: #569: 1: Success after glibc: 10 commits new 0f0987574b 89: onsuccess: #570: 1: Success after linux: 11 commits new 890891241f 90: onsuccess: #572: 1: Success after binutils: 15 commits new fb6294bc53 91: onsuccess: #574: 1: Success after glibc: 3 commits new b857444360 92: onsuccess: #575: 1: Success after linux: 34 commits new 138d8ea531 93: onsuccess: #576: 1: Success after binutils/gcc/linux/gli [...] new 007a68e802 94: onsuccess: #577: 1: Success after binutils/gcc/linux/gli [...] new 87d2e70b69 95: onsuccess: #578: 1: Success after binutils/gcc/linux/gli [...] new bcdd834fd0 96: onsuccess: #579: 1: Success after binutils/gcc/linux/gdb [...] new 6f1d2d57b7 97: onsuccess: #580: 1: Success after binutils/gcc/linux/gli [...] new 2b139d67cd 98: onsuccess: #581: 1: Success after binutils/gcc/linux/gli [...] new a7a479e98c 99: onsuccess: #582: 1: Success after binutils/gcc/linux/gli [...] new 2d83b0ddc0 100: onsuccess: #583: 1: Success after binutils/gcc/linux/gl [...] new a3e7be687c 101: onsuccess: #584: 1: Success after binutils/gcc/linux/gd [...] new 137eecbbd3 102: onsuccess: #586: 1: Success after binutils: 5 commits new a4a9ddeddc 103: onsuccess: #589: 1: Success after binutils: 3 commits new 03983f13b8 104: onsuccess: #591: 1: Success after binutils/gcc/linux/gl [...] new d54ff72480 105: onsuccess: #592: 1: Success after binutils/gcc/linux/gd [...] new 7d8ddfac7f 106: onsuccess: #593: 1: Success after binutils/gcc/linux/gd [...] new b02c0f9e3f 107: onsuccess: #594: 1: Success after binutils/gcc/linux/gl [...] new 8461318c46 108: onsuccess: #595: 1: Success after binutils/gcc/linux/gd [...] new 6e7036fc04 109: onsuccess: #596: 1: Success after binutils/gcc/linux/gd [...] new f9ff128984 110: onsuccess: #597: 1: Success after binutils/gcc/linux/gl [...] new b4e3da6b7b 111: onsuccess: #598: 1: Success after binutils/gcc/gdb: 48 commits new 89ea5c778b 112: onsuccess: #599: 1: Success after binutils/gcc/gdb: 68 commits new 357d8cf22f 113: onsuccess: #600: 1: Success after binutils/gcc/linux/gd [...] new ce194e6c18 114: onsuccess: #601: 1: Success after binutils/gcc/linux/gd [...] new 47fa96658c 115: onsuccess: #602: 1: Success after binutils/gcc/linux/gd [...] new 139fcdc340 116: onsuccess: #603: 1: Success after binutils/gcc/linux/gd [...] new 77afe34cda 117: onsuccess: #604: 1: Success after binutils/gcc/linux/gl [...] new ca191af5da 118: onsuccess: #605: 1: Success after binutils/gcc/linux/gl [...] new 2cb302b650 119: onsuccess: #606: 1: Success after binutils/gcc/linux/gl [...] new b2d67fad2e 120: onsuccess: #607: 1: Success after binutils/gcc/linux/gd [...] new 7c42053977 121: onsuccess: #608: 1: Success after binutils/gcc/linux/gl [...] new 2fd03e0954 122: onsuccess: #609: 1: Success after binutils/gcc/linux/gl [...] new 9a7a7f1069 123: onsuccess: #610: 1: Success after binutils/gcc/linux/gd [...] new b1642359d7 124: onsuccess: #612: 1: Success after binutils: 18 commits new bf4498db73 125: onsuccess: #614: 1: Success after linux: 12 commits new 0696e98bc6 126: onsuccess: #615: 1: Success after binutils/gcc/linux/gl [...] new bb1e82cfbb 127: onsuccess: #616: 1: Success after binutils/gcc/linux/gl [...] new 08e4599a19 128: onsuccess: #618: 1: Success after binutils/gcc/linux/gl [...] new fbcb0bd644 129: onsuccess: #619: 1: Success after binutils/gcc/linux/gd [...] new 6db97e57b4 130: onsuccess: #620: 1: Success after binutils/gcc/linux/gd [...] new 01ca749531 131: onsuccess: #621: 1: Success after binutils/gcc/linux/gl [...] new 11ce1dd8c9 132: onsuccess: #622: 1: Success after binutils/gcc/linux/gd [...] new 71b585707e 133: onsuccess: #623: 1: Success after binutils/gcc/linux/gl [...] new fcdd8d9f5b 134: onsuccess: #624: 1: Success after binutils/gcc/linux/gl [...] new 9614f47974 135: onsuccess: #625: 1: Success after binutils/gcc/linux/gl [...] new 3d7569387e 136: onsuccess: #626: 1: Success after binutils/gcc/linux/gd [...] new afbb402a1d 137: onsuccess: #627: 1: Success after binutils/gcc/gdb: 14 commits new 80106865cc 138: onsuccess: #628: 1: Success after binutils/gcc/linux/gl [...] new 1ead25fe83 139: onsuccess: #629: 1: Success after binutils/gcc/linux/gl [...] new 3288503d1a 140: onsuccess: #631: 1: Success after binutils/gcc/linux/gl [...] new d6545f42d9 141: onsuccess: #633: 1: Success after binutils/gcc/linux/gl [...] This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (0b42063425) \ 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 1768 -> 1756 bytes 02-prepare_abe/console.log.xz | Bin 2760 -> 2776 bytes 03-build_abe-binutils/console.log.xz | Bin 53648 -> 54588 bytes 04-build_abe-gcc/console.log.xz | Bin 234652 -> 235700 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 9504 -> 8548 bytes 07-build_abe-glibc/console.log.xz | Bin 238060 -> 236420 bytes 08-build_abe-gdb/console.log.xz | Bin 52480 -> 52208 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3828 -> 3884 bytes 10-build_abe-check_gdb/console.log.xz | Bin 2256 -> 2376 bytes 11-check_regression/console.log.xz | Bin 11308 -> 12252 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 40 +- 11-check_regression/mail-body.txt | 172 +- 11-check_regression/results.compare | 85 +- 11-check_regression/results.compare2 | 356 +- 11-check_regression/results.regressions | 85 +- 12-update_baseline/console.log | 56 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 174 +- mail/mail-subject.txt | 2 +- manifest.sh | 39 +- results | 85 +- sumfiles/gdb.log.xz | Bin 1817952 -> 1807220 bytes sumfiles/gdb.sum | 7275 ++++++++++++++++++++----------- 31 files changed, 5310 insertions(+), 3075 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

[linux] branch master updated (9d2f6060fe4c -> 8395ae05cb5a)

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 linux. from 9d2f6060fe4c Merge tag 'trace-v6.2-1' of git://git.kernel.org/pub/scm/l [...] new 66dfc517e8ec perf python: Don't stop building if python setuptools isn' [...] new 30d647f5ba9e Merge remote-tracking branch 'torvalds/master' into perf/core new 0bc1d0e2c167 tools headers disabled-cpufeatures: Sync with the kernel sources new 51c4f2bf5397 tools headers cpufeatures: Sync with the kernel sources new 43a3ce77aee9 tools headers UAPI: Sync linux/fscrypt.h with the kernel sources new eeac18e2bff3 tools headers UAPI: Sync drm/i915_drm.h with the kernel sources new a66558dcb107 tools arch x86: Sync the msr-index.h copy with the kernel sources new 6d5edd15c982 tools headers UAPI: Sync powerpc syscall table with the ke [...] new b235e5b51f7d tools headers UAPI: Sync linux/kvm.h with the kernel sources new 188ac720d364 perf debug: Set debug_peo_args and redirect_to_stderr vari [...] new 7c0a6144f9a6 perf tools: Fix usage of the verbose variable new 8b269b755512 perf probe: Check -v and -q options in the right place new 59119c09ae74 perf lock contention: Factor out lock_type_table new b4a7eff93c39 perf lock contention: Add -Y/--type-filter option new 529772c4df28 perf lock contention: Support lock type filtering for BPF new 511e19b9e211 perf lock contention: Add -L/--lock-filter option new 5e3febe7b7b9 perf lock contention: Support lock addr/name filtering for BPF new cb459c89b734 perf test: Update 'perf lock contention' test new 0c0a0db87e1c perf tools: Add .DELETE_ON_ERROR special Makefile target t [...] new b50d691e50e6 perf test: Fix "all PMU test" to skip parametrized events new ea335ef3ddcd perf srcline: Do not return NULL for srcline new 06ea72a42d96 perf symbol: Add filename__has_section() new 3b27222dd6cf perf srcline: Skip srcline if .debug_line is missing new d5e33ce06ba4 perf srcline: Conditionally suppress addr2line warnings new cb6e92c76427 perf hist: Add perf_hpp_fmt->init() callback new ec222d7e7cfd perf hist: Improve srcline sort key performance new f0cdde28fecc perf hist: Improve srcfile sort key performance new ad9ef9eb64a2 perf hist: Improve srcline_{from,to} sort key performance new ed4c1778cc1a perf test pmu-events: Fake PMU metric workaround new 266b2ca72742 perf vendor events intel: Refresh alderlake metrics new a5abef626f35 perf vendor events intel: Refresh alderlake-n metrics new 6fa91f645f6f perf vendor events intel: Refresh bonnell events new fec57a8e4a2c perf vendor events intel: Refresh broadwell metrics and events new f6ee944ce4e8 perf vendor events intel: Refresh broadwellde metrics and events new 5e241aad6205 perf vendor events intel: Refresh broadwellx metrics and events new 8358b1222798 perf vendor events intel: Refresh cascadelakex metrics and events new 5cebe49ce803 perf vendor events intel: Refresh elkhartlake events new 387bc79f8394 perf vendor events intel: Refresh goldmont events new a335420d3298 perf vendor events intel: Refresh goldmontplus events new 8749311045ef perf vendor events intel: Refresh haswell metrics and events new 667433c4eb84 perf vendor events intel: Refresh haswellx metrics and events new f8473086e344 perf vendor events intel: Refresh icelake metrics and events new f8e23ad10520 perf vendor events intel: Refresh icelakex metrics and events new d86ac8d7cd31 perf vendor events intel: Refresh ivybridge metrics and events new 8ee37818a057 perf vendor events intel: Refresh ivytown metrics and events new e85af8a641ba perf vendor events intel: Refresh jaketown metrics and events new 2c3fd22bb3ff perf vendor events intel: Refresh knightslanding events new 5362e4d1f24e perf vendor events intel: Refresh meteorlake events new 7e353370cd17 perf vendor events intel: Refresh nehalemep events new d4e50e519ba0 perf vendor events intel: Refresh nehalemex events new 28641ef5f387 perf vendor events intel: Refresh sandybridge metrics and events new 400dd489d42f perf vendor events intel: Refresh sapphirerapids metrics a [...] new 1b91a994a2ac perf vendor events intel: Refresh silvermont events new 00ca782ec9f8 perf vendor events intel: Refresh skylake metrics and events new ecabdc6a7280 perf vendor events intel: Refresh skylakex metrics and events new 9b4240831af7 perf vendor events intel: Refresh snowridgex events new 69f685e0c125 perf vendor events intel: Refresh tigerlake metrics and events new 598020743153 perf vendor events intel: Refresh westmereep-dp events new bcea0838b9db perf vendor events intel: Refresh westmereep-sp events new 6abaa0204c34 perf vendor events intel: Refresh westmereex events new 658448281d19 perf vendor events amd: Add Zen 4 core events new 5b2ca349c313 perf vendor events amd: Add Zen 4 uncore events new aba4cb3eb5b8 perf vendor events amd: Add Zen 4 metrics new 5fe089d3a3eb perf vendor events amd: Add Zen 4 mapping new c3c2e8ebe365 perf build: Remove explicit reference to python 2.x devel files new 9854e7ad35fe perf arm64: Simplify mksyscalltbl new f257ba9c160f perf scripting python: Don't be strict at handling libtrac [...] new 09e6f9f98370 perf python: Fix splitting CC into compiler and options new d1ac1a2b1426 Merge tag 'perf-tools-for-v6.2-2-2022-12-22' of git://git. [...] new 36f82c93ee0b afs: Fix lost servers_outstanding count new 318b83b71242 afs: remove variable nr_servers new b3d3ca556757 afs: remove afs_cache_netfs and afs_zap_permits() declarations new a9eb558a5bea afs: Stop implementing ->writepage() new ff75ec43a2f6 Merge tag 'afs-next-20221222' of git://git.kernel.org/pub/ [...] new 6456ab5d7ccd scsi: libfc: Include the correct header new 9f5436f47c58 scsi: sd: sd_zbc: Trace zone append emulation new 255c4f4a6d5b block: Add error codes for common PR failures new c9293c1199ec scsi: core: Rename status_byte to sg_status_byte new 04b3c8c0025a scsi: sd: Convert SCSI errors to PR errors new 7fb42780d06c nvme: Convert NVMe errors to PR errors new 68ad83188d78 scsi: qla2xxx: Fix crash when I/O abort times out new 8395ae05cb5a Merge tag 'scsi-misc' of git://git.kernel.org/pub/scm/linu [...] The 82 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: drivers/nvme/host/core.c | 33 +- drivers/scsi/libfc/fc_disc.c | 2 +- drivers/scsi/qla2xxx/qla_init.c | 14 +- drivers/scsi/scsi_ioctl.c | 2 +- drivers/scsi/sd.c | 35 +- drivers/scsi/sd_trace.h | 84 + drivers/scsi/sd_zbc.c | 6 + drivers/scsi/sg.c | 2 +- fs/afs/dir.c | 1 + fs/afs/file.c | 3 +- fs/afs/fs_probe.c | 5 +- fs/afs/internal.h | 8 - fs/afs/volume.c | 6 +- fs/afs/write.c | 83 +- include/scsi/scsi.h | 1 + include/scsi/sg.h | 2 +- include/uapi/linux/pr.h | 17 + tools/arch/x86/include/asm/cpufeatures.h | 6 + tools/arch/x86/include/asm/disabled-features.h | 17 +- tools/arch/x86/include/asm/msr-index.h | 24 +- tools/include/uapi/drm/i915_drm.h | 62 +- tools/include/uapi/linux/fscrypt.h | 4 +- tools/include/uapi/linux/kvm.h | 13 +- tools/perf/Documentation/perf-lock.txt | 27 +- tools/perf/Makefile.config | 11 +- tools/perf/Makefile.perf | 3 + tools/perf/arch/arm64/entry/syscalls/mksyscalltbl | 23 +- tools/perf/arch/powerpc/entry/syscalls/syscall.tbl | 7 +- tools/perf/builtin-lock.c | 311 +- tools/perf/builtin-probe.c | 17 +- tools/perf/builtin-record.c | 4 +- tools/perf/builtin-script.c | 2 +- tools/perf/builtin-stat.c | 4 +- tools/perf/dlfilters/dlfilter-test-api-v0.c | 2 +- .../pmu-events/arch/x86/alderlake/adl-metrics.json | 116 +- .../arch/x86/alderlaken/adln-metrics.json | 18 +- tools/perf/pmu-events/arch/x86/amdzen4/branch.json | 82 + tools/perf/pmu-events/arch/x86/amdzen4/cache.json | 772 + tools/perf/pmu-events/arch/x86/amdzen4/core.json | 122 + .../pmu-events/arch/x86/amdzen4/data-fabric.json | 1090 + .../arch/x86/amdzen4/floating-point.json | 818 + tools/perf/pmu-events/arch/x86/amdzen4/memory.json | 174 + tools/perf/pmu-events/arch/x86/amdzen4/other.json | 138 + .../perf/pmu-events/arch/x86/amdzen4/pipeline.json | 98 + .../pmu-events/arch/x86/amdzen4/recommended.json | 334 + tools/perf/pmu-events/arch/x86/bonnell/cache.json | 93 - .../arch/x86/bonnell/floating-point.json | 47 +- .../perf/pmu-events/arch/x86/bonnell/frontend.json | 11 - tools/perf/pmu-events/arch/x86/bonnell/memory.json | 19 - tools/perf/pmu-events/arch/x86/bonnell/other.json | 74 +- .../perf/pmu-events/arch/x86/bonnell/pipeline.json | 65 +- .../arch/x86/bonnell/virtual-memory.json | 15 - .../pmu-events/arch/x86/broadwell/bdw-metrics.json | 137 +- .../perf/pmu-events/arch/x86/broadwell/cache.json | 957 - .../arch/x86/broadwell/floating-point.json | 40 - .../pmu-events/arch/x86/broadwell/frontend.json | 56 - .../perf/pmu-events/arch/x86/broadwell/memory.json | 890 - .../perf/pmu-events/arch/x86/broadwell/other.json | 8 - .../pmu-events/arch/x86/broadwell/pipeline.json | 272 - .../arch/x86/broadwell/uncore-cache.json | 19 - .../arch/x86/broadwell/uncore-other.json | 25 +- .../arch/x86/broadwell/virtual-memory.json | 76 - .../arch/x86/broadwellde/bdwde-metrics.json | 143 +- .../pmu-events/arch/x86/broadwellde/cache.json | 153 - .../arch/x86/broadwellde/floating-point.json | 40 - .../pmu-events/arch/x86/broadwellde/frontend.json | 56 - .../pmu-events/arch/x86/broadwellde/memory.json | 86 - .../pmu-events/arch/x86/broadwellde/other.json | 8 - .../pmu-events/arch/x86/broadwellde/pipeline.json | 272 - .../arch/x86/broadwellde/uncore-cache.json | 414 +- .../arch/x86/broadwellde/uncore-memory.json | 477 +- .../arch/x86/broadwellde/uncore-other.json | 163 +- .../arch/x86/broadwellde/uncore-power.json | 57 - .../arch/x86/broadwellde/virtual-memory.json | 76 - .../arch/x86/broadwellx/bdx-metrics.json | 1703 +- .../perf/pmu-events/arch/x86/broadwellx/cache.json | 191 - .../arch/x86/broadwellx/floating-point.json | 40 - .../pmu-events/arch/x86/broadwellx/frontend.json | 56 - .../pmu-events/arch/x86/broadwellx/memory.json | 143 - .../perf/pmu-events/arch/x86/broadwellx/other.json | 8 - .../pmu-events/arch/x86/broadwellx/pipeline.json | 272 - .../arch/x86/broadwellx/uncore-cache.json | 3740 +- .../arch/x86/broadwellx/uncore-interconnect.json | 1225 +- .../arch/x86/broadwellx/uncore-memory.json | 2052 +- .../arch/x86/broadwellx/uncore-other.json | 2410 +- .../arch/x86/broadwellx/uncore-power.json | 198 +- .../arch/x86/broadwellx/virtual-memory.json | 76 - .../pmu-events/arch/x86/cascadelakex/cache.json | 3644 -- .../arch/x86/cascadelakex/clx-metrics.json | 2217 +- .../arch/x86/cascadelakex/floating-point.json | 24 - .../pmu-events/arch/x86/cascadelakex/frontend.json | 109 - .../pmu-events/arch/x86/cascadelakex/memory.json | 2194 - .../pmu-events/arch/x86/cascadelakex/other.json | 490 - .../pmu-events/arch/x86/cascadelakex/pipeline.json | 194 - .../arch/x86/cascadelakex/uncore-memory.json | 3185 +- .../arch/x86/cascadelakex/uncore-other.json | 29770 ++++++------ .../arch/x86/cascadelakex/uncore-power.json | 45 +- .../arch/x86/cascadelakex/virtual-memory.json | 56 - .../pmu-events/arch/x86/elkhartlake/cache.json | 252 - .../arch/x86/elkhartlake/floating-point.json | 11 - .../pmu-events/arch/x86/elkhartlake/frontend.json | 36 - .../pmu-events/arch/x86/elkhartlake/memory.json | 84 - .../pmu-events/arch/x86/elkhartlake/other.json | 143 - .../pmu-events/arch/x86/elkhartlake/pipeline.json | 213 - .../arch/x86/elkhartlake/virtual-memory.json | 117 - tools/perf/pmu-events/arch/x86/goldmont/cache.json | 288 - .../arch/x86/goldmont/floating-point.json | 6 - .../pmu-events/arch/x86/goldmont/frontend.json | 16 - .../perf/pmu-events/arch/x86/goldmont/memory.json | 6 - tools/perf/pmu-events/arch/x86/goldmont/other.json | 10 - .../pmu-events/arch/x86/goldmont/pipeline.json | 77 - .../arch/x86/goldmont/virtual-memory.json | 14 - .../pmu-events/arch/x86/goldmontplus/cache.json | 470 - .../arch/x86/goldmontplus/floating-point.json | 11 - .../pmu-events/arch/x86/goldmontplus/frontend.json | 32 - .../pmu-events/arch/x86/goldmontplus/memory.json | 10 - .../pmu-events/arch/x86/goldmontplus/other.json | 20 - .../pmu-events/arch/x86/goldmontplus/pipeline.json | 143 - .../arch/x86/goldmontplus/virtual-memory.json | 69 - tools/perf/pmu-events/arch/x86/haswell/cache.json | 211 - .../arch/x86/haswell/floating-point.json | 20 - .../perf/pmu-events/arch/x86/haswell/frontend.json | 58 - .../pmu-events/arch/x86/haswell/hsw-metrics.json | 117 +- tools/perf/pmu-events/arch/x86/haswell/memory.json | 149 - tools/perf/pmu-events/arch/x86/haswell/other.json | 8 - .../perf/pmu-events/arch/x86/haswell/pipeline.json | 258 - .../pmu-events/arch/x86/haswell/uncore-cache.json | 50 - .../pmu-events/arch/x86/haswell/uncore-other.json | 21 +- .../arch/x86/haswell/virtual-memory.json | 98 - tools/perf/pmu-events/arch/x86/haswellx/cache.json | 217 - .../arch/x86/haswellx/floating-point.json | 20 - .../pmu-events/arch/x86/haswellx/frontend.json | 58 - .../pmu-events/arch/x86/haswellx/hsx-metrics.json | 1467 +- .../perf/pmu-events/arch/x86/haswellx/memory.json | 170 - tools/perf/pmu-events/arch/x86/haswellx/other.json | 8 - .../pmu-events/arch/x86/haswellx/pipeline.json | 258 - .../pmu-events/arch/x86/haswellx/uncore-cache.json | 2448 +- .../arch/x86/haswellx/uncore-interconnect.json | 722 +- .../arch/x86/haswellx/uncore-memory.json | 2037 +- .../pmu-events/arch/x86/haswellx/uncore-other.json | 1834 +- .../pmu-events/arch/x86/haswellx/uncore-power.json | 150 +- .../arch/x86/haswellx/virtual-memory.json | 98 - tools/perf/pmu-events/arch/x86/icelake/cache.json | 412 - .../arch/x86/icelake/floating-point.json | 28 - .../perf/pmu-events/arch/x86/icelake/frontend.json | 144 - .../pmu-events/arch/x86/icelake/icl-metrics.json | 151 +- tools/perf/pmu-events/arch/x86/icelake/memory.json | 171 - tools/perf/pmu-events/arch/x86/icelake/other.json | 132 - .../perf/pmu-events/arch/x86/icelake/pipeline.json | 349 +- .../pmu-events/arch/x86/icelake/uncore-other.json | 10 +- .../arch/x86/icelake/virtual-memory.json | 80 - tools/perf/pmu-events/arch/x86/icelakex/cache.json | 316 +- .../arch/x86/icelakex/floating-point.json | 28 - .../pmu-events/arch/x86/icelakex/frontend.json | 140 - .../pmu-events/arch/x86/icelakex/icx-metrics.json | 2192 +- .../perf/pmu-events/arch/x86/icelakex/memory.json | 139 +- tools/perf/pmu-events/arch/x86/icelakex/other.json | 117 - .../pmu-events/arch/x86/icelakex/pipeline.json | 344 +- .../arch/x86/icelakex/uncore-memory.json | 1878 +- .../pmu-events/arch/x86/icelakex/uncore-other.json | 45144 +++++++++---------- .../pmu-events/arch/x86/icelakex/uncore-power.json | 115 +- .../arch/x86/icelakex/virtual-memory.json | 88 - .../perf/pmu-events/arch/x86/ivybridge/cache.json | 235 - .../arch/x86/ivybridge/floating-point.json | 34 - .../pmu-events/arch/x86/ivybridge/frontend.json | 60 - .../pmu-events/arch/x86/ivybridge/ivb-metrics.json | 119 +- .../perf/pmu-events/arch/x86/ivybridge/memory.json | 54 - .../perf/pmu-events/arch/x86/ivybridge/other.json | 8 - .../pmu-events/arch/x86/ivybridge/pipeline.json | 250 - .../arch/x86/ivybridge/uncore-cache.json | 50 - .../arch/x86/ivybridge/uncore-other.json | 28 +- .../arch/x86/ivybridge/virtual-memory.json | 36 - tools/perf/pmu-events/arch/x86/ivytown/cache.json | 274 - .../arch/x86/ivytown/floating-point.json | 34 - .../perf/pmu-events/arch/x86/ivytown/frontend.json | 60 - .../pmu-events/arch/x86/ivytown/ivt-metrics.json | 133 +- tools/perf/pmu-events/arch/x86/ivytown/memory.json | 121 - tools/perf/pmu-events/arch/x86/ivytown/other.json | 8 - .../perf/pmu-events/arch/x86/ivytown/pipeline.json | 250 - .../pmu-events/arch/x86/ivytown/uncore-cache.json | 388 +- .../arch/x86/ivytown/uncore-interconnect.json | 505 +- .../pmu-events/arch/x86/ivytown/uncore-memory.json | 209 +- .../pmu-events/arch/x86/ivytown/uncore-other.json | 254 +- .../pmu-events/arch/x86/ivytown/uncore-power.json | 95 - .../arch/x86/ivytown/virtual-memory.json | 40 - tools/perf/pmu-events/arch/x86/jaketown/cache.json | 289 - .../arch/x86/jaketown/floating-point.json | 30 - .../pmu-events/arch/x86/jaketown/frontend.json | 64 - .../pmu-events/arch/x86/jaketown/jkt-metrics.json | 91 +- .../perf/pmu-events/arch/x86/jaketown/memory.json | 103 - tools/perf/pmu-events/arch/x86/jaketown/other.json | 12 - .../pmu-events/arch/x86/jaketown/pipeline.json | 255 - .../pmu-events/arch/x86/jaketown/uncore-cache.json | 266 +- .../arch/x86/jaketown/uncore-interconnect.json | 132 - .../arch/x86/jaketown/uncore-memory.json | 58 - .../pmu-events/arch/x86/jaketown/uncore-other.json | 155 +- .../pmu-events/arch/x86/jaketown/uncore-power.json | 51 - .../arch/x86/jaketown/virtual-memory.json | 32 - .../pmu-events/arch/x86/knightslanding/cache.json | 411 - .../arch/x86/knightslanding/floating-point.json | 3 - .../arch/x86/knightslanding/frontend.json | 7 - .../pmu-events/arch/x86/knightslanding/memory.json | 201 - .../arch/x86/knightslanding/pipeline.json | 44 - .../arch/x86/knightslanding/uncore-other.json | 1016 +- .../arch/x86/knightslanding/virtual-memory.json | 7 - tools/perf/pmu-events/arch/x86/mapfile.csv | 17 +- .../perf/pmu-events/arch/x86/meteorlake/cache.json | 170 +- .../pmu-events/arch/x86/meteorlake/frontend.json | 6 - .../pmu-events/arch/x86/meteorlake/memory.json | 77 +- .../perf/pmu-events/arch/x86/meteorlake/other.json | 24 +- .../pmu-events/arch/x86/meteorlake/pipeline.json | 222 +- .../arch/x86/meteorlake/virtual-memory.json | 28 +- .../perf/pmu-events/arch/x86/nehalemep/cache.json | 524 - .../arch/x86/nehalemep/floating-point.json | 28 - .../pmu-events/arch/x86/nehalemep/frontend.json | 3 - .../perf/pmu-events/arch/x86/nehalemep/memory.json | 134 - .../perf/pmu-events/arch/x86/nehalemep/other.json | 18 - .../pmu-events/arch/x86/nehalemep/pipeline.json | 127 +- .../arch/x86/nehalemep/virtual-memory.json | 13 - .../perf/pmu-events/arch/x86/nehalemex/cache.json | 519 - .../arch/x86/nehalemex/floating-point.json | 28 - .../pmu-events/arch/x86/nehalemex/frontend.json | 3 - .../perf/pmu-events/arch/x86/nehalemex/memory.json | 134 - .../perf/pmu-events/arch/x86/nehalemex/other.json | 18 - .../pmu-events/arch/x86/nehalemex/pipeline.json | 127 +- .../arch/x86/nehalemex/virtual-memory.json | 13 - .../pmu-events/arch/x86/sandybridge/cache.json | 441 - .../arch/x86/sandybridge/floating-point.json | 30 - .../pmu-events/arch/x86/sandybridge/frontend.json | 64 - .../pmu-events/arch/x86/sandybridge/memory.json | 108 - .../pmu-events/arch/x86/sandybridge/other.json | 12 - .../pmu-events/arch/x86/sandybridge/pipeline.json | 257 - .../arch/x86/sandybridge/snb-metrics.json | 83 +- .../arch/x86/sandybridge/uncore-cache.json | 50 - .../arch/x86/sandybridge/uncore-other.json | 28 +- .../arch/x86/sandybridge/virtual-memory.json | 32 - .../pmu-events/arch/x86/sapphirerapids/cache.json | 350 +- .../arch/x86/sapphirerapids/floating-point.json | 63 - .../arch/x86/sapphirerapids/frontend.json | 144 - .../pmu-events/arch/x86/sapphirerapids/memory.json | 125 +- .../pmu-events/arch/x86/sapphirerapids/other.json | 91 +- .../arch/x86/sapphirerapids/pipeline.json | 424 +- .../arch/x86/sapphirerapids/spr-metrics.json | 2309 +- .../arch/x86/sapphirerapids/uncore-memory.json | 526 +- .../arch/x86/sapphirerapids/uncore-other.json | 6606 ++- .../arch/x86/sapphirerapids/uncore-power.json | 84 +- .../arch/x86/sapphirerapids/virtual-memory.json | 80 - .../perf/pmu-events/arch/x86/silvermont/cache.json | 133 - .../arch/x86/silvermont/floating-point.json | 1 - .../pmu-events/arch/x86/silvermont/frontend.json | 8 - .../pmu-events/arch/x86/silvermont/memory.json | 1 - .../perf/pmu-events/arch/x86/silvermont/other.json | 2 - .../pmu-events/arch/x86/silvermont/pipeline.json | 35 - .../arch/x86/silvermont/virtual-memory.json | 7 - tools/perf/pmu-events/arch/x86/skylake/cache.json | 660 - .../arch/x86/skylake/floating-point.json | 14 - .../perf/pmu-events/arch/x86/skylake/frontend.json | 109 - tools/perf/pmu-events/arch/x86/skylake/memory.json | 358 - tools/perf/pmu-events/arch/x86/skylake/other.json | 4 - .../perf/pmu-events/arch/x86/skylake/pipeline.json | 192 - .../pmu-events/arch/x86/skylake/skl-metrics.json | 155 +- .../pmu-events/arch/x86/skylake/uncore-cache.json | 18 - .../pmu-events/arch/x86/skylake/uncore-other.json | 31 +- .../arch/x86/skylake/virtual-memory.json | 56 - tools/perf/pmu-events/arch/x86/skylakex/cache.json | 368 - .../arch/x86/skylakex/floating-point.json | 18 - .../pmu-events/arch/x86/skylakex/frontend.json | 109 - .../perf/pmu-events/arch/x86/skylakex/memory.json | 310 - tools/perf/pmu-events/arch/x86/skylakex/other.json | 30 - .../pmu-events/arch/x86/skylakex/pipeline.json | 194 - .../pmu-events/arch/x86/skylakex/skx-metrics.json | 2134 +- .../arch/x86/skylakex/uncore-memory.json | 2303 +- .../pmu-events/arch/x86/skylakex/uncore-other.json | 29356 ++++++------ .../pmu-events/arch/x86/skylakex/uncore-power.json | 45 +- .../arch/x86/skylakex/virtual-memory.json | 56 - .../perf/pmu-events/arch/x86/snowridgex/cache.json | 252 - .../arch/x86/snowridgex/floating-point.json | 11 - .../pmu-events/arch/x86/snowridgex/frontend.json | 36 - .../pmu-events/arch/x86/snowridgex/memory.json | 84 - .../perf/pmu-events/arch/x86/snowridgex/other.json | 143 - .../pmu-events/arch/x86/snowridgex/pipeline.json | 213 - .../arch/x86/snowridgex/uncore-memory.json | 624 +- .../arch/x86/snowridgex/uncore-other.json | 26334 +++++------ .../arch/x86/snowridgex/uncore-power.json | 114 +- .../arch/x86/snowridgex/virtual-memory.json | 117 - .../perf/pmu-events/arch/x86/tigerlake/cache.json | 210 +- .../arch/x86/tigerlake/floating-point.json | 27 - .../pmu-events/arch/x86/tigerlake/frontend.json | 125 - .../perf/pmu-events/arch/x86/tigerlake/memory.json | 77 - .../perf/pmu-events/arch/x86/tigerlake/other.json | 13 - .../pmu-events/arch/x86/tigerlake/pipeline.json | 287 +- .../pmu-events/arch/x86/tigerlake/tgl-metrics.json | 141 +- .../arch/x86/tigerlake/uncore-other.json | 96 +- .../arch/x86/tigerlake/virtual-memory.json | 60 - .../pmu-events/arch/x86/westmereep-dp/cache.json | 445 - .../arch/x86/westmereep-dp/floating-point.json | 28 - .../arch/x86/westmereep-dp/frontend.json | 3 - .../pmu-events/arch/x86/westmereep-dp/memory.json | 137 - .../pmu-events/arch/x86/westmereep-dp/other.json | 22 - .../arch/x86/westmereep-dp/pipeline.json | 129 +- .../arch/x86/westmereep-dp/virtual-memory.json | 21 - .../pmu-events/arch/x86/westmereep-sp/cache.json | 517 - .../arch/x86/westmereep-sp/floating-point.json | 28 - .../arch/x86/westmereep-sp/frontend.json | 3 - .../pmu-events/arch/x86/westmereep-sp/memory.json | 134 - .../pmu-events/arch/x86/westmereep-sp/other.json | 22 - .../arch/x86/westmereep-sp/pipeline.json | 129 +- .../arch/x86/westmereep-sp/virtual-memory.json | 18 - .../perf/pmu-events/arch/x86/westmereex/cache.json | 516 - .../arch/x86/westmereex/floating-point.json | 28 - .../pmu-events/arch/x86/westmereex/frontend.json | 3 - .../pmu-events/arch/x86/westmereex/memory.json | 135 - .../perf/pmu-events/arch/x86/westmereex/other.json | 22 - .../pmu-events/arch/x86/westmereex/pipeline.json | 129 +- .../arch/x86/westmereex/virtual-memory.json | 21 - tools/perf/tests/builtin-test.c | 2 +- tools/perf/tests/dlfilter-test.c | 2 +- tools/perf/tests/pmu-events.c | 17 +- tools/perf/tests/shell/lock_contention.sh | 58 +- tools/perf/tests/shell/stat_all_pmu.sh | 13 +- tools/perf/util/bpf_lock_contention.c | 57 +- tools/perf/util/bpf_skel/lock_contention.bpf.c | 38 +- tools/perf/util/debug.c | 4 + tools/perf/util/dlfilter.c | 2 +- tools/perf/util/hist.c | 10 +- tools/perf/util/hist.h | 1 + tools/perf/util/lock-contention.h | 10 + tools/perf/util/scripting-engines/Build | 2 +- tools/perf/util/setup.py | 13 +- tools/perf/util/sort.c | 129 +- tools/perf/util/sort.h | 1 + tools/perf/util/srcline.c | 20 +- tools/perf/util/symbol-elf.c | 28 + tools/perf/util/symbol-minimal.c | 5 + tools/perf/util/symbol.h | 1 + 335 files changed, 92282 insertions(+), 124781 deletions(-) create mode 100644 drivers/scsi/sd_trace.h create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/branch.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/cache.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/core.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/data-fabric.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/floating-point.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/memory.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/other.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/pipeline.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen4/recommended.json -- To stop receiving notification emails like this one, please contact the administrator of this repository.

2 years, 5 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022