Open nickp60 opened 1 year ago
@nickp60 I was long due to comment on this issue.
Project-level merge runs after each analysis is completed (FAILED
or SUCCEEDED
) And is only submitted when no other analyses on the project is pending to finish (SUBMITTED
or STARTED
), if there are pending running analyses the merge is skipped.
I believe what you're seeing is that it runs when FINISHED
are available. We should add FINISHED
to pending status:
status__in="STARTED,SUBMITTED,FINISHED",
Description
When running
isabl process-finished
to complete a group of analyses, the project-level merge logic is run after each is completed. This is very time consuming, and would probably be best run after the command is finished to avoid wasting resources.What I Did
isabl process-finished -fi projects 20
Isabl runs the merge analysis after processing each analysis.New feature
Perhaps a fix could be to disable
trigger_analyses_merge
when executingpatch_instance
from the process-finished command. Instead, the process-finished cmd could keep a list of analysis keys, individuals, and projects affected by the query and run those after updaing the status