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
I recently worked on a test that involved using a setup step to untar a rather large database (~8 GB), see here. These tests were causing the GitHub runners to fail because they ran out of space. So that's when I discovered that files for an identical setup step are staged and results generated individually. Leading to more than 24 GB space being used.
In pytest, there is a concept of fixture scope, which can be per function, module, or the entire test session. Results of fixtures are cached and reused accordingly. I think, that'd be a fantastic feature for nf-test as well.
The text was updated successfully, but these errors were encountered:
This would be awesome, having the same issue as with @Midnighter !
I actually had assumed that the global setup meant that the output would be reused across each test, and only learnt today that that wasn't the case - so it would make more sense 'intuitively' to me too :)
I recently worked on a test that involved using a setup step to untar a rather large database (~8 GB), see here. These tests were causing the GitHub runners to fail because they ran out of space. So that's when I discovered that files for an identical setup step are staged and results generated individually. Leading to more than 24 GB space being used.
In pytest, there is a concept of fixture scope, which can be per function, module, or the entire test session. Results of fixtures are cached and reused accordingly. I think, that'd be a fantastic feature for nf-test as well.
The text was updated successfully, but these errors were encountered: