When something goes wrong in a test, we sometimes get ambiguous error messages like 'socket.timeout' or unclear stack traces when we execute scripts in a sandbox. This is a tracking bug to improve error reporting so instead of getting confusing messages, we can get a better idea of where the error is coming from.
[mass update] Setting Harness bugs to all P3
Priority: -- → P3
All dependencies of this bug have been fixed. Also I don't see any strange output anymore.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.