[bug #68033] mkoctfile does not work using version 11.0.92 on Windows 11
Markus Mützel <[email protected]>
| Newsgroups | gmane.comp.gnu.octave.bugs |
|---|---|
| Message-ID | <[email protected]> |
Please use the bug tracker to post updates to a bug report. The mailing list is intended as a read-only notification stream. Info posted to this mailing list address won't appear in the tracker database where it is most useful.
Follow-up Comment #12, bug #68033 (group octave):
One of the new tests is failing when testing cross-compiled Octave (using
qemu):
>>>>> processing
>>>>> /home/runner/work/octave/octave/.build/libinterp/corefcn/toplev.cc-tst
***** test <*68033>
[status, output] = system (sprintf ('"%s" "--version" 2>&1 1>%s', ...
octave_exe_path, nul_device));
assert (status, 0);
assert (ischar (output));
assert (isempty (output));
!!!!! regression: https://octave.org/testfailure/?68033
assert (isempty (output)) failed
shared variables
octave_exe_path = /home/runner/work/octave/octave/.build/src/octave
nul_device = /dev/null
Apparently, redirecting output doesn't work as expected. Another new test lead
to the following output during `make check`:
libinterp/corefcn/toplev.cc-tst ................................octave: X11
DISPLAY environment variable not set
octave: disabling GUI features
octave: X11 DISPLAY environment variable not set
octave: disabling GUI features
pass 12/13 [ 0.056s | 0.255s]
Given that this is on Linux and the actual changes from this report only
affect Windows, this is very likely not new. It is just revealed by the new
tests.
Should we do something about that? (My best guess is that this has something
to do with running executables through qemu-user-binfmt.)
Preferably, we could just skip those two tests when running with emulation.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68033>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
(application/pgp-signature, 228 B)
-----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaYscsQAKCRCqLAuaBUf3 TttWAQCjLyhyz/4VYWMcXb5pWZEQUTy4HLoQ2tqpLi6UndbviAEAn8iROAC/TfMS yawFCRdi1wbbVIDPN81OOoS590AXAA8= =1ZHp -----END PGP SIGNATURE-----