-
Notifications
You must be signed in to change notification settings - Fork 1
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
Make system testing github actions run faster #74
Comments
I have then added remaining 3 of the 4 system tests, and system testing workflow took about 1.5 hrs. Note that 4 system test jobs are run in serial fashion within a server/runner. In this scenario, first system test sets up necessary singularity contianers and therefore the remaining 3 system tests would not require setting them up again, as they are already present in the server. |
I had a discussion with James about this setup of 4 system testing jobs taking so long (1.5hrs). His recommendation was to run these jobs parallely instead of running them serially.
My concern is that such setup will end up using more resources in terms of setting up dependencies in 4 different servers and then running the system tests. This is not a great argument point though. |
Note that the major bottleneck atm is not setting up the depenencies but instead the quac itself. It takes ~16-20mins even if singularity containers were already set up. Among the jobs triggered by quac workflow, picard takes way longer to finish, which is the major cause of bottleneck. Here is the time-taken stats for quac workflow (exome mode, prior QC mode) run in slurm (cheaha). <style> </style>
In the github actions workflow for comparable system testing, |
Github actions for system testing ran for ~0.5hr, where we ran only one (WGS mode AND no prior QC data) of the 4 system tests. Here are the potential ways this can be run faster:
We discussed in the development drop-in hours about making it faster by caching the dependencies but it was decided it is not worthwhile atm to spend time on optimizing the workflow. Followed were discussed during this meeting:
The text was updated successfully, but these errors were encountered: