Skip Menu |
 

This queue is for tickets about the IPC-Shareable CPAN distribution.

Report information
The Basics
Id: 91841
Status: open
Priority: 0/
Queue: IPC-Shareable

People
Owner: Nobody in particular
Requestors: chriscooper1991 [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Sudden test fail in t/38ipchv.t from "Could not create shared memory segment: Invalid argument"
Date: Fri, 3 Jan 2014 15:30:09 -0500
To: bug-IPC-Shareable [...] rt.cpan.org
From: Chris Cooper <chriscooper1991 [...] gmail.com>
Download (untitled) / with headers
text/plain 716b
I've been building perl nightly and then installing this module for many weeks just fine. Suddenly, here is the consistent output, resulting in everything hanging: t/00base.t .... ok t/05sv.t ...... ok t/10av.t ...... ok t/15hv.t ...... ok t/20ref.t ..... ok t/25ipc.t ..... ok t/30lock.t .... ok t/35clean.t ... ok t/36ipcav.t ... ok t/38ipchv.t ... IPC::Shareable::SharedMem: shmget: Invalid argument at /tmp/NightlyBuildTmp/perllib/IPC-Shareable-0.61-GVjGhT/blib/lib/IPC/Shareable.pm line 567. Could not create shared memory segment: Invalid argument at t/38ipchv.t line 64. This is on: Debian GNU/Linux 6.0.6 (squeeze) Linux 2.6.32-bpo.5-amd64 x86_64 Any idea on why this might be happening? Thanks, Chris
Download (untitled) / with headers
text/html 1010b
Subject: Re: [rt.cpan.org #91841] Sudden test fail in t/38ipchv.t from "Could not create shared memory segment: Invalid argument"
Date: Fri, 3 Jan 2014 15:36:33 -0600
To: bug-IPC-Shareable [...] rt.cpan.org
From: Mike South <msouth [...] gmail.com>
Download (untitled) / with headers
text/plain 2.7k
No, I have no idea. I only took over maintainership to add in already-suggested patches that were being ignored, but which fixed bugs for certain cases. Did a dependent module change? Are you able to try installing IPC::Shareable in, say, a fresh perlbrew environment, and then look at the dependency chain that gets installed and see what changed recently? Another thing I know can cause problems is if you store something with one version of perl (and IPC::Shareable) and retrieve with another. For example, on one system with perl 5.8.8 with Shareable $VERSION = 0.51; and a perlbrewed 5.14.2 with Shareable 0.61: [user_one@somehost ~]$ perl -v |grep ', v' This is perl, v5.8.8 built for x86_64-linux [user_one@somehost ~]$ perl -MIPC::Shareable -MData::Dumper -e 'my %H ; tie(%H, "IPC::Shareable", "www", {create => 1, mode => 0666,}); print Dumper(\%H),$/' $VAR1 = { 'slow_select' => 155 }; [user_two@somehost ~]$ perl -v |grep ', v' This is perl 5, version 14, subversion 2 (v5.14.2) built for x86_64-linux [user_two@somehost ~]$ perl -MIPC::Shareable -MData::Dumper -e 'my %H ; tie(%H, "IPC::Shareable", "www", {create => 1, mode => 0666,}); print Dumper(\%H),$/' Could not create semaphore set: Invalid argument at -e line 1. It's probably highly unlikely that that's even related to what you're seeing, but I saw that 'invalid argument' text in yours and I thought it looked familiar so I dug out my docs on it. mike On Fri, Jan 3, 2014 at 2:31 PM, chriscooper1991@gmail.com via RT < bug-IPC-Shareable@rt.cpan.org> wrote: Show quoted text
> Fri Jan 03 15:31:11 2014: Request 91841 was acted upon. > Transaction: Ticket created by chriscooper1991@gmail.com > Queue: IPC-Shareable > Subject: Sudden test fail in t/38ipchv.t from "Could not create > shared memory segment: Invalid argument" > Broken in: (no value) > Severity: (no value) > Owner: Nobody > Requestors: chriscooper1991@gmail.com > Status: new > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=91841 > > > > I've been building perl nightly and then installing this module for many > weeks just fine. Suddenly, here is the consistent output, resulting in > everything hanging: > > t/00base.t .... ok > t/05sv.t ...... ok > t/10av.t ...... ok > t/15hv.t ...... ok > t/20ref.t ..... ok > t/25ipc.t ..... ok > t/30lock.t .... ok > t/35clean.t ... ok > t/36ipcav.t ... ok > t/38ipchv.t ... IPC::Shareable::SharedMem: shmget: Invalid argument > at > > /tmp/NightlyBuildTmp/perllib/IPC-Shareable-0.61-GVjGhT/blib/lib/IPC/Shareable.pm > line 567. > Could not create shared memory segment: Invalid argument > at t/38ipchv.t line 64. > > This is on: > Debian GNU/Linux 6.0.6 (squeeze) > Linux 2.6.32-bpo.5-amd64 x86_64 > > Any idea on why this might be happening? > > Thanks, > Chris > >
Subject: Re: [rt.cpan.org #91841] Sudden test fail in t/38ipchv.t from "Could not create shared memory segment: Invalid argument"
Date: Fri, 3 Jan 2014 18:55:35 -0500
To: bug-IPC-Shareable [...] rt.cpan.org
From: Chris Cooper <chriscooper1991 [...] gmail.com>
Download (untitled) / with headers
text/plain 3.4k
Thanks for the quick response, Mike! $ perl -v |grep ', v' This is perl 5, version 18, subversion 1 (v5.18.1) built for x86_64-linux That isn't the evidence, but I'm quite confident that it's running under the same perl that was used to build it. You're probably right with the first suggestion that it has to do with a dependant module changing. I guess I'll dig a little deeper then... Thanks, Chris On Fri, Jan 3, 2014 at 4:36 PM, Mike South via RT < bug-IPC-Shareable@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=91841 > > > No, I have no idea. I only took over maintainership to add in > already-suggested patches that were being ignored, but which fixed bugs for > certain cases. > > Did a dependent module change? Are you able to try installing > IPC::Shareable in, say, a fresh perlbrew environment, and then look at the > dependency chain that gets installed and see what changed recently? > > Another thing I know can cause problems is if you store something with one > version of perl (and IPC::Shareable) and retrieve with another. For > example, on one system with perl 5.8.8 with Shareable $VERSION = 0.51; and > a perlbrewed 5.14.2 with Shareable 0.61: > > [user_one@somehost ~]$ perl -v |grep ', v' > This is perl, v5.8.8 built for x86_64-linux > [user_one@somehost ~]$ perl -MIPC::Shareable -MData::Dumper -e 'my %H ; > tie(%H, "IPC::Shareable", "www", {create => 1, mode => 0666,}); print > Dumper(\%H),$/' > $VAR1 = { > 'slow_select' => 155 > }; > > [user_two@somehost ~]$ perl -v |grep ', v' > This is perl 5, version 14, subversion 2 (v5.14.2) built for x86_64-linux > [user_two@somehost ~]$ perl -MIPC::Shareable -MData::Dumper -e 'my %H ; > tie(%H, "IPC::Shareable", "www", {create => 1, mode => 0666,}); print > Dumper(\%H),$/' > Could not create semaphore set: Invalid argument > at -e line 1. > > It's probably highly unlikely that that's even related to what you're > seeing, but I saw that 'invalid argument' text in yours and I thought it > looked familiar so I dug out my docs on it. > > mike > > > On Fri, Jan 3, 2014 at 2:31 PM, chriscooper1991@gmail.com via RT < > bug-IPC-Shareable@rt.cpan.org> wrote: >
> > Fri Jan 03 15:31:11 2014: Request 91841 was acted upon. > > Transaction: Ticket created by chriscooper1991@gmail.com > > Queue: IPC-Shareable > > Subject: Sudden test fail in t/38ipchv.t from "Could not create > > shared memory segment: Invalid argument" > > Broken in: (no value) > > Severity: (no value) > > Owner: Nobody > > Requestors: chriscooper1991@gmail.com > > Status: new > > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=91841 > > > > > > > I've been building perl nightly and then installing this module for many > > weeks just fine. Suddenly, here is the consistent output, resulting in > > everything hanging: > > > > t/00base.t .... ok > > t/05sv.t ...... ok > > t/10av.t ...... ok > > t/15hv.t ...... ok > > t/20ref.t ..... ok > > t/25ipc.t ..... ok > > t/30lock.t .... ok > > t/35clean.t ... ok > > t/36ipcav.t ... ok > > t/38ipchv.t ... IPC::Shareable::SharedMem: shmget: Invalid argument > > at > > > >
> /tmp/NightlyBuildTmp/perllib/IPC-Shareable-0.61-GVjGhT/blib/lib/IPC/Shareable.pm
> > line 567. > > Could not create shared memory segment: Invalid argument > > at t/38ipchv.t line 64. > > > > This is on: > > Debian GNU/Linux 6.0.6 (squeeze) > > Linux 2.6.32-bpo.5-amd64 x86_64 > > > > Any idea on why this might be happening? > > > > Thanks, > > Chris > > > >
> >


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.