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@INCbefore 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-Dwith no arg to addlib,blib/libandblib/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.rcfile. 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 allApp::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 aTest2::Plugin::Coversubclass.--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β useTest2::Plugin::Coverto collect coverage data for what files are touched by what tests. UnlikeDevel::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 byps).
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 fromMEDIUMtoLONG.--yathui-medium-duration 5,--no-yathui-medium-durationβ minimum duration length (seconds) before a test goes fromSHORTtoMEDIUM.--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
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
- ubuntu stonking: libtest2-harness-perl 1.000172-1 Β· Artistic-1.0-Perl OR GPL-1.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms