hydra/t/test.pl
Rick van Schijndel 8858abb1a6
Some checks failed
Test / tests (push) Has been cancelled
t/test.pl: increase event-timeout, set qvf
Only log issues/failures when something's actually up.
It has irked me for a long time that so much output came
out of running the tests, this seems to silence it.
It does hide some warnings, but I think it makes the output
so much more readable that it's worth the tradeoff.

Helps for highly parallel running of jobs, sometimes they'd not give output for a while.
Setting this timeout higher appears to help.
Not completely sure if this is the right place to do it, but it works fine for me.
2024-08-11 16:08:35 +02:00

34 lines
965 B
Perl

#!/usr/bin/env perl
# HARNESS-NO-PRELOAD
# HARNESS-CAT-LONG
# THIS IS A GENERATED YATH RUNNER TEST
use strict;
use warnings;
use lib 'lib';
BEGIN {
use File::Which qw(which);
$App::Yath::Script::SCRIPT = which 'yath';
}
use App::Yath::Util qw/find_yath/;
use List::SomeUtils qw(none);
if (defined($ENV{"NIX_BUILD_CORES"})
and not defined($ENV{"YATH_JOB_COUNT"})
and not defined($ENV{"T2_HARNESS_JOB_COUNT"})
and not defined($ENV{"HARNESS_JOB_COUNT"})) {
$ENV{"YATH_JOB_COUNT"} = $ENV{"NIX_BUILD_CORES"};
print STDERR "test.pl: Defaulting \$YATH_JOB_COUNT to \$NIX_BUILD_CORES (${\$ENV{'NIX_BUILD_CORES'}})\n";
}
system($^X, find_yath(), '-D', 'test', '--qvf', '--event-timeout', 240, '--default-search' => './', @ARGV);
my $exit = $?;
# This makes sure it works with prove.
print "1..1\n";
print "not " if $exit;
print "ok 1 - Passed tests when run by yath\n";
print STDERR "yath exited with $exit" if $exit;
exit($exit ? 255 : 0);