From @schwern

Created by @schwern

$ ./perl harness lib/ipc_sysv.t lib/ipc_sysv........ok 16/16FAILED tests 2, 5-6
  Failed 3/16 tests, 81.25% okay
Failed Test Status Wstat Total Fail Failed List of failed
-------------------------------------------------------------------------------
lib/ipc_sysv.t 16 3 18.75% 2, 5-6

I figured I'd try out 64 bit support under Linux for kicks. This was
the only failure.

Site configuration information for perl v5.5.670:

Configured by schwern at Thu Mar  2 16:15:55 EST 2000.

Summary of my perl5 (revision 5.0 version 5 subversion 670) configuration:
  Platform:
    osname=linux, osvers=2.2.10, archname=i686-linux-64all
    uname='linux athens 2.2.10 #3 smp mon aug 2 16:48:09 edt 1999 i686 unknown '
    config_args=''
    hint=recommended, useposix=true, d_sigaction=define
    usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
    useperlio=undef d_sfio=undef uselargefiles=define 
    use64bitint=define use64bitall=define uselongdouble=define usesocks=undef
  Compiler:
    cc='cc', optimize='-g', gccversion=2.95.2 20000116 (Debian GNU/Linux)
    cppflags='-Dbool=char -DHAS_BOOL -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -DDEBUGGING_OPS -DDEBUGGING_MSTATS'
    ccflags ='-Dbool=char -DHAS_BOOL -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -DDEBUGGING_OPS -DDEBUGGING_MSTATS'
    stdchar='char', d_stdstdio=define, usevfork=false
    intsize=4, longsize=4, ptrsize=4, doublesize=8
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
    ivtype='long long', ivsize=8, nvtype='long double', nvsize=12, Off_t='off_t', lseeksize=4
    alignbytes=4, usemymalloc=y, prototype=define
  Linker and Libraries:
    ld='cc', ldflags =' -L/usr/local/lib'
    libpth=/usr/local/lib /lib /usr/lib
    libs=-lnsl -lndbm -lgdbm -ldbm -ldb -ldl -lm -lc -lposix -lcrypt
    libc=/lib/libc-2.1.3.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
    cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'

Locally applied patches:
    


@INC for perl v5.5.670:
    lib
    /home/schwern/lib/perl5/site_perl/5.005
    /usr/local/perl5.6/lib/i686-linux-64all
    /usr/local/perl5.6/lib
    /usr/local/perl5.6/lib
    .


Environment for perl v5.5.670:
    HOME=/home/schwern
    LANG=C
    LANGUAGE (unset)
    LD_LIBRARY_PATH (unset)
    LOGDIR (unset)
    PATH=/home/schwern/bin:/usr/local/sbin:/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:.
    PERL5LIB=/home/schwern/lib/perl5/site_perl/5.005
    PERL_BADLANG (unset)
    SHELL=/bin/bash

From @jhi

Michael G Schwern writes​:

This is a bug report for perl from schwern@​pobox.com,
generated with the help of perlbug 1.27 running under perl v5.5.670.

-----------------------------------------------------------------
[Please enter your report here]

$ ./perl harness lib/ipc_sysv.t lib/ipc_sysv........ok 16/16FAILED tests 2, 5-6
Failed 3/16 tests, 81.25% okay
Failed Test Status Wstat Total Fail Failed List of failed
-------------------------------------------------------------------------------
lib/ipc_sysv.t 16 3 18.75% 2, 5-6

I figured I'd try out 64 bit support under Linux for kicks. This was
the only failure.

Could you run

  ./perl t/lib/ipc_sysv.t

and tell me what that outputs? The tests 2, 5, 6, and are connected.

--
$jhi++; # http​://www.iki.fi/jhi/
  # There is this special biologist word we use for 'stable'.
  # It is 'dead'. -- Jack Cohen

From @schwern

On Fri, Mar 03, 2000 at 10​:21​:58PM +0200, Jarkko Hietaniemi wrote​:

Could you run

\./perl t/lib/ipc\_sysv\.t

and tell me what that outputs? The tests 2, 5, 6, and are connected.

Ooops, forgot to include that. Yes, I'm getting the "we're all
connected" warnings.

$ ./perl t/lib/ipc_sysv.t
1..16
ok 1
not ok 2
#
# The failure of the subtest #2 may indicate that the message queue
# resource limits either of the system or of the testing account
# have been reached. Error message "Operating would block" is
# usually indicative of this situation. The error message was now​:
# "Invalid argument"
#
# You can check the message queues with the 'ipcs' command and
# you can remove unneeded queues with the 'ipcrm -q id' command.
# You may also consider configuring your system or account
# to have more message queue resources.
#
# Because of the subtest #2 failing also the substests #5 and #6 will
# very probably also fail.
#
ok 3
ok 4
not ok 5
#
# This failure was to be expected because the subtest #2 failed.
#
not ok 6
#
# This failure was to be expected because the subtest #2 failed.
#
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15
ok 16

--

Michael G Schwern http​://www.pobox.com/~schwern/ schwern@​pobox.com
You will feel tremendous pain at the area where foreign materials are
inserted. I usually don't recommend anyone to insert artificial materials.
Keep everything natural is best!
  --Alex Chiu, Immortality Guy

From @schwern

5.8.1 RC2 builds fine on Debian ia64

@schwern - Status changed from 'open' to 'resolved'