https://bugs.kde.org/show_bug.cgi?id=468575
--- Comment #20 from Paul Floyd <pjfl...@wanadoo.fr> --- And regtest results == 737 tests, 6 stderr failures, 2 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures == gdbserver_tests/hgtls (stdoutB) memcheck/tests/pointer-trace (stderr) none/tests/double_close_range (stderr) none/tests/double_close_range_sup (stderr) none/tests/double_close_range_xml (stderr) none/tests/riscv64/compressed (stdout) none/tests/riscv64/compressed (stderr) none/tests/riscv64/integer (stdout) none/tests/riscv64/integer (stderr) I've seen memcheck/tests/pointer-trace issues before where the working directory is on NFS. Not riscv related. The double_close_range tests are fairly new and may need some extra filtering. The two riscv64 fails look like a problem with the toolchain. I'll see if trying a local build of the toolchain helps. -- You are receiving this mail because: You are watching all bug changes.
