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

๐Ÿ’– NAME ๐Ÿ’–

App::Yath::Command::times โ€” ok bestie, this is the yath subcommand that goes and fetches alllll the timing data out of a test log. You're reading the manual for App::Y...::times(3pm) and honestly? You're gonna slay this. ๐Ÿ•โœจ


๐ŸŒธ DESCRIPTION ๐ŸŒธ

So here's the vibe: this command eats the log from a previous run and then spits out every single piece of timing data, sorted from the shortest test to the longest one. ๐Ÿขโžก๏ธ๐Ÿ‡

And because you're a main character who has opinions, you can pick your own sort order โ€” just list the fields you want, in the order you want them, right there after the log file on the command line. The order you type them is the order they get sorted. Iconic, honestly. ๐Ÿ’…


๐Ÿฆ‹ USAGE ๐Ÿฆ‹

$ yath [YATH OPTIONS] times [COMMAND OPTIONS]

โœจ YATH OPTIONS โœจ

๐Ÿ”ง Developer ๐Ÿ”ง

  • --dev-lib, --dev-lib=lib, -D, -D=lib, -Dlib, --no-dev-lib โ€” adds paths to @INC before ANYTHING gets loaded. This is literally the one you reach for when you're developing yath itself or writing yath plugins โ€” it makes sure the yath script finds your local code instead of the installed versions of that same code. You can hand it an argument (-Dfoo) to give it a custom path, or you can just raw-dog -D with no arg and it'll add lib, blib/lib and blib/arch for you. ๐Ÿซถ

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 it falls back to the current directory. And if the current directory isn't writable, it defaults to /tmp/yath-persist.json โ€” which, heads up, limits you to one persistent runner on your whole system. ๐Ÿ˜ญ
  • --project ARG, --project=ARG, --project-name ARG, --project-name=ARG, --no-project โ€” this lets you slap a label on your current project/codebase. Best used in a .yath.rc file. And ngl, this one is necessary for a persistent runner. No label, no persistent runner, no cap. ๐Ÿ‘‘

๐Ÿ†˜ Help and Debugging ๐Ÿ†˜

  • --show-opts, --no-show-opts โ€” exits right after showing you what yath thinks your options mean. Vibe check on your own flags, love that for you. ๐Ÿ”
  • --version, -V, --no-version โ€” exits after showing a helpful usage message.

๐Ÿงš Plugins ๐Ÿงš

  • --no-scan-plugins, --no-no-scan-plugins โ€” normally yath scans for and loads every App::Yath::Plugin::* module so it can bring in whatever command-line options those plugins provide. This flag disables that whole thing. It's useful when you've got a naughty plugin that's loading other modules when it absolutely should not be. ๐Ÿ™ˆ
  • --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 about what files get touched by what tests. Unlike Devel::Cover, this has very little performance impact (About 4% difference). Four percent!! That's basically nothing, we love a low-cost queen. ๐Ÿ”ฅ
  • --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 pointing at 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 can't you should specify it yourself. Here's the tea: json is old style single-blob coverage data, jsonl is the new by-test style, and log is a logfile from a previous run. ๐Ÿ—‚๏ธ
  • --cover-manager My::Coverage::Manager, --no-cover-manager โ€” coverage 'from' manager to use when the coverage data doesn't 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 if even if the coverage file/url is invalid. (yep, that typo is canon, we keep it fr fr ๐Ÿ˜Œ)
  • --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's 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). ๐Ÿ—ƒ๏ธ

๐Ÿ™ 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, starting from the most recent and stopping when it hits a commit that's also present in the history of the branch/commit you 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, with stdin forwarded to it. ๐ŸŽฎ
  • --keep-dirs, --keep_dir, -k, --no-keep-dirs โ€” do not delete directories when done. This is useful if you want to go poke around 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. This is 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. ๐Ÿง˜โ€โ™€๏ธ
  • --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


๐Ÿ“ฆ SOURCE ๐Ÿ“ฆ

The source code repository for Test2-Harness can be found at http://github.com/Test-More/Test2-Harness/. Go clone it bestie, it's free. ๐ŸŒˆ


๐Ÿซถ 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/


๐Ÿ’– and that's a wrap!! this was perl v5.40.1, dated 2026-05-10, manual page App::Y...::times(3pm) โ€” now go forth and sort some timings, you absolute legend ๐Ÿ’–
๐Ÿ“ฆ where this page comes from