Closed dianabarsan closed 1 year ago
Example of successful capture of run failure: https://github.com/medic/cht-core/actions/runs/4277828531/jobs/7447091600#step:16:2097
I'm now getting the screenshot and logs say:
Executed 1 of 2 specs (1 FAILED) (1 PENDING) in 1 sec.
>> 01:28:07.816 INFO [ActiveSessions$1.onStop] - Removing session 52785e2b69b9f77df80e35649e74f1b8 (org.openqa.selenium.chrome.ChromeDriverService)
[01:28:07] I/launcher - 0 instance(s) of WebDriver still running
[01:28:07] I/launcher - chrome #01 failed 1 test(s)
[01:28:07] I/launcher - overall: 1 failed spec(s)
Closing report
[ProtractorJasmineRetry] Test failed after 5 attempts, exiting with code 1
Merged. No AT required.
Describe the issue We added retries to protractor e2e test failures. However, they do not seem to work: the retry will fail immediately with an error:
Example run: https://github.com/medic/cht-core/actions/runs/4269504105/jobs/7433297666#step:16:634 The report folder is also overwritten, and the other failure screenshots are deleted, which makes debugging harder.
Describe the improvement you'd like Fix it so retries will happen.
Describe alternatives you've considered Have it so the retrying will not clear previous results folder. even if retries don't work.