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
slurm: 17.11.9-2 -> 18.08.0-1 #45925
Conversation
@GrahamcOfBorg test slurm |
Success on x86_64-linux (full log) Attempted: slurm Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: tests.slurm Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: slurm Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: tests.slurm Partial log (click to expand)
|
@GrahamcOfBorg build python27Packages.pyslurm python36Packages.pyslurm |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: python27Packages.pyslurm, python36Packages.pyslurm Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: python27Packages.pyslurm, python36Packages.pyslurm Partial log (click to expand)
|
Looks like |
Failure on aarch64-linux (full log) Attempted: python27Packages.pyslurm, python36Packages.pyslurm Partial log (click to expand)
|
|
Yes, unfortunately |
I think that |
@veprbl I agree. The choice in
|
I suggest opening an upstream issue to support latest slurm.
|
Hi, I help to maintain PySlurm. The versioning could certainly be improved. The version checks are sanity checks to make sure that PySlurm is compiled against the right version of Slurm. This was necessary a few years back when there would be changes to Switching between major or minor versions almost always requires updates to PySlurm that match the changes to the slurm headers and any code in the API that is wrapped or referenced by PySlurm. I updated the test container to 18.08.0 over the weekend and I've started to update PySlurm for 18.08.0-1. |
@giovtorres Thanks! |
slurm 18.08 requires ClusterName to be set (set to default).
There's still a merge conflict |
The conflict is resolved. I did a rebase. Just added a new version of pySlurm. It should build now properly. |
@GrahamcOfBorg build python37Packages.pyslurm |
don't have python37 yet 😄 |
No attempt on x86_64-darwin (full log) The following builds were skipped because they don't evaluate on x86_64-darwin: python36Packages.pyslurm Partial log (click to expand)
|
We actually do: /nix/store/q38ddqq7nz82lv6z0arl5wdk9s3w3j96-python3-3.7.0 |
Success on x86_64-linux (full log) Attempted: python36Packages.pyslurm Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: python36Packages.pyslurm Partial log (click to expand)
|
Failure on x86_64-linux (full log) Attempted: python37Packages.pyslurm Partial log (click to expand)
|
Timed out, unknown build status on aarch64-linux (full log) Attempted: python37Packages.pyslurm Partial log (click to expand)
|
Is this ready to merge? (If you like to work on python37 support, that should probably be a separate PR) |
Yes, I would say it is ready. Python 3.7 seems to be very experimental as
of now. I couldn't even find hydra builds.
…On Sun, 9 Sep 2018, 11:26 xeji, ***@***.***> wrote:
Is this ready to merge? (If you like to work on python37 support, that
should probably be a separate PR)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#45925 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AZPmldkpcLlUAB17FPC5bpNTibhncSpFks5uZN7egaJpZM4WWa5m>
.
|
Motivation for this change
Update
slurm
and adapt nixos module.Things done
clusterName
to module.slurm 18.08 requires
ClusterName
to be set.sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)