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
#1776 is showing the broken CI.
A similar issue happened with the previous commit: #2749.
Checks are broken here.
Actual result
Iroha 1.5 support is getting much harder.
Expected result
CI should work normally.
Notes
Vasily Zyabkin claims there are at least two possible reasons for the CI issue:
Cached Iroha 2 build images that were recently added take too much disk space, previously used by I1 CI. There would be more caching added for Cargo lock.
The self-hosted runners were removed, leaving only two. The failed jobs should've launched on said self-hosted runners, but there may be an issue with those.
He explained that a custom action like may give more disk space, for example, depot/setup-action provides 50 Gb.
It is also possible to try this action. It wasn't tested internally yet, so we'll need to check its reliability first.
OS and Environment
GitHub CI
GIT commit hash
3b190aac34
Minimum working example / Steps to reproduce
#1776 is showing the broken CI.
A similar issue happened with the previous commit: #2749.
Checks are broken here.
Actual result
Iroha 1.5 support is getting much harder.
Expected result
CI should work normally.
Notes
Vasily Zyabkin claims there are at least two possible reasons for the CI issue:
He explained that a custom action like may give more disk space, for example,
depot/setup-action
provides 50 Gb.It is also possible to try this action. It wasn't tested internally yet, so we'll need to check its reliability first.
Who can help to reproduce?
@iceseer
@BAStos525
The text was updated successfully, but these errors were encountered: