Originally posted by Cybmax
View Post
Originally posted by Cybmax
View Post
Originally posted by Cybmax
View Post
58 failures on a single system is way higher that the wine automated testing so showing. 51 was merged results with the highest per system run only being 30 so 58 is 28 higher than expected. Either Microsoft has broken a lot more with build 1909 that would not be a surprise or your windows driver combination is just bring out a real horrible like a broken installed driver.
Every one of those 58 test failure at least 10 applications that will not work. At the that is at least 580 applications that will not work on your system. If you use any of that 580+ applications that is another question.
Odds that windows compatibility shims fix any of the detects ABI bugs by the wine test suite in windows less than 1 in 1000.
Originally posted by duby229
View Post
The stable releases of wine are tested with real apps and games. There are 4-5 stable releases a year this is slower to allow for that testing.
duby229 the wine test suite has the behaviours of over 6000 applications. Automated installing 6000 applications is going to take you more than 2 weeks let alone running any tests. Stable releases are only tested with 2000 real applications and that is to keep inside the 2 month window.
You are saying use real world applications. My problem is how in a 2 week release cycle is this possible. Remember that wine test suite is avoiding have to install 6000 applications+. Horrible part here 6000 applications will not be compatible with each other all the time either.
Yes you are right that wine "correct" behaviour it testsuite is checking for is kind of imaginary because windows ABI is all over the place. But wine test suite is checking for behaviours we know applications expect and if they don't have those behaviours they don't run.
Comment