discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] Release candidate 3.0.3rc1 available for testing


From: Berndt Josef Wulf
Subject: Re: [Discuss-gnuradio] Release candidate 3.0.3rc1 available for testing
Date: Thu, 22 Feb 2007 21:58:10 +1030
User-agent: KMail/1.9.5

On Thursday 22 February 2007 15:18, Eric Blossom wrote:
> On Thu, Feb 22, 2007 at 02:43:09PM +1030, Berndt Josef Wulf wrote:
> > G'day,
> >
> > RC1 built fine, but I'm seeing a number of these errors during "gmake
> > check".
> >
> >
> > ======================================================================
> > ERROR: test_fff_002 (__main__.test_fft_filter)
> > ----------------------------------------------------------------------
> > Traceback (most recent call last):
> >   File "./qa_fft_filter.py", line 191, in test_fff_002
> >     self.fg.run()
> >
> > File
> > "/usr/src/gnuradio/gnuradio-3.0.3rc1/gnuradio-core/src/python/gnuradio/gr
> >/flow_graph.py", line 112, in run
> >     self.start ()
> >
> > File
> > "/usr/src/gnuradio/gnuradio-3.0.3rc1/gnuradio-core/src/python/gnuradio/gr
> >/flow_graph.py", line 93, in start
> >     self.scheduler.start ()
> >
> > File
> > "/usr/src/gnuradio/gnuradio-3.0.3rc1/gnuradio-core/src/python/gnuradio/gr
> >/scheduler.py", line 57, in start
> >     thread.start()
> >
> > File
> > "/usr/src/gnuradio/gnuradio-3.0.3rc1/gnuradio-core/src/python/gnuradio/gr
> >/gr_threading_24.py", line 420, in start
> >     _start_new_thread(self.__bootstrap, ())
> > error: can't start new thread
>
> Not sure about those...
> Sounds like you are running out of some system resource.
>
> > another issue already highlighted by Greg Toxel is
> >
> > Testing gr_vmcircbuf_sysv_shm_factory...
> > gr_vmcircbuf_sysv_shm: shmat (1): Too many open files
> > gr_vmcircbuf_sysv_shm: shmget (1): Invalid argument
> > ....... gr_vmcircbuf_sysv_shm_factory: Doesn't work
> > Testing gr_vmcircbuf_mmap_shm_open_factory...
>
> Those aren't (hard) failures.  They just indicate that under stress
> testing your shm* stuff won't work.  Greg posted a note to the list a
> while ago about how to bum p up the default number of shm segments
> available.  When shm* doesn't work, we use other techniques such as
> shm_open or mmap'ing a tmp file.
>
> > Will install and test RC1 later tonight.
>
> Thanks,
> Eric

Greg's suggestion of bumping the values for shmmni and shmseg helped to solve 
the shmat(1) related matter. shmget(1) still fails with "invalid argument" 
when the second parameter of shmget evaluates to 8396800 - e.g.

shmget(IPC_PRIVATE=0, size=8396800, pagesize=4096)

No luck with thread related errors. It may be due to recent changes we had in 
the NetBSD source tree.

Running the usual suspects from gnuradio-examples appear to be fine.

cheerio Berndt




reply via email to

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