unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: "Štěpán Němec" <stepnem@smrk.net>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: [PATCH 2/4] msgmap: mid_insert: reraise on unexpected errors, [PATCH 3/4] t/v2writable: test ENOSPC from fast-import
Date: Wed, 24 Jul 2024 09:22:29 +0200	[thread overview]
Message-ID: <20240724092229+0200.264800-stepnem@smrk.net> (raw)
In-Reply-To: <20240723212837.3931413-3-e@80x24.org> (Eric Wong's message of "Tue, 23 Jul 2024 21:28:35 +0000, Tue, 23 Jul 2024 21:28:36 +0000")

Just a few nits in the new test messages, if I may:

[2/4]:
On Tue, 23 Jul 2024 21:28:35 +0000
Eric Wong wrote:

> SQLITE_CONSTRAINT is the only SQLite error we really expect under
> normal circumstances.  This avoids infinite loops when writing
> to inboxes after hitting ENOSPC.
[...]
> diff --git a/t/msgmap.t b/t/msgmap.t
[...]
> @@ -70,4 +73,17 @@ is(eval {
>  	'ok'
>  }, 'ok', 'atfork_* work on tmp_clone');
>  
> -done_testing();
> +SKIP: {
> +	my $strace = strace_inject;
> +	open my $fh, '>', my $trace = "$tmpdir/trace.out";
> +	my $rd = popen_rd([ $strace, '-p', $$, '-o', $trace,
> +		'-e', 'inject=pwrite64:error=ENOSPC'], undef, { 2 => 1 });
> +	$rd->poll_in(10) or die 'strace not ready';
> +	is eval { $d->mid_insert('this-better-trigger-ENOSPC@error') },
> +		undef, 'insert fails w/ ENOSPC';
> +	like $@, qr/ disk is full/, 'set $@ for ENOSPC';
                                     ^^^^^^^^^^^^^^^^^
> +	kill 'TERM', $rd->attached_pid;
> +	$rd->close;
> +}
> +
> +done_testing;
> diff --git a/t/v2writable.t b/t/v2writable.t
[...]
> @@ -335,4 +337,18 @@ ok($@, 'V2Writable fails on non-existent dir');
>  	is($mode, 0664, sprintf('0%03o', $mode).' is 0664');
>  }
>  
> -done_testing();
> +SKIP: {
> +	my $strace = strace_inject;
> +	my $eml = eml_load 't/plack-qp.eml';
> +	open my $fh, '>', my $trace = "$inboxdir/trace.out";
> +	my $rd = popen_rd([ $strace, '-p', $$, '-o', $trace,
> +		'-e', 'inject=pwrite64:error=ENOSPC'], undef, { 2 => 1 });
> +	$rd->poll_in(10) or die 'strace not ready';
> +	ok ! eval { $im->add($eml) }, 'v2w->add fails on ENOSPC';
> +	like $@, qr/ disk is full/, 'set $@ for ENOSPC';
                                     ^^^^^^^^^^^^^^^^^

[3/4]:
On Tue, 23 Jul 2024 21:28:36 +0000
Eric Wong wrote:

> This also ensures we can recover after the ENOSPC condition
> is resolved.
> ---
>  t/v2writable.t | 34 +++++++++++++++++++++++++++++++++-
>  1 file changed, 33 insertions(+), 1 deletion(-)
>
> diff --git a/t/v2writable.t b/t/v2writable.t
> index a062d1b3..93385456 100644
> --- a/t/v2writable.t
> +++ b/t/v2writable.t
[...]
> @@ -340,15 +341,46 @@ ok($@, 'V2Writable fails on non-existent dir');
[...]
> +	$rd->poll_in(10) or die 'strace not ready';
> +	ok !eval { $im->done }, 'done fails with ENOSPC';
> +	ok $@, '$@ set on ENOSPC';
                ^^^^^^^^^^^^^^^^
If I'm correct in assuming that no semantic nuance is
intended between the 'set $@ for ENOSPC' and '$@ set on
ENOSPC' variants, I suggest unifying on the latter (the
unequivocal passive reads clearer than the
imperative-looking 'set $@').

[...]

> +	$im->add($eml) or xbail '->add fail after fixing ENOSPC';

s/fail/fails/ ?

> +	$im->done;
> +	ok !$im->add($eml), '->add detects existing message';
> +	$im->done;
> +	is -s $fh, 0, 'nothing new fast-import stderr';

s/new/new on/ ?

Thanks.

-- 
Štěpán

  reply	other threads:[~2024-07-24  7:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 21:28 [PATCH 0/4] fix ENOSPC on writes Eric Wong
2024-07-23 21:28 ` [PATCH 1/4] t/msgmap: updates for Perl 5.12+ and copyrights Eric Wong
2024-07-23 21:28 ` [PATCH 2/4] msgmap: mid_insert: reraise on unexpected errors Eric Wong
2024-07-24  7:22   ` Štěpán Němec [this message]
2024-07-25  0:38     ` [PATCH 2/4] msgmap: mid_insert: reraise on unexpected errors, [PATCH 3/4] t/v2writable: test ENOSPC from fast-import Eric Wong
2024-07-25  6:42       ` Štěpán Němec
2024-07-23 21:28 ` Eric Wong
2024-07-23 21:28 ` [PATCH 4/4] t/v2writable: use 5.10.1 and autodie more Eric Wong
2024-07-26 21:31 ` [PATCH v2 0/4] fix ENOSPC on writes Eric Wong
2024-07-26 21:31   ` [PATCH v2 1/4] t/msgmap: updates for Perl 5.12+ and copyrights Eric Wong
2024-07-26 21:31   ` [PATCH v2 2/4] msgmap: mid_insert: reraise on unexpected errors Eric Wong
2024-07-26 21:31   ` [PATCH v2 3/4] t/v2writable: test ENOSPC from fast-import Eric Wong
2024-07-26 21:31   ` [PATCH v2 4/4] t/v2writable: use 5.10.1 and autodie more Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240724092229+0200.264800-stepnem@smrk.net \
    --to=stepnem@smrk.net \
    --cc=e@80x24.org \
    --cc=meta@public-inbox.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).