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
Hello @sormuras. We added schedule for e2e tests and didn't see any errors. Could you please confirm that you hadn't faced up with this issue since last time you reported ?
As Dmitry mentioned, we have added e2e tests scheduled twice per day (every test runs about ~150 test cases) and didn't reproduce this issue for the last week.
I will close this issue for now but we will keep these tests scheduled and will monitor them. Please let us know if you see this issue again.
If it reproduces, we definitely should consider adding some kind of retry logic for action.
Hello,
This happened more than a few times today to me, forcing a trigger of all versions of the job again, each one having a non-null chance of failing…
Activity
dmitry-shibanov commentedon Apr 12, 2021
Hello @sormuras. Thank you for report. Could you please answer some more question.
sormuras commentedon Apr 12, 2021
Saw it only once. So zero times reproduced, yet.
Hosted.
Find more details at https://github.com/sormuras/bach-application-template/runs/2321248297
dmitry-shibanov commentedon Apr 12, 2021
Thank you for providing information @sormuras. We added schedule for e2e in scope of this pull request to monitor this issue.
dmitry-shibanov commentedon Apr 20, 2021
Hello @sormuras. We added schedule for e2e tests and didn't see any errors. Could you please confirm that you hadn't faced up with this issue since last time you reported ?
sormuras commentedon Apr 20, 2021
Aye, Dmitry. The error didn't occur again - so far.
maxim-lobanov commentedon Apr 21, 2021
As Dmitry mentioned, we have added e2e tests scheduled twice per day (every test runs about ~150 test cases) and didn't reproduce this issue for the last week.
I will close this issue for now but we will keep these tests scheduled and will monitor them. Please let us know if you see this issue again.
If it reproduces, we definitely should consider adding some kind of retry logic for action.
joel-costigliola commentedon Jun 16, 2021
this occured in https://github.com/assertj/doc/runs/2838393644?check_suite_focus=true
joel-costigliola commentedon Jun 16, 2021
and it's ok now.
tshirtman commentedon Oct 30, 2021
Hello,
This happened more than a few times today to me, forcing a trigger of all versions of the job again, each one having a non-null chance of failing…
https://github.com/kivy/pyjnius/runs/4054696309?check_suite_focus=true
https://github.com/kivy/pyjnius/runs/4054612694?check_suite_focus=true
https://github.com/kivy/pyjnius/runs/4054612794?check_suite_focus=true
https://github.com/kivy/pyjnius/runs/4054501552?check_suite_focus=true
https://github.com/kivy/pyjnius/runs/4054501596?check_suite_focus=true
https://github.com/kivy/pyjnius/runs/4054449871?check_suite_focus=true