Sponsoring The Perl Toolchain Summit 2025: Help make this important event another success Learn more

use strict;
our $VERSION = '1.000017';
use Test2::Util::Table qw/table/;
option brief => (
prefix => 'display',
category => 'Display Options',
description => 'Show only files that failed, newline separated, no other output. If a file dailed once but passed on a retry it will NOT be shown.',
);
sub summary { "Replay a test run from an event log" }
sub group { 'log' }
sub cli_args { "[--] event_log.jsonl[.gz|.bz2] [job1, job2, ...]" }
sub description {
return <<" EOT";
This yath command will re-run the harness against an event log produced by a
previous test run. The only required argument is the path to the log file,
which maybe compressed. Any extra arguments are assumed to be job id's. If you
list any jobs, only listed jobs will be processed.
This command accepts all the same renderer/formatter options that the 'test'
command accepts.
EOT
}
sub run {
my $self = shift;
my $settings = $self->settings;
my $args = $self->args;
shift @$args if @$args && $args->[0] eq '--';
$self->{+LOG_FILE} = shift @$args or die "You must specify a log file";
die "'$self->{+LOG_FILE}' is not a valid log file" unless -f $self->{+LOG_FILE};
die "'$self->{+LOG_FILE}' does not look like a log file" unless $self->{+LOG_FILE} =~ m/\.jsonl(\.(gz|bz2))?$/;
my $stream = Test2::Harness::Util::File::JSONL->new(name => $self->{+LOG_FILE});
my %failed;
while(1) {
my @events = $stream->poll(max => 1000) or last;
for my $event (@events) {
my $stamp = $event->{stamp} or next;
my $job_id = $event->{job_id} or next;
my $f = $event->{facet_data} or next;
next unless $f->{harness_job_end};
next unless $f->{harness_job_end}->{fail} || $failed{$job_id};
push @{$failed{$job_id}} => $f->{harness_job_end};
}
}
my $rows = [];
while (my ($job_id, $ends) = each %failed) {
if ($settings->display->brief) {
print $ends->[-1]->{rel_file}, "\n" if $ends->[-1]->{fail};
}
else {
push @$rows => [$job_id, scalar(@$ends), $ends->[-1]->{rel_file}, $ends->[-1]->{fail} ? "NO" : "YES"];
}
}
return 0 if $settings->display->brief;
print "\nThe following jobs failed at least once:\n";
print join "\n" => table(
header => ['Job ID', 'Times Run', 'Test File', "Succeded Eventually?"],
rows => $rows,
);
print "\n";
return 0;
}
1;
__END__
=pod
=encoding UTF-8
=head1 NAME
App::Yath::Command::failed - Replay a test run from an event log
=head1 DESCRIPTION
This yath command will re-run the harness against an event log produced by a
previous test run. The only required argument is the path to the log file,
which maybe compressed. Any extra arguments are assumed to be job id's. If you
list any jobs, only listed jobs will be processed.
This command accepts all the same renderer/formatter options that the 'test'
command accepts.
=head1 USAGE
$ yath [YATH OPTIONS] failed [COMMAND OPTIONS]
=head2 YATH OPTIONS
=head3 Developer
=over 4
=item --dev-lib
=item --dev-lib=lib
=item -D
=item -D=lib
=item -Dlib
=item --no-dev-lib
Add paths to @INC before loading ANYTHING. This is what you use if you are developing yath or yath plugins to make sure the yath script finds the local code instead of the installed versions of the same code. You can provide an argument (-Dfoo) to provide a custom path, or you can just use -D without and arg to add lib, blib/lib and blib/arch.
Can be specified multiple times
=back
=head3 Environment
=over 4
=item --persist-dir ARG
=item --persist-dir=ARG
=item --no-persist-dir
Where to find persistence files.
=item --persist-file ARG
=item --persist-file=ARG
=item --pfile ARG
=item --pfile=ARG
=item --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 will fall back to the current directory. If the current directory is not writable it will default to /tmp/yath-persist.json which limits you to one persistent runner on your system.
=item --project ARG
=item --project=ARG
=item --project-name ARG
=item --project-name=ARG
=item --no-project
This lets you provide a label for your current project/codebase. This is best used in a .yath.rc file. This is necessary for a persistent runner.
=back
=head3 Help and Debugging
=over 4
=item --show-opts
=item --no-show-opts
Exit after showing what yath thinks your options mean
=item --version
=item -V
=item --no-version
Exit after showing a helpful usage message
=back
=head3 Plugins
=over 4
=item --no-scan-plugins
=item --no-no-scan-plugins
Normally yath scans for and loads all App::Yath::Plugin::* modules in order to bring in command-line options they may provide. This flag will disable that. This is useful if you have a naughty plugin that it loading other modules when it should not.
=item --plugins PLUGIN
=item --plugins +App::Yath::Plugin::PLUGIN
=item --plugins PLUGIN=arg1,arg2,...
=item --plugin PLUGIN
=item --plugin +App::Yath::Plugin::PLUGIN
=item --plugin PLUGIN=arg1,arg2,...
=item -pPLUGIN
=item --no-plugins
Load a yath plugin.
Can be specified multiple times
=back
=head2 COMMAND OPTIONS
=head3 Display Options
=over 4
=item --brief
=item --no-brief
Show only files that failed, newline separated, no other output. If a file dailed once but passed on a retry it will NOT be shown.
=back
=head3 Help and Debugging
=over 4
=item --dummy
=item -d
=item --no-dummy
Dummy run, do not actually execute anything
Can also be set with the following environment variables: C<T2_HARNESS_DUMMY>
=item --help
=item -h
=item --no-help
exit after showing help information
=item --keep-dirs
=item --keep_dir
=item -k
=item --no-keep-dirs
Do not delete directories when done. This is useful if you want to inspect the directories used for various commands.
=back
=head3 YathUI Options
=over 4
=item --yathui-api-key ARG
=item --yathui-api-key=ARG
=item --no-yathui-api-key
Yath-UI API key. This is not necessary if your Yath-UI instance is set to single-user
=item --yathui-grace
=item --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.
=item --yathui-long-duration 10
=item --no-yathui-long-duration
Minimum duration length (seconds) before a test goes from MEDIUM to LONG
=item --yathui-medium-duration 5
=item --no-yathui-medium-duration
Minimum duration length (seconds) before a test goes from SHORT to MEDIUM
=item --yathui-mode summary
=item --yathui-mode qvf
=item --yathui-mode qvfd
=item --yathui-mode complete
=item --no-yathui-mode
Set the upload mode (default 'qvfd')
=item --yathui-project ARG
=item --yathui-project=ARG
=item --no-yathui-project
The Yath-UI project for your test results
=item --yathui-retry
=item --no-yathui-retry
How many times to try an operation before giving up
Can be specified multiple times
=item --yathui-url http://my-yath-ui.com/...
=item --no-yathui-url
Yath-UI url
=back
=head1 SOURCE
The source code repository for Test2-Harness can be found at
=head1 MAINTAINERS
=over 4
=item Chad Granum E<lt>exodist@cpan.orgE<gt>
=back
=head1 AUTHORS
=over 4
=item Chad Granum E<lt>exodist@cpan.orgE<gt>
=back
=head1 COPYRIGHT
Copyright 2020 Chad Granum E<lt>exodist7@gmail.comE<gt>.
This program is free software; you can redistribute it and/or
modify it under the same terms as Perl itself.
=cut