You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2019. It is now read-only.
Something about the Travis VM environment changed to cause the Python 3 tests to always fail. This is not related to a code change, the old revisions that were passing Travis are now failing. I installed a Trusty VM locally, and cannot reproduce the issue. So Travis changed something about their VM environment that caused the breakage.
The errors are all like:
AssertionError: assert not 'Failed to PTRACE_PEEKDATA at 0x10: Input/output error\n'
This indicates a null pointer dereference via ptrace. Basically ptrace has a pointer to some struct and is trying to dereference a field in the struct, but the struct pointer is null.
Ideally I could get an actual VM image used by Travis so I could debug locally. Otherwise I can just try adding lots of sanity checks to the code and run many builds, and try to work things out backwards. I'm worried though that if the error is something like the ELF symbol table is different in some unusual way on Travis, that it would be extremely time consuming to debug the issue using this approach.
The text was updated successfully, but these errors were encountered:
Something about the Travis VM environment changed to cause the Python 3 tests to always fail. This is not related to a code change, the old revisions that were passing Travis are now failing. I installed a Trusty VM locally, and cannot reproduce the issue. So Travis changed something about their VM environment that caused the breakage.
The errors are all like:
This indicates a null pointer dereference via ptrace. Basically ptrace has a pointer to some struct and is trying to dereference a field in the struct, but the struct pointer is null.
Ideally I could get an actual VM image used by Travis so I could debug locally. Otherwise I can just try adding lots of sanity checks to the code and run many builds, and try to work things out backwards. I'm worried though that if the error is something like the ELF symbol table is different in some unusual way on Travis, that it would be extremely time consuming to debug the issue using this approach.
The text was updated successfully, but these errors were encountered: