mcapra wrote:I would need to see the full call trace from the RC server to determine if it's a "false negative" or not. I know check_selenium by itself will throw a "CRITICAL" if it finds the word "ERROR" anywhere in the test case's output, though I believe the RC server will re-try the test if it can't establish a session ID on the first attempt in many cases. So the first session on these tests might be failing, but a second/third may be succeeding. The logic in check_selenium i'm referring to:
Though this could cause issues with the status output overflowing as @avandemore pointed out.
Suggested output change makes ALL Selenium script fail with Out of bond 255 error.
Version 5.4.2 upgrade made no difference to the RC "ERROR Server Exception" as attached (script does finish anyways and definitely OK on the re-try) / is there a way not to produce FAIL for "ERROR Server Exception" somehow? - Even the UNKNOWN will do just fine
Thank you
You do not have the required permissions to view the files attached to this post.
mcapra wrote:You could try adding a separate regex match to check_selenium for Jetty (the web server component used by the RC server) server exceptions: