Use "octave-cli" instead of "octave", such that the unit tests will not wait for the GUI to launch. Also, use option --no-init-file, for avoiding idiosyncrasies from the user's octaverc, and --quiet, for having a cleaner output.
My apologies for not noticing this before the 1.0 release.
Yes, I also noticed that recent versions of octave have undefined behavior on starting GUI and command line interfaces, switching back and forth between releases. This is a good workaround.
Use "octave-cli" instead of "octave", such that the unit tests will not wait for the GUI to launch. Also, use option --no-init-file, for avoiding idiosyncrasies from the user's octaverc, and --quiet, for having a cleaner output.
My apologies for not noticing this before the 1.0 release.