Here is one run that completed: <https://cloud.seq...
# bamtofastq
f
Here is one run that completed: https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/2FhAY2PJew6LtH/v2/tasks with aws-nofusion-test-ireland and one after that one that did not https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/3Szj2hwYx9DL6P/v2/logs with aws_ireland_fusionv2_nvme_cpu - how should we continue? Is there a way to specifyy the compute environment, so that it works when I do the release again?
@Rike Hanssen any chance you can start a run again for the current dev branch @Maxime Garcia
because then we could do the release: https://github.com/nf-core/bamtofastq/pull/127 I even did the template merge
m
On, let me get back to a computer and I'll try it out
Rike is off today
BTW, you should be able to trigger it easily from https://github.com/nf-core/bamtofastq/actions/workflows/awsfulltest.yml
👍 1
failed again on
CHECK_IF_PAIRED_END
f
rike made it work with th aws-nofusion
🎉 1
@Rike Hanssen I forgot that we still need this full_size run thing fixed (fusion issues?)
r
ah right. Raising this internally
🎉 1
f
Ah @Edmund merged the release PR, does that mean we have a solution for how to display the test_full results on the nf-core website?
e
Hopefully?
I think it just shows whatever is in the bucket
r
yep, what are the issues with the result display?
f
its incomplete because its showing the results of the run with fusion https://nf-co.re/bamtofastq/2.2.0/results/bamtofastq/results-869832186b25d2ccbcd31d5f69edacc1ba32b718/ but we need the results of the run without fusion
m
Ok, so I have ideas
For #C062H82UCRG I helped @James Fellows Yates set up the megatest action on a CE without fusion. (For me it's a temporary fix until we resolve the solution properly).
But given that we already release. I'm guessing we might just want to delete these results and copy the other ones
👍 1
j
Isn't it suspicious a bunch of us are getting fusion issues fry
paranoid 1
m
You know my answer to that
f
Can someone take care of copying the proper results so that are being displayes correctly on the nf-core website? 🙂
🤔 1
e
@Famke Bäuerle They should auto populate
f
They dont because the full tests did not run. through because of the fusion issue so @Maxime Garcia suggested we copy the results of the no-fusion machine
j
Do you have the results directory of the working run @Famke Bäuerle? I might be able to transfer it tomorrow in a break
Or rather both the working run, and the one that is shown on the website
f
not sure i am afraid which one the one on the website is 😕 but this is one that completed: https://cloud.seqera.io/orgs/nf-core/workspaces/AWSmegatests/watch/2FhAY2PJew6LtH/v2/tasks Maybe there has to be another run so that the release version is correct in all version files though
j
It should say in the URL I think of the results Tab
j
Does this look correct?
image.png
👍 1
For the full run?
Because if so it's currently in a directory called
results-dev
- I can copy that over
Made on
f
yeah that seems like the run @Rike Hanssen started there were no changes except the merge from dev to main so I think we can use those
j
OK so I've moved
<s3://nf-core-awsmegatests/bamtofastq/results-dev/>
to
<s3://nf-core-awsmegatests/bamtofastq/results-869832186b25d2ccbcd31d5f69edacc1ba32b718/>
However for two files I got the following error:
🎉 1
image.png
(forgot to press enter sorry twitching eye )
I don't know if this is a limiation of the GUI though... @Maxime Garcia @Rike Hanssen any idea?
And it might take a few hours for the new results to display on the website
OK RTFM James
🤣 1
OK I need time to fuck around with my aws config... if Maxime or Rike have time they can do it in the meantime (I'm currently at a retreat and should be concentrating)
m
I'm at a conference. And presenting in an hour or so. But I can help this afternoon
It should be a simple aws s3 mv command
👍 1
j
OK fixed my config
Transfer done @Famke Bäuerle should be all good now - the website already shows the stuff transferred yesterday already 🙂
👍 1
The last two files should come later today on teh website