Back to the main page.

Bug 1714 - Some automated tests only fail when run on Torque

Status CLOSED FIXED
Reported 2012-09-17 15:31:00 +0200
Modified 2019-08-10 11:55:49 +0200
Product: FieldTrip
Component: release
Version: unspecified
Hardware: PC
Operating System: Linux
Importance: P3 normal
Assigned to:
URL:
Tags:
Depends on:
Blocks:
See also:

Boris Reuderink - 2012-09-17 15:31:45 +0200

Jan-Mathijs reported last week that he fixed a bug in test_ft_plot_vector, but that the Dashboard still shows a failing test. I dug into the problem, and when I schedule a test manually using the exact same scripts, it shows that the test passes, but when the test is scheduled on Torque, it fails with an unclear error: ===== Test Case Failure ===== Location: /home/mrphys/borreu/code/ft-test/revs/r6467/plotting/test/test_ft_plot_vector.m Name: test_ft_plot_vector /home/mrphys/borreu/code/matlab-env/fieldtrip/plotting/ft_plot_vector.m at line 220 /home/mrphys/borreu/code/ft-test/revs/r6467/plotting/test/test_ft_plot_vector.m at line 16 Attempted to access hdat(10); index out of bounds because numel(hdat)=1.


Robert Oostenveld - 2012-09-17 15:36:59 +0200

it suggests that somehow the data is different in the two cases. I suggest you try with a locally modified version of ft_plot_vector that as very first thing does save(tempfilename) i.e. save all input arguments to a mat file. Also you might want to do disp(path) and disp(pwd) in the ft_plot_vector function.


Boris Reuderink - 2012-09-27 13:54:58 +0200

Indeed it was a path issue; the test all were run with my manually updated SVN version on the path :/. Now the issue is resolved with a 'restoredefaultpath', and indeed ft_plot_vector is passing as it should.


Boris Reuderink - 2012-09-27 13:55:39 +0200

PS: I purged all previous test results since their revision is now unreliable.


Boris Reuderink - 2012-11-02 13:29:54 +0100

I am no longer working on FieldTrip. Hence, I donate all my bugs to the joint development user.


Robert Oostenveld - 2019-08-10 11:51:52 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on https://github.com/fieldtrip/fieldtrip/issues.


Robert Oostenveld - 2019-08-10 11:55:49 +0200

This closes a whole series of bugs that have been resolved (either FIXED/WONTFIX/INVALID) for quite some time. If you disagree, please file a new issue describing the issue on https://github.com/fieldtrip/fieldtrip/issues.