Open wild-endeavor opened 3 years ago
Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏
Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏
Hello 👋, this issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will engage on it to decide if it is still applicable. Thank you for your contribution and understanding! 🙏
Describe the bug This short test file will reproduce the issue. If you copy paste this into a test file, each of the two tests will succeed on its own. However if you run it together as a file in a pytest command, it will break.
It is unclear what is happening. Somehow, the
flyte_patch
patching logic is interfering with the normalmock.patch
. The mere presence of the second test, basically makes it seem like themock.patch
isn't there on the first test. BasicallyImperativeWorkflow.execute
is not patched and returns what it normally would return, and hence the exception isn't raised.If you copy paste the
wb
workflow and use a new variable for it for the second test, then things pass. This will take some digging into the mock library to understand how they're interfering with each other.