coreutils
[Top][All Lists]
Advanced

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

Re: AIX: "make check" results


From: Michael
Subject: Re: AIX: "make check" results
Date: Tue, 2 Jan 2018 17:12:57 +0100
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:56.0) Gecko/20100101 Thunderbird/56.0

On 02/01/2018 13:26, Michael wrote:
On 02/01/2018 11:40, Michael wrote:
On 01/01/2018 18:50, Michael wrote:
On 01/01/2018 14:58, Pádraig Brady wrote:
On 29/12/17 15:46, Michael wrote:
On 27/12/2017 19:47, Pádraig Brady wrote:
This is to announce coreutils-8.29, a stable release.
See the NEWS below for more details.
Just want to add - that building and packaging - no issues (one warning
message only).


Just finished a build a test on local filesystem on AIX 6.1, with XLC - test results are the same (normal make check, i.e., not 'expensive')

On AIX 6.1, using gcc 4.7.4, and running the tests as root - get some differences:

============================================================================
Testsuite summary for GNU coreutils 8.29
============================================================================
# TOTAL: 603
# PASS:  399
# SKIP:  198
# XFAIL: 0
# FAIL:  6
# XPASS: 0
# ERROR: 0
============================================================================
See ./tests/test-suite.log
Please report to address@hidden
============================================================================
make: 1254-004 The error code from the last command is 1.

...

FAIL: tests/misc/help-version
=============================

env: '[': No such file or directory
env: '[': No such file or directory
env: '[': No such file or directory
FAIL: [
0+1 records in
0+1 records out

#### Conclusion: after building with gnu make installed, and not installed - on systems that had '[' at the end - I must now state - "Eating my previous words" - that GNU make is required to get '[' generated. So, please disregard my previous comment about not needing it - (chomp chomp) - obviously, I had gnu make installed earlier.

#### swallow, and continue...

** FAIL: tests/misc/date-debug

This might be a difference in the way the TZ environment variable is defined.

FAIL: tests/misc/date-debug
===========================

--- exp8_1      2018-01-02 12:23:46.000000000 +0000
+++ out8_1      2018-01-02 12:23:46.000000000 +0000
@@ -1,11 +1,11 @@
  date: parsed date part: (Y-M-D) 2011-12-11
- date: parsed local_zone part: isdst=0
- date: input timezone: TZ="Europe/Helsinki" environment value
+ date: parsed zone part: UTC+02
+ date: input timezone: parsed date/time string (+02)
  date: warning: using midnight as starting time: 00:00:00
- date: starting date/time: '(Y-M-D) 2011-12-11 00:00:00'
- date: '(Y-M-D) 2011-12-11 00:00:00' = 1323554400 epoch-seconds
+ date: starting date/time: '(Y-M-D) 2011-12-11 00:00:00 TZ=+02'
+ date: '(Y-M-D) 2011-12-11 00:00:00 TZ=+02' = 1323554400 epoch-seconds
  date: timezone: TZ="Europe/Helsinki" environment value
  date: final: 1323554400.000000000 (epoch-seconds)
  date: final: (Y-M-D) 2011-12-10 22:00:00 (UTC)
  date: final: (Y-M-D) 2011-12-11 00:00:00 (UTC+02)
- Sun Dec 11 00:00:00 EET 2011
+ Sun Dec 11 00:00:00 GMT+02:00 2011
--- exp8_2      2018-01-02 12:23:46.000000000 +0000
+++ out8_2      2018-01-02 12:23:46.000000000 +0000
@@ -1,11 +1,11 @@
  date: parsed date part: (Y-M-D) 2011-06-11
- date: parsed local_zone part: isdst=1
- date: input timezone: TZ="Europe/Helsinki" environment value, dst
+ date: parsed zone part: UTC+03
+ date: input timezone: parsed date/time string (+03)
  date: warning: using midnight as starting time: 00:00:00
- date: starting date/time: '(Y-M-D) 2011-06-11 00:00:00'
- date: '(Y-M-D) 2011-06-11 00:00:00' = 1307739600 epoch-seconds
+ date: starting date/time: '(Y-M-D) 2011-06-11 00:00:00 TZ=+03'
+ date: '(Y-M-D) 2011-06-11 00:00:00 TZ=+03' = 1307739600 epoch-seconds
  date: timezone: TZ="Europe/Helsinki" environment value
  date: final: 1307739600.000000000 (epoch-seconds)
  date: final: (Y-M-D) 2011-06-10 21:00:00 (UTC)
  date: final: (Y-M-D) 2011-06-11 00:00:00 (UTC+03)
- Sat Jun 11 00:00:00 EEST 2011
+ Sat Jun 11 00:00:00 GMT+03:00 2011
FAIL tests/misc/date-debug.sh (exit status: 1)

On AIX 5.3 and AIX 6.1 (with xlc):

address@hidden:[/home/prj/gnu/coreutils-8.29]grep TZ /etc/environment
TZ=UTC0
address@hidden:[/home/prj/gnu/coreutils-8.29]grep TZ /etc/environment
TZ=UTC0

No, those seem to be identical. So, it seems the test runs differently (as root?)

* FAIL: tests/misc/stdbuf
=======================

stdbuf: invalid mode 'l'
stdbuf: invalid mode '18446744073709551616': Value too large to be stored in data type
stdbuf: line buffering stdin is meaningless
Try 'stdbuf --help' for more information.
stdbuf: you must specify a buffering mode option
Try 'stdbuf --help' for more information.
stdbuf: failed to run command '.': Permission denied
stdbuf: failed to run command 'no_such': No such file or directory
...

--- exp 2018-01-02 12:25:38.000000000 +0000
+++ out 2018-01-02 12:25:40.000000000 +0000
@@ -1 +1,2 @@
  1
+ 2
--- exp 2018-01-02 12:25:40.000000000 +0000
+++ out 2018-01-02 12:25:43.000000000 +0000
@@ -1 +1,2 @@
  1
+ 2
FAIL tests/misc/stdbuf.sh (exit status: 1)

* FAIL: tests/cp/preserve-mode
============================

FAIL tests/cp/preserve-mode.sh (exit status: 1)

* FAIL: tests/cp/special-bits
===========================

chroot --skip-chdir --user=$NON_ROOT_USERNAME / env PATH="$PATH" cp -p c c2 \
FAIL tests/cp/special-bits.sh (exit status: 1)

* FAIL: tests/misc/chroot-credentials
===================================

chroot --userspec=$NON_ROOT_UID: / true || fail=1
  chroot --userspec=$NON_ROOT_USERNAME:$NON_ROOT_GROUP / whoami
  chroot --userspec=$NON_ROOT_USERNAME:$NON_ROOT_GROUP \
chroot: no group specified for unknown uid: -2: No such process
chroot: invalid group ' ': No such process
chroot: invalid group list ','
chroot: invalid group '0trail': No such process
chroot: no group specified for unknown uid: -2: No such process
id: '+12342': no such user
chroot: no group specified for unknown uid: 12342: No such process
FAIL tests/misc/chroot-credentials.sh (exit status: 1)





thanks,
Pádraig















reply via email to

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