sed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: new snapshot available: sed-4.7.13-3c1e


From: Assaf Gordon
Subject: Re: new snapshot available: sed-4.7.13-3c1e
Date: Mon, 6 Jan 2020 12:31:46 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0

Hello Jim,

On 2020-01-05 5:13 p.m., Jim Meyering wrote:
It's been a year since the preceding release, so this feels overdue.
Please give it a whirl and let us know how it goes.

sed snapshot:
   https://meyering.net/sed/sed-4.7.13-3c1e.tar.xz

Thanks for that!

TL;DR - I believe non of these (and Bruno's recent reports) are
show-stoppers. Most of them are false-positives.

---

To complement Bruno's testing (thanks Bruno!),
I'm seeing the following. My analysis below.

No failures on the following:
  Debian 8.11 (i686)
  Debian unstable (sparc64)
  FreeBSD 12.1-RELEASE-p1 (amd64)
  CentOS 7 - Linux 3.10.0-862.14.4.el7.ppc64 (ppc64)
  CentOS 7 - Linux 3.10.0-957.12.2.el7.x86_64 (x86_64)
  CentOS 7 - Linux 3.10.0-957.21.3.el7.ppc64le (ppc64le)
  Alpine 3.10.3 Linux 4.19.80-0-virt (x86_64)
  OpenBSD 6.6 (amd64)
  Oracle SunOS 5.11 (i86pc)
  Oracle SunOS 5.11 (sun4u)
  Raspbian 10 (armv7l)
  Ubuntu 14.04 (aarch64)

And the following failures:

  Oracle SunOS 5.10/i86pc:
     FAIL: testsuite/misc
     FAIL: testsuite/debug

  Cygwin 10/64bit with GCC:
     FAIL: testsuite/panic-tests

  NetBSD 8.1:
     FAIL: testsuite/cmd-l
     FAIL: testsuite/colon-with-no-label
     FAIL: testsuite/compile-errors
     FAIL: testsuite/compile-tests
     FAIL: testsuite/in-place-suffix-backup
     FAIL: testsuite/mb-bad-delim
     FAIL: testsuite/mb-y-translate
     FAIL: testsuite/missing-filename
     FAIL: testsuite/normalize-text
     FAIL: testsuite/panic-tests
     FAIL: testsuite/posix-mode-addr
     FAIL: testsuite/posix-mode-bad-ref
     FAIL: testsuite/posix-mode-s
     FAIL: testsuite/recursive-escape-c
     FAIL: testsuite/regex-errors
     FAIL: testsuite/sandbox
     FAIL: testsuite/temp-file-cleanup
     FAIL: testsuite/follow-symlinks

----

* OpenSolaris 5.10:
(both in my testing and in Bruno's):
I suspect something is wrong with the $PATH. I don't see it
in Bruno's log ( https://lists.gnu.org/archive/html/sed-devel/2020-01/msg00003.html ), but in my log I see the following:

  FAIL: testsuite/misc
  ====================

PATH = /usr/gnu/bin:/usr/xpg6/bin:/usr/xpg4/bin/:/opt/csw/bin:usr /sfw/bin:/usr/bin:/bin
  sed: illegal option -- version
  Usage:  sed [-n] script [file...]
          sed [-n] [-e script]...[-f script_file]...[file...]

-----

* Alpine Linux:
In my testing on local Alpine 3.10.3 with Perl installed - everything
worked. In Bruno's testing (https://lists.gnu.org/archive/html/sed-devel/2020-01/msg00011.html )
the failure is  likely due to missing (or undetectable?) Perl,
as he noted. Bruno's log shows:

   FAIL: testsuite/misc
   ====================

   ../build-aux/test-driver: line 107: -w: not found
   FAIL testsuite/misc.pl (exit status: 127)

(I guess "-w" is left over from an empty "$PERL -w" shell variable).

---

* IRIX 6.5:
Bruno's IRIX testing ( https://lists.gnu.org/archive/html/sed-devel/2020-01/msg00004.html ) shows the following error:

   FAIL: testsuite/misc
   ====================

Can't locate warnings.pm in @INC (@INC contains: ../testsuite /usr/share/lib/perl5/irix-n32/5.00404 /usr/share/lib/perl5 /usr/share/lib/perl5/site_perl/irix-n32 /usr/share/lib/perl5/site_perl /usr/share/lib/perl5/sgi_perl .) at ../testsuite/CuSkip.pm line 20.
   BEGIN failed--compilation aborted at ../testsuite/CuSkip.pm line 20.
   BEGIN failed--compilation aborted.
   FAIL testsuite/misc.pl (exit status: 2)

So either a bad PERL installation is something else is amiss,
but not directly related to sed.

---

* Cygwin and Haiku "FAIL: panic-tests"
( Cygwin log attached, Bruno's Haiku is here https://lists.gnu.org/archive/html/sed-devel/2020-01/msg00010.html )

In both cases this is likely due to the underlying filesystem (e.g. NTFS) not behaving the POSIX way, so trying to mark a directory read-only to trigger a "panic" (failure to create temp file) doesn't work.

---

* NetBSD 8.1 - multiple failures (log attached).

This is the same NetBSD 8.1 which showed weird errors in the recent GREP
testing. I suspect it is a bad installation. Will investigate further.

---

regards,
 - assaf


Attachment: Oracle_SunOS_5.10_i86pc--tests-suite-summary.log.gz
Description: application/gzip

Attachment: CYGWIN_NT-10.0_2.11.10.329_5_3_x86_64--tests-suite-summary.log.gz
Description: application/gzip

Attachment: NetBSD_8.1_amd64--tests-suite-summary.log.gz
Description: application/gzip


reply via email to

[Prev in Thread] Current Thread [Next in Thread]