ISOTOVIDEO(1)

πŸ“¦ version 5.1782197906.2148e4c5, in ubuntu stonking

πŸ’– ISOTOVIDEO β€” like, the whole vibe πŸ’–

okay bestie, so this is isotovideo, a page from the User Contributed Perl Documentation, and it's literally the girlboss that tests the given assets/ISOs for you. she parses your command line parameters, she reads your vars.json, and then she runs the tests. main character energy fr fr. πŸŽ€


✨ SYNOPSIS ✨

isotovideo [OPTIONS] [TEST PARAMETERS]

she parses command line parameters and vars.json, and then she tests the given assets/ISOs. that's the whole job. no cap. πŸ’…


🌸 OPTIONS 🌸

  • -d, --debug β€” turns on direct output straight to STDERR instead of writing it to autoinst-log.txt. lowkey unhinged but highkey useful when you're debugging. 🫢
  • --workdir= β€” isotovideo will chdir to that directory on startup. she just moves in. periodt. πŸ‘‘
  • --color=[yes|no] β€” explicitly enables or disables color output. defaults to "yes". alternatively you can set ANSI_COLORS_DISABLED or NO_COLOR to any value to disable colors. so many ways to say no to color, iconic. 🌈
  • -v, --version β€” shows the current program version and the test API version. she's telling you her age and her star sign. ⭐
  • -e, -?, --exit-status-from-test-results β€” isotovideo will exit with status 1 when a test module fails. dramatic exit, honestly deserved. πŸ’€
  • -h, -?, --help β€” shows this help. she's helping!! 🧚
⚠️ note that -? shows up twice, once for --exit-status-from-test-results and once for --help. that's just how it is, bestie. i don't make the rules.

πŸ¦‹ TEST PARAMETERS πŸ¦‹

all additional command line arguments written in the key=value format get parsed as test parameters, and these take precedence over the settings in the vars.json file. like, they win. and for pure convenience, lower case key names get transformed into upper case automatically. she's doing the extra work for you, so sweet. πŸ’œ


πŸ”₯ EXIT CODES πŸ”₯

  1. 0 β€” SUCCESS isotovideo successfully executed a complete run. and if you passed the --exit-status-from-test-results flag, additionally all test modules passed or softfailed. slay. ✨
  2. 1 β€” ERROR an error ocurred during the test execution related to a test backend failure. yeah, that one hurts. 😭
  3. 100 β€” NO TEST MODULES SCHEDULED no test module was scheduled.

this exit code can only be reported when invoked with the --exit-status-from-test-results flag.

  1. 101 β€” TEST MODULES FAILED at least one test module did not end with result "ok" or "softfail".

this exit code can only be reported when invoked with the --exit-status-from-test-results flag. πŸ’”


and that's the whole page!! this was generated by perl v5.42.3 on 2026-08-22, so shoutout to perl for the timestamp, and shoutout to you for reading all the way to the bottom. obsessed with you fr fr. go test those ISOs, bestie!! πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from