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

Tag failed stages/exit gracefully when inputs for later stages not found. #44

Open
mdales opened this issue Apr 23, 2024 · 0 comments
Open
Assignees

Comments

@mdales
Copy link
Collaborator

mdales commented Apr 23, 2024

Now that we have more bits of shark working, I'm getting to the point where things in the container will fail, which is fine, but then we fail because there's no data for a later stage, and we blow up. That blow up looks a lot like a shark bug I've had to fight in the past, confusing me :)

When we can't find data for a later stage I need to stop markdown result generation and return what we have, as the output blocks would make it clear what happened from the stdout/stderr of the command. But we should also (incase things don't log) note when commands exit unsuccessfully, and add that to the output markdown.

Basically we've got shark to the point where it's not always what's wrong, but I need it to tell me the other ways in which I've messed up in the code I'm running in shark :)

@mdales mdales self-assigned this Apr 23, 2024
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

No branches or pull requests

1 participant