ethereum / ethereum/execution-specs
CI doesn't produce useful stacktraces when pypy3 finishes first.
Open
A-spec-tools
C-feat
E-easy
P-medium
stale
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 505
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 116
Description
Hm, looks like because the pypy tests finish first, and have backtraces turned off, you don't get a lot of useful information from CI—because the py3 environment gets cancelled.
Options for a solution might be:
- Enabling backtraces for pypy3 (though this might cost more memory);
- Allowing py3 to finish even if pypy3 fails.
_Originally posted by @SamWilsn in https://github.com/ethereum/execution-specs/issues/1276#issuecomment-3085139647_
Contributor guide
Assessment
This issue has not been assessed yet.