Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Segfault when using --run with --jobs sys
See original GitHub issueHiya! Working on dockerizing Coconut in PR #183, and may have come across a segfault bug?
In this commit, I’ve managed to minimize the developer docker container image from 600+MB to 389.2MB, but there’s ONE test which fails.
Here’s a gist showing what happens when I tried to briefly look into it.
(There’s two runs of the tests in that gist, first run fails 6 tests due to tests having hardcoded use of the python binary, which was fixed by symlinking the python3 binary on line 2056).
@evhub Would you have a chance/capacity to help me look into whether this is Coconut’s fault, or the minimized alpine base container image’s fault?
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@x10an14 It’s only a temporary solution, but for right now just change
["--run"]to["--run", "--jobs", "0"]in https://github.com/evhub/coconut/blob/develop/tests/main_test.py#L183.'Aight! How do I go about modifying this correctly to run without segfault on Docker, with changes implying the least maintenance?
It’s currently the command
make testthat invokes the--jobs sys.Do you have any suggestion for how to avoid that invocation, with the least required maintenance (as opposed to just utilizing the makefile rules?).