forked from joejulian/gio
Daniel Martí
c2cbcee78d
This way, if the user has a custom winecfg, it can't possibly affect the tests. I was encountering this as DXVK does not work on virtual Xorg servers (which we use), and Gio thus failed to render on such a combination. >From the numbers below, it can be seen that setting up a new WINEPREFIX takes roughly five seconds: $ rm -rf ~/.cache/gio-e2e-wine $ go test -run EndToEnd/Windows PASS ok gioui.org/cmd/gogio 16.369s $ go test -run EndToEnd/Windows PASS ok gioui.org/cmd/gogio 11.810s A repeated run still has a slow "wine winecfg /?", for some reason. Add a TODO since I can see it taking a third of the time on my terminal. I haven't been able to properly investigate why, unfortunately. As far as I can tell, winecfg is just faster when run with a terminal instead of an output buffer. They might use isatty on stdout/stderr. The overall time to run the wine sub-test is increased from ~5s to ~11s, but it's worth it to make it run everywhere. It looks like there is plenty of room as per the TODO above, as winecfg seems to mostly do nothing. We're also not too worried, as all e2e subtests run in parallel. Fixes #106. Signed-off-by: Daniel Martí <mvdan@mvdan.cc>