[ 
https://issues.apache.org/jira/browse/PROTON-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313151#comment-17313151
 ] 

michael goulish commented on PROTON-2362:
-----------------------------------------

I am running batches of 50 threaderciser tests, 64 threads each, turning off 
one feature at a time, and counting failures.

See if you can spot the case, below, that I feel may be interesting.

 

All Features On       crash: 10

-no-close-connect    crash: 12

-no-listen               crash: 0    hang: 2

-no-close-listen      (y)   :)    (*)(*r)(*g) {color:#de350b}*NO PROBLEMS 
(*g)(*r)(*)    :)   (y)*      {color}

{color:#de350b}{color:#172b4d}                                ~{color:#c1c7d0} 
(sorry, I can't figure out how to make the above text 
blink){color}~{color}{color} 

 

 

 

p.s.

    _"Brontosaurus"_ means _"Thunder Lizard"_, a kind of dinosaur.  

      I do not have a dinosaur.

      _"Brontonomicon",_ on the other hand, means _"What the Thunder Said"_    
or   _"Words of the Thunder"_   or possibly   _"The Book of Thunder"_.

      That's what I've got. 

      And when the thunder speaks, the software had better listen.

 

 

> c-threaderciser timed out on 32-core machine.
> ---------------------------------------------
>
>                 Key: PROTON-2362
>                 URL: https://issues.apache.org/jira/browse/PROTON-2362
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>            Reporter: michael goulish
>            Priority: Major
>
> Using recent master – maybe 3 days old or so – I just ran Proton's ctest, 
> after turning on THREADERCISER.  I ran it on a box with 32 physical cores, 64 
> threads.
>  
> Test number 6 – c-threaderciser – failed with timeout after 1500 seconds.
> ( 1.5e18 femtoseconds. )
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to