The complete Test262 test/ run at the recorded Attar AOT boundary. Raw runner results stay separate from accepted product exclusions.
Non-PASS results remain. The counts are the original runner IDs; nothing is reclassified.
| Result | Variants | Share |
|---|---|---|
PassPASS | 69,656 | 67.88 % |
Runtime failureRUNTIME | 21,141 | 20.60 % |
Negative result unverifiedNEGATIVE_UNVERIFIED | 8,392 | 8.18 % |
Compile failureCOMPILE | 2,448 | 2.39 % |
Module pipeline boundaryMODULE | 842 | 0.82 % |
Unexpected accepted negativeNEGATIVE_ACCEPTED | 63 | 0.06 % |
Negative phase mismatchNEGATIVE_PHASE | 27 | 0.03 % |
Async completion incompleteASYNC_INCOMPLETE | 48 | 0.05 % |
TimeoutTIMEOUT | 2 | 0.00 % |
INTENTIONALLY_UNSUPPORTED marks non-PASS variants that match an accepted Attar language or platform boundary. The label explains the scope. It changes no raw result ID and never counts as PASS.
Rules overlap, so the per-rule counts do not add up to the union. The 48 async eval rows stay ASYNC_INCOMPLETE in the raw run.
This is a full corpus measurement for the pinned Test262 checkout. It is not a claim that Attar supports all JavaScript.
Raw PASS is the measured execution.
The overlay separates accepted exclusions from work that still needs a fix or more evidence.
Web Platform Tests and packaged application acceptance are measured on their own; see the compliance overview.
The JSON files carry public test names, statuses and aggregate identities. They carry no local paths and no failure detail text.