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
When using failsafeUndeployment, if the container is unable to delete the app archive, it doesn't raise an exception and marks the file for deletion at the end of the test.
However, failing to delete the application archive results in the application not stopping, so the test fails saying "application did not stop" with no information about the underlying cause
Expected Behaviour
Either test should not fail, or the failure message should say that the application file could not be deleted.
Current Behaviour
Test fails because the application did not stop
Steps To Reproduce
enable failsafeUndeployment with dropins
use another process to lock application archive file while the test is running
The text was updated successfully, but these errors were encountered:
Issue Overview
When using failsafeUndeployment, if the container is unable to delete the app archive, it doesn't raise an exception and marks the file for deletion at the end of the test.
However, failing to delete the application archive results in the application not stopping, so the test fails saying "application did not stop" with no information about the underlying cause
Expected Behaviour
Either test should not fail, or the failure message should say that the application file could not be deleted.
Current Behaviour
Test fails because the application did not stop
Steps To Reproduce
The text was updated successfully, but these errors were encountered: