I found no open or closed issues for "Fatal Python...
# developmente
enough-analyst-54434
02/26/2021, 12:21 AMI found no open or closed issues for "Fatal Python error: Illegal instruction" but just hit it in a CI burn: https://github.com/pantsbuild/pants/issues/11605
Presumably thats an engine issue.
h
hundreds-father-404
02/26/2021, 12:22 AMdon't think I've seen this one
a
average-vr-56795
02/26/2021, 12:56 AMIIRC it's what happens when the engine panics?
average-vr-56795
02/26/2021, 12:57 AMIf CI isn't running with env
RUST_BACKTRACE=fulle
enough-analyst-54434
02/26/2021, 1:03 AMIt is.
a
average-vr-56795
02/26/2021, 1:04 AMI thought we had code to print out the rust portion of backtrace from the Python if that was set?
average-vr-56795
02/26/2021, 1:05 AMOh wait, this is forking a separate python process which runs a scheduler?
average-vr-56795
02/26/2021, 1:06 AMWe may want to add that to the test env, I guess?
average-vr-56795
02/26/2021, 1:06 AMWeird edge case, for sure :)
e
enough-analyst-54434
02/26/2021, 1:20 AMNo forking. If you look at the backtrace in the ticket, we enter the engine in the test here: https://github.com/pantsbuild/pants/blob/master/src/python/pants/testutil/rule_runner.py#L176
a
average-vr-56795
02/26/2021, 7:14 AMThen why do I see
/tmp/process-execution7mBvjsaverage-vr-56795
02/26/2021, 7:18 AMIt looks like we're forking to run pytest out of process, not clear that process has
RUST_BACKTRACEw
witty-crayon-22786
02/26/2021, 4:58 PMwe could probably set that globally: https://www.pantsbuild.org/docs/python-test-goal#setting-environment-variables
h
hundreds-father-404
03/03/2021, 7:42 PMI got this again in GitHub actions