Closed gq1 closed 1 month ago
nf-core lint
overall result: Passed :white_check_mark: :warning:Posted for pipeline commit 947706f
+| ✅ 131 tests passed |+
#| ❔ 21 tests were ignored |#
!| ❗ 1 tests had warnings |!
https://cloud.seqera.io/orgs/sanger-tol/workspaces/github-ci/watch/5VUhThWsZpmaJm The job completed successfully now.
Oki, thanks. In that case, to avoid the risk of other pipelines failing for the same reason. Should we apply the plan you discussed last time ? i.e. change the TOWER_COMPUTE_ENV
value to point at the 4 GB environment.
That way, all pipelines are changed at once.
From the perspective of compute efficiency, I'd be OK with that because it is justified and limited (there aren't that many Tower jobs coming through)
Oki, thanks. In that case, to avoid the risk of other pipelines failing for the same reason. Should we apply the plan you discussed last time ? i.e. change the
TOWER_COMPUTE_ENV
value to point at the 4 GB environment. That way, all pipelines are changed at once.
Yes, can you update? And then we can close this PR and delete the new repo level secret I added this morning.
Changed. At the same time I've renamed the environments in Tower to be explicit about the RAM (rather than "small", "large")
Repo level secret deleted and no action for this PR itself.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).