Closed QuLogic closed 6 years ago
Thanks :)
Regarding Travis-CI, I was actually thinking of installing a Builbot (I already have a dedicated server building each night the Flatpak version of Paperwork and distributing it). It would be not only for Pyinsane, but also Pyocr, Libpilllowfight, and Paperwork. Quite frankly, I haven't had time yet to look at which solution would be best nor to set one of them up, and I don't know when I will.
If you have time for that and are willing, you can also contribute on that point :-)
Ah, I forgot about the port to GNOME infrastructure; surely they will have some sort of builtin CI with GitLab.
I guess. But right now they are not ready anyway, and I don't know how long they will need to get their Gitlab out of testing.
Looks like it might be possible to migrate now: https://wiki.gnome.org/GitLab/IncubatorReqs
Good to know. I'm still planning on switching to gitlab.gnome.org. But while waiting for Gnome's Gitlab, I made my own buildbot. So at least the CI issue is solved (and also it updates the Flatpak repository automatically and rebuilds Windows versions automatically as well).
Tests were not correctly falling back to the test device when real devices were not available.
BTW, why not run these tests on Travis-CI?