[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57236] [octave forge] (netcdf) failure in tes
From: |
Mike Miller |
Subject: |
[Octave-bug-tracker] [bug #57236] [octave forge] (netcdf) failure in test_netcdf |
Date: |
Thu, 21 Nov 2019 15:32:50 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36 |
Follow-up Comment #5, bug #57236 (project octave):
Ah, I just brute forced the test suite by adding a new private function to
each of the inst/private/test_netcdf_... files. The difference is whether the
file in inst/private is a script or a function file.
Any of the private function files (test_netcdf_constant.m,
test_netcdf_create.m, test_netcdf_datatypes.m, etc) are allowed to call other
private functions or scripts.
But any of the private scripts, such as test_netcdf_high_level_interface.m,
cannot call a private function file even if it's in the same directory. That
seems to be a change from Octave 5.1, not sure if it's intentional or not.
So another valid fix would be to turn test_netcdf_high_level_interface.m into
a function file.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57236>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/