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

32-bit nightlies are not being tested #17344

Closed
alexcrichton opened this Issue Sep 17, 2014 · 7 comments

Comments

Projects
None yet
4 participants
@alexcrichton
Copy link
Member

alexcrichton commented Sep 17, 2014

The OSX and Linux nightly builders are not testing the 32-bit nightlies because they're only testing the 64-bit nightlies.

The most recent 32-bit cargo builds instantly segfault, which leads me to believe that there may be codegen bugs?

@brson brson added the I-nominated label Sep 17, 2014

@brson brson self-assigned this Sep 17, 2014

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Sep 17, 2014

Let's fix distcheck to test all hosts.

@brson brson referenced this issue Sep 17, 2014

Closed

Automation metabug #17356

45 of 65 tasks complete
@pnkfelix

This comment has been minimized.

Copy link
Member

pnkfelix commented Sep 18, 2014

Under the assumption that we will actually manually test the distribution artifacts by hand before releasing 1.0, Felix agrees fixing this infrastructure issue need not block 1.0

P-high, not 1.0 milestone.

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Sep 19, 2014

@alexcrichton distcheck doesn't even test the packaged bins besides a smoke test, though it's true it only tests the build triple, not all hosts.

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Sep 19, 2014

Probably the right way to get coverage here is to make make check test all hosts and all targets before packaging.

@brson brson removed their assignment Apr 9, 2015

@steveklabnik

This comment has been minimized.

Copy link
Member

steveklabnik commented Oct 27, 2015

@alexcrichton @brson @edunham is this still true today?

@alexcrichton

This comment has been minimized.

Copy link
Member Author

alexcrichton commented Oct 27, 2015

Yes, this is still an issue

@brson

This comment has been minimized.

Copy link
Contributor

brson commented Jul 14, 2016

Whatever.

@brson brson closed this Jul 14, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.