-
Notifications
You must be signed in to change notification settings - Fork 111
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
CI fails with crashing server on Python 3.3, 3.6 #788
Labels
bug
unintented behaviour in tlsfuzzer code
Comments
I've disabled gmpy and gmpy2 on py3.3 for now, lets see if it helps |
tomato42
changed the title
CI fails with crashing server on Python 3.3
CI fails with crashing server on Python 3.3, 3.6
Feb 9, 2022
It also sometimes crashes on 3.6: https://github.com/tlsfuzzer/tlsfuzzer/runs/5127335500?check_suite_focus=true |
multiple crashes on py3.6 again, with m2crypto installed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
System Information
Problem description
server sometimes crashes during scripts_retention.py with -11 (SIGSEGV)
Describe how to reproduce the problem
run the CI test suite on python 3.3
Expected behaviour
consistently passing test suite
Include errors or backtraces
logging doesn't capture the backtrace :/
Additional context
crashed when running the
test-certificate-request.py
test andtest-certificate-malformed.py
while the runs on py3.3 don't use m2crypto, they do use gmpy and gmpy2
The text was updated successfully, but these errors were encountered: