On Fri, 13 Jan 2017 04:30:38 +0100, Chris Murphy <li...@colorremedies.com> wrote:

On Thu, Jan 12, 2017 at 4:32 PM, Adam Williamson
<adamw...@fedoraproject.org> wrote:
Hi folks! So I finally got around to that 'think about USB test
coverage' item that's been on my todo list forever.

I propose we add a table to the Installation Validation page. The
purpose is simply to check that writing images is working with
mediawriter in the major supported environments: Windows, macOS , and
the supported stable Fedora releases. So it could just look like this:

                        Windows    macOS    Fedora 24    Fedora 25

with the intent being that we at least check that writing any one
release blocking image with mediawriter in each environment.

We could split Windows into 7, 8 and 10 or something, but not sure if
it's really necessary...


Well I don't really want to eat a hat, because I've had my fill for a
lifetime, but I'd eat my hat if FMW works on Windows 10 but does not
work on Windows 7. Or vice versa. So may be ask mbriza which one to
test on, and hope the numbers game fills in the rest on its own. The
API/ABI stability on Windows is pretty extreme.  In order of market
share though, by a long shot it's Windows 7, then 10, and a distant
third is 8.1 and then 8(.0) barely registers. So weirdly enough,
chances are it'll work on 8/8.1 if it works on 7 and 10. So a thorough
test would be testing both 7 and 10. Less thorough, but sane, is
testing just on 10.

(For those who don't know, it's possible to get a free copy of Windows
Enterprise, the installer iSO will install a copy of Windows that'll
work for 90 days, the timer starts from the time of installation; i.e.
it's not the download ISO that's time limited.)

FWIW at the moment on Fedora 25 I'm running into these two bugs and
can't write images at all with FMW.

It does not work on Windows 7 for some folks. On my laptop with Win 7, it works. I've got a virtual machine where it doesn't work for testing though. I suspect there's a problem with ANGLE (which is a library that translates OpenGL calls to DirectX on Windows) combined with hardware drivers not supporting recent enough OpenGL. This is probably a problem with Qt packaging on Fedora but as of now, I don't know how to fix that. There's a bug [1] open for this specific issue for a while now.

I'm currently waiting for the release of Qt 5.8 where there is a more advanced level of deciding which rendering backend to use for QML and it can even fallback to a software renderer now which could be sufficient for FMW. However, I need to test that first.

So in the light of this, I agree with Chris that testing on Windows 7 and 10 would probably be what we should do.

Chris, regarding the issues you mentioned:
 #1412063 should be fixed in 4.0.8 (now in updates-testing)
#1412057 I have a fix for this using a different method in the UDisks2 API - now FMW will seem to be "benchmarking" a drive instead of writing (especially in polkit dialogs). OpenForRestore doesn't restore writing AND reading the written data, hence I needed to use a method that allows me to do so. The source of your problem was using OpenForRestore and then OpenForBackup - in case of large images or slow flash drives, a timeout somewhere in polkit ran out and it requested authentication again.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1319946
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org

Reply via email to