[CT-2310] [Bug] The test_no_introspect test fails intermittently

[peterallenwebb]

The Tests and Code Checks action has been failing on the main branch of dbt-core due to intermittent failure of the test_no_introspect test. We need to improve the reliablity of this test.

Initial investigation uncovered log lines suggesting that the issue may be related to closing an already-closed connection:

[DEBUG] file_log: 14:50:53.859407 [debug] [Thread-1  ]: Traceback (most recent call last):
  File "/home/runner/work/dbt-core/dbt-core/plugins/postgres/dbt/adapters/postgres/connections.py", line 66, in exception_handler
    yield
  File "/home/runner/work/dbt-core/dbt-core/core/dbt/adapters/sql/connections.py", line 80, in add_query
    cursor = connection.handle.cursor()
psycopg2.InterfaceError: connection already closed

However, there is another issue, which is that the resulting DbtRuntimeException is constructed with the wrong type in postgres/connections.py at line 89. The parameter is an Exception rather than a str:

raise dbt.exceptions.DbtRuntimeError(e) from e

As a result, a secondary exception is generated during exception handling.

[jtcohen6]

Was this really resolved by #7208? Or did we just mark the test to skip?

https://github.com/dbt-labs/dbt-core/pull/7208/files#r1151279272

I'm going to reopen this and add it to the Flaky Tests epic

[martynydbt]

@emmyoop Will run these tests through the flakey tester to determine 1. if they are still flakey and 2. how flakey.
If they are pretty flakey we will try to address this sprint. If not we will punt to next sprint.

[emmyoop]

https://github.com/dbt-labs/dbt-core/actions/runs/5671681780

[emmyoop]

This test is marked to be skipped on main. It's not flaky. It failed 1000/1000 runs once I removed the skip.