Note: this was originally posted by @mbocek to github (previous forge where this project was hosted for a while):
$ jattool runtest /usr/share/jats/suite/demo/webackup
cannot reload session of different test
Workaround: $ rm -rf /var/tmp/jat/session/ to clean session from a previous failed test.
$ rm -rf /var/tmp/jat/session/
Thanks for the report!
This happens because of the way how JAT is designed to support interrupted test sessions (eg. reboot within test). The mechanism is kind of stupid: anytime when a session is being initiated but there is already an active one, it's automatically regarded as attempt to reload the old one.
At least it fails because test ids don't match. OTOH we have to expect tests to be able to crash, so I'll have to figure out how to handle this in more robust way.
For now I'll try to at least provide some more useful message. Also a simple session management CLI that will allow user to investigate what's running and throw it away without having to know the /var/tmp path, etc.
Metadata Update from @netvor:
- Issue tagged with: changes--func, isa--bug
to comment on this ticket.