https://bugs.winehq.org/show_bug.cgi?id=49423
--- Comment #11 from Sveinar Søpler cybermax@dexter.no --- (In reply to Zebediah Figura from comment #10)
Can you please expand on exactly how?
Note that because of the nature of regression testing, as joaopa mentioned, doubling the number of commits means only one extra compilation and run.
Certainly regression testing is time-consuming, and learning to build Wine is also time-consuming. I don't particularly *like* demanding that people do it, but it's an order of magnitude difference for developers.
Well, since this is staging, it is not ONLY wine commits that has to be bisected. Lets say it is 200 commits between wine-deve-4.16 -> 4.17 (to narrow it down). I know 4.16 = "good", and 4.17 = "Bad". My first bisect would then be 4.16+100 (half right?).
Thats fine, exept i might not be able to apply staging at that point. Staging does not get rebased on a "per commit" basis in case of breakage, but sometimes quite a few commits later. So lets say the rebased "staging" is then 4.16+132. Fine, that is also "bad". Next bisec would then be 4.16+66. Lets say once again i am unable to apply staging, but have to apply to eg. 4.16+49. This is "good". Oki.. then i might end up unable to apply staging AT ALL on any of the commits between 4.16+49 -> 4.16+132
I cant see me applying staging to 4.16 and the merging 4.16+100 either, as that is 99% sure to fail, not to mention having to keep tabs on what patchsets gets added/removed/disabled/enabled inbetween those commits.
I know it might not be exactly like this, but i have done tries before, and have ended up with a commit range not likely to be accurate enough for any devs to bother.
Sorry if i have missunderstood the whole consept tho, but bisecting "staging" when you do not know if it is a staging patch or a wine commit that is the culprit is a bit over medium hard for "regular folks" imo.
I know it might be that wine-4.16 only needs 2-3 patchsets to work with Battle.net/WoW, but i do not know the minimal patchset needed. I am willing to try if someone know the absolute minimum patchset tho, so it is way less to fiddle with. (Verified one at that, not "it should probably possible work with only X and Y")
By contrast, a bisect will usually point exactly where the problem is. In terms of developer time, it takes quite a lot less.
I do understand... no problem. It is just not that easy ref. my attempt to describe the problem above.
Another thing to worsen this problem is that WoW is NOT playable with WineD3D AT ALL (nope.. having 4-5 fps is NOT playable). So you would need DXVK to get this working, and recent DXVK might need recent wine and/or vulkan patches to work properly too.
Sorry, i do understand your problem, but hopefully you also understand mine :) That is why i asked if there was something that could be logged. Maybe a overly amount of "key-press-buffer-overrun" or whatever that MAY point in a certain direction :)