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
This is needed because sometimes sikuli events do not seem to get through to ctp2, so far the reason is unknown (RaiMan/SikuliX1#54). This problem seems to appear more often/likely if the GL-CI server (runner) are very busy. There is no option to pause between auto-repeated GL-CI jobs, so if GL-CI is very busy for some time, and all 3 tries of a job fall into that period, they are likely to fail. In that case it is best to re-run the pipeline again manually after some hours passed, not ideal but manageable. Increasing the number of auto-tries might not be desirable in this case, because they are likely just wasting the precious cost-free 2000 GL-CI minutes per month.
The text was updated successfully, but these errors were encountered:
In regard to #84 (comment), see also #104:
GL-CI for ctp2 is configured such that each job is tried 3 times automatically
civctp2/.gitlab-ci.yml
Line 91 in f8f1c59
This is needed because sometimes sikuli events do not seem to get through to ctp2, so far the reason is unknown (RaiMan/SikuliX1#54). This problem seems to appear more often/likely if the GL-CI server (runner) are very busy. There is no option to pause between auto-repeated GL-CI jobs, so if GL-CI is very busy for some time, and all 3 tries of a job fall into that period, they are likely to fail. In that case it is best to re-run the pipeline again manually after some hours passed, not ideal but manageable. Increasing the number of auto-tries might not be desirable in this case, because they are likely just wasting the precious cost-free 2000 GL-CI minutes per month.
The text was updated successfully, but these errors were encountered: