Comment 4 for bug 1901783

I have tried to put together a unique fingerprint for a e-r query for this but the lvs error code 139 does not always correspond to a job failure. My guess is that there are a number of operations where perhaps lvs is retried and eventually succeeds when it initially fails with error 139, so oftentimes jobs can result in SUCCESS even when they encounter lvs fails with error 139.