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

Warnings in tests #9571

Closed
ViralBShah opened this issue Jan 3, 2015 · 5 comments
Closed

Warnings in tests #9571

ViralBShah opened this issue Jan 3, 2015 · 5 comments

Comments

@ViralBShah
Copy link
Member

I see these errors and warnings when doing make test-reflection. The error sounds scary, but the tests do not fail.

The following 'Returned code...' warnings indicate normal behavior:
Warning: Returned code may not match what actually runs.
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
Warning: Returned code may not match what actually runs.
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
error: failed to compute relocation: X86_64_RELOC_UNSIGNED
Warning: Returned code may not match what actually runs.
Warning: Returned code may not match what actually runs.
@tkelman
Copy link
Contributor

tkelman commented Jan 3, 2015

see #9521, cc @timholy on that one

on the same issue title, we also have: #9518 (comment) when you do make testall1

and some Windows-only bash.exe: warning: could not find /tmp, please create! that I should probably try to figure out how to suppress on appveyor fixed

@vtjnash
Copy link
Member

vtjnash commented Jan 3, 2015

are you using LLVM3.5+ on a Mac? if so, those warnings are due to an upstream issue that Keno knows how to fix with reading MachO debug info reloc tables. the net result for now is that the line numbers are missing in backtraces.

@ViralBShah
Copy link
Member Author

Yes, I am using LLVM 3.5. I had forgotten that I had a Make.user that used the newer LLVM.

@ViralBShah
Copy link
Member Author

Please close this if there is already an issue about this.

@tkelman
Copy link
Contributor

tkelman commented Jan 3, 2015

#7910, right? just the extra-long warnings because of it are new

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants