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

Possibly more i686 issues #8731

Closed
staticfloat opened this issue Oct 19, 2014 · 6 comments
Closed

Possibly more i686 issues #8731

staticfloat opened this issue Oct 19, 2014 · 6 comments
Labels
system:32-bit Affects only 32-bit systems

Comments

@staticfloat
Copy link
Member

Launchpad builds are now throwing some InexactErrors() on the 32-bit builds (which I just recently switched from targeting pentium4 to instead targeting i686):

exception on 5: ERROR: test failed: ishermitian(A' * A)
 in expression: ishermitian(A' * A)
 in error at error.jl:21
 in default_handler at test.jl:25
 in do_test at test.jl:50
 in runtests at /build/buildd/julia-0.4.0/test/testdefs.jl:5
 in anonymous at multi.jl:828
 in run_work_thunk at multi.jl:593
 in anonymous at task.jl:828
while loading arrayops.jl, in expression starting on line 897
exception on 4: ERROR: test error in expression: Dates.DateTime("[14:51:00.118]","[HH:MM:SS.sss]") == t
InexactError()
 in slotparse at dates/io.jl:99
 in getslot at dates/io.jl:108
 in parse at dates/io.jl:120
 in anonymous at test.jl:83
 in do_test at test.jl:47
 in include_string at loading.jl:97
 in include_from_node1 at ./loading.jl:131
 in runtests at /build/buildd/julia-0.4.0/test/testdefs.jl:5
 in anonymous at multi.jl:828
 in run_work_thunk at multi.jl:593
 in anonymous at task.jl:828
while loading /build/buildd/julia-0.4.0/test/dates/io.jl, in expression starting on line 272
while loading dates.jl, in expression starting on line 14
ERROR: test error in expression: Dates.DateTime("[14:51:00.118]","[HH:MM:SS.sss]") == t
InexactError()
 in include_from_node1 at ./loading.jl:131
 in start_reading at stream.jl:617
 in worker_id_from_socket at multi.jl:343
 in Worker at multi.jl:95
 in anonymous at task.jl:898
while loading /build/buildd/julia-0.4.0/test/dates/io.jl, in expression starting on line 272
while loading dates.jl, in expression starting on line 14
while loading /build/buildd/julia-0.4.0/test/runtests.jl, in expression starting on line 40
@staticfloat
Copy link
Member Author

@quinnj pinging you on the dates stuff

@tkelman
Copy link
Contributor

tkelman commented Oct 19, 2014

Which test is the hermitian failure in? I can reproduce the dates failure with the linux-i386 nightly (why does it say master is a fork?)

  | | |_| | | | (_| |  |  Version 0.4.0-dev+1132 (2014-10-18 20:43 UTC)
 _/ |\__'_|_|_|\__'_|  |  master/636f481 (fork: 40 commits, 4 days)
|__/                   |  i386-redhat-linux

but it passes with a win32 build (without MARCH set).

@staticfloat
Copy link
Member Author

It's from arrayops.jl, right?
On Oct 19, 2014 12:04 AM, "Tony Kelman" [email protected] wrote:

Which test is the hermitian failure in? I can reproduce the dates failure
with the linux-i386 nightly (why does it say master is a fork?)

| | || | | | (| | | Version 0.4.0-dev+1132 (2014-10-18 20:43 UTC)
/ |__'|||'_| | master/636f481 (fork: 40 commits, 4 days)
|
/ | i386-redhat-linux

but it passes with a win32 build (without MARCH set).


Reply to this email directly or view it on GitHub
#8731 (comment).

@ivarne
Copy link
Member

ivarne commented Oct 21, 2014

@tkelman master (or any branch) is considered a fork if it contains commits that is not present in the origin/master branch.

I tried not to hardcode origin as remote, but rather searched for the remote with JuliaLang/julia.git in its url. When that fails, my intention was to just assume that master was a valid branch, but it seems like @staticfloat compiles without creating a local master branc on his buildbots, so he removed what I thought was a reasonable fallback.

What is the output of git config -l 2>/dev/null | grep 'remote\.\w*\.url'?

@staticfloat
Copy link
Member Author

I didn't think I removed anything; all I did was ensure that $origin would be set to something at all, right? Because if it's not, then we get git erroring out on every operation that involves $origin.

ivarne referenced this issue Oct 21, 2014
On some buildbots and friends, we don't have remotes as you normally think of them.  Provide a fallback for $origin in that case.
@tkelman tkelman added the system:32-bit Affects only 32-bit systems label Oct 21, 2014
@staticfloat
Copy link
Member Author

Closing this in favor of #8812

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
system:32-bit Affects only 32-bit systems
Projects
None yet
Development

No branches or pull requests

3 participants