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
charliecloud: 0.12 -> 0.18 #95888
charliecloud: 0.12 -> 0.18 #95888
Conversation
Thank you! Greatly appreciate our packagers. :) |
Co-authored-by: Daniël de Kok <me@github.danieldk.eu>
bf602e4
to
0779ea1
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.
Thanks for all the work you have put in! I think the derivation has become much more robust as a result.Two final requested changes:
- Add
sudo
to the wrapper. - Remove the test from this PR, with a suggestion of you the test could be structured to automatically run by Hydra/ofborg.
Then it should be ready for merging.
@@ -0,0 +1,42 @@ | |||
#/bin/env bash |
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.
Having a test is nice, but it is probably not so useful when they are not run automatically. Such tests tend to get stale over time.
What you could do in another PR when this one is merged, if you are interested in putting in the time, is write a NixOS test. If you are not familiar with NixOS tests, they run in a VM and therefore provide the opportunity to set up a real testing environment. E.g., you could automatically set up a Docker registry in the test (there is already a NixOS test that does this, that can be used for inspiration, nixos/tests/docker-registry.nix
) and then test charliecloud against that registry.
Then that test could be added to passthru.tests
in this derivation and it would be run automatically by ofborg and Hydra.
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.
Okay! I wrote the test. I used dockerTools.examples.nix
as a base image. Hope this is fine.
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.
Great! I amended the commit, seems that you forgot to commit the change to alltests.nix
. So, should be good now.
Let's see if ofborg is also happy.
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.
Oh, yes sorry. Ofborg has passed the passthru.tests.charliecloud
test anyway, I checked that
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.
It didn't, it just skips that step if passthru.tests
cannot be properly be evaluated.
30260e0
to
96e0cbe
Compare
@ofborg build charliecloud |
96e0cbe
to
1601ff7
Compare
@ofborg eval |
Many thanks for your help @danieldk ! |
Thanks for packaging Charliecloud!! Very much appreciate your efforts. And please do let us know if upstream can do anything to make you work easier. |
Motivation for this change
An important bug has been fixed https://github.com/hpc/charliecloud/pull/826/files
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)