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
The allowed failure is the slowest entry (takes almost 1 hour vs the 1-2 minutes of the other entries). It happens that even if all the other jobs are green, a success status is not sent to Github until that slow entry finishes, even though it's not necessary for the status calculation.
I'd love that the CI status would be sent as soon as all required jobs are finished.
The text was updated successfully, but these errors were encountered:
Did you consider to create separate AppVeyor project against the same repo, which will build only ruby_version: _trunk as a workaround? For this project you can set Custom commit status context (UI-only settings on the General tab) so you can distinguish statuses set by this build.
I have 6 required jobs and 1 allowed failure in my appveyor matrix.
The allowed failure is the slowest entry (takes almost 1 hour vs the 1-2 minutes of the other entries). It happens that even if all the other jobs are green, a success status is not sent to Github until that slow entry finishes, even though it's not necessary for the status calculation.
I'd love that the CI status would be sent as soon as all required jobs are finished.
The text was updated successfully, but these errors were encountered: