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

CI with nimble #309

Closed
wants to merge 22 commits into from
Closed

CI with nimble #309

wants to merge 22 commits into from

Conversation

markspanbroek
Copy link
Member

Runs continuous integration with nimble instead of nimbus build system. Both simplifies the CI configuration and speeds up the build, but it's probably not wise to merge this until a version of Nimble that supports lock files has been released with Nim.

Depends on #305.

This enables faster development cycles at
the expense of code coverage accuracy.
To get a reasonable test execution time.
To prevent subsequent `make` command to build a
different version of Nim.
So that nimbus-build-system doesn't have to
do it afterwards.
Will automatically update caches when a new minor version
of Nim is released.

See also:
https://github.com/actions/cache/blob/main/workarounds.md#update-a-cache
Requires an update to latest nim-nat-traversal
To get a reasonable test execution time.
To get a reasonable test execution time.
To get a reasonable test execution time.
Start Ethereum node *after* the unit tests are run.
Allows for faster feedback loops; a next attempt to run
the CI will start sooner.
@markspanbroek markspanbroek changed the base branch from main to fix-nimble November 14, 2022 10:52
Base automatically changed from fix-nimble to main November 16, 2022 12:10
@gmega
Copy link
Member

gmega commented Mar 19, 2024

Incredibly I think this may start making sense to consider again once nimble integrates the SAT solver that's been in the works for Atlas, assuming package maintainers also start issuing proper releases. But I'd close this PR for now as I don't think it's anything we'll be doing short-term, what do you think @markspanbroek?

@markspanbroek
Copy link
Member Author

Yeah, let's close this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants