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.

Sign up for GitHub

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

Jump to bottom

[18.03]: rustc build broken on i686 #39110

Closed
xeji opened this issue Apr 18, 2018 · 4 comments
Closed

[18.03]: rustc build broken on i686 #39110

xeji opened this issue Apr 18, 2018 · 4 comments

Comments

@xeji
Copy link
Contributor

xeji commented Apr 18, 2018

Issue description

rustc build appears to be broken on i686, resulting in a number of hydra failures. For example, look at nixos.closures.xfce.i686-linux or nixos.tests.firefox.i686-linux in linked hydra eval.

Technical details

nixos-18.03.132050.0a97eb36be8

--

/cc @Mic92
@Mic92
Copy link
Member

Mic92 commented Apr 21, 2018

cc @vcunat how much i686 do we still support?

@Mic92
Copy link
Member

Mic92 commented Apr 21, 2018

It runs out of memory while running tests. I will disable tests for rustc i686 as well.

@xeji
Copy link
Contributor Author

xeji commented Apr 21, 2018

Independent of this issue, we should have some sort of "official" i686 support policy and mark all unsupported packages as broken to get rid of those hydra jobs.

Mic92 added a commit that referenced this issue Apr 21, 2018
@Mic92
rustc: disable test on i686
ca5bc1e 
They run out of memory and lead to failing tests.

fixes #39110

(cherry picked from commit 14a119e)
@Mic92 Mic92 closed this as completed in 14a119e Apr 21, 2018
@vcunat
Copy link
Member

vcunat commented Apr 22, 2018

Maybe it was just a transient problem.

Officially we currently don't "guarantee" i686 support (except for packages like wine). It's more like there's not enough interest to keep it in a good shape, but certainly feel free to improve on that (anyone). There are a few open issues, e.g. #36947

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Mic92 @vcunat @xeji