Marked blocked bug to show impact.

This would be a change to the recipe expectations; it's not immediately clear what the best way to do this would be. In general I think it will be very spammy so I if we want this we wouldn't want to turn it on all the time.

I think the correct way to do this today I would be to set a "breakpoint" in the code (i.e. `import pdb; pdb.set_trace()`, maybe under some conditional) and then run the debugger (`./recipes.py test debug --filter recipe_name.recipe_test_name`). This would let you use normal pdb debugging techniques for a given simulation.

Going to close this as wontfix (suggestion: use the debugger instead). Please reopen if you think the debugger isn't enough to cover this usecase and we should add additional code to the recipe engine to support it.

I tried that first for the issue at hand. This was unfortunately blocked by  issue 715520  as the recipe couldn't run locally.

Furthermore, debugging locally first in order to recalculate the input values of a given step script is substantially harder than just reading the input values from a log.

But I hear you in regards to expectations. Maybe by default, those expectations could be hidden?

Another problem might be the log size. Maybe some input files are very large. If they're exposed to logdog by default, or even buildbot, it might eat some resources. If such a feature existed, maybe it could be used as opt-in, e.g. by providing a parameter to json.input or raw_io.input?

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Guess it's wontfix as nobody will work on this. Hope that folks try to write their recipes in ways that are easy to debug, e.g. expose non-trivial inputs explicitly...