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
Currently there are two helper methods for checking output files:
Find all files with a pattern and generate an md5 (when contents stable between tests)
Find all files with a pattern and check existence by file name (when contents are unstable between tests)
While the of unstability fallback is good e.g. binary files, it's not as good as checking inside a file for consistent contents (E.g. when maybe it's only a single timestamp inside the file is unstable).
An intermediate check is to check for certain strings, e.g. maybe 'SUCCESSFUL RUN' at the end of a log.
It would be nice to have a function that does the same as the two existing methods, but with the string checking functionality.
The text was updated successfully, but these errors were encountered:
jfy133
changed the title
Function to recursively check all files with a suffix for a specific string
Function to recursively check all detected files for a specific string
Oct 11, 2024
For simple cases, I think this can actually be done without any new functions using groovy to iterate the files returned by the existing getAllFilesFromDir and the existing nf-test file support:
@TCLamnidis Tom wrote a load of code, and then deleted it because apparently a whole separate function might be overkill... maybe you can try the above with the eager tests?
Currently there are two helper methods for checking output files:
While the of unstability fallback is good e.g. binary files, it's not as good as checking inside a file for consistent contents (E.g. when maybe it's only a single timestamp inside the file is unstable).
An intermediate check is to check for certain strings, e.g. maybe 'SUCCESSFUL RUN' at the end of a log.
It would be nice to have a function that does the same as the two existing methods, but with the string checking functionality.
The text was updated successfully, but these errors were encountered: