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.

Sign up for GitHub

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

Jump to bottom

Hard to determine which dependency failed #345

Closed
iskandr opened this issue Feb 10, 2016 · 3 comments · Fixed by #361
Closed

Hard to determine which dependency failed #345

iskandr opened this issue Feb 10, 2016 · 3 comments · Fixed by #361
Labels
FAQ

Comments

@iskandr
Copy link
Member

iskandr commented Feb 10, 2016

Currently the Ketrew web UI requires manual recursive exploration of the dependency tree to determine why a target failed. I would prefer to just get a list of failing leaf nodes.
@smondet
Copy link
Member

smondet commented Feb 10, 2016

not-dependency-dead

@smondet smondet added the FAQ label Feb 10, 2016
@iskandr
Copy link
Member Author

iskandr commented Feb 10, 2016

Cool, thanks for pointing me to the help page. I'm still not clear how to use this to drill down into the failing components of a target.

@iskandr
Copy link
Member Author

iskandr commented Feb 10, 2016

For anyone else who comes across this thread: change your filter to (and (created-in-the-past (weeks 4)) (is-failed) (not (is-dependency-dead))). One caveat is that this shows you all failed nodes from any user-submitted job.

@smondet It would be nice to add a (child-of node-id) predicate to allow filtering for children of my one target of interest.

It would also be nice to have this filter setting be enabled via a button click on failed jobs (rather than having to type or copy it).

@iskandr iskandr mentioned this issue Feb 10, 2016
Open
smondet added a commit that referenced this issue Feb 12, 2016
@smondet
Add 2 entries to the FAQ.md
05949e9 
This adds 2 sections:

- “Trakeva Missing Backends” → fix #341
- “Which Dependency Failed?” → fix #345
@smondet smondet mentioned this issue Feb 12, 2016
Merged
smondet added a commit that referenced this issue Feb 12, 2016
@smondet
Merge PR #361 (@smondet, FAQ #341 & #345)
dd16dd7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
FAQ
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add 2 entries to the FAQ.md hammerlab/ketrew
2 participants
@iskandr @smondet