On 19Feb2017 1554, Donald Stufft wrote:
We don’t actually have Windows tests being run at all on pull requests
(largely because AppVeyor took too long to run), though we obviously
still have the buildbot fleet running post commit. This is something we
should ideally rectify though!
On the Travis builders, we skip running the unit tests all together if
the PR was for something that couldn’t possibly change the outcome. I’m
not familiar enough with the capabilities of the Python test runner to
know if it can mark tests somehow to be excluded by default and only run
if a certain flag is ran, if so it shouldn’t be very hard to make
something that only runs those tests on changes to PCBuilder/* or
tools/msi/*. Otherwise it might need a separate set of tests for it that
can be independently ran.
I can easily get some VSTS (*.visualstudio.com) test runners going with
VMs on Azure. I'm just not quite sure how to feed the results back into
the github status checks right now, or how to make them publicly
maintainable (that is, they'd be very much owned and only accessible by
me, and likely only as long as I'm employed by Microsoft, which isn't
great for sustainability - though of course anyone else can also set up
the build definition and their own pool of VMs).
No promises on dates, but this is something that I'll likely do
regardless. I want the Windows tests as badly as anyone :)
Cheers,
Steve
_______________________________________________
core-workflow mailing list
core-workflow@python.org
https://mail.python.org/mailman/listinfo/core-workflow
This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct
