When UFT runs a test and returns a value for Err.Number that is non-zero, a setting of "Reporter.Filter=rfDisableAll" can be set within ALM to not log this error. However, the non-zero value still causes a failure to be logged in Jenkins.
It would be useful to have HPToolsRunner honor this same setting, and only report a failure to Jenkins when this property isn't set.

Reporter.Filter=rfDisableAll   is current UFT/QTP functionality to disable logging of failures to QC at runtime.  It is used to bypass expected errors that UFT interprets as failures.
The issue is that when we have logging off, it does NOT log a failure to QC, which is what we expect.  The bug is that a failure is still logged to Jenkins when logging is disabled.  Jenkins logging should report EXACTLY what QC sees for results, so we end up with a Pass in QC and a Fail in Jenkins.  
So we need this flag to be interpreted by Jenkins executions properly too.  This is a UFT issue, not a QC issue.