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

fft test broken #2274

Closed
JeffBezanson opened this issue Feb 11, 2013 · 3 comments
Closed

fft test broken #2274

JeffBezanson opened this issue Feb 11, 2013 · 3 comments
Labels
kind:bug Indicates an unexpected problem or unintended behavior status:priority This should be addressed urgently

Comments

@JeffBezanson
Copy link
Sponsor Member

     * fft
ERROR: assertion failed: |:(rfftn_m4[i,j]) - :(true_fftn_m4[i,j])| < 2.3364326363345896e-10
  :(rfftn_m4[i,j]) = -13.0 + 2.0im
  :(true_fftn_m4[i,j]) = 0.0 + 0.0im
 in test_approx_eq at test.jl:54
 in anonymous at no file:159
 in include_from_node1 at loading.jl:76
 in runtests at /home/jeff/src/julia2/julia/test/runtests.jl:6
 in anonymous at no file:22
 in include_from_node1 at loading.jl:76
 in process_options at client.jl:255
 in _start at client.jl:318
at /home/jeff/src/julia2/julia/test/fft.jl:167

This also happens on travis.
@stevengj

StefanKarpinski added a commit that referenced this issue Feb 11, 2013
… more than once in fft etc.; also add r2r execution convenience function" [#2274, #2275]

This reverts commit 583b9f1.
@StefanKarpinski
Copy link
Sponsor Member

We are doing a very shitty job of not breaking things right now. This has to stop. This was partly my fault for not testing that pull request before merging it. I assumed that it would at least pass the fft tests :-\

@stevengj
Copy link
Member

Sorry, stupid error on my part.

@StefanKarpinski
Copy link
Sponsor Member

I actually already did something like that: bed9511. Hopefully that's good enough; if there's a better fix, please do submit, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:bug Indicates an unexpected problem or unintended behavior status:priority This should be addressed urgently
Projects
None yet
Development

No branches or pull requests

3 participants