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

testserver - travisCI - illegal instruction (core dumped) #16845

Closed
beeekind opened this issue Jul 3, 2017 · 3 comments
Closed

testserver - travisCI - illegal instruction (core dumped) #16845

beeekind opened this issue Jul 3, 2017 · 3 comments
Assignees
Labels
C-investigation Further steps needed to qualify. C-label will change. O-community Originated from the community

Comments

@beeekind
Copy link

beeekind commented Jul 3, 2017

BUG REPORT

  1. Log File unavailable (this took place in Travis)

  2. Please describe the issue you observed:

  • What did you do?

I attempted to start a testserver within a Travis Build but it led to a -1 exit with the output shown here

  • What did you expect to see?

I expected the test to pass as it did on my local machine.

  • What did you see instead?

The -1 exit code.

RESOLUTION:

On a hunch I was able to resolve the issue by adding the following line at the top of my travis.yml file:

sudo: true

I'm assuming there are constraints in the non-sudo environment that prevented the cockroachdb testserver from running, either way it would be nice to remove the sudo requirement as it does slow down builds.

@andreimatei
Copy link
Contributor

@mberhault, can this be the avx2 regressions discussed here?#16808 (comment)

I forgot which version the testserver downloads by default.

@bdarnell
Copy link
Contributor

bdarnell commented Jul 3, 2017

testserver downloads builds from master, not the release: cockroachdb/cockroach-go#19

@knz knz added the O-community Originated from the community label Apr 27, 2018
@knz knz added the C-investigation Further steps needed to qualify. C-label will change. label Apr 27, 2018
@benesch
Copy link
Contributor

benesch commented Apr 27, 2018

There's a good chance this was resolved when we turned off SSE4.2 for release builds: #15589. Marking as fixed, but feel free to reopen if it's still a problem.

@benesch benesch closed this as completed Apr 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-investigation Further steps needed to qualify. C-label will change. O-community Originated from the community
Projects
None yet
Development

No branches or pull requests

5 participants