Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nightly build #630

Open
tzaffi opened this issue Jan 4, 2023 · 1 comment
Open

Nightly build #630

tzaffi opened this issue Jan 4, 2023 · 1 comment
Labels
new-feature-request Feature request that needs triage Team Scytale

Comments

@tzaffi
Copy link
Contributor

tzaffi commented Jan 4, 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 and indexer.

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?

  • Coverage reports using: https://github.com/nedbat/coveragepy
  • 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

@tzaffi tzaffi added the new-feature-request Feature request that needs triage label Jan 4, 2023
@tzaffi
Copy link
Contributor Author

tzaffi commented Feb 23, 2023

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 tzaffi changed the title Draft: Nightly build Nightly build Feb 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-feature-request Feature request that needs triage Team Scytale
Projects
None yet
Development

No branches or pull requests

1 participant