You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Alan M. Carroll" <am...@network-geographics.com> on 2010/05/20 03:33:17 UTC
2.1.0 Segfaulting in regression tests
I am trying to run regression tests (traffic_server -R 1) but it segfaults in Cache_part. According to TS-74
"for the 'Cache_part' regression test to pass a cache storage has to be allocated > 128MB."
I checked there is a cache.db file that is 144M. Does this really mean a cache storage partition? And by "pass" does it mean that absent that cache storage a segfault (as opposed to a FAIL) is to be expected?
Re: 2.1.0 Segfaulting in regression tests
Posted by "Alan M. Carroll" <am...@network-geographics.com>.
Sure. It will be a day or two, I want to get the capabilities put to
bed first.
Thursday, May 20, 2010, 11:23:00 AM, you wrote:
> Hi Alan,
> Can you file this as a Jira Ticket and provide as much as possible the
> necessary repro environment, code line, etc.
> thanks,
> -George
Re: 2.1.0 Segfaulting in regression tests
Posted by George Paul <ge...@apache.org>.
Hi Alan,
Can you file this as a Jira Ticket and provide as much as possible the
necessary repro environment, code line, etc.
thanks,
-George
On 5/19/10 8:14 PM, Alan M. Carroll wrote:
> Yes.
>
> Wednesday, May 19, 2010, 9:28:42 PM, you wrote:
>
>> On 05/19/2010 07:33 PM, Alan M. Carroll wrote:
>>> I am trying to run regression tests (traffic_server -R 1) but it segfaults in Cache_part. According to TS-74
>>>
>>> "for the 'Cache_part' regression test to pass a cache storage has to be allocated> 128MB."
>>>
>>> I checked there is a cache.db file that is 144M. Does this really mean a cache storage partition? And by "pass" does it mean that absent that cache storage a segfault (as opposed to a FAIL) is to be expected?
>>>
>
>> Does by chance your stack trace look anything like this?
>
>> 0 RegressionSM::run (this=0x7fffc8013850) at RegressionSM.cc:174
>> #1 0x00000000004f8de9 in RegressionSM::regression_sm_waiting
>> (this=0x7fffc8013850,
>> event=<value optimized out>, data=<value optimized out>) at
>> RegressionSM.cc:87
>> #2 0x00000000006c7824 in handleEvent (this=0x7ffff640e010,
>> e=0x7fff9c069370,
>> calling_code=2) at I_Continuation.h:147
>> #3 EThread::process_event (this=0x7ffff640e010, e=0x7fff9c069370,
>> calling_code=2)
>> at UnixEThread.cc:143
>> #4 0x00000000006c8333 in EThread::execute (this=0x7ffff640e010) at
>> UnixEThread.cc:220
>> #5 0x00000000006c63aa in spawn_thread_internal (a=0xbbbf00) at Thread.cc:85
>> #6 0x0000003cc2e06a3a in start_thread (arg=0x7ffff4df7710) at
>> pthread_create.c:297
>> #7 0x0000003cc22de62d in clone () at
>> ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
>> #8 0x0000000000000000 in ?? ()
>
>
>> -- leif
>
>
Re: 2.1.0 Segfaulting in regression tests
Posted by "Alan M. Carroll" <am...@network-geographics.com>.
Yes.
Wednesday, May 19, 2010, 9:28:42 PM, you wrote:
> On 05/19/2010 07:33 PM, Alan M. Carroll wrote:
>> I am trying to run regression tests (traffic_server -R 1) but it segfaults in Cache_part. According to TS-74
>>
>> "for the 'Cache_part' regression test to pass a cache storage has to be allocated> 128MB."
>>
>> I checked there is a cache.db file that is 144M. Does this really mean a cache storage partition? And by "pass" does it mean that absent that cache storage a segfault (as opposed to a FAIL) is to be expected?
>>
> Does by chance your stack trace look anything like this?
> 0 RegressionSM::run (this=0x7fffc8013850) at RegressionSM.cc:174
> #1 0x00000000004f8de9 in RegressionSM::regression_sm_waiting
> (this=0x7fffc8013850,
> event=<value optimized out>, data=<value optimized out>) at
> RegressionSM.cc:87
> #2 0x00000000006c7824 in handleEvent (this=0x7ffff640e010,
> e=0x7fff9c069370,
> calling_code=2) at I_Continuation.h:147
> #3 EThread::process_event (this=0x7ffff640e010, e=0x7fff9c069370,
> calling_code=2)
> at UnixEThread.cc:143
> #4 0x00000000006c8333 in EThread::execute (this=0x7ffff640e010) at
> UnixEThread.cc:220
> #5 0x00000000006c63aa in spawn_thread_internal (a=0xbbbf00) at Thread.cc:85
> #6 0x0000003cc2e06a3a in start_thread (arg=0x7ffff4df7710) at
> pthread_create.c:297
> #7 0x0000003cc22de62d in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
> #8 0x0000000000000000 in ?? ()
> -- leif
Re: 2.1.0 Segfaulting in regression tests
Posted by Leif Hedstrom <zw...@apache.org>.
On 05/19/2010 07:33 PM, Alan M. Carroll wrote:
> I am trying to run regression tests (traffic_server -R 1) but it segfaults in Cache_part. According to TS-74
>
> "for the 'Cache_part' regression test to pass a cache storage has to be allocated> 128MB."
>
> I checked there is a cache.db file that is 144M. Does this really mean a cache storage partition? And by "pass" does it mean that absent that cache storage a segfault (as opposed to a FAIL) is to be expected?
>
Does by chance your stack trace look anything like this?
0 RegressionSM::run (this=0x7fffc8013850) at RegressionSM.cc:174
#1 0x00000000004f8de9 in RegressionSM::regression_sm_waiting
(this=0x7fffc8013850,
event=<value optimized out>, data=<value optimized out>) at
RegressionSM.cc:87
#2 0x00000000006c7824 in handleEvent (this=0x7ffff640e010,
e=0x7fff9c069370,
calling_code=2) at I_Continuation.h:147
#3 EThread::process_event (this=0x7ffff640e010, e=0x7fff9c069370,
calling_code=2)
at UnixEThread.cc:143
#4 0x00000000006c8333 in EThread::execute (this=0x7ffff640e010) at
UnixEThread.cc:220
#5 0x00000000006c63aa in spawn_thread_internal (a=0xbbbf00) at Thread.cc:85
#6 0x0000003cc2e06a3a in start_thread (arg=0x7ffff4df7710) at
pthread_create.c:297
#7 0x0000003cc22de62d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#8 0x0000000000000000 in ?? ()
-- leif