|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice |
Date: | Fri, 29 Jun 2018 12:49:28 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #16, bug #54180 (project octave): For the development branch, I pushed a cset (http://hg.savannah.gnu.org/hgweb/octave/rev/a87b4dca2ce3) that will emit a warning if a file has %!tests which leak file descriptors. Do we want to do something similar for global variables? How about for any variables? I would think that the ideal tests are run in their own workspace and don't pollute the base workspace at all. Normally, that would only mean checking for new globals, but since there are tests for evalin it is possible that local variables could also be created in the caller workspace which would be the base workspace. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?54180> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |