search

test262-fyi / test262.fyi

Daily runner of test262 for many engines
https://test262.fyi
MIT License
75 stars 12 forks source link

Result history #13

Open linusg opened 1 year ago

linusg commented 1 year ago

You already know what this is about, just making a tracking issue :)

The way LibJS does it is just appending to an ever growing JSON file, which in hindsight is not really that scalable - especially not when you have results for 10 different engines.

This could either be tracking the total score, or even per-file results to see when certain engines implemented certain features.

CanadaHonk commented 1 year ago

Basic history tracking (overall, not per file/dir) was added a few days ago in e4a76f4d7c3dadd02e904cc1c9c75b7c1adef5f9. No graph yet as collecting data for a while first :)

linusg commented 1 year ago

Hmm, it appears that this appends a new entry every time an engine finishes, which could make this grow rather quickly - is that avoidable?

Agreed that per-file is overkill. FYI I've set up a daily mirror of the various JSON files at https://files.linus.dev/test262.fyi, and I'll probably keep that going for a while - so if there's any data you want to backfill, feel free to take it from there.

CanadaHonk commented 1 year ago

Was a bug - just rewrote it (lol) and should be much future-proof-ier now :) Thanks for info and mirror!

CanadaHonk commented 1 year ago

Also to note, thanks to @linusg, we can likely use historical data from test262.report for The Graph™!