Dump the error log on randgen test failures
When a randgen test fails in drizzle-automation, we dump the output of the randgen run. Unfortunately, as the randgen is still being tweaked for drizzle, this isn't always the most useful output. Assertions, etc end up in the error log. We might want to dump the error log as well on a randgen test failure, at least for the foreseeable future.
Blueprint information
- Status:
- Complete
- Approver:
- Patrick Crews
- Priority:
- Undefined
- Drafter:
- Patrick Crews
- Direction:
- Needs approval
- Assignee:
- Patrick Crews
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Patrick Crews
- Completed by
- Patrick Crews
Related branches
Related bugs
Sprints
Whiteboard
Found that the error log wasn't as informative as we would have liked.
Instead, it was determined that a lot of the randgen failures were crashes. Drizzle-automation now has a crash_check() function that will check for a running server and attempt to produce a backtrace.
This feature is also used at certain places in the dbt2 and drizzleslap runs. Calls to the function were placed in areas that were shown to fail in odd ways on test runs.
