Skip to content

Add a basic script to validate metadata content

In the context of recent examples of inconsistencies in the in-file metadata content due to interference of jobs running in containers (ATLASG-2686, AFT-711), this MR adds a script to check the sanity of the metadata:

  • check if the number of events from EventStreamInfo equals to the number of entries in DataHeader
  • check if /TagInfo metadata contains inconsistent information
  • check presence of FileMetaData
  • check uniqueness of run/lumiblock/event number per event and against the summary in the FileMetaData

This is of course non-exhaustive, so I'm open to suggestions regarding other checks.

I've added this to run in one of the ART tests, please let me know if this is sufficient and correct.

/cc @gemmeren @amete

Merge request reports