Non-deterministic segfault of tests with Z3 in Travis
See original GitHub issueI noted that the builds having the z3 solver can non-deterministically yield a segfault on Travis.
I tried to reproduce the problem locally even using the docker Travis image with no luck.
We could try two different strategies here:
- Update Z3 to a newer nightly build and see if the problem goes away
- Try to update the libstdc++ of the travis image (it is more a feeling than a suspect, but in my local experiment with the
quay.io/travisci/travis-python
docker image I had to update this to make Z3 work at all)
Issue Analytics
- State:
- Created 6 years ago
- Comments:22 (16 by maintainers)
Top Results From Across the Web
Non-deterministic behaviour of Z3_mk_solver_for_logic ...
In this issue on pysmt (link) we have identified a possible bug in the Z3_mk_solver_for_logic python API. The z3.z3core.
Read more >Non-deterministic segfault (only triggered on GitHub Actions ...
I'm encountering a strange segfault error in my package tests that appears to be non-deterministic, and is only triggered during CI with GitHub...
Read more >Unexpected Segmentation fault for python project
Hi, For the past few days, our tests stopped working with Segmentation Fault. We are running out ideas to fix it, after clear...
Read more >Recent changes — Coq 8.12.1 documentation - GitHub Pages
Fixed: The sorting order of the timing script make-both-time-files.py and the target print-pretty-timed-diff is now deterministic even when the sorting ...
Read more >Changelog.md · 7aa7e708f9e889cc0b0529654b0d2ae4bdaa153c ...
SMTChecker: Fix internal error when trying to generate counterexamples with old z3. SMTChecker: Fix segmentation fault that could occur on certain ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@marcogario Just to clarify: the issue is now fixed on the pysmt side with the workaround in #713. @Hook25 (many thanks!) posted the issue upstream, if/when Z3 fixes the issue we can get rid of the workaround.
I think I finally isolated the issue! On #564 I disabled the test
test_tactics_z3
intest_solving.py
and since then I got no more segfault errors. This smells of victory because the test actually accesses the internal Z3 nodes and applies a custom tactic, so it may very well mess up the ref/deref system.I still have no clear explanation/fix of the problem, but I’ll have a look asap.