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
A short look at recent PRs shows that Azure CI takes between 90 and 140 minutes to complete. More than 90% of that time is compiling the code. We also spend some time running the tests. Take a look at data from a recent example below.
I went looking for more tests we could add to Azure. The critiria were that the whole .py file take less than 20 seconds to complete and uses only either silo or blueprint data or no data files at all. That produced the list of tests below. If I sum all the time for running all these tests from recent runs on poodle, it amounts to 10.5 minutes of extra time. So, instead of taking 90 mins for Azure CI to complete, it will take 100 mins. I propose we add these tests to Azure CI.
A short look at recent PRs shows that Azure CI takes between 90 and 140 minutes to complete. More than 90% of that time is compiling the code. We also spend some time running the tests. Take a look at data from a recent example below.
I went looking for more tests we could add to Azure. The critiria were that the whole
.py
file take less than 20 seconds to complete and uses only either silo or blueprint data or no data files at all. That produced the list of tests below. If I sum all the time for running all these tests from recent runs on poodle, it amounts to 10.5 minutes of extra time. So, instead of taking 90 mins for Azure CI to complete, it will take 100 mins. I propose we add these tests to Azure CI.The text was updated successfully, but these errors were encountered: