https://nf-co.re logo
Join Slack
Powered by
For the next release of ampliseq I wanted to test ...
# aws-megatests
d
For the next release of ampliseq I wanted to test whether AWS runs are still fine. I submitted 
nf-core AWS test
on dev (not "full size tests" to minimize test costs), but it failed: github.com/nf-core/ampliseq/…/110261116126. I have no idea of Platform/AWS, so I am a bit lost. Shall I just re-try? Shall I run 
nf-core AWS full size tests
on dev instead? Edit: as far as I see no run was triggered on platform
r
yes please retry, we are working on updating this action so it's more stable.
👍 1
if it doesn't want to work at all, I'll bump your permissions on platform so you can run from there directly (another hackathon task to give everyone better scoped permission)
d
Thanks, submission worked. However, unexpectedly, the error I get is
Copy code
Essential container in task exited

N E X T F L O W  ~  version 26.04.6
Pulling nf-core/ampliseq:d24c196d9be624a51cba51db6c9a8fdea04f0753 ...
 downloaded from <https://github.com/nf-core/ampliseq.git>
Downloading plugin nf-schema@2.7.2
Launching `<https://github.com/nf-core/ampliseq>` [boring_ptolemy] - revision: d24c196d9be624a51cba51db6c9a8fdea04f0753
ERROR ~ Script compilation error
- file : /.nextflow/assets/.repos/nf-core/ampliseq/clones/d24c196d9be624a51cba51db6c9a8fdea04f0753/main.nf
- cause: Unexpected input: '{' @ line 76, column 8.
   params {
          ^
1 error
NOTE: If this is the beginning of a process or workflow, there may be a syntax error in the body, such as a missing or extra comma, for which a more specific error message could not be produced.
 -- Check 'nf-2tHs72jnh4uXr9.log' file for details
But I cannot reproduce that locally (-profile test,aws_scratch) and it seems to me that there were no changes to aws files to the previous passing pipeline release 2.18.0 (release PR: github.com/nf-core/ampliseq/pull/1091). (I let an AI debug, but because I cannot reproduce it I dont think it can solve it.)
r
which nextflow version are you using locally?
d
nextflow version 26.04.6.12646
r
ah I think it might be a parser issue. Are you using the v2 syntax parser?
d
Yes I think I use v2 syntax parser.
Trying with v2 parser here
That run went further! (but not much 😬)
r
ok that worked failed for sth else: cloud.seqera.io/orgs/…/logs
yep it failed because the queue directive wasn't properly resolved. It's on my list of things to work on during the hackathon
😅 1
ok the v2 parser at the moment is not properly passed through the github action. So this will hit you again when you release/run the full size test. Only option today is to relaunch from platform and enable the parser there
I bumped your permissions, so hopefully you can do this yourself
d
Ok, I'll write a reminder to myself into the PR, thanks!
The release itself will need a few more days due to missing reviews, wanted to check in time whether the pipelines needs adjustments before release.
r
sounds good.
d
But cloud.seqera.io/orgs/…/logs unfortunately still fails, but doesnt seem to be a pipeline issue?
r
wth, no this means that the aws cli is not installed, which makes little sense cause Evangelos ran a pipeline on the same CE minutes ago. let me restart
facepalm I had relaunched it by setting a fusion enabled queue. I think this got it confused, because it on the other hand says fusion.enabled false. Let me try on the non-fusion queue
d
> I bumped your permissions, so hopefully you can do this yourself Thanks! I had a look but I dont now how to do that. I attempted to relaunched the failed run for release 3.0.0 but fail to modify the advanced settings for 
Enable Nextflow syntax parser v2
(its greyed out, I seem to be not able to modify any of the "advanced settings"). And that seems required, as far as I understood (as well as 
fusion.enabled false
).
Open in Slack
PreviousNext
Powered by