New issue
Advanced search Search tips

Issue 725205 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Recipe traceback cleanup

Project Member Reported by iannucci@chromium.org, May 22 2017

Issue description

Recipe tracebacks are currently verbose and unhelpful. We can improve these a lot

  * If recipe's RunSteps is on stack, remove all stack frames above
  * If the stack ends with <user_code> -> <engine_code>, remove the last frame, print the exception text
  * If the stack ends with more than one engine_code block, ask the user to file a boundary check bug against the engine.
  * Replace all paths with some better notation (i.e. PACKAGE[engine]/...)
  * Remove all decorators and other meta shit from stack
  * Preserve original stack trace in proto
  * Add `$recipe_engine['full_frames'] = True` property to avoid this cleanup. Ex.
PACKAGE[user_repo]/recipes/foo.py:12 -- RunSteps(...)
    api.wat
PACKAGE[user_repo]/recipe_modules/foo.py:12 -- api.foo(...)
    api.wat
SomeException: Your pants are on fire.

 
Labels: -Type-Bug -Pri-3 Pri-2 Type-Feature
Project Member

Comment 2 by sheriffbot@chromium.org, May 23 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Cc: -d...@chromium.org
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
Still valid.
Cc: iannu...@google.com

Sign in to add a comment