-
Notifications
You must be signed in to change notification settings - Fork 76
flake: build dev profile instead of release #1228
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
base: master
Are you sure you want to change the base?
Conversation
this results in much faster builds and therefore checks, improving developer experience. if we additionally want to build the packages in release mode, or run certain tests in release mode, we can build the workspace dependencies using both release and dev profiles as appropriate, but unless we intend to ship e.g. docker containers based on our built packages we don't need the release profile for the foreseeable future.
Pull Request Test Coverage Report for Build 20240963871Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
benalleng
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ack much faster, nice
|
I am actually getting a failure on the check locally... |
I also experieced this made mention of it in |
|
do you guys see failures if you only run one of the test jobs at a time instead of all 3? easiest way to do this is to specify re #1224 (comment) maybe it's better to set |
|
FWIW I also get timeout errors on the integration tests before this change (latest master): |
|
specifying the job numbers did work for me |
|
based on the test, this looks like it's timing out calling the bitcoin RPC interface? i suspect |
this results in much faster builds and therefore checks, improving developer experience.
if we additionally want to build the packages in release mode, or run certain tests in release mode, we can build the workspace dependencies using both release and dev profiles as appropriate, but unless we intend to ship e.g. docker containers based on our built packages we don't need the release profile for the foreseeable future.
Pull Request Checklist
Please confirm the following before requesting review:
AI
in the body of this PR.