test: ensure apt *and* python c extensions work properly #1103
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.
I ran into a tricky problem:
apt
in this caseapt
(and, more importantly, I'm assuming many other system commands) with the following error:This error can be fixed by reverting the mutated
LD_LIBRARY_PATH
from:to:
Did some research:
I'm new to nix. It seems like creating a bespoke shell env with
LD
modified is the way to go, but that wouldn't actually solve this issue sinceLD_LIBRARY_PATH
would be inherited by the py process and therefore passed to the shell (unless the modifiedLD
only applies to package installation, but I'm confident that would work either.In any case, I'm curious what folks think here. I added a failing test to work off of, but unsure of the best solution.
Docker container success assertion
In investigating this, I found that the docker container execution is not asserted to be successful. This feels like a good change
to make for all containers to avoid swallowing otherwise important errors.