galaxyproject / galaxyproject/galaxy
output collection of failed job shows no info about the (failed) job that created it
- Dominant language
- Python
- Stars
- 1.9k
- Forks
- 1.2k
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 169
Description
When a tool (such as [faSplit](https://toolshed.g2.bx.psu.edu/repository?repository_id=b4b3e22cd2cd74ea)) that generates a collection (in this case a collection of type list) fails, it leaves a red collection but no info on the underlying failed job. The failed collection is empty.

This is consistent with the usual collection behaviour, i.e. being created as containers for datasets that are themselves created by jobs, but is problematic because there is now no straightforward way to debug the tool failure.
Contributor guide
Research direction
Reproduce the empty failed collection with the linked faSplit tool and inspect how the collection and its underlying failed job are represented. The issue names no files or tests, so trace the collection output and failure display paths first; done means the failed collection provides a straightforward way to view the job failure information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100