[Bug 48847] dotnet471: often gets a critical section timeout

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=48847

--- Comment #14 from Austin English <austinenglish at gmail.com> ---
(In reply to m0rvj from comment #13)
> If someone can explain to me how to automate the testing, I'd be minded to
> give it a go... I've done plenty of regression testing so I know how to do
> the bisect etc. The bit I'd need advice on is how to test whether the dotnet
> installation succeeded?

`winetricks --verify dotnet471` will reproduce it, rarely, when run in a loop
(be sure to cleanup between runs). I more often see it when running
winetricks's unit tests, see https://github.com/Winetricks/winetricks#tests

But again, it's not consistent,  and what causes it to fail is unclear. In
addition, native .net in general has had several intermixed regressions that
will make this a challenge to accurately bisect.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.