-
Notifications
You must be signed in to change notification settings - Fork 37.7k
ci: Add environment files for all settings #16623
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
Conversation
c52d9c0
to
e5ada9a
Compare
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.
This approach pollutes the calling bash environment. Should work without export
?
Concept ACK.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
f181477
to
29f4819
Compare
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.
Concept ACK
I'll run through each of the different ENV builds locally. Have done amd64_asan
and amd64_qt5
so far.
For a future change / discussion, it'd be handy if the Docker containers were named. amd64_qt
is more useful than peaceful_rubin
once there are a bunch floating around.
Also, maybe we could stop (although not destroy) containers automatically after successful completion of the tests?
Can you explain what command exactly does that? I can't find any. It will potentially pollute your ccache dir and the git repo with build artifacts, but that has nothing to do with bash. |
Good suggestions @fanquake. I'll probably leave those as follow-up features that can be added. |
ACK. I would find it easier if the new files were numbered the same as its equivalent Travis machine. Recipe to verify the move:
I tried (cloned in /home/travis/bitcoin): cd bitcoin
FILE_ENV="./ci/test/00_setup_env_amd64_qt5.sh" ./ci/test_run_all.sh This fails at the configure step:
It may have gotten poluted from a previous run, so I tried purging docker instances and nuking the git repository:
Now it runs. Because Docker has root privileges, things very quickly turn into permission hell if you try to run more than one instance. As a followup, it would be nice if you can run all configurations with a single command (stopping if any fails). |
fa21737 ci: Add environment files for all settings (MarcoFalke) Pull request description: This moves all environment settings from travis to files in the ci folder. Now, it is possible to easily run each travis configuration with a single command. Top commit has no ACKs. Tree-SHA512: 989c6b62eb3839eb1fa5461e986496e9660167e2438a789c7588a6fee4f9c37b332782c010fe5c7de8f606bcf98dffb2481d2777cbce88f87cc9f0c42fb2d7fc
You can't run more than one ci instance on the repo at the same time.
I'll leave this as follow-up ;) |
I was running them in sequence. |
That should work as long as you run |
fa21737 ci: Add environment files for all settings (MarcoFalke) Pull request description: This moves all environment settings from travis to files in the ci folder. Now, it is possible to easily run each travis configuration with a single command. Top commit has no ACKs. Tree-SHA512: 989c6b62eb3839eb1fa5461e986496e9660167e2438a789c7588a6fee4f9c37b332782c010fe5c7de8f606bcf98dffb2481d2777cbce88f87cc9f0c42fb2d7fc
This moves all environment settings from travis to files in the ci folder. Now, it is possible to easily run each travis configuration with a single command.