-
Notifications
You must be signed in to change notification settings - Fork 4
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
Use travis to build and test in 32-bit mode #9
Comments
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
jberryman
changed the title
Use travis to build and test in 32-bit mode and with --ghcjs
Use travis to build and test in 32-bit mode
Nov 16, 2016
jberryman
added a commit
that referenced
this issue
Nov 16, 2016
This also exercises 32-bit support, but we really want to do this explicitly in #9.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hopefully we can do this with something like:
travis-ci/travis-ci#5770 (comment)
We get a lot of coverage of 32-bit consistency with GHCJS, but can't rely on that (e.g. we need to test that Word64 are stored in the way we expect, etc). And see #8 and #7
The text was updated successfully, but these errors were encountered: