do we want to try this one?

What’s the version change fix you need?

We noticed something weird

Any link to the issues?

@Rike Hanssen knows it all

I haven't created an issue yet, cause I don't know what for. But basically: deepvariant appears to be working fine on the small CI tests, when I run it on AWS it breaks for the full size tests. Now before someone says it's fusions fault, I have tried: • Basic Fusion CE •

scratch=true

-> disabling the streaming • Point the deepvariant process to a non fusion queue all failed. Last thing I can think of trying is to run the entire pipeline on the non-fusion queue. This has failed so far because we don't have auto-expandable storage anymore and I haven't configured bug enough boot disk size yet. But also I am not very hopeful this will fix it. As far as I can tell, the container hasn't changed to master. and I also don't think the container on docker hub had an update (failure on our part here btw to not have moved that container to our quay.io) So I am pretty stumped. I am scared it's somewhere deep down AWS AMI changes or sth like that. Claudio also had no good idea so far.

Hmm I will look at this tomorrow in more detail if I get the chance but I can tell you I am currently running DeepVariant in my own pipeline on batch with the 1.10.0 image from the Google docker and I haven't had any issues like this. My AMI should be the latest one too.

ok great. This is making me a little less anxious about the release

I was about to say conflicts

🙏 cloud.seqera.io/orgs/…/logs

Oh yeah, I noticed it was running