You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hmm, I guess this is to detect computational / memory / types related issues?
Why 3 is better than 10? Is it faster or smaller?
Mostly just because it's faster. Running OSTest on the raspberrypi-pico gets stuck on getprime for about 5 minutes because of the number of runs. That seems excessive to me, I'm not sure we'd really catch any new memory errors that way? I could be wrong, but I feel like a smaller number might be enough for really weak targets?
This isn't really a glaring issue but it slow down my testing of RC2 today haha!
Are you sure this is not some other rpi-pico issues like hanging ostest and/or usbnsh that I am also observing? Does it always take 5 minutes for you on these primes? :-)
Are you sure this is not some other rpi-pico issues like hanging ostest and/or usbnsh that I am also observing? Does it always take 5 minutes for you on these primes? :-)
This was over UART shell. It does take a lot of time yes, I should maybe time it precisely. I know it isn't hanging because after the really long duration, the rest of the test continues and succeeds.
Negative :-( Unfortunately #3809 that changed iterations count broke CI and probably some platforms. #3832 reverts this. Iterations needs to be decreased only for small platforms.. or some additional fix in the code is required in addition to only defines change.
Activity
cederom commentedon Jul 8, 2026
Hmm, I guess this is to detect computational / memory / types related issues?
Why 3 is better than 10? Is it faster or smaller?
linguini1 commentedon Jul 8, 2026
Mostly just because it's faster. Running OSTest on the raspberrypi-pico gets stuck on getprime for about 5 minutes because of the number of runs. That seems excessive to me, I'm not sure we'd really catch any new memory errors that way? I could be wrong, but I feel like a smaller number might be enough for really weak targets?
This isn't really a glaring issue but it slow down my testing of RC2 today haha!
cederom commentedon Jul 8, 2026
Are you sure this is not some other rpi-pico issues like hanging ostest and/or usbnsh that I am also observing? Does it always take 5 minutes for you on these primes? :-)
linguini1 commentedon Jul 8, 2026
This was over UART shell. It does take a lot of time yes, I should maybe time it precisely. I know it isn't hanging because after the really long duration, the rest of the test continues and succeeds.
cederom commentedon Jul 8, 2026
Allright, for me rpi-pico* seems unreliable but I used it only over usbnsh :-)
cederom commentedon Oct 11, 2026
Negative :-( Unfortunately #3809 that changed iterations count broke CI and probably some platforms. #3832 reverts this. Iterations needs to be decreased only for small platforms.. or some additional fix in the code is required in addition to only defines change.
testing/ostest: shrink default round-robin getprime test duration