octave also has an option to show the code it executes.
That has given me the same snippet for both tests it triggers.
47367 + if (__verbose < 1)
47368 + fprintf (__fid, "%s%s\n", __signal_block, __block);
47369 + fflush (__fid);
47370 + endif
47371 + fprintf (__fid, "%s\n", __msg);
47372 !!!!! test failed
47373 int32 scalar cannot be indexed with {
47374 + ## Show the variable context.
47375 + if (! strcmp (__type, "error")
47376 + && ! strcmp (__type, "testif")
47377 + && ! strcmp (__type, "xtest")
47378 + && ! all (__shared == " "))
That code is from
octave-common: /usr/share/octave/6.1.1~hg.2020.12.27-1/m/testfun/test.m
And it really seems it did just print that former error.
That message is constructed at
persistent __signal_fail = "!!!!! ";
...
__msg = "test failed";
endif
__msg = [__signal_fail __msg "\n" lasterr()];
So we'd want to add something like stacktrace() when this is
constructed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911400
Title:
autopkgtests broken in hirsute - error: int32 scalar cannot be indexed
with .
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/octave/+bug/1911400/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
