Revision 712be3d5b3524706be3dedfc653752afe41d05c8 authored by James Graham on 12 April 2018, 13:01:19 UTC, committed by James Graham on 12 April 2018, 17:16:55 UTC
Split the internal handling of errors during a test into two cases; INTERNAL-ERROR that is produced if there's an exception in the harness and ERROR that is for exceptions reported by the test. Both are still reported as ERROR to the user, but in the INTERNAL-ERROR case the runner is always restarted, just like EXTERNAL-TIMEOUT, since we assume that the internal state is compromised somehow.
1 parent e504871
File | Mode | Size |
---|---|---|
resources | ||
shared-renderer | ||
OWNERS | -rw-r--r-- | 17 bytes |
longtask-attributes.html | -rw-r--r-- | 1.9 KB |
longtask-in-childiframe-crossorigin.html | -rw-r--r-- | 2.2 KB |
longtask-in-childiframe.html | -rw-r--r-- | 2.3 KB |
longtask-in-externalscript.html | -rw-r--r-- | 1.6 KB |
longtask-in-parentiframe.html | -rw-r--r-- | 1.1 KB |
longtask-in-raf.html | -rw-r--r-- | 1.6 KB |
longtask-in-sibling-iframe-crossorigin.html | -rw-r--r-- | 1.5 KB |
longtask-in-sibling-iframe.html | -rw-r--r-- | 1.3 KB |
longtask-tojson.html | -rw-r--r-- | 2.7 KB |
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...