From: Ruediger Meier <sweet_f_a@gmx.de>
To: util-linux@vger.kernel.org
Subject: Re: [PATCH] tests: add test for loop option in fstab
Date: Fri, 12 Feb 2016 17:23:09 +0100 [thread overview]
Message-ID: <201602121723.09217.sweet_f_a@gmx.de> (raw)
On Friday 12 February 2016 at 16:55, you wrote:
> Ruediger Meier wrote:
> > On Thursday 11 February 2016, Stanislav Brabec wrote:
> >> Add a new fstab tests which check loop mount of the same source
> >> multiple times in multiple steps.
> >>
> >> The test is currently failing, but it should not fail once the
> >> triggering bug will be fixed.
> >
> > Will this be fixed quickly? Otherwise we should add
> > TS_KNOWN_FAIL="yes"
> > to the test. Then you would still see it in the build log and test
> > diff but it wouldn't bother you with build error.
>
> This statement was valid in the time of sending the patch. Karel
> promptly fixed it, so the fix appeared in the main tree even one
> commit earlier:
Ah sorry I've missed that. The test fails for me because of another
minor problem. I'll send a patch.
cu,
Rudi
next reply other threads:[~2016-02-12 16:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 16:23 Ruediger Meier [this message]
2016-02-12 16:28 ` [PATCH] tests: mkfs.ext3 image-file needs option -F Ruediger Meier
2016-02-12 17:09 ` Karel Zak
-- strict thread matches above, loose matches on Subject: below --
2016-02-11 19:45 [PATCH] tests: add test for loop option in fstab Stanislav Brabec
2016-02-12 10:10 ` Karel Zak
2016-02-12 15:28 ` Ruediger Meier
2016-02-12 15:55 ` Stanislav Brabec
2016-02-15 11:42 ` Ruediger Meier
2016-02-16 14:49 ` Karel Zak
2016-02-19 18:27 ` Stanislav Brabec
2016-02-22 10:12 ` Karel Zak
2016-02-22 10:29 ` Ruediger Meier
2016-02-22 10:53 ` Karel Zak
2016-02-22 16:36 ` Stanislav Brabec
2016-02-24 18:58 ` Stanislav Brabec
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201602121723.09217.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.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