[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failu
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 17:10:57 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Follow-up Comment #20, bug #54180 (project octave):
This is fine. Originally, I thought about using whos because there was extra
information--specifically the global flag--which I thought might provide a way
to ensure that no variables changed nature during the tests. But the way you
did it seems like it will be faster and have a smaller memory footprint.
If you create a global variable in the base workspace this is reported twice:
1) as a variable created in the base workspace, and 2) as a global variable
created in the base workspace. Could eliminate that by using setdiff one more
time to subtract the global variables from the local variables. But, it
probably isn't worth it. This shouldn't be happening very frequently and
should be corrected immediately.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?54180>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, (continued)
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, John W. Eaton, 2018/06/25
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Rik, 2018/06/25
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Dan Sebald, 2018/06/25
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Rik, 2018/06/26
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Andrew Janke, 2018/06/26
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Rik, 2018/06/27
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Rik, 2018/06/29
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Dan Sebald, 2018/06/29
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, Rik, 2018/06/29
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice, John W. Eaton, 2018/06/29
- [Octave-bug-tracker] [bug #54180] libinterp/corefcn/file-io.cc-tst failure and weird output when test suite is run twice,
Rik <=