FLUSTER(1)

✨ FLUSTER(1) ✨

okay so you're looking at the manual page for fluster — yes, the fluster(1) one, the video decoder conformance testing queen 👑

---

🌸 NAME 🌸

fluster — a testing framework for video decoder conformance 💅

---

🦋 SYNOPSIS 🦋

fluster [-h] [-r RESOURCES] [-o OUTPUT] [-ne] [-tsd TEST_SUITES_DIR]
{list,l,run,r,download,d,reference,f}

---

💜 DESCRIPTION 💜

so fluster is a testing framework, and it's written in Python, and its whole personality is video decoder conformance. it's literally made of a command-line application that runs a bunch of test suites against the decoders you've got, bestie. 🫶

its whole thing is checking different decoder implementations against known test suites that have known and proven results. like, the receipts are already in the group chat, we're just seeing who matches them. ✨

it was originally designed to check the conformance of H.265/HEVC decoders, but it ALSO supports H.264/AVC, H.266/VVC, VP8, VP9, AV1 and AAC. she's versatile, she's multi-talented, she ate. 🔥

---

🎀 OPTIONS 🎀

• -h, --help — show the help message and dip. that's it, that's the whole vibe 🙈
• -r RESOURCES, --resources RESOURCES — set the directory where resources are taken from.
• -o OUTPUT, --output OUTPUT — set the directory where test results will be stored.
• -ne OUTPUT, --no-emoji — set this to use plain text instead of emojis. (yes bestie, no emojis. tragic but valid 😭)
• -tsd TEST_SUITES_DIR, --test-suites-dir TEST_SUITES_DIR — set the directory where the test suite will be read from.

---

👑 FLUSTER COMMANDS 👑

🌈 list (l)

Show a list of available test suites and decoders. window shopping, no commitment, iconic. 🛍️

---

🧚 run (r)

Run test suites for decoders. this is the main character command fr fr 💅

Options:

• -j JOBS, --jobs JOBS — number of parallel jobs to use. defaults to 1x logical cores. 0 means all logical cores.
• -t TIMEOUT, --timeout TIMEOUT — timeout in secs for each decoding. defaults to 30 secs.
• -ff, --failfast — stop after first fail. no notes, we move on ✋
• -q, --quiet — don't show every test run. silence is golden, lowkey.
• -ts TESTSUITES, --testsuites TESTSUITES — run only the specific test suites.
• -tv TESTVECTORS, --testvectors TESTVECTORS — run only the specific test vectors.
• -d DECODERS, --decoders DECODERS — run only the specific decoders.
• -s, --summary — generate a summary in Markdown format for each test suite.
• -so SUMMARY_OUTPUT, --summary-output SUMMARY_OUTPUT — dump summary output to file.
• -f {md,csv,junitxml}, --format {md,csv,junitxml} — specify the format for the summary file. pick your fighter: md, csv or junitxml ⭐
• -k, --keep — keep output files generated during the test. hoarder energy, we love her 🎀
• -th THRESHOLD, --threshold THRESHOLD — set exit code to 2 if threshold tests are not success. exit code is 0 otherwise.
• -tth TIME_THRESHOLD, --time-threshold TIME_THRESHOLD — set exit code to 3 if the test suite takes longer than threshold seconds. exit code is 0 otherwise. she's on a schedule bestie ⏰
• -v, --verbose — show stdout and stderr of commands executed. spill the tea, all of it ☕

---

🍓 download (d) testsuites

Downloads test suites resources. fetch, but make it conformance testing 🫶

Arguments:

• testsuites — list of testsuites to download. defaults to all.

Options:

• -j JOBS, --jobs JOBS — number of parallel jobs to use. defaults to 2x logical cores. 0 means all logical cores. (yes, 2x here, not 1x — read the room 👀)
• -k, --keep — keep the original downloaded file after extracting. only applicable to compressed files such as .zip, .tar.gz, etc.

---

💫 reference (r)

Use a specific decoder to set its results for the test suites given. setting the blueprint, being the standard, main character behaviour ngl 💅

Options:

• -j JOBS, --jobs JOBS — number of parallel jobs to use. defaults to 1x logical cores. 0 means all logical cores.
• -t TIMEOUT, --timeout TIMEOUT — timeout in secs for each decoding. defaults to 30 secs.
• -ff, --failfast — stop after first fail.
• -q, --quiet — don't show every test run.
• -ts TESTSUITES, --testsuites TESTSUITES — run only the specific test suites.
• -tv TESTVECTORS, --testvectors TESTVECTORS — run only the specific test vectors.
• -d DECODERS, --decoders DECODERS — run only the specific decoders.
• -s, --summary — generate a summary in Markdown format for each test suite.
• -so SUMMARY_OUTPUT, --summary-output SUMMARY_OUTPUT — dump summary output to file.
• -f {md,csv,junitxml}, --format {md,csv,junitxml} — specify the format for the summary file.
• -k, --keep — keep output files generated during the test.
• -th THRESHOLD, --threshold THRESHOLD — set exit code to 2 if threshold tests are not success. exit code is 0 otherwise.
• -tth TIME_THRESHOLD, --time-threshold TIME_THRESHOLD — set exit code to 3 if the test suite takes longer than threshold seconds. exit code is 0 otherwise.
• -v, --verbose — show stdout and stderr of commands executed.

---

💖 AUTHORS 💖

fluster is developed by Pablo Marcos Oltra, Andoni Morales Alastruey and contributors. absolute legends, no cap 👑

This manual page was written by Christopher Obbard <obbardc@debian.org> for the Debian GNU/Linux system (but may be used by others). shoutout to him, he did that 💅

---

and that's the whole page bestie ✨ you just read the fluster(1) manual page — go run some conformance tests, slay, and remember: the exit codes are 0, 2 and 3, and they mean things 🎀 💜 🦋