When cancelling 'Run Tests with Coverage' it shouldn't try to get coverage after.

Issue #1532 resolved
Justin Julicher created an issue

Pretty self explanatory I think. Let me know if you need more.

Comments (4)

  1. Scott Wells repo owner

    No, that makes sense. The reason this happens now is the coverage aspect is scheduled before the test run starts to occur after the test run completes because of how the whole Run With Coverage action works in the test framework. I'd just need to capture some state about whether the test run was cancelled and check that when the coverage step kicks in.

  2. Log in to comment