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
If I exit the execution (with --num-tries set to 1) before an AssertionError is thrown, there is only one log file produced (database0-cur.log), which has all of the successfully executed queries.
If instead an AssertionError is thrown, then there are two log files produced (database0-cur.log and database0.log), both of which only have the unsuccessful query.
I only found this behavior on MySQL, but it may also occur with other DBMS's (they never errored during my testing).
The text was updated successfully, but these errors were encountered:
If I exit the execution (with
--num-tries
set to 1) before an AssertionError is thrown, there is only one log file produced (database0-cur.log
), which has all of the successfully executed queries.If instead an
AssertionError
is thrown, then there are two log files produced (database0-cur.log
anddatabase0.log
), both of which only have the unsuccessful query.I only found this behavior on MySQL, but it may also occur with other DBMS's (they never errored during my testing).
The text was updated successfully, but these errors were encountered: