Page MenuHomeElementl

Make run storage test a bit less strict
AbandonedPublic

Authored by dgibson on Jul 28 2021, 2:49 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Nov 19, 5:43 PM
Unknown Object (File)
Mon, Nov 14, 9:56 PM
Unknown Object (File)
Mon, Nov 14, 9:55 PM
Unknown Object (File)
Sat, Nov 12, 2:26 PM
Unknown Object (File)
Mon, Nov 7, 10:18 PM
Unknown Object (File)
Thu, Nov 3, 7:46 PM
Unknown Object (File)
Thu, Nov 3, 4:59 PM
Unknown Object (File)
Wed, Nov 2, 2:44 AM
Subscribers
None

Details

Summary

Test for a specific error message to encompass different types of run storage

Test Plan

BK

Diff Detail

Repository
R1 dagster
Branch
graphqlstorage (branched from master)
Lint
Lint Passed
Unit
No Test Coverage

Event Timeline

jordansanders added inline comments.
python_modules/dagster/dagster_tests/core_tests/storage_tests/utils/run_storage.py
900

Why are some run storage implementations raising an exception that doesn't inherit from DagsterRunNotFoundError? This feels like the test accurately describes behavior and we have implementations that should change.

This revision now requires changes to proceed.Jul 28 2021, 3:06 PM