https://bugs.winehq.org/show_bug.cgi?id=41339
--- Comment #5 from fjfrackiewicz@gmail.com --- (In reply to Austin English from comment #4)
(In reply to fjfrackiewicz from comment #3)
(In reply to Bruno Jesus from comment #2)
Thank you for your effort. The problem of debugging random failures is that sometimes we end with false commits. The commit that resulted from your test literally only renames variables so it can't be the offender.
I see. Well, I do apologize for mislabelling the commit then.
The bisect never turned anything else up when testing with Wine 1.9.16 as "good" and Wine 1.9.18 as "bad"
Sorry for the hassle, please feel free to close the bug if required.
It's still a valid but, it just needs more careful testing. E.g., testing each commit several times, or putting the system under load first to see if if it's more reproducible that way.
Right, I understand.
So far what I did was the following:
- create or update a prefix via "winecfg" several time per commit - install a program
I'll try again and see if I can't find an application that will put the system under load a bit more.