You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's a useful sanity check when we update the .rrd:s in the test set, that the new ones covers approximately the same things
Produce the same visuals? Difficult to get right
What .rrd files?
Snippets?
Examples?
One .rrd file containing all known components/archetypes/datatypes?
When and how do we add more .rrd files to the test set?
What if something does break?
We do not yet promise full backwards compatibility, but any CI failure regarding this should be a red flag, and we should only accept it (and upload a new .rrd file) if we are really ok with this breaking change.
The text was updated successfully, but these errors were encountered:
emilk
changed the title
Add data files to git lfs to test backwards compatibility
Add .rrd files to git lfs to test backwards compatibility
Feb 25, 2025
We want to have automated tests to make sure we have backwards compatible chunk loaders.
Ideally we should add .rrd files to
git lfs
for all previous versions of all components and archetypes.What to test?
rerun rrd verify
rerun rrd verify
#9128rerun print
output?What .rrd files?
When and how do we add more .rrd files to the test set?
What if something does break?
We do not yet promise full backwards compatibility, but any CI failure regarding this should be a red flag, and we should only accept it (and upload a new .rrd file) if we are really ok with this breaking change.
The text was updated successfully, but these errors were encountered: