You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-----------------------------------------------
Running test run_pgaudit_test (starting at 2023-10-03 10:26:59+00:00) ...
-----------------------------------------------
c644c8223c59eb64a932a2d1cd2e13e9f3bee4a1c7fd79ec69e1df6e37a788c0
Created container c644c8223c59eb64a932a2d1cd2e13e9f3bee4a1c7fd79ec69e1df6e37a788c0
test/run: line 340: $1: unbound variable
Tests finished with EXIT=1
It is little bit confusing what the log line Tests finished with EXIT=1 is saying to us.
In reality it means, that the exit code of the test script was not zero, however, this does not mean, that the TESTSUITE_RESULT was success or that the tests finished successfully.
I do not see the results of run_pgaudit_test in the logs that Peto has found. That could mean, that unbound variable led to exiting the whole testsuite even before the test result itself was recorded.
This is not really bad behaviour, unfortunately from the log I can not see, if the overal test results were green or red. Everything leads to conclusion that they were red - so I consider this behaviour to be at least partly correct.
What can we do in order to increase readibility of the logs:
change sentence Tests finished with EXIT=1 to something like Tests finished unexpectedly with EXIT=1
do not exit test script on unbound variable, just fail the specific testcase if this happens.
From my POV this problem does not have high priority. @phracek Do you want to add something?
There is an error in
test/run
script:Tests are passing:
Originally posted by @phracek in #399 (comment)
The text was updated successfully, but these errors were encountered: