|
From: | Mike Miller |
Subject: | [Octave-bug-tracker] [bug #55577] test in file-io.cc-tst fails on Octave 5.0.90 (only in GUI with run_test_suite) |
Date: | Fri, 25 Jan 2019 17:34:05 -0500 (EST) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36 |
Follow-up Comment #2, bug #55577 (project octave): I also think this particular test might be outdated. These input validation tests %!error textscan (single (40)) %!error textscan ({40}) have been in Octave since 3.6.4 (with the value 4 instead of 40). They used to both return an error about the _type_ of the argument. But starting with Octave 4.2, the input validation changed and the error message changed. This is also when textscan was rewritten as a compiled function. Octave 4.0: >> textscan (single (40)) error: textscan: first argument must be a file id or character string error: called from textscan at line 108 column 5 Octave 4.2 and later: >> textscan (single (40)) error: textscan: invalid stream number = 40 Maybe you have enough open files in your Octave session that 40 is a valid file descriptor, and the test is not producing an error. Maybe having open tabs in the file editor counts against the file descriptor count, so this number may be higher? So really I think this test should be deleted, if textscan now accepts a single argument as a valid file descriptor. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?55577> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |