Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The default dmtcp should really be updated to a more recent version, as it is now a major version behind (and more). I'm a nix newbie, but I needed to use this soon so it seemed like a good chance to test out nix-build. So there are a few possible issues:
--replace
commands may or may not be working correctly. Without these, a python expression trying to access$USER
(e.g.os.environ['USER']
) fails; it seems likeUSER
is not being set correctly in the build environment. I attempted to hardcode it to the first build user for now (I guess this would work if it is possible to disable parallel builds). However, I have not checked that this works correctly because specifyingnix-build -A -K dmtcp
does not seem to leave the directory around, even though it now fails much later in the check phase.doCheck = true
. I haven't investigated these yet, but dmtcp seems to work well enough in general. I will try to investigate these more. Part of the problem could be I'm running in virtualbox for the moment.