Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

There are some issues with the CI System (cross + GitHub Actions) #237

Closed
6 of 7 tasks
CryZe opened this issue Sep 6, 2019 · 2 comments
Closed
6 of 7 tasks

There are some issues with the CI System (cross + GitHub Actions) #237

CryZe opened this issue Sep 6, 2019 · 2 comments
Labels
bug There is a bug. ci Affects the Continuous Integration.

Comments

@CryZe
Copy link
Collaborator

CryZe commented Sep 6, 2019

The switch to GitHub Actions and the new release of cross introduced a couple of issues:

  • Sometimes the network connection fails on the Windows jobs (checking out the commit or publishing a release). Issue
  • You can't restart individual jobs, only the whole thing. Issue
  • This uses a custom pre-release version of cross.
  • The 32-bit macOS build has been disabled. It doesn't seem to build. Supposedly 32-bit macOS is deprecated. Not sure if that's the problem though. Rust itself is removing 32-bit macOS, so I'm considering it dead as well.
  • The asmjs build is disabled until the next cross version comes out.
  • FreeBSD is not supported anymore by cross. We have so many other new platforms we support now. If anyone cares enough about FreeBSD, they can fix the cross-compilation in cross.
  • crates.io doesn't support the GitHub Actions badge yet, there's a PR Support GitHub Actions Badges rust-lang/crates.io#1838
@CryZe CryZe added bug There is a bug. ci Affects the Continuous Integration. blocked Progress is blocked and can't progress. labels Sep 6, 2019
CryZe added a commit that referenced this issue Sep 9, 2019
@CryZe CryZe changed the title Cross-compiling on CI is broken for some targets There are some issues with the CI System (cross + GitHub Actions) Sep 13, 2019
@CryZe
Copy link
Collaborator Author

CryZe commented Oct 15, 2019

  • Looks like asmjs is broken again. I don't understand what's wrong with it. I guess we want to disable it until the LLVM backend emscripten is used by cross. We are not supporting emscripten anymore as of Remove emscripten entirely #298

@CryZe
Copy link
Collaborator Author

CryZe commented Jan 1, 2021

Alright, so I'll close this. While you still can't rerun an individual job, it's not that bad as GitHub Actions runs pretty fast and it's not something we can do something about. Eventually they'll support it and then we can be happy about it, but that's about it.

@CryZe CryZe closed this as completed Jan 1, 2021
@CryZe CryZe removed the blocked Progress is blocked and can't progress. label Jan 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug There is a bug. ci Affects the Continuous Integration.
Projects
None yet
Development

No branches or pull requests

1 participant