To be fair, the runtimes aren't exactly comparable because they currently run different things. Azure runs 3.7 whereas Travis doesn't, and Azure still needs to run the slow tests, docs build, and PyPy tests.
Regarding the optional dependency build, it is currently failing because of some broken conda packages. I'm hoping that once conda-forge finishes its compiler migration it will work. See https://github.com/sympy/sympy/issues/15385 for more information. Aaron Meurer On Thu, Nov 8, 2018 at 7:49 AM Sidhant Nagpal <sidhantnagpa...@gmail.com> wrote: > > Nice, the tests seem to run faster on Azure on individual jobs compared to > Travis. > Although, the overall testing time seems to be comparable for both. > > https://dev.azure.com/SymPy/SymPy/_build/results?buildId=266&view=logs > https://travis-ci.org/sympy/sympy/builds/444273129?utm_source=github_status&utm_medium=notification > > By the way, is there a blocker for making optional dependency tests to work > on Azure? > (The status badge for Azure builds reads "partially succeeded") > > On Saturday, October 13, 2018 at 12:46:54 AM UTC+5:30, Aaron Meurer wrote: >> >> You may have noticed some Azure pipelines builds in the pull requests. >> Till now, they have only run the doctests, but I have just merged a PR >> which adds the rest of the test suite (there are still a few things >> missing, see https://github.com/sympy/sympy/issues/15385). >> >> For now, the Azure builds are not required to merge pull requests. The >> idea here is to experiment, to see if it is worth using Azure over >> Travis. So even though they are not required, take a look if the tests >> fail there, and also make a note if Azure or Travis is more reliable. >> >> My plan is >> >> 1. Run both Travis and Azure in parallel. >> >> 2. Once it is clear Azure tests are passing make them required to >> merge, just like Travis. >> >> 3. Add the missing stuff to Azure >> (https://github.com/sympy/sympy/issues/15385). >> >> 4. If it becomes clear that Azure is more reliable than Travis >> (finishes faster, no build restarts), we can remove the Travis builds. >> But we should let both run for at least a month before doing this. >> >> 5. If we remove Travis, we will need to keep at least the Travis docs >> build, because doctr doesn't support Azure yet (and I don't plan to >> add the docs build to Azure because of this). >> >> Or if it turns out that Azure really is worse than Travis, we can >> scrap it, or maybe use it only for some specific builds. I already >> have some gripes with it, and the UI is not as clean as on Travis. But >> I'd like to hear what other think. >> >> Aaron Meurer > > -- > You received this message because you are subscribed to the Google Groups > "sympy" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sympy+unsubscr...@googlegroups.com. > To post to this group, send email to sympy@googlegroups.com. > Visit this group at https://groups.google.com/group/sympy. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sympy/fbbe2fff-af5f-4a1e-bee7-cc7aa577fc99%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sympy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sympy+unsubscr...@googlegroups.com. To post to this group, send email to sympy@googlegroups.com. Visit this group at https://groups.google.com/group/sympy. To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6L73w94qCSgZNtodvBnNQmB3DFiHsDN5%2BmP%3DA8-2Rwcfg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
