Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating workflows/epigenetics/consensus-peaks from 1.1 to 1.2 #527

Conversation

gxydevbot
Copy link
Contributor

Hello! This is an automated update of the following workflow: workflows/epigenetics/consensus-peaks. I created this PR because I think one or more of the component tools are out of date, i.e. there is a newer version available on the ToolShed.

By comparing with the latest versions available on the ToolShed, it seems the following tools are outdated:

  • toolshed.g2.bx.psu.edu/repos/iuc/samtools_view/samtools_view/1.15.1+galaxy2 should be updated to toolshed.g2.bx.psu.edu/repos/iuc/samtools_view/samtools_view/1.20+galaxy3
  • toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.11+galaxy1 should be updated to toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.24.1+galaxy0
  • toolshed.g2.bx.psu.edu/repos/iuc/samtools_view/samtools_view/1.15.1+galaxy2 should be updated to toolshed.g2.bx.psu.edu/repos/iuc/samtools_view/samtools_view/1.20+galaxy3
  • toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.11+galaxy1 should be updated to toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.24.1+galaxy0
  • toolshed.g2.bx.psu.edu/repos/iuc/samtools_view/samtools_view/1.15.1+galaxy2 should be updated to toolshed.g2.bx.psu.edu/repos/iuc/samtools_view/samtools_view/1.20+galaxy3
  • toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.11+galaxy1 should be updated to toolshed.g2.bx.psu.edu/repos/iuc/multiqc/multiqc/1.24.1+galaxy0

The workflow release number has been updated from 1.1 to 1.2.

@lldelisle
Copy link
Contributor

I am waiting for the autoupdate of the other workflows of the directory.

@gxydevbot gxydevbot changed the title Updating workflows/epigenetics/consensus-peaks from 1.1 to 1.2 Updating workflows/epigenetics/consensus-peaks from 1.1 to 1.2 Sep 24, 2024
@gxydevbot
Copy link
Contributor Author

There are new updates, they have been integrated to the PR, check the file diff.

@gxydevbot gxydevbot force-pushed the workflows/epigenetics/consensus-peaks branch from 11991a7 to fe9d314 Compare September 24, 2024 14:01
@lldelisle lldelisle merged commit 7a1919b into galaxyproject:main Sep 24, 2024
6 checks passed
@mvdbeek
Copy link
Member

mvdbeek commented Sep 24, 2024

Attention: deployment skipped!

https://github.com/galaxyproject/iwc/actions/runs/11022045695

1 similar comment
@mvdbeek
Copy link
Member

mvdbeek commented Sep 24, 2024

Attention: deployment skipped!

https://github.com/galaxyproject/iwc/actions/runs/11022045695

@lldelisle
Copy link
Contributor

lldelisle commented Sep 25, 2024

I have a Could not get container description for tool 'toolshed.g2.bx.psu.edu/repos/iuc/bedtools/bedtools_bamtobed/2.31.1+galaxy0' (https://github.com/galaxyproject/iwc/actions/runs/11022045695/job/30611417989#step:6:7743) while bedtools has not been upgraded and in the CI of the PR I got https://github.com/galaxyproject/iwc/actions/runs/11021689499/job/30629513965#step:6:9598 galaxy.tool_util.deps.container_resolvers.mulled DEBUG 2024-09-25 08:08:38,705 [pN:main.1,p:5350,tN:LocalRunner.work_thread-3] Image name for tool toolshed.g2.bx.psu.edu/repos/iuc/bedtools/bedtools_bamtobed/2.31.1+galaxy0: mulled-v2-8186960447c5cb2faa697666dc1e6d919ad23f3e:caa33073524aca7a4919ccd6ac088104e51e441a. Any idea?

@mvdbeek
Copy link
Member

mvdbeek commented Sep 25, 2024

That's quay.io failing to respond to the request that lists container images. A rerun will likely work

@lldelisle
Copy link
Contributor

OK, I run it twice but let's hope at the end it will work.
Thanks

@lldelisle
Copy link
Contributor

The third time was the good one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants