-
Notifications
You must be signed in to change notification settings - Fork 71
Enable GitHub action to build and test code #162
Comments
@Jeffwan: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign @SumLare |
@Jeffwan: GitHub didn't allow me to assign the following users: SumLare. Note that only kubeflow members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
https://github.com/kubeflow/common/runs/3648012266 Interesting, in the latest workflow, I didn't see failure logs.. |
Well https://status.coveralls.io/ still doesn't look good |
Yeah, that's the problem
|
coveralls crashes sometimes. |
Let's do this to overcome the issue. Since goveralls is nice to have, we can ignore the failures in CI. I can not believe recovery takes that long..
|
This can be closed. thanks @SumLare ! |
See #161
#141 introduces some build failures but we don't notice that before we merge the code. Travis somehow was deleted at that time. @gaocegege suggests to use Github actions.
Let's migrate scripts https://github.com/kubeflow/common/blob/master/.travis.yml to a Github Action manner.
We do need this to guarantee code quality
/help
/good-first-issue
The text was updated successfully, but these errors were encountered: