App::Y...failed(3pm)

✨ NAME ✨

App::Yath::Command::failed β€” show the failed tests from an event log πŸ’…

(this is a User Contributed Perl Documentation page, bestie, so you know it's real)


πŸ’– DESCRIPTION πŸ’–

okay so, this yath command is literally the girl who remembers who failed. It lists all the test scripts from an event log that have failed 😭

The only required argument is the path to the log file β€” and yes, that log file can be compressed, go off compressed logs 🫢

Any extra arguments you toss in are assumed to be job id's. And if you list any jobs, then only the listed jobs get processed. Nothing else. It's giving selective attention, and honestly? Iconic.

Also β€” this command accepts all the same renderer/formatter options that the test command accepts. Same energy, different job. πŸ¦‹


πŸŽ€ USAGE πŸŽ€

$ yath [YATH OPTIONS] failed [COMMAND OPTIONS]

YATH OPTIONS 🌈

Developer πŸ’»

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib, --no-dev-lib β€” add paths to @INC before loading ANYTHING. This is the one you use if you're developing yath or yath plugins, so the yath script finds your local code instead of the installed versions of that same code. You can pass an argument (-Dfoo) to give a custom path, or just use -D with no arg to add lib, blib/lib and blib/arch. Can be specified multiple times ✨

Environment 🌸

  • --persist-dir ARG, --persist-dir=ARG, --no-persist-dir β€” where to find persistence files.
  • --persist-file ARG, --persist-file=ARG, --pfile ARG, --pfile=ARG, --no-persist-file β€” where to find the persistence file. The default is /{system-tempdir}/project-yath-persist.json. If no project is specified then it falls back to the current directory. If the current directory is not writable it defaults to /tmp/yath-persist.json, which limits you to one persistent runner on your system. no cap 🫠
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project β€” this lets you provide a label for your current project/codebase. Best used in a .yath.rc file. This is necessary for a persistent runner. You need this one bestie πŸ’œ

Help and Debugging πŸ”

  • --show-opts, --no-show-opts β€” exit after showing what yath thinks your options mean.
  • --version, -V, --no-version β€” exit after showing a helpful usage message.

Plugins 🧩

  • --no-scan-plugins, --no-no-scan-plugins β€” normally yath scans for and loads all App::Yath::Plugin::* modules so it can bring in the command-line options they may provide. This flag disables that. Useful if you have a naughty plugin that's loading other modules when it should not. Not the vibe πŸ™ˆ
  • --plugins PLUGIN, --plugins +App::Yath::Plugin::PLUGIN, --plugins PLUGIN=arg1,arg2,..., --plugin PLUGIN, --plugin +App::Yath::Plugin::PLUGIN, --plugin PLUGIN=arg1,arg2,..., -pPLUGIN, --no-plugins β€” load a yath plugin. Can be specified multiple times πŸ”₯

COMMAND OPTIONS πŸ‘‘

Cover Options 🌈

  • --cover-aggregator ByTest, --cover-aggregator ByRun, --cover-aggregator +Custom::Aggregator, --cover-agg ByTest, --cover-agg ByRun, --cover-agg +Custom::Aggregator, --no-cover-aggregator β€” choose a custom aggregator subclass.
  • --cover-class ARG, --cover-class=ARG, --no-cover-class β€” choose a Test2::Plugin::Cover subclass.
  • --cover-dirs ARG, --cover-dirs=ARG, --cover-dir ARG, --cover-dir=ARG, --no-cover-dirs β€” NO DESCRIPTION - FIX ME πŸ™ˆ Can be specified multiple times.
  • --cover-exclude-private, --no-cover-exclude-private, --cover-files, --no-cover-files β€” use Test2::Plugin::Cover to collect coverage data for what files are touched by what tests. Unlike Devel::Cover, this has very little performance impact (about 4% difference). slay, low overhead πŸ’…
  • --cover-from path/to/log.jsonl, --cover-from http://example.com/coverage, --cover-from path/to/coverage.jsonl, --no-cover-from β€” this can be a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. Tests will not be run if the file/url is invalid. ⚠️
  • --cover-from-type json, --cover-from-type jsonl, --cover-from-type log, --no-cover-from-type β€” file type for the coverage source. Usually it can be detected, but when it cannot be, you should specify. "json" is old style single-blob coverage data, "jsonl" is the new by-test style, "log" is a logfile from a previous run.
  • --cover-manager My::Coverage::Manager, --no-cover-manager β€” the coverage 'from' manager to use when coverage data does not provide one.
  • --cover-maybe-from path/to/log.jsonl, --cover-maybe-from http://example.com/coverage, --cover-maybe-from path/to/coverage.jsonl, --no-cover-maybe-from β€” this can be a test log, a coverage dump (old style json or new jsonl format), or a url to any of the previous. Tests will coninue even if the coverage file/url is invalid. (yes, "coninue" β€” the manpage said it, so I say it πŸŽ€)
  • --cover-maybe-from-type json, --cover-maybe-from-type jsonl, --cover-maybe-from-type log, --no-cover-maybe-from-type β€” same as "from_type" but for "maybe_from". Defaults to "from_type" if that is specified, otherwise auto-detect.
  • --cover-metrics, --no-cover-metrics, --cover-types ARG, --cover-types=ARG, --cover-type ARG, --cover-type=ARG, --no-cover-types β€” NO DESCRIPTION - FIX ME πŸ™ˆ Can be specified multiple times.
  • --cover-write, --cover-write=coverage.jsonl, --cover-write=coverage.json, --no-cover-write β€” create a json or jsonl file of all coverage data seen during the run (this implies --cover-files).

Display Options πŸ¦‹

  • --brief, --no-brief β€” show only the files that failed, newline separated, no other output. If a file failed once but passed on a retry it will NOT be shown. periodt πŸ’…

Git Options ⭐

  • --git-change-base master, --git-change-base HEAD^, --git-change-base df22abe4, --no-git-change-base β€” find files changed by all commits in the current branch, from most recent, stopping when a commit is found that is also present in the history of the branch/commit specified as the change base.

Help and Debugging πŸ’œ

  • --dummy, -d, --no-dummy β€” dummy run, do not actually execute anything. Can also be set with the following environment variables: "T2_HARNESS_DUMMY".
  • --help, -h, --no-help β€” exit after showing help information.
  • --interactive, -i, --no-interactive β€” use interactive mode, 1 test at a time, stdin forwarded to it.
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs β€” do not delete directories when done. Useful if you want to inspect the directories used for various commands.
  • --procname-prefix ARG, --procname-prefix=ARG, --no-procname-prefix β€” add a prefix to all proc names (as seen by ps).

YathUI Options πŸŽ€

  • --yathui-api-key ARG, --yathui-api-key=ARG, --no-yathui-api-key β€” Yath-UI API key. Not necessary if your Yath-UI instance is set to single-user.
  • --yathui-grace, --no-yathui-grace β€” if yath cannot connect to yath-ui it normally throws an error; use this to make it fail gracefully. You get a warning, but things keep going. she's resilient πŸ’–
  • --yathui-long-duration 10, --no-yathui-long-duration β€” minimum duration length (seconds) before a test goes from MEDIUM to LONG.
  • --yathui-medium-duration 5, --no-yathui-medium-duration β€” minimum duration length (seconds) before a test goes from SHORT to MEDIUM.
  • --yathui-mode summary, --yathui-mode qvf, --yathui-mode qvfd, --yathui-mode complete, --no-yathui-mode β€” set the upload mode (default 'qvfd').
  • --yathui-project ARG, --yathui-project=ARG, --no-yathui-project β€” the Yath-UI project for your test results.
  • --yathui-retry, --no-yathui-retry β€” how many times to try an operation before giving up. Can be specified multiple times.
  • --yathui-url http://my-yath-ui.com/..., --uri http://my-yath-ui.com/..., --no-yathui-url β€” Yath-UI url.

🌈 SOURCE

The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/. go star it bestie ⭐


πŸ‘‘ MAINTAINERS

Chad Granum <exodist@cpan.org>


πŸ’œ AUTHORS

Chad Granum <exodist@cpan.org>


Copyright 2026 Chad Granum <exodist7@gmail.com>.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

See http://dev.perl.org/licenses/


aaaand that's the whole page bestie 🫢 this was App::Y...failed(3pm), living in perl v5.40.1, dated 2026-05-10, and it ate. no notes. πŸ’…βœ¨

πŸ“¦ where this page comes from