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
In order to enable important tests which take a long time to run, but not impede the development cadence, we may want to add a nightly build as is present in go-algorand and indexer.
I'm creating this issue to have a placeholder for strategizing and deciding how to move forward.
Very slow unit and integration tests that are still deemed important to run. One example is the source mapper for python 3.10 (on 3.11 the tests are fast enough to run on every commit)
Urgency
Medium
The text was updated successfully, but these errors were encountered:
Nightly tests are currently running. When #650 is merged they'll do a lot more. But then we're hoping to speed up the source mapper to the point that the nightly tests are no longer needed.
Before removing completely, let's decide if this can be useful for something such as the coverage reports that are linked to above.
tzaffi
changed the title
Draft: Nightly build
Nightly build
Feb 23, 2023
Should we have nightly tests?
In order to enable important tests which take a long time to run, but not impede the development cadence, we may want to add a nightly build as is present in
go-algorand
andindexer
.I'm creating this issue to have a placeholder for strategizing and deciding how to move forward.
What might we want to run in a nightly build?
Urgency
Medium
The text was updated successfully, but these errors were encountered: