![]() |
![]() |
#1 |
Dec 2020
32 Posts |
![]()
Would it be possible to include the failed FFT size in the results.txt file for a torture test?
Currently it only displays the passed FFT sizes and the error message, but not the FFT size where the error actually happened in the log file. In the worker thread window you can at least also see which FFT size was started and then deduce from that where the error happened, but for the log file there's not even such an indication. I've even tried to make an educated guess by looking at the order of FFT sizes, but unfortunately this only works for smaller FFT sizes, for larger ones there seems to be a random order in which the FFT sizes are tested, and therefore any prediction seems to be impossible (I also tried to find and understand the C code that defines the order of FFT sizes, but to my embarrassment failed to do so ๐). |
![]() |
![]() |
![]() |
#2 |
P90 years forever!
Aug 2002
Yeehaw, FL
2·4,079 Posts |
![]()
I will add that information in the next release.
|
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
GMP-ECM 7.0-dev assertion failed! | Antonio | GMP-ECM | 9 | 2015-03-10 08:21 |
Assertion failed | Andi47 | GMP-ECM | 2 | 2009-08-04 14:11 |
integrator failed | MatWur-S530113 | Msieve | 5 | 2009-01-28 03:54 |
connection failed | musos | Information & Answers | 1 | 2008-12-12 14:29 |
Test 1: failed? | No0dles | Hardware | 12 | 2005-11-05 09:23 |