All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Cc: daniel.kiper@oracle.com,development@efficientek.com
Subject: Re: [PATCH v3] tests: Add pathological iso9660 filesystem tests
Date: Thu, 16 Feb 2023 19:36:40 +0100	[thread overview]
Message-ID: <46553908148521047429@scdbackup.webframe.org> (raw)
In-Reply-To: <20230216115920.224b16cc@crass-HP-ZBook-15-G2>

Hi,

Glenn Washburn wrote:
> > > +echo "Testing for proper recognition of CE loops ... "
> Ugh, this should be "echo -n".

My make "check" wrote:
> >   Testing for proper recognition of CE loops ...
> >   FAIL (iso9660_ce_loop)
> >   FAIL iso9660_test (exit status: 1)

Actually this looks quite ok to me.

With
  echo -n "Testing for proper recognition of CE loops ... "
and a disabled loop breaker i get in test-suite.log:

  Testing for proper recognition of CE loops ... FAIL (iso9660_ce_loop)
  FAIL iso9660_test (exit status: 1)

which looks to me like a newline is missing.


The combination of "echo -n" and "..." seems not to occur in the GRUB code:
  $ grep -r 'echo -n .*\.\.\.' . | less

Some echo without -n have "...":
  $ grep -r 'echo .*\.\.\.' . | wc -l
  65
  $ grep -r 'echo .*\.\.\.' tests
  tests/partmap_test.in:echo "Checking MSDOS partition types..."
  tests/partmap_test.in:echo "Checking GPT partition types..."
  tests/partmap_test.in:echo "Checking SUN partition types..."
  tests/partmap_test.in:echo "Checking APPLE partition types..."
  tests/partmap_test.in:echo "Checking DVH partition types..."
  tests/partmap_test.in:echo "Checking AMIGA partition types..."
  tests/partmap_test.in:echo "Checking DragonFly BSD disklabel64..."
  $

If "..." as line end is too near to ./configure style, then how about

  echo "Testing for proper recognition of CE loops:"


Have a nice day :)

Thomas



  reply	other threads:[~2023-02-16 18:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  7:04 [PATCH v3] tests: Add pathological iso9660 filesystem tests Glenn Washburn
2023-02-16 12:20 ` Thomas Schmitt
2023-02-16 17:59   ` Glenn Washburn
2023-02-16 18:36     ` Thomas Schmitt [this message]
2023-02-18 22:33       ` Glenn Washburn

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=46553908148521047429@scdbackup.webframe.org \
    --to=scdbackup@gmx.net \
    --cc=daniel.kiper@oracle.com \
    --cc=development@efficientek.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.