You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Local builds often look like they're hung for an extended period. When run with /p:BuildInParallel=false or /p:TestInParallel=false, see output similar to the following
Those 66 minutes to execute tests in that assembly are way long. Most assemblies test in less than a minute. Just run other runs for longer than 5 minutes.
Similar long builds are not visible on the CI, tending to build in about 20 minutes. However AppVeyor build duration varies widely from ~25 minutes to ~55 minutes. Builds prior to 5403af6 tended to build in ~8 minutes. That commit added a large number of tests and affected only System.Net.Http.Formatting.Test.
Likely this slowness and variability (not all builds are this slow) relates to system changes and not our code changes. AppVeyor and local dev machines are kept more up-to-date than our CI agents. Then, again, the problem might relate to #95 or system-specific interactions with the recently-upgraded test dependencies (also done last October / November).
The text was updated successfully, but these errors were encountered:
so are you certain these are related to the environment changes?
No, only speculating at this point.
How long do the local runs take?
As shown in the original post, just testing the one project can take more than an hour. Local builds taking 45 minutes are common and that greatly reduces productivity in this repo.
Local builds often look like they're hung for an extended period. When run with
/p:BuildInParallel=false
or/p:TestInParallel=false
, see output similar to the followingThose 66 minutes to execute tests in that assembly are way long. Most assemblies test in less than a minute. Just run other runs for longer than 5 minutes.
Similar long builds are not visible on the CI, tending to build in about 20 minutes. However AppVeyor build duration varies widely from ~25 minutes to ~55 minutes. Builds prior to 5403af6 tended to build in ~8 minutes. That commit added a large number of tests and affected only System.Net.Http.Formatting.Test.
Likely this slowness and variability (not all builds are this slow) relates to system changes and not our code changes. AppVeyor and local dev machines are kept more up-to-date than our CI agents. Then, again, the problem might relate to #95 or system-specific interactions with the recently-upgraded test dependencies (also done last October / November).
The text was updated successfully, but these errors were encountered: