WT-9265 and WT-9282 are examples of reported failures due to oldest pinned transaction ID rolled back for eviction.  When this is reported, a WT_ROLLBACK would be returned to the caller.  WT-9063 and WT-8991 made fixes so that WT_ROLLBACK returned to a "automatically created" transaction will cause the transaction to be retried.  However, if the retry succeeds the message from eviction remains and can cause an error in the test suite (since the test suite expects zero output on stdout/stderr).

However, if there this kind of output and no other error, it can be safely ignored.  Our Python interface converts all error returns to exceptions, so if we don't get an exception and have that output, there's no problem.

To be specific: we should show the message if the test fails (as it may help diagnose).  But we should ignore the message if the test has passed.  This can be done fully in python, probably in wttest.py .