Fri 22 Nov 2013 05:36:57 PM UTC, comment #6:
Oh great, you can reproduce this bug :(
For the record, I am using a virtual machine configured with a single processor and Windows XP. The CLI version definitely seems to have more problems. I'm CC'ing jwe because he produced the fix for bug #38691 in the first place and he might have an idea why a 'rehash' is occasionally necessary.
I think it could be a timing issue. I also notice that if I use keyboard() to bring about a prompt in the %!test then it always succeeds as well. So it could be something about the %!test environment which is run deep inside unwind_protect blocks and eval'ed command line functions.
|
Fri 22 Nov 2013 04:58:50 PM UTC, comment #5:
Cross compiled from id 96a4ac0dc01f on a Fedora 19 machine and running on Windows 7 Prof, 64bit, Intel i7-2640M (installed via the mxe-octave NSIS installer)
I was running the GUI.
|
Fri 22 Nov 2013 02:52:40 PM UTC, comment #2:
bug #38236 is a known failure on all platforms. Bug 38691 is an occasional failure. If you are using _run_test_suite_() it may or may not fail on that particular run, but that is only a single test instance.
If you cd to the bug-38691 test directory and run the test repeatedly, does it always pass?
|
Thu 21 Nov 2013 10:40:31 PM UTC, original submission:
The fixed tests in the test directory include a test for bug #38691 where Octave's loadpath is not correctly updated after using addpath.
The bug was fixed for Linux, but on MinGW it continues to fail in a probabilistic manner. Using the following code,
I see 68 successes instead of 100 successes.
If I alter the .tst script to update the cache with rehash
then I get 100 passing tests.
|