if you update the full size yml with this: <github...
# variantbenchmarking
r
if you update the full size yml with this: github.com/nf-core/tools/pull/4501/changes it should get passed the error or alternatively merge in the template update
🙌 1
thanks 1
k
Hello Rike, I added the changes to my 'dev' and relaunch the pipeline but it didnt work.. What can I be missing :D
r
can you please link me the failing action or pipeline run
k
I think aws configuration is not being copied to platform
r
can you link the action run please
k
but I triggered the run myself this time
it wasnt automated
r
it's shown as skipped? where is the execution that triggered the failing run in platform
k
I relaunch the pipeline from the platform cloud.seqera.io/orgs/…/watch
r
but how did you get it there? we need to figue out why the action is not adding the config update to the API call to platform
k
I am confused 😄 I rerun this one cloud.seqera.io/orgs/…/logs (which was automatically pushed from github actions)
r
ok so It is not picked up by the github action
Copy code
workspace_id: 59994744926013
    access_token: ***
    compute_env: aws_ireland_fusionv2_nvme_cpu_spot
    revision: dev
    workdir: <s3://nf-core-awsmegatests/work/variantbenchmarking/work-dev>
    nextflow_config: plugins {
    id 'nf-slack@0.5.0'
  }
are you sure that this was on a git sha that had that commit in already?
works here: cloud.seqera.io/orgs/…/configuration
Copy code
plugins {
  id 'nf-slack@0.5.0'
  id 'nf-schema@2.7.2'
}
slack {
  enabled = true
  bot {
    token = 'xoxb-482441985799-10537029949076-t09RU1r1Z3dgMeKY1vWbd8i9'
    channel = 'variantbenchmarking'
  }
  onStart {
    enabled = false
  }
  onComplete {
    message = ':white_check_mark: *variantbenchmarking/test_full* completed successfully! :tada:'
  }
  onError {
    message = ':x: *variantbenchmarking/test_full* failed :crying_cat_face:'
  }
}
🤷
k
🫠 indeed
latest push I had to 'dev' was yesterday and I rerun it today.. so it must be there already
r
ok the run you linked was from 5 days ago. Mayvbe double check the shas on when you added the plugin and merged it to dev just to be sure, but I don't see anything to be concerned about
k
that was the original one tho
r
git blam e says it was merged 2 days ago