Hello Adithyay, thanks for opening the PR, no worries we can ignore the timeout, the machines are under high demand so timeouts can't be avoided. In fact, we switched from Travis and Appveyor to azure pipelines to avoid those timeouts, but the MSI installer is still part of the Appveyor config, which hasn't been converted yet, so we still run the Appveyor job on the side.
Thanks, Marcus > On 7. Jan 2020, at 21:14, Adithya Praveen <[email protected]> wrote: > > Hey there, > > So I created a pull request after updating docs (detailed in previous > threads). It passed 16 out 17 > checks(https://github.com/mlpack/mlpack/pull/2143 > <https://github.com/mlpack/mlpack/pull/2143>). The check that failed was the > appveyor build (https://ci.appveyor.com/project/mlpack/mlpack/builds/29951034 > <https://ci.appveyor.com/project/mlpack/mlpack/builds/29951034>). However the > first job seemed to have succeeded. It was the second job that failed. The > message displayed in the "messages" tab is the following: "Build execution > time has reached the maximum allowed time for your plan (90 minutes)." > (https://ci.appveyor.com/project/mlpack/mlpack/builds/29951034/job/bk5h0rexv6kp6rek/messages > > <https://ci.appveyor.com/project/mlpack/mlpack/builds/29951034/job/bk5h0rexv6kp6rek/messages>). > > Is there something I can do to solve this issue? > > Cheers, > Adi. > _______________________________________________ > mlpack mailing list > [email protected] > http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack
_______________________________________________ mlpack mailing list [email protected] http://knife.lugatgt.org/cgi-bin/mailman/listinfo/mlpack
