https://bugs.winehq.org/show_bug.cgi?id=53057
--- Comment #6 from Morgan Wesström winehq@pp.dyndns.biz --- (In reply to Rafał Mużyło from comment #5)
Is there a way to get a timestamp in the trace log?
Exactly that, 'timestamp' channel.
Thank you, I feel stupid now. :)
Also, see git-3.eclass - likely EGIT_COMMIT and EGIT_CHECKOUT_DIR are a part of the answer for 9999 ebuild though chances are it won't be all that straightforward/convenient (live ebuilds rarely are).
I stumbled over EGIT_COMMIT too in my investigation so if it comes to it, I'll make a local copy of the 9999-ebuild and try that.
I did however make a faulty assumption in my first assessment of this bug and I apologize for that. I'm normally using wine-staging and this bug hit me in wine-staging 7.8. To rule out the staging patchset I installed wine-vanilla 7.8 and confirmed the bug was there too, then making the assumption the bug appeared between 7.7. and 7.8. During further investigation today I realized the bug is there in even earlier versions of wine-vanilla but not in wine-staging. I'm currently compiling wine-vanilla 7.3 but it takes about an hour per version on my old machine so it may take a while until I figure out exactly which version introduced the bug. Interesting though that the staging patchset reversed the bug up until 7.7.
I will updated this report as soon as I've found the first regular version where the bug appears. Hopefully that can give a hint to what commit is responsible but I will give the regression testing a shot if necessary.