Tcwg-commits December 2022

tcwg-commits@lists.linaro.org

5 participants
4659 discussions

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig updated (71ff7e40266a -> e09f1b71efa0)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-master-arm-mainline-defconfig in repository toolchain/ci/base-artifacts. from 71ff7e40266a 34: onsuccess: #475: boot: Success after binutils/gcc/linu [...] new e09f1b71efa0 35: onsuccess: #476: boot: Success after binutils/gcc/linu [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1768 -> 1752 bytes 02-prepare_abe/console.log.xz | Bin 2792 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 32076 -> 31740 bytes 04-build_abe-stage1/console.log.xz | Bin 93128 -> 91484 bytes 05-build_abe-qemu/console.log.xz | Bin 30664 -> 31144 bytes 06-build_linux/console.log.xz | Bin 6008 -> 5984 bytes 07-boot_linux/console.log.xz | Bin 5704 -> 5628 bytes 08-check_regression/console.log.xz | Bin 4200 -> 4236 bytes 08-check_regression/mail-body.txt | 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 | 10 +++++++--- mail/mail-subject.txt | 2 +- manifest.sh | 30 +++++++++++++++--------------- results | 2 +- 19 files changed, 36 insertions(+), 28 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (17b41a28396 -> 97a8e88cd7d)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 17b41a28396 gcc-changelog: stop using --flake8 new 97a8e88cd7d rs6000: use li;x?oris to build constant The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/rs6000/rs6000.cc | 37 +++++++++++++++++++++----- gcc/testsuite/gcc.target/powerpc/pr106708.c | 41 +++++++++++++++++++++++++++++ 2 files changed, 72 insertions(+), 6 deletions(-) create mode 100644 gcc/testsuite/gcc.target/powerpc/pr106708.c -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (88b531d0323 -> 17b41a28396)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from 88b531d0323 x86: Don't add crtfastmath.o for -shared new 17b41a28396 gcc-changelog: stop using --flake8 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: contrib/gcc-changelog/setup.cfg | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-arm updated (5557f247eb97 -> 3cebb7841342)

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 5557f247eb97 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc [...] discards 4b5cefa70a16 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4a [...] discards 038b7f4d1648 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: [...] discards 3e6393b097de 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: [...] discards 6467ce48a675 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/q [...] discards efaab75833df 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits discards 4a95784e3b50 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: [...] discards 7937255f7687 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/q [...] discards 33ab0b0d8a24 259: onsuccess: #1988: 7: Success after binutils/gcc/linux [...] discards 8113c2bef0ff 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/q [...] discards de4c4189c6b0 257: onsuccess: #1986: 7: Success after binutils/gcc/linux [...] discards 65c174bfdbae 256: onsuccess: #1985: 7: Success after binutils/gcc/linux [...] discards b9eeab9ef306 255: onsuccess: #1984: 7: Success after binutils/gcc/linux [...] discards 240ee70347cd 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/q [...] discards 85fc8ef06090 253: onsuccess: #1982: 7: Success after basepoints/gcc-13- [...] discards 6eb52d64ac0e 252: onsuccess: #1981: 7: Success after binutils/gcc/linux [...] discards c7c20037b7c6 251: onsuccess: #1980: 7: Success after binutils/gcc/linux [...] discards 9b4bd66e759a 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: [...] discards 8a855c57de0f 249: onsuccess: #1978: 7: Success after binutils/gcc/linux [...] discards b0522108c3c2 248: onsuccess: #1977: 7: Success after binutils/gcc/linux [...] discards a90ea6fb29a2 247: onsuccess: #1976: 7: Success after binutils/gcc/linux [...] discards c268609915c9 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: [...] discards 0c3119c69577 245: onsuccess: #1974: 7: Success after binutils/linux/gdb [...] discards b19240bc82e6 244: onsuccess: #1973: 7: Success after binutils/gcc/linux [...] discards 649ef5008b18 243: onsuccess: #1972: 7: Success after binutils/gcc/linux [...] discards 85665034f2d4 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc [...] discards cf2a90a3ed3a 241: onsuccess: #1970: 7: Success after binutils/gcc/linux [...] discards 8cc1d16e69e3 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits discards 9c66dd7f9b60 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: [...] discards dd5794231cb0 238: onsuccess: #1967: 7: Success after binutils/gcc/linux [...] discards 2d3d6f485e3e 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits discards cb662b855753 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: [...] discards 0ca50b2d2f80 235: onsuccess: #1964: 7: Success after binutils/linux/gli [...] discards 07c2275f5f82 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: [...] discards b6cf201c8971 233: onsuccess: #1962: 7: Success after gcc: 6 commits discards a57996afeabc 232: onsuccess: #1961: 7: Success after binutils/gcc/linux [...] discards 7137d4acb50b 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc [...] discards 2797cbeaca07 230: onsuccess: #1958: 7: Success after binutils/gcc/linux [...] discards 3671dc83a197 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc [...] discards 90d2c28da22d 228: onsuccess: #1956: 7: Success after gcc: 5 commits discards dc252d6263cd 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits discards 92d28a923ec3 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc [...] discards 6fa89293f2b2 225: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] discards f5473dc9a20f 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/q [...] discards 392d2cbb4511 223: onsuccess: #1951: 3: Success after binutils/gcc/linux [...] discards 8797772c92a0 222: onsuccess: #1950: 3: Success after basepoints/gcc-13- [...] discards be124727383b 221: force: #1949: 3: Failure after basepoints/gcc-13-4492 [...] discards 3815296a0e7b 220: force: #1948: 5: Success after gcc: 4 commits discards 8122c71c8525 219: onsuccess: #1945: 5: Success after binutils: 8 commits discards 8d291451a4fa 218: onsuccess: #1943: 5: Success after gdb: 3 commits discards b10eac773fe6 217: force: #1942: 5: Failure after gdb-12-branchpoint-294 [...] discards 908965a34719 216: onsuccess: #1940: 7: Success after linux: 12 commits discards bfa4ce63dda3 215: onsuccess: #1938: 7: Success after gcc: 4 commits discards 812c35752dcf 214: onsuccess: #1937: 7: Success after binutils: 4 commits discards 1005a17ecfb1 213: onsuccess: #1935: 7: Success after gcc: 2 commits discards 9544ae628dcb 212: onsuccess: #1934: 7: Success after gcc: 3 commits discards 10da0a4018d8 211: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] discards d3e00a705bf3 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: [...] discards b016523f8f12 209: onsuccess: #1931: 7: Success after binutils/gcc/linux [...] discards 2458f5b7ce8d 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits discards 0b3f0b01fc8f 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: [...] discards a0319befd027 206: onsuccess: #1927: 7: Success after binutils/gcc/linux [...] discards 62481084913a 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: [...] discards 62fd2ec8d5a2 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: [...] discards 9d4404bbc6d8 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: [...] discards 2a05e9fdfd9d 202: onsuccess: #1923: 7: Success after binutils/gcc/linux [...] discards 6920a58070dc 201: onsuccess: #1905: 7: Success after binutils/gcc/linux [...] discards 20a9fc5df1d1 200: onsuccess: #1899: 7: Success after binutils/gcc/linux [...] discards f150d6f0b2f3 199: onsuccess: #1881: 7: Success after binutils/gcc/linux [...] discards 4199eb984b3c 198: onsuccess: #1878: 7: Success after binutils/gcc/linux [...] discards a49f6b09cd0d 197: onsuccess: #1856: 4: Success after binutils/gcc/linux [...] discards 38b07f98bae7 196: onsuccess: #1855: 4: Success after gcc: 30 commits discards f8576285ed5e 195: force: #1854: 4: Failure after basepoints/gcc-13-3918 [...] discards 9c698a094ce8 194: force: #1853: 7: Success after gcc: 26 commits discards 0ea705e4b4de 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint [...] discards c18b65c6480f 192: onsuccess: #1848: 7: Success after linux: 213 commits discards 9d58bdbca999 191: onsuccess: #1846: 7: Success after binutils: 4 commits discards e09c6b1ece51 190: onsuccess: #1834: 7: Success after binutils: 25 commits discards 4789cc516407 189: onsuccess: #1829: 7: Success after binutils/gcc/linux [...] discards 93fab1e40a1a 188: onsuccess: #1827: 7: Success after binutils/gcc/linux [...] discards 27d0a9f1021d 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc [...] discards dc1174523200 186: onsuccess: #1825: 7: Success after binutils/gcc/linux [...] discards a365be38ea88 185: onsuccess: #1815: 7: Success after binutils/gcc/linux [...] discards 2110b40e6887 184: onsuccess: #1777: 7: Success after binutils/gcc/linux [...] discards 4b0f815184cb 183: onsuccess: #1776: 7: Success after binutils/gcc/linux [...] discards d11ed99aa3f5 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: [...] discards e314d038bea1 181: onsuccess: #1773: 7: Success after binutils/gcc/linux [...] discards fc95f7d17229 180: onsuccess: #1724: 7: Success after binutils/gcc/linux [...] discards 8e26ed68f7e8 179: onsuccess: #1696: 7: Success after binutils/gcc/linux [...] discards 4758d8cf9ccc 178: onsuccess: #1694: 7: Success after binutils/gcc/linux [...] discards 99b5b68b8815 177: onsuccess: #1692: 7: Success after binutils/gcc/linux [...] discards 2b3f9f96f467 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc [...] discards e372964d440f 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: [...] discards 136848538f84 174: onsuccess: #1689: 7: Success after binutils/gcc/linux [...] discards 13fec55629de 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qe [...] discards 649bb4d171a8 172: onsuccess: #1687: 7: Success after gcc: 11 commits discards fcc6d3a5b67c 171: onsuccess: #1686: 7: Success after binutils/gcc/linux [...] discards 3ad0e0976489 170: onsuccess: #1685: 7: Success after binutils/gcc/linux [...] discards 7e16d89a97e1 169: onsuccess: #1684: 7: Success after binutils/gcc/linux [...] discards 5c2b7908062c 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: [...] discards 3295d06b5c81 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new 5defc5a3336d 167: onsuccess: #1682: 7: Success after gcc/linux: 119 commits new f70b284f28b6 168: onsuccess: #1683: 7: Success after binutils/gcc/gdb: [...] new f46798d37311 169: onsuccess: #1684: 7: Success after binutils/gcc/linux [...] new a06d576ca365 170: onsuccess: #1685: 7: Success after binutils/gcc/linux [...] new 010381788edc 171: onsuccess: #1686: 7: Success after binutils/gcc/linux [...] new f6c67ab428ef 172: onsuccess: #1687: 7: Success after gcc: 11 commits new 38419c24fc10 173: onsuccess: #1688: 7: Success after gcc/linux/glibc/qe [...] new 53c6f16e936c 174: onsuccess: #1689: 7: Success after binutils/gcc/linux [...] new 410be6332358 175: onsuccess: #1690: 7: Success after binutils/gcc/gdb: [...] new 42c454d2af4b 176: onsuccess: #1691: 7: Success after binutils/gcc/glibc [...] new 2932310536bc 177: onsuccess: #1692: 7: Success after binutils/gcc/linux [...] new 7261d3df02fe 178: onsuccess: #1694: 7: Success after binutils/gcc/linux [...] new 11707f2ca06a 179: onsuccess: #1696: 7: Success after binutils/gcc/linux [...] new 8427765fa697 180: onsuccess: #1724: 7: Success after binutils/gcc/linux [...] new 06138d94d75d 181: onsuccess: #1773: 7: Success after binutils/gcc/linux [...] new 76bd06df9294 182: onsuccess: #1774: 7: Success after binutils/gcc/gdb: [...] new 01a286625217 183: onsuccess: #1776: 7: Success after binutils/gcc/linux [...] new d38558cf00c5 184: onsuccess: #1777: 7: Success after binutils/gcc/linux [...] new 0c8dcfaaabf6 185: onsuccess: #1815: 7: Success after binutils/gcc/linux [...] new 9df13ea49aef 186: onsuccess: #1825: 7: Success after binutils/gcc/linux [...] new f488e8a94217 187: onsuccess: #1826: 7: Success after binutils/gcc/glibc [...] new dfb6e4a7e7de 188: onsuccess: #1827: 7: Success after binutils/gcc/linux [...] new 55b9a39ba846 189: onsuccess: #1829: 7: Success after binutils/gcc/linux [...] new f23562d6b939 190: onsuccess: #1834: 7: Success after binutils: 25 commits new 88293f138e6d 191: onsuccess: #1846: 7: Success after binutils: 4 commits new ff7992bafd6f 192: onsuccess: #1848: 7: Success after linux: 213 commits new 1e63c6c338d7 193: onsuccess: #1850: 7: Success after gdb-12-branchpoint [...] new 859da30b212f 194: force: #1853: 7: Success after gcc: 26 commits new 69dc2f0161f0 195: force: #1854: 4: Failure after basepoints/gcc-13-3918 [...] new 21add2acc1c9 196: onsuccess: #1855: 4: Success after gcc: 30 commits new a95b833d4629 197: onsuccess: #1856: 4: Success after binutils/gcc/linux [...] new 9a1071ffed85 198: onsuccess: #1878: 7: Success after binutils/gcc/linux [...] new 6bab3a7757e6 199: onsuccess: #1881: 7: Success after binutils/gcc/linux [...] new a561f87b4509 200: onsuccess: #1899: 7: Success after binutils/gcc/linux [...] new 1836365f6872 201: onsuccess: #1905: 7: Success after binutils/gcc/linux [...] new 0dce1ef6ead6 202: onsuccess: #1923: 7: Success after binutils/gcc/linux [...] new 3948fb7520f5 203: onsuccess: #1924: 7: Success after binutils/gcc/gdb: [...] new 7125958afbe1 204: onsuccess: #1925: 7: Success after binutils/gcc/gdb: [...] new 6507324fd3cc 205: onsuccess: #1926: 7: Success after binutils/gcc/gdb: [...] new fad5bfd3c2a9 206: onsuccess: #1927: 7: Success after binutils/gcc/linux [...] new 034c92398ef0 207: onsuccess: #1929: 7: Success after binutils/gcc/gdb: [...] new ba21f2272725 208: onsuccess: #1930: 7: Success after gcc/glibc: 5 commits new 89dca278f729 209: onsuccess: #1931: 7: Success after binutils/gcc/linux [...] new a4da30ff8819 210: onsuccess: #1932: 7: Success after binutils/gcc/gdb: [...] new 038701af5abe 211: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] new 2742e79e66b5 212: onsuccess: #1934: 7: Success after gcc: 3 commits new 25f81a2b8a7d 213: onsuccess: #1935: 7: Success after gcc: 2 commits new b2985d311293 214: onsuccess: #1937: 7: Success after binutils: 4 commits new db703f0196a9 215: onsuccess: #1938: 7: Success after gcc: 4 commits new 4e007f6e99df 216: onsuccess: #1940: 7: Success after linux: 12 commits new d217a9ebee63 217: force: #1942: 5: Failure after gdb-12-branchpoint-294 [...] new 9c51d8d5a543 218: onsuccess: #1943: 5: Success after gdb: 3 commits new f987c95fd52d 219: onsuccess: #1945: 5: Success after binutils: 8 commits new 26ce939b251c 220: force: #1948: 5: Success after gcc: 4 commits new 09edbf404097 221: force: #1949: 3: Failure after basepoints/gcc-13-4492 [...] new 26563014d1da 222: onsuccess: #1950: 3: Success after basepoints/gcc-13- [...] new 58dd55e00c6e 223: onsuccess: #1951: 3: Success after binutils/gcc/linux [...] new 2618fa1294e3 224: onsuccess: #1952: 7: Success after binutils/gcc/gdb/q [...] new d158e42041d8 225: onsuccess: #1953: 7: Success after binutils/gcc/linux [...] new 3fee71fc208a 226: onsuccess: #1954: 7: Success after binutils/gcc/glibc [...] new d8c2633b1167 227: onsuccess: #1955: 7: Success after binutils/gdb: 10 commits new 79300126a745 228: onsuccess: #1956: 7: Success after gcc: 5 commits new b381be29d942 229: onsuccess: #1957: 7: Success after binutils/gcc/glibc [...] new 0848dd89810f 230: onsuccess: #1958: 7: Success after binutils/gcc/linux [...] new a44af139d63d 231: onsuccess: #1960: 7: Success after binutils/gcc/glibc [...] new db5ee3744bd0 232: onsuccess: #1961: 7: Success after binutils/gcc/linux [...] new 496469919648 233: onsuccess: #1962: 7: Success after gcc: 6 commits new 05edbef4602b 234: onsuccess: #1963: 7: Success after binutils/gcc/gdb: [...] new 91dc92bb3273 235: onsuccess: #1964: 7: Success after binutils/linux/gli [...] new 90469de9ccba 236: onsuccess: #1965: 7: Success after binutils/gcc/gdb: [...] new 5be8135eee6c 237: onsuccess: #1966: 7: Success after gcc/linux: 3 commits new bd4ef6e335d6 238: onsuccess: #1967: 7: Success after binutils/gcc/linux [...] new 4ec03c4ab3f4 239: onsuccess: #1968: 7: Success after binutils/gcc/gdb: [...] new 299b0f5c4ba6 240: onsuccess: #1969: 7: Success after gcc/linux: 9 commits new 114598571bc2 241: onsuccess: #1970: 7: Success after binutils/gcc/linux [...] new e837c09a39c0 242: onsuccess: #1971: 7: Success after binutils/gcc/glibc [...] new b81dcaf3546d 243: onsuccess: #1972: 7: Success after binutils/gcc/linux [...] new 43c87e14b5a2 244: onsuccess: #1973: 7: Success after binutils/gcc/linux [...] new ab9be907887b 245: onsuccess: #1974: 7: Success after binutils/linux/gdb [...] new 40e3579af4b5 246: onsuccess: #1975: 7: Success after binutils/gcc/gdb: [...] new 3ceb7e0637c0 247: onsuccess: #1976: 7: Success after binutils/gcc/linux [...] new 01d71bbca994 248: onsuccess: #1977: 7: Success after binutils/gcc/linux [...] new 772dda66639b 249: onsuccess: #1978: 7: Success after binutils/gcc/linux [...] new de8bc490e999 250: onsuccess: #1979: 7: Success after binutils/gcc/gdb: [...] new b4846c9877d4 251: onsuccess: #1980: 7: Success after binutils/gcc/linux [...] new 0c573239b8c9 252: onsuccess: #1981: 7: Success after binutils/gcc/linux [...] new b1296c42b71c 253: onsuccess: #1982: 7: Success after basepoints/gcc-13- [...] new be8b25508453 254: onsuccess: #1983: 7: Success after binutils/gcc/gdb/q [...] new ff903950effb 255: onsuccess: #1984: 7: Success after binutils/gcc/linux [...] new 59e5505faf73 256: onsuccess: #1985: 7: Success after binutils/gcc/linux [...] new fb4adab964d2 257: onsuccess: #1986: 7: Success after binutils/gcc/linux [...] new e4345b8cf7fc 258: onsuccess: #1987: 7: Success after binutils/gcc/gdb/q [...] new b9d3912409a8 259: onsuccess: #1988: 7: Success after binutils/gcc/linux [...] new 6c07df78724e 260: onsuccess: #1989: 7: Success after binutils/gcc/gdb/q [...] new 92e55569a16b 261: onsuccess: #1990: 7: Success after binutils/gcc/gdb: [...] new cdf6bfa88e99 262: onsuccess: #1991: 7: Success after gcc/linux: 109 commits new 3ac07da3d111 263: onsuccess: #1992: 7: Success after binutils/gcc/gdb/q [...] new 77290f553cfc 264: onsuccess: #1993: 7: Success after binutils/gcc/gdb: [...] new bb72111e7e52 265: onsuccess: #1994: 7: Success after binutils/gcc/gdb: [...] new f38d96d73a81 266: onsuccess: #1995: 7: Success after v7.2.0-211-g562d4a [...] new b57821a341e7 267: onsuccess: #1996: 7: Success after binutils/gcc/glibc [...] new 3cebb7841342 268: onsuccess: #1997: 7: Success after glibc: 2 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 (5557f247eb97) \ 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 1792 -> 1748 bytes 02-prepare_abe/console.log.xz | Bin 2800 -> 2808 bytes 04-build_abe-binutils/console.log.xz | Bin 32372 -> 32200 bytes 05-build_abe-stage1/console.log.xz | Bin 92628 -> 92788 bytes 07-build_abe-linux/console.log.xz | Bin 8648 -> 8776 bytes 08-build_abe-glibc/console.log.xz | Bin 235748 -> 236720 bytes 09-build_abe-stage2/console.log.xz | Bin 226184 -> 227832 bytes 10-build_abe-gdb/console.log.xz | Bin 39008 -> 39384 bytes 11-build_abe-qemu/console.log.xz | Bin 30912 -> 31004 bytes 12-check_regression/console.log.xz | Bin 3708 -> 3360 bytes 13-update_baseline/console.log | 52 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++++-------- 17 files changed, 43 insertions(+), 43 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-allnoconfig updated (f51cc56533f6 -> bd94c69e9f73)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_kernel/gnu-release-arm-stable-allnoconfig in repository toolchain/ci/base-artifacts. from f51cc56533f6 28: onsuccess: #375: all: Success after binutils/gcc/linux [...] new bd94c69e9f73 29: onsuccess: #376: all: Success after binutils/gcc/qemu: [...] The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1740 -> 1788 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2808 bytes 03-build_abe-binutils/console.log.xz | Bin 30060 -> 30724 bytes 04-build_abe-stage1/console.log.xz | Bin 86500 -> 87948 bytes 05-build_abe-qemu/console.log.xz | Bin 30976 -> 31192 bytes 06-build_linux/console.log.xz | Bin 3324 -> 3352 bytes 07-boot_linux/console.log.xz | Bin 496 -> 496 bytes 08-check_regression/console.log.xz | Bin 3832 -> 3756 bytes dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++++++++------------- 16 files changed, 20 insertions(+), 20 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[gcc] branch master updated (e4337398620 -> 88b531d0323)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository gcc. from e4337398620 RISC-V: Fix RVV related testsuite new 88b531d0323 x86: Don't add crtfastmath.o for -shared The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: gcc/config/i386/gnu-user-common.h | 2 +- gcc/doc/invoke.texi | 3 ++- 2 files changed, 3 insertions(+), 2 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (ecb828308c8 -> b1fb5034045)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from ecb828308c8 gprofng/testsuite: adjust linking of synprog new 6cafa878248 gprofng/testsuite: correct names for signal handling tests new 08b50e1e03b gprofng/testsuite: correct line continuation in endcases.c new f8b6a781fb6 gprofng/testsuite: eliminate bogus casts new b1fb5034045 gprofng/testsuite: skip Java test without JDK The 4 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: gprofng/Makefile.am | 1 + gprofng/Makefile.in | 1 + gprofng/testsuite/gprofng.display/display.exp | 4 +++- gprofng/testsuite/gprofng.display/synprog/endcases.c | 2 +- gprofng/testsuite/gprofng.display/synprog/so_syn.c | 2 +- gprofng/testsuite/gprofng.display/synprog/so_syx.c | 2 +- gprofng/testsuite/gprofng.display/synprog/synprog.c | 4 ++-- 7 files changed, 10 insertions(+), 6 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm updated (be13f2aa9866 -> 2a10bca4282a)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts. discards be13f2aa9866 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] discards b9be8c349c3a 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] discards a5c0d7a1f067 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] discards 034998545881 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] discards 54148bc5dc09 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] discards 441728d6c4a0 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits discards a181683218b7 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits discards 535dd3558404 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] discards d8de88511f07 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] discards c351a9120130 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] discards 5f2a6aac5106 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] discards 025a6e8a015d 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] discards 2fe9ec9b2cb5 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] discards b673af039494 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] discards 955f7d139512 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] discards 942f774c4937 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] discards ab473055725b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] discards bea06e2d4b23 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] discards e4338b3d9e7d 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] discards e2696a342886 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] discards b2de80d90a01 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] discards 7bee930dfb5f 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] discards 469b052efee7 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] discards 9355ec31a89c 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] discards b0f4bd4ec988 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] discards 6174f58f4a8b 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] discards 3ee454a94467 232: onsuccess: #2048: 1: Success after glibc: 2 commits discards 7a9a36c3e0cd 231: onsuccess: #2047: 1: Success after gcc: 4 commits discards 6c7cb4c1ad3a 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] discards 154bf4888b9e 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] discards 36155c1568d5 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] discards 8ec1bea3978a 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] discards 967b33037cf3 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] discards 99c8883710f7 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] discards a6c61694ae4b 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] discards 74eaa9fee734 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] discards 3927f6efd055 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] discards eda2be0082fe 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits discards 7c0daa3fd839 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] discards fe4adff0130c 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] discards 82d58a9f9269 218: onsuccess: #2030: 1: Success after gcc: 5 commits discards 4519c9e75bb1 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] discards 9a899d7e031b 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] discards bcb21ad975f7 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] discards 5c21db3b32ca 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] discards 4f435973c7f0 213: onsuccess: #2024: 1: Success after binutils: 3 commits discards 7fcd2d386df6 212: onsuccess: #2022: 1: Success after linux: 3 commits discards a5cf8801b151 211: onsuccess: #2020: 1: Success after binutils: 10 commits discards 0c200bd26576 210: onsuccess: #2017: 1: Success after binutils: 6 commits discards f9ed18389a03 209: onsuccess: #2014: 1: Success after binutils: 12 commits discards 415d902750e3 208: onsuccess: #2012: 1: Success after linux: 12 commits discards 5e7f83ddc8fa 207: onsuccess: #2010: 1: Success after gcc: 4 commits discards 01cf95ca6db1 206: onsuccess: #2007: 1: Success after gcc: 2 commits discards 0e9217761a76 205: onsuccess: #2006: 1: Success after gcc: 3 commits discards ef3d72fc08e5 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] discards cfc8df138a01 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] discards ee0e1972d736 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] discards 24182b270edb 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits discards 1f9249ef7bf5 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] discards 96a99b9e88db 199: onsuccess: #2000: 1: Success after gcc: 5 commits discards f423f96db3f0 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] discards 857767816d7b 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] discards 4374d6db0d9c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] discards 8aee78f25145 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] discards 68b463337535 194: onsuccess: #1995: 1: Success after linux: 517 commits discards c75f6526e644 193: onsuccess: #1992: 1: Success after binutils: 151 commits discards 17e162ccb739 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] discards ab3261a100ce 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] discards 751aee728426 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] discards 1c66d5483cda 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] discards dfca55204459 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] discards 58e7978b4fec 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] discards 8997dd64a562 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] discards 7a6e49197988 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] discards f2d684f883b9 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] discards 48d81d659860 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] discards a54962c26825 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] discards a4525588ff3d 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] discards 4d95e1873cb6 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] discards c760ee2f1ee0 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] discards 1f03eebaa63a 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] discards 8e0b461d611d 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] discards e52ff5a40d9c 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] discards f85d51b7be04 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] discards 74a2f38afb8a 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] discards c4d6fcd741a6 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] discards 2bb7da1713d6 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] discards 70ac5c540f8d 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] discards 1b85a6d3401e 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] discards 07f95f11629a 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] discards 87aeb29cfbb4 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] discards 2f30cd7952f5 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] discards 3bcd2ddd2168 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] discards 782b0a861c57 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] discards 557aed00de7d 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] discards 8fe70621c913 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits discards f1caab26f946 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] discards fce60882ba06 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] discards 087e521abf37 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] discards 949297093f44 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] discards 13f8efdce9c3 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new a9dd4ed84202 158: onsuccess: #1759: 1: Success after binutils/gcc/linux [...] new 50abdef8b610 159: onsuccess: #1760: 1: Success after binutils/gcc/gdb: [...] new 925598e5b0cc 160: onsuccess: #1761: 1: Success after binutils/gcc/gdb: [...] new 89c88611a776 161: onsuccess: #1762: 1: Success after binutils/gcc/linux [...] new a0b775abee50 162: onsuccess: #1763: 1: Success after binutils/gcc/linux [...] new 661e9550128d 163: onsuccess: #1764: 1: Success after gcc/linux: 141 commits new 56806be7fadf 164: onsuccess: #1765: 1: Success after binutils/gcc/gdb: [...] new d5d3a583cdc5 165: onsuccess: #1766: 1: Success after binutils/gcc/linux [...] new ec2eca1db91a 166: onsuccess: #1767: 1: Success after binutils/gcc/linux [...] new 2432845cf3a9 167: onsuccess: #1768: 1: Success after binutils/gcc/linux [...] new 7750bc557dde 168: onsuccess: #1769: 1: Success after binutils/gcc/gdb: [...] new ccff34bc4113 169: onsuccess: #1770: 1: Success after gcc/linux/glibc/qe [...] new 1c245d26aef9 170: onsuccess: #1771: 1: Success after binutils/gcc/linux [...] new b36a51a7be75 171: onsuccess: #1772: 1: Success after binutils/gcc/gdb: [...] new d9e1e5cd602c 172: onsuccess: #1773: 1: Success after binutils/gcc/glibc [...] new 59ea962a99ac 173: onsuccess: #1774: 1: Success after binutils/gcc/glibc [...] new 0343a68be702 174: onsuccess: #1775: 1: Success after binutils/gcc/linux [...] new 9ca968367ac6 175: onsuccess: #1776: 1: Success after binutils/gcc/linux [...] new 4203b64349c6 176: onsuccess: #1791: 1: Success after binutils/gcc/linux [...] new 46a3b73a0b25 177: onsuccess: #1793: 1: Success after binutils/gcc/linux [...] new 1ee287007077 178: onsuccess: #1799: 1: Success after binutils/gcc/linux [...] new 811d9781bcdc 179: onsuccess: #1810: 1: Success after binutils/gcc/linux [...] new a5327f367c51 180: onsuccess: #1831: 1: Success after binutils/gcc/linux [...] new cee563e223bd 181: onsuccess: #1857: 1: Success after binutils/gcc/linux [...] new b78301c6089b 182: onsuccess: #1860: 1: Success after binutils/gcc/linux [...] new e1638bd62ec9 183: onsuccess: #1897: 1: Success after binutils/gcc/linux [...] new 0fd180ac307c 184: onsuccess: #1898: 1: Success after binutils/gcc/gdb: [...] new 9155d2e68441 185: onsuccess: #1906: 1: Success after binutils/gcc/linux [...] new d519e36770cc 186: onsuccess: #1907: 1: Success after binutils/gcc/gdb: [...] new 2da90d2cbbb6 187: onsuccess: #1908: 1: Success after binutils/gcc/linux [...] new 257e6318f309 188: onsuccess: #1909: 1: Success after binutils/gcc/gdb: [...] new 2ed4e3d6d383 189: onsuccess: #1912: 1: Success after binutils/gcc/linux [...] new ad12d701423b 190: onsuccess: #1913: 1: Success after binutils/gcc/linux [...] new a398ecaf17fc 191: onsuccess: #1949: 1: Success after binutils/gcc/linux [...] new 0f963bec040f 192: onsuccess: #1951: 1: Success after binutils/gcc/gdb: [...] new 3406e032c13e 193: onsuccess: #1992: 1: Success after binutils: 151 commits new 55003b2a4b24 194: onsuccess: #1995: 1: Success after linux: 517 commits new c44dbf542d76 195: onsuccess: #1996: 1: Success after binutils/gcc/glibc [...] new abab124cba0c 196: onsuccess: #1997: 1: Success after binutils/gcc/gdb: [...] new b94750a92a1c 197: onsuccess: #1998: 1: Success after binutils/gcc/gdb: [...] new 08f8eeb843d8 198: onsuccess: #1999: 1: Success after binutils/gcc/linux [...] new 98d176fea4d8 199: onsuccess: #2000: 1: Success after gcc: 5 commits new e7f1a35e112c 200: onsuccess: #2001: 1: Success after binutils/gcc/gdb: [...] new d9f21da9bf83 201: onsuccess: #2002: 1: Success after gcc/glibc: 5 commits new a2f7fbd65375 202: onsuccess: #2003: 1: Success after binutils/gcc/linux [...] new cd9faffc05e1 203: onsuccess: #2004: 1: Success after binutils/gcc/gdb: [...] new 9701d4e6cb74 204: onsuccess: #2005: 1: Success after binutils/gcc/linux [...] new 357683dea84a 205: onsuccess: #2006: 1: Success after gcc: 3 commits new ae951f1ffe1b 206: onsuccess: #2007: 1: Success after gcc: 2 commits new 2d9fd9e35281 207: onsuccess: #2010: 1: Success after gcc: 4 commits new d4ec44fc8cfc 208: onsuccess: #2012: 1: Success after linux: 12 commits new b6d91da0d94f 209: onsuccess: #2014: 1: Success after binutils: 12 commits new 019c44871c8b 210: onsuccess: #2017: 1: Success after binutils: 6 commits new 4f923f59f79a 211: onsuccess: #2020: 1: Success after binutils: 10 commits new 7bef72682981 212: onsuccess: #2022: 1: Success after linux: 3 commits new 1647f309a47d 213: onsuccess: #2024: 1: Success after binutils: 3 commits new 1fd6eb87ff19 214: onsuccess: #2026: 1: Success after binutils/gcc/gdb/q [...] new ac3fbc0d92a8 215: onsuccess: #2027: 1: Success after binutils/gcc/glibc [...] new 560dd825c6ab 216: onsuccess: #2028: 1: Success after binutils/gcc/linux [...] new f0b498d9f57f 217: onsuccess: #2029: 1: Success after binutils/gcc/glibc [...] new 1939bff4e140 218: onsuccess: #2030: 1: Success after gcc: 5 commits new 4f864f668bbf 219: onsuccess: #2031: 1: Success after binutils/gcc/glibc [...] new 256e0ec25c60 220: onsuccess: #2032: 1: Success after binutils/gcc/linux [...] new fb3e66a31bd5 221: onsuccess: #2033: 1: Success after binutils/gdb: 2 commits new 637d5bb1f8c3 222: onsuccess: #2035: 1: Success after binutils/gcc/glibc [...] new 4a8dd1ca247c 223: onsuccess: #2036: 1: Success after binutils/gcc/linux [...] new b13697bed9c6 224: onsuccess: #2038: 1: Success after binutils/gcc/linux [...] new 01915941f1c4 225: onsuccess: #2039: 1: Success after binutils/linux/gli [...] new 7edd4b6f7747 226: onsuccess: #2040: 1: Success after binutils/gcc/gdb: [...] new 4bf2e0a29324 227: onsuccess: #2041: 1: Success after binutils/gcc/linux [...] new 752eebce39df 228: onsuccess: #2042: 1: Success after basepoints/gcc-13- [...] new 3480cfc75117 229: onsuccess: #2043: 1: Success after binutils/gcc/linux [...] new cdacd23979a8 230: onsuccess: #2044: 1: Success after binutils/gcc/linux [...] new 1e9bf349a003 231: onsuccess: #2047: 1: Success after gcc: 4 commits new 73fc28cbb871 232: onsuccess: #2048: 1: Success after glibc: 2 commits new 7c745c8d7e17 233: onsuccess: #2049: 1: Success after binutils/gcc/linux [...] new 93ed29067ca1 234: onsuccess: #2050: 1: Success after binutils/gcc/linux [...] new db244503737a 235: onsuccess: #2051: 1: Success after binutils/linux/gdb [...] new 5358f667dbff 236: onsuccess: #2052: 1: Success after binutils/gcc/gdb: [...] new c557435935af 237: onsuccess: #2053: 1: Success after binutils/gcc/linux [...] new 874c93321800 238: onsuccess: #2054: 1: Success after binutils/gcc/linux [...] new 7e37f47033f8 239: onsuccess: #2055: 1: Success after binutils/gcc/linux [...] new bd8e8d8cb1b6 240: onsuccess: #2056: 1: Success after binutils/gcc/gdb: [...] new 9d75e0ae3f74 241: onsuccess: #2057: 1: Success after binutils/gcc/linux [...] new a722e288d49b 242: onsuccess: #2058: 1: Success after binutils/gcc/linux [...] new ab8c7df5b724 243: onsuccess: #2059: 1: Success after basepoints/gcc-13- [...] new 856e94fe7779 244: onsuccess: #2060: 1: Success after binutils/gcc/gdb/q [...] new b04173afbefb 245: onsuccess: #2061: 1: Success after binutils/gcc/linux [...] new 3e6133dedcde 246: onsuccess: #2062: 1: Success after binutils/gcc/linux [...] new 4c887918c58f 247: onsuccess: #2063: 1: Success after binutils/gcc/linux [...] new 5f6afb469207 248: onsuccess: #2064: 1: Success after binutils/gcc/gdb/q [...] new b856c117c280 249: onsuccess: #2065: 1: Success after binutils/gcc/linux [...] new e72adad598ad 250: onsuccess: #2066: 1: Success after binutils/gcc/linux [...] new 9eea6e775e2a 251: onsuccess: #2067: 1: Success after binutils/gcc/gdb: [...] new 490b35b0e014 252: onsuccess: #2068: 1: Success after binutils/gdb: 6 commits new 375c696b9f02 253: onsuccess: #2069: 1: Success after gcc/linux: 109 commits new 92f5218f843c 254: onsuccess: #2070: 1: Success after binutils/gcc/gdb/q [...] new cfd6ecccf7c6 255: onsuccess: #2071: 1: Success after binutils/gcc/gdb: [...] new 949058c360f4 256: onsuccess: #2072: 1: Success after binutils/gcc/gdb: [...] new 0454463ba832 257: onsuccess: #2073: 1: Success after v7.2.0-211-g562d4a [...] new 45de8557f27f 258: onsuccess: #2074: 1: Success after binutils/gcc/glibc [...] new 2a10bca4282a 259: onsuccess: #2075: 1: Success after glibc: 2 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 (be13f2aa9866) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...] You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever. The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1836 -> 1784 bytes 02-prepare_abe/console.log.xz | Bin 2764 -> 2768 bytes 03-build_abe-binutils/console.log.xz | Bin 31684 -> 31592 bytes 04-build_abe-stage1/console.log.xz | Bin 91740 -> 91344 bytes 05-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 06-build_abe-linux/console.log.xz | Bin 8608 -> 8624 bytes 07-build_abe-glibc/console.log.xz | Bin 235356 -> 235176 bytes 08-build_abe-stage2/console.log.xz | Bin 224640 -> 223572 bytes 09-build_abe-gdb/console.log.xz | Bin 39116 -> 39020 bytes 10-build_abe-qemu/console.log.xz | Bin 30700 -> 30624 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3864 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 2500 -> 2496 bytes 13-check_regression/console.log.xz | Bin 5628 -> 5192 bytes 13-check_regression/mail-body.txt | 26 - 13-check_regression/results.compare | 26 +- 13-check_regression/results.compare2 | 22 +- 14-update_baseline/console.log | 62 +- dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 28 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 +- sumfiles/g++.log.xz | Bin 2682104 -> 2652856 bytes sumfiles/g++.sum | 120 +- sumfiles/gcc.log.xz | Bin 2239132 -> 2271756 bytes sumfiles/gcc.sum | 2456 ++++++++++++++++----------------- sumfiles/gfortran.log.xz | Bin 894480 -> 895224 bytes sumfiles/gfortran.sum | 40 +- sumfiles/libatomic.log.xz | Bin 2260 -> 2264 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 213912 -> 213848 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2664 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 429744 -> 427352 bytes sumfiles/libstdc++.sum | 10 +- 37 files changed, 1394 insertions(+), 1454 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[binutils-gdb] branch master updated (2a517ca94d3 -> ecb828308c8)

by git＠git.linaro.org

This is an automated email from the git hooks/post-receive script. unknown user pushed a change to branch master in repository binutils-gdb. from 2a517ca94d3 Automatic date update in version.in new 4fdeb2a3799 x86: omit Cpu prefixes from opcode table new 8e0eb7c6b35 Arm: break gas dependency on libopcodes new ecb828308c8 gprofng/testsuite: adjust linking of synprog The 3 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: gas/configure | 2 +- gas/configure.ac | 2 +- gprofng/testsuite/gprofng.display/synprog/Makefile | 2 +- opcodes/i386-gen.c | 695 ++-- opcodes/i386-opc.tbl | 3763 ++++++++++---------- 5 files changed, 2241 insertions(+), 2223 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

[toolchain/ci/base-artifacts] branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 updated (8a5428155d24 -> 58308e0a2fa3)

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 8a5428155d24 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc [...] discards d5fa751745bb 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4a [...] discards 33b7401b78c7 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: [...] discards 9bdde86b17e2 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: [...] discards a2e450b8ca27 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/q [...] discards cb80e53e8846 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits discards 8278accb2de5 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits discards 1767932aec5f 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: [...] discards b78561336bfd 244: onsuccess: #1941: 7: Success after binutils/gcc/linux [...] discards 465c7201ab71 243: onsuccess: #1940: 7: Success after binutils/gcc/linux [...] discards 5cb7b760f90f 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/q [...] discards 7a703a618a55 241: onsuccess: #1938: 7: Success after binutils/gcc/linux [...] discards 360d92aad7cb 240: onsuccess: #1937: 7: Success after binutils/gcc/linux [...] discards 752fe71d5df0 239: onsuccess: #1936: 7: Success after binutils/gcc/linux [...] discards a66553628506 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/q [...] discards f19361a26cdb 237: onsuccess: #1934: 7: Success after basepoints/gcc-13- [...] discards 89e6831f2f92 236: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] discards f811d821c19c 235: onsuccess: #1932: 7: Success after binutils/gcc/linux [...] discards 0c60f67ce515 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: [...] discards c7fd02283d48 233: onsuccess: #1930: 7: Success after binutils/gcc/linux [...] discards e798560afc0c 232: onsuccess: #1929: 7: Success after binutils/gcc/linux [...] discards df0b9d824434 231: onsuccess: #1928: 3: Success after gcc: 8 commits discards 652695efadd3 230: force: #1927: 3: Failure after basepoints/gcc-13-4618 [...] discards 6222501c5b14 229: force: #1926: 7: Success after gcc: 7 commits discards 8ec539318732 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint [...] discards 06908e2b278d 227: onsuccess: #1906: 7: Success after binutils: 9 commits discards ee73d145bfd1 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: [...] discards 17676d2b9d0b 225: onsuccess: #1903: 7: Success after binutils/gcc/linux [...] discards 584ddb9195ad 224: onsuccess: #1902: 7: Success after binutils/gcc/linux [...] discards 29af7edffbb5 223: onsuccess: #1901: 7: Success after basepoints/gcc-13- [...] discards 5302b3d5eaa9 222: onsuccess: #1900: 7: Success after binutils/gcc/linux [...] discards 9b5dfc31fb23 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: [...] discards c0b0f2f039fe 220: onsuccess: #1898: 7: Success after binutils/linux/gli [...] discards 1abdfaa6eb36 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: [...] discards 97095e663aed 218: onsuccess: #1896: 7: Success after binutils/gcc/linux [...] discards aa6872a241df 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: [...] discards 88521a6193e6 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits discards 0abd7945e869 215: onsuccess: #1891: 7: Success after binutils/gcc/linux [...] discards 8afce9eb6257 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc [...] discards 7477c0b0f969 213: onsuccess: #1889: 7: Success after gcc: 5 commits discards c9d06fb5142e 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc [...] discards ff7b7facbe25 211: onsuccess: #1887: 7: Success after binutils/gcc/linux [...] discards 12795443e710 210: onsuccess: #1868: 7: Success after binutils: 7 commits discards d1266af0e02a 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/q [...] discards c57813d3494e 208: onsuccess: #1865: 7: Success after linux: 12 commits discards 4856d37028e6 207: onsuccess: #1862: 7: Success after binutils: 4 commits discards acfc0c92d581 206: onsuccess: #1860: 7: Success after gcc: 2 commits discards ed22584e792a 205: onsuccess: #1859: 7: Success after gcc: 3 commits discards c65a5a2f6f3f 204: onsuccess: #1858: 7: Success after binutils/gcc/linux [...] discards d74a5ffb5238 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: [...] discards 040d8a664470 202: onsuccess: #1856: 7: Success after gcc: 2 commits discards fca1afe610fd 201: onsuccess: #1855: 7: Success after binutils/gcc/linux [...] discards 87a47cfd13db 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits discards 00c23b2097e6 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: [...] discards 9d3ba6c91d90 198: onsuccess: #1852: 7: Success after gcc: 5 commits discards 0d13f96838c8 197: onsuccess: #1851: 7: Success after binutils/gcc/linux [...] discards 786497423422 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: [...] discards 8d88f11d7b15 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: [...] discards ece87e4dcffc 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: [...] discards b1e80b74d681 193: onsuccess: #1847: 7: Success after binutils/gcc/linux [...] discards 15aa6925f236 192: onsuccess: #1816: 7: Success after binutils/gcc/linux [...] discards 1c091c22bf67 191: onsuccess: #1808: 7: Success after binutils/gcc/linux [...] discards daacd1b0e848 190: onsuccess: #1774: 7: Success after binutils: 10 commits discards 07aa576855f4 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: [...] discards 3dc361d08d4a 188: onsuccess: #1765: 7: Success after binutils/gcc/linux [...] discards 809d798eaadb 187: onsuccess: #1763: 7: Success after binutils/gcc/linux [...] discards 647ebf349bfe 186: onsuccess: #1761: 7: Success after binutils/gcc/linux [...] discards 226c952ab40f 185: onsuccess: #1716: 7: Success after binutils/linux/gdb [...] discards cd6e8b422d30 184: onsuccess: #1715: 7: Success after binutils/gcc/linux [...] discards 7f468eaf1e68 183: onsuccess: #1712: 7: Success after binutils/gcc/linux [...] discards 05aa47d9a109 182: onsuccess: #1711: 7: Success after binutils/gcc/linux [...] discards 2ea41302f19a 181: onsuccess: #1700: 7: Success after binutils/gcc/linux [...] discards d0104e79445f 180: onsuccess: #1636: 7: Success after binutils/linux/gdb [...] discards a4d57b818793 179: onsuccess: #1634: 7: Success after binutils/gcc/linux [...] discards de9b0258b0ee 178: onsuccess: #1631: 7: Success after binutils/gcc/linux [...] discards 0178b12ad437 177: onsuccess: #1630: 7: Success after binutils/gcc/linux [...] discards 45f6f541c61a 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc [...] discards b524e32bb4d6 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc [...] discards f908e3ceb250 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: [...] discards f48abe8b8c61 173: onsuccess: #1626: 7: Success after binutils/gcc/linux [...] discards ef5032a08911 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qe [...] discards 34d887217d9e 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: [...] discards c1d2d5c5e3b3 170: onsuccess: #1623: 7: Success after binutils/gcc/linux [...] discards 79cc8cac3590 169: onsuccess: #1622: 7: Success after binutils/gcc/linux [...] discards d5909412b936 168: onsuccess: #1621: 7: Success after binutils/gcc/linux [...] discards 0d02ba11f215 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: [...] discards 4b640e7bc63f 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits discards 750b4ede7baf 165: onsuccess: #1618: 7: Success after binutils/gcc/linux [...] discards d9ea88c2ac43 164: onsuccess: #1617: 7: Success after binutils/gcc/linux [...] discards 99f4e1bdf2e5 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: [...] discards afb9ab52eb3c 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: [...] discards 9cba9dc851c3 161: onsuccess: #1614: 7: Success after binutils/gcc/linux [...] discards 5c01c1538171 160: onsuccess: #1613: 7: Success after binutils/gcc/linux [...] discards c98ab34d2d59 159: onsuccess: #1612: 7: Success after gcc: 4 commits discards e1b28649be06 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc [...] discards 73ea95670fa9 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits discards 5dee39694869 156: onsuccess: #1609: 7: Success after gcc: 2 commits discards 690e81f9c4d6 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gd [...] discards cdad48c8ac39 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards 45f5530d0ec1 153: force: #1606: 1: Failure after basepoints/gcc-13-3004 [...] discards 24faac0f5f9b 152: force: #1605: 7: Success after gcc: 9 commits new f751198a60b1 152: force: #1605: 7: Success after gcc: 9 commits new 1d709e47e5aa 153: force: #1606: 1: Failure after basepoints/gcc-13-3004 [...] new cb0d8ba0fd57 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 33ac09b0d87a 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gd [...] new b2beb2e9ebc3 156: onsuccess: #1609: 7: Success after gcc: 2 commits new 93723ec04081 157: onsuccess: #1610: 7: Success after gcc/linux: 21 commits new b0eecd7534c5 158: onsuccess: #1611: 7: Success after binutils/gcc/glibc [...] new 06593aae3bbb 159: onsuccess: #1612: 7: Success after gcc: 4 commits new 7d59194ed72b 160: onsuccess: #1613: 7: Success after binutils/gcc/linux [...] new 194ada5a3833 161: onsuccess: #1614: 7: Success after binutils/gcc/linux [...] new f61713ce30c4 162: onsuccess: #1615: 7: Success after binutils/gcc/gdb: [...] new d5c6219124fd 163: onsuccess: #1616: 7: Success after binutils/gcc/gdb: [...] new a7a39d30a844 164: onsuccess: #1617: 7: Success after binutils/gcc/linux [...] new 7badde895918 165: onsuccess: #1618: 7: Success after binutils/gcc/linux [...] new 167a315e11ab 166: onsuccess: #1619: 7: Success after gcc/linux: 141 commits new 72b86c1fc795 167: onsuccess: #1620: 7: Success after binutils/gcc/gdb: [...] new b957e2f9eddd 168: onsuccess: #1621: 7: Success after binutils/gcc/linux [...] new 227469b77653 169: onsuccess: #1622: 7: Success after binutils/gcc/linux [...] new 8d6c7c2af0fb 170: onsuccess: #1623: 7: Success after binutils/gcc/linux [...] new d0afaa773e0c 171: onsuccess: #1624: 7: Success after binutils/gcc/gdb: [...] new 345c4e1d0d42 172: onsuccess: #1625: 7: Success after gcc/linux/glibc/qe [...] new faabb284d308 173: onsuccess: #1626: 7: Success after binutils/gcc/linux [...] new 36f15625f21b 174: onsuccess: #1627: 7: Success after binutils/gcc/gdb: [...] new 638e27fcacdc 175: onsuccess: #1628: 7: Success after binutils/gcc/glibc [...] new 7d53f4c237f1 176: onsuccess: #1629: 7: Success after binutils/gcc/glibc [...] new 9c6e9a190949 177: onsuccess: #1630: 7: Success after binutils/gcc/linux [...] new 9ba7e737223c 178: onsuccess: #1631: 7: Success after binutils/gcc/linux [...] new 5afaf4f59632 179: onsuccess: #1634: 7: Success after binutils/gcc/linux [...] new f7f8335d6a72 180: onsuccess: #1636: 7: Success after binutils/linux/gdb [...] new 1abf1dcce800 181: onsuccess: #1700: 7: Success after binutils/gcc/linux [...] new a14c2453270b 182: onsuccess: #1711: 7: Success after binutils/gcc/linux [...] new 18988bb421d5 183: onsuccess: #1712: 7: Success after binutils/gcc/linux [...] new ef219da4a55b 184: onsuccess: #1715: 7: Success after binutils/gcc/linux [...] new d9df487caf77 185: onsuccess: #1716: 7: Success after binutils/linux/gdb [...] new 3c43d447d839 186: onsuccess: #1761: 7: Success after binutils/gcc/linux [...] new e01e75c2b46c 187: onsuccess: #1763: 7: Success after binutils/gcc/linux [...] new 1bee048bfa81 188: onsuccess: #1765: 7: Success after binutils/gcc/linux [...] new cf1156db71b4 189: onsuccess: #1766: 7: Success after binutils/gcc/gdb: [...] new 38009452ecbc 190: onsuccess: #1774: 7: Success after binutils: 10 commits new f32c72d0ae1a 191: onsuccess: #1808: 7: Success after binutils/gcc/linux [...] new 3d7d57e502a9 192: onsuccess: #1816: 7: Success after binutils/gcc/linux [...] new bd12d49d7a47 193: onsuccess: #1847: 7: Success after binutils/gcc/linux [...] new cd3f469ff496 194: onsuccess: #1848: 7: Success after binutils/gcc/gdb: [...] new 245834d3d2a5 195: onsuccess: #1849: 7: Success after binutils/gcc/gdb: [...] new 888e40c3655d 196: onsuccess: #1850: 7: Success after binutils/gcc/gdb: [...] new 8d0b6e20082d 197: onsuccess: #1851: 7: Success after binutils/gcc/linux [...] new c9cfd81ce0ee 198: onsuccess: #1852: 7: Success after gcc: 5 commits new f70cd0a4d3f9 199: onsuccess: #1853: 7: Success after binutils/gcc/gdb: [...] new b280071560a9 200: onsuccess: #1854: 7: Success after gcc/glibc: 5 commits new 29d24fdd6886 201: onsuccess: #1855: 7: Success after binutils/gcc/linux [...] new 8d781685d028 202: onsuccess: #1856: 7: Success after gcc: 2 commits new b9f8e82b3526 203: onsuccess: #1857: 7: Success after binutils/gcc/gdb: [...] new a42d5b90196a 204: onsuccess: #1858: 7: Success after binutils/gcc/linux [...] new 3e68268a0f59 205: onsuccess: #1859: 7: Success after gcc: 3 commits new 7bc7571c2a0f 206: onsuccess: #1860: 7: Success after gcc: 2 commits new fac0b54f06ae 207: onsuccess: #1862: 7: Success after binutils: 4 commits new 9c2dac0a89f0 208: onsuccess: #1865: 7: Success after linux: 12 commits new e91c93d16b07 209: onsuccess: #1866: 7: Success after binutils/gcc/gdb/q [...] new 477483012ad2 210: onsuccess: #1868: 7: Success after binutils: 7 commits new 00ea03178210 211: onsuccess: #1887: 7: Success after binutils/gcc/linux [...] new a1a32065680e 212: onsuccess: #1888: 7: Success after binutils/gcc/glibc [...] new 17a91b922ff6 213: onsuccess: #1889: 7: Success after gcc: 5 commits new 5b06a24d20dc 214: onsuccess: #1890: 7: Success after binutils/gcc/glibc [...] new e1e4e7216504 215: onsuccess: #1891: 7: Success after binutils/gcc/linux [...] new 2d9746ab9a73 216: onsuccess: #1892: 7: Success after binutils/gdb: 2 commits new a53fc26c5e7c 217: onsuccess: #1893: 7: Success after binutils/gcc/gdb: [...] new aff9030f9d0d 218: onsuccess: #1896: 7: Success after binutils/gcc/linux [...] new c3a7a8e94493 219: onsuccess: #1897: 7: Success after binutils/gcc/gdb: [...] new a4c23300f2b9 220: onsuccess: #1898: 7: Success after binutils/linux/gli [...] new 98c7f4c23307 221: onsuccess: #1899: 7: Success after binutils/gcc/gdb: [...] new dbbc7eb96fe3 222: onsuccess: #1900: 7: Success after binutils/gcc/linux [...] new 1a55acdf34c5 223: onsuccess: #1901: 7: Success after basepoints/gcc-13- [...] new 7fb7a406919e 224: onsuccess: #1902: 7: Success after binutils/gcc/linux [...] new ed0504ca613a 225: onsuccess: #1903: 7: Success after binutils/gcc/linux [...] new 172202575a41 226: onsuccess: #1904: 7: Success after binutils/gcc/gdb: [...] new cff191fdea27 227: onsuccess: #1906: 7: Success after binutils: 9 commits new 553fd2ff018e 228: onsuccess: #1914: 7: Success after gdb-12-branchpoint [...] new 23cd3390eea6 229: force: #1926: 7: Success after gcc: 7 commits new 63246eceb350 230: force: #1927: 3: Failure after basepoints/gcc-13-4618 [...] new 20170acf9480 231: onsuccess: #1928: 3: Success after gcc: 8 commits new 32c36e45a968 232: onsuccess: #1929: 7: Success after binutils/gcc/linux [...] new 6649de3966a7 233: onsuccess: #1930: 7: Success after binutils/gcc/linux [...] new 9f970a47c7f3 234: onsuccess: #1931: 7: Success after binutils/gcc/gdb: [...] new 15074f38d00f 235: onsuccess: #1932: 7: Success after binutils/gcc/linux [...] new 015570034dab 236: onsuccess: #1933: 7: Success after binutils/gcc/linux [...] new 5cc742bb77c6 237: onsuccess: #1934: 7: Success after basepoints/gcc-13- [...] new 92e3a9827dd1 238: onsuccess: #1935: 7: Success after binutils/gcc/gdb/q [...] new cb0810ffe672 239: onsuccess: #1936: 7: Success after binutils/gcc/linux [...] new 66180f750b5f 240: onsuccess: #1937: 7: Success after binutils/gcc/linux [...] new c113ef1e8786 241: onsuccess: #1938: 7: Success after binutils/gcc/linux [...] new 516f2111582d 242: onsuccess: #1939: 7: Success after binutils/gcc/gdb/q [...] new a640298351cd 243: onsuccess: #1940: 7: Success after binutils/gcc/linux [...] new 18dbdc933603 244: onsuccess: #1941: 7: Success after binutils/gcc/linux [...] new 264f2d3a6854 245: onsuccess: #1942: 7: Success after binutils/gcc/gdb: [...] new f68f90d57327 246: onsuccess: #1943: 7: Success after binutils/gdb: 6 commits new 798029a8f2f8 247: onsuccess: #1944: 7: Success after gcc/linux: 109 commits new 73b45105fb20 248: onsuccess: #1945: 7: Success after binutils/gcc/gdb/q [...] new a61bc2da0f53 249: onsuccess: #1946: 7: Success after binutils/gcc/gdb: [...] new 0731f4e7381c 250: onsuccess: #1947: 7: Success after binutils/gcc/gdb: [...] new 449f9fcf88f6 251: onsuccess: #1948: 7: Success after v7.2.0-211-g562d4a [...] new a50e116a13e2 252: onsuccess: #1949: 7: Success after binutils/gcc/glibc [...] new 58308e0a2fa3 253: onsuccess: #1950: 7: Success after glibc: 2 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 (8a5428155d24) \ 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 1820 -> 1768 bytes 02-prepare_abe/console.log.xz | Bin 2808 -> 2780 bytes 04-build_abe-binutils/console.log.xz | Bin 32316 -> 32828 bytes 05-build_abe-stage1/console.log.xz | Bin 73568 -> 73596 bytes 07-build_abe-linux/console.log.xz | Bin 8660 -> 8636 bytes 08-build_abe-glibc/console.log.xz | Bin 245852 -> 243448 bytes 09-build_abe-stage2/console.log.xz | Bin 206936 -> 205476 bytes 10-build_abe-gdb/console.log.xz | Bin 39452 -> 39316 bytes 11-build_abe-qemu/console.log.xz | Bin 31784 -> 31272 bytes 12-check_regression/console.log.xz | Bin 3744 -> 3280 bytes 13-update_baseline/console.log | 70 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/glibc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 24 ++++++------ 17 files changed, 52 insertions(+), 52 deletions(-) -- To stop receiving notification emails like this one, please contact the administrator of this repository.

1 year, 11 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

Tcwg-commits December 2022