[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #48312] MXE Octave: test fails
From: |
Philip Nienhuis |
Subject: |
[Octave-bug-tracker] [bug #48312] MXE Octave: test fails |
Date: |
Sun, 26 Jun 2016 21:31:28 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 SeaMonkey/2.40 |
Follow-up Comment #9, bug #48312 (project octave):
AFAIK Nan/Inf mix-ups have been a MinGW issue for several years.
IIRC JWE has "fixed" these (or xfailed them) in the tests several months if
not a year ago or so.
printd.m - I based my conclusions on fntests.log (which is attached to comment
#6), I just noted similar output. I didn't look further :-)
But running the test by hand it shows strings r2 and r4 differ (leght of r4 =
224, r2 = 30).
I have no details on the fixed tests; I do not know how to run them.
"test io.tst" bails out with "fwrite: invalid stream number = -1" and "test
system.tst" gives:
***** assert (geteuid () >= 0)
!!!!! test failed
assert (geteuid () >= 0) failed
both "manual" tests stop right there.
It is really unfortunate that fntests.log gets clipped after
statistics\tests\z_test_2.m. Maybe a case of improper file buffer flushing?
I've been a bit sloppy in rigorously running ___run_test_suite___ in
cross-builds during the last months. I just noted that it also happens in a
w64 cross-build from early May.
I have quite a few older cross-builds archived back to Oct 2015, so I could
try a few more. Should I enter a separate bug report for this?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48312>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/25
- Message not available
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/25
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/26
- Message not available
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/26
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/26
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Mike Miller, 2016/06/26
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails,
Philip Nienhuis <=
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Mike Miller, 2016/06/26
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/27
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Mike Miller, 2016/06/27
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Avinoam Kalma, 2016/06/28
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/28
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/28
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Mike Miller, 2016/06/28
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Philip Nienhuis, 2016/06/28
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Mike Miller, 2016/06/29
- [Octave-bug-tracker] [bug #48312] MXE Octave: test fails, Mike Miller, 2016/06/30