[HIVE-14669] Have the actual error reported when a q test fails instead of having to go through the logs

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.0.0-alpha-1
• Target Version/s: 3.0.0
• Assignee: László Bodor
• Reporter: Siddharth Seth
• Created: 30/Aug/16 19:49
• Updated: 17/Nov/22 08:54
• Resolved: 04/May/19 17:29

Description

QTest runs end up invoking CliDriver.processLine. This, in most cases, reports a numeric exit code - 0 for success. Non-zero for various different error types (which are defined everywhere in the code).

Internally CliDriver does have more information via CommandResult. A lot of this is not exposed though. That's alright for the end user cli - (Command line tool translating the error to a code and message). However, it makes debugging very difficult for QTests - since the log needs to be looked at each time.

Errors generated by the actual backend execution are mostly available to the client, and information about these should show up as well. (If it doesn't - we have a usability issues to fix).

cc ekoifman