Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve schema evolution testing #530

Closed
11 tasks done
makortel opened this issue Apr 10, 2023 · 0 comments
Closed
11 tasks done

Improve schema evolution testing #530

makortel opened this issue Apr 10, 2023 · 0 comments

Comments

@makortel
Copy link
Collaborator

makortel commented Apr 10, 2023

Motivated by cms-sw/cmssw#41246

For each class that is part of RAW data tier, craft a test where we read in a ROOT file (stored in https://github.com/cms-data/) with one Event that has an object that is "fully filled" (all member containers have at least one element). Add a README.md for each DataFormat package holding such class explaining the test, and a policy that whenever such class is updated, a new test file needs to be added whenever the class or any of its contained classes are changed. Maybe also craft a test where one cmsRun writes a file with the object and another reads file, both in the same release. Currently RAW data tier includes

Add similar tests for Scouting data formats

Add similar tests for RAW' data formats

Finally

Not really about schema evolution testing, but to track in this issue the earlier milestone on "responding to schema evolution failure"

Progress tracked in https://github.com/makortel/framework/milestone/31

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants