Duke-GCB / Duke-GCB/bespin

allow users to debug failed jobs

Open
#8 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Provide a way for users to determine why a Bespin job failed.

The following data may be useful in determining what went wrong:
- workflow runner logs
- intermediate/output data
- input data
- system data
- workflow and job order

For a job that failed the `workflow runner logs` and `intermediate/output data` only exist on the pvc/volume associated with the job.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.