On test.winehq.org I see that dmloader:dmloader crashed on gitlab-debian-64 due to an assertion (2023-01-12):
060c:loader: 104 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped. dmloader:loader:060c done (-2147483391) in 0s 88B Test failed: crash (80000101)
https://test.winehq.org/data/patterns.html#dmloader:loader
I'd like to know if this is caused by the one assert() in stream_get_chunk(). A backtrace could help in that regard but:
* The test report on test.winehq.org only has the test output, not Wine's stderr traces which is where a backtrace would be. http://winetest.dolphin/data/047118247ce489a7138428c8b2cd5692ed04337e/linux_...
* And the GitLab log has neither the test output nor the Wine traces. https://gitlab.winehq.org/wine/wine/-/jobs/8996
So are the Wine traces available somewhere for GitLab's nightly WineTest runs?
On Fri, Jan 20, 2023 at 9:36 AM Francois Gouget fgouget@codeweavers.com wrote:
- The test report on test.winehq.org only has the test output, not Wine's stderr traces which is where a backtrace would be.
http://winetest.dolphin/data/047118247ce489a7138428c8b2cd5692ed04337e/linux_...
That link isn't publicly accessible (I suspect it may be an internal CodeWeavers' address?).
On Fri, 20 Jan 2023, Austin English wrote:
On Fri, Jan 20, 2023 at 9:36 AM Francois Gouget fgouget@codeweavers.com wrote:
- The test report on test.winehq.org only has the test output, not Wine's stderr traces which is where a backtrace would be.
http://winetest.dolphin/data/047118247ce489a7138428c8b2cd5692ed04337e/linux_...
That link isn't publicly accessible (I suspect it may be an internal CodeWeavers' address?).
No, that's from my development test.winehq.org server (which I like despite the 30MB page because it has 6 months of history). Sometimes I copy/paste from the wrong browser window :-(
In such cases it's just a matter of replacing the hostname. The link below should work: https://test.winehq.org/data/047118247ce489a7138428c8b2cd5692ed04337e/linux_...
-
Austin English -
Francois Gouget