tools-iuc: List of tools that fail containerized tool tests

Hello IUC,

Tl;DR:

Help us fix tool tests!

we would like to make sure that our tools are well tested and working in the widest range of deployment scenarios possible. And as you may have noticed, tool dependency installation from Conda may break (or be fixed!) as time passes due to dependency-of-a-dependency upgrades, newer/older Conda versions etc.

To make sure that our tool wrappers will work on a wide range of deployments it is important that we include all dependencies that a tool has (i.e include coreutils if a wrapper uses paste, include sed if a wrapper uses sed, include python if a wrapper calls a python script). One way to make sure this is the case is to run tool tests in a minimal container that does not contain any software except the one listed in our tool wrappers <requirements/> tag set.

We also currently build containers for all IUC tools as well as other tool repositories listed in https://github.com/galaxyproject/planemo-monitor, but so far we are not testing that tool runs actually succeed in these containers. For dependencies (and dependency combinations) that are not available as a downloadable container Galaxy can build containers when needed. This functionality is also available via planemo test --biocontainers.

We have set up a github workflow that tests all IUC tools using planemo test and the --biocontainers flag. The test run can be seen here: https://github.com/mvdbeek/tools-iuc/commit/529a26943046ca80b18bccae31021db5c317eb7e/checks?check_suite_id=331921644 And a html report of only the failing tests is here: https://mvdbeek.github.io/iuc-tool-test-results/ Note also that the tool tests run against python 3.7, so this could be another class of errors we may need to fix (should concern only the cheetah templating).

The list of tools with failing tests is the following:

If you’re currently working on one of these tools write your name under the tool, so that we avoid duplicating our work

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 42 (41 by maintainers)

Commits related to this issue

Most upvoted comments

All of the tools that can be fixed are fixed now, so I think we can close this. If you want to check if a tool is currently passing you can check https://github.com/galaxyproject/tools-iuc/actions?query=workflow%3A"Weekly+global+Tool+Linting+and+Tests" which is run weekly.

All or nothing! 🎉

Yes, but we need to understand the problem at first. For conda-forge we now have: fonts-conda-ecosystem … but no clue if this fixes our problem. Just something to look out for and ping me if you see it … goenrichment seems to have this exact problem.

One error-class that we should look out for is that all Java based tools that do some plotting might miss some fonts in the container. Keep an eye on this.

Hi, will try to take care of stacks(2) samtools and maxbin2.

PR: Should be done against iuc-repo? Will IUC testing then be in the simple container?