CI doesn't produce useful stacktraces when pypy3 finishes first. #1331
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 #1276 (comment)