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
I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
The test was designed to fail during setup (expected) and then catch said failure, to demonstrate that the job timeout configuration is working as intended. However, because the test fails during setup, the test itself cannot catch the exception to evaluate it, and instead just fails outright. The test fails inconsistently, suggesting that the test setup occasionally completes in under 1s (the timeout threshold for the test).
Expected Behavior
The test should create a timeout scenario that is predictable and fails during the test execution, not during the setup. The test should then catch that exception with a pytest.raises call.
Is this a new bug in dbt-bigquery?
Current Behavior
The test was designed to fail during setup (expected) and then catch said failure, to demonstrate that the job timeout configuration is working as intended. However, because the test fails during setup, the test itself cannot catch the exception to evaluate it, and instead just fails outright. The test fails inconsistently, suggesting that the test setup occasionally completes in under 1s (the timeout threshold for the test).
Expected Behavior
The test should create a timeout scenario that is predictable and fails during the test execution, not during the setup. The test should then catch that exception with a
pytest.raises
call.Steps To Reproduce
See failed runs for examples:
https://github.com/dbt-labs/dbt-bigquery/actions/runs/10550048706/job/29225776817
Relevant log output
No response
Environment
Additional Context
No response
The text was updated successfully, but these errors were encountered: