Wine and mingw-w64 cooperation
Jacek Caban
jacek at codeweavers.com
Thu Jun 6 11:13:49 CDT 2019
On 6/5/19 9:42 PM, Martin Storsjö wrote:
> On Wed, 5 Jun 2019, Francois Gouget wrote:
>
>>> 3. Build a few projects - to make sure they build.
>>>
>>> Wine, Wine Gecko, VLC should give a good coverage.
>>
>> That sounds like long running tasks so we will likely need new
>> hardware so the TestBot can run them for every patch that gets
>> submitted: if patches come at a rate of about one per hour, then the
>> TestBot needs to process the resulting jobs at a rate of at least one
>> per hour. That said we already need new hardware for PCI-passthrough
>> for Wine (though the exact details are not set yet).
>
> Those projects are rather large, so either you need quite beefy
> hardware, or you just run some smaller test setup for each patch
> (rebuild mingw-w64 and build a few smoketests maybe?) and then run a
> full build of those projects e.g. nightly (e.g. with a known good
> pinned version of those projects, which can be updated regularly).
We don't have that many pushes, it shouldn't be too bad IMHO. For
patches submitted manually, there could be checkboxes for tests you'd
like to run, so could just skip tests if they don't need to be ran.
Jacek
More information about the wine-devel
mailing list