https://bugs.kde.org/show_bug.cgi?id=488635
--- Comment #4 from kloczek <kloczko.tom...@gmail.com> --- > Look at the code, see where it fails, try to figure out why it's failing and > whether that reason is caused by a faulty assumption in the code, a local > issue on your machine, ot something else. The same way you debug any failing > code, really. So looking on the diagnostics messages you cannot say anything about possible cause? If yes so for what are those messages? On build infra which I'm using I saw many cases when only change between Intel and AMD cased that some test suited started failing so if something is not failing in your CI it does not mean that there is no bug so .. closing ticket as resolved is not helpful. -- You are receiving this mail because: You are watching all bug changes.
