Following up that we now have another sporadic eunit failure:

module 'couch_work_queue'
  module 'couch_work_queue_tests'
    Single producer and consumer
      Queue with 3 max items
        couch_work_queue_tests:143: should_have_no_items_for_new_queue...ok
        couch_work_queue_tests:213: 
should_block_producer_on_full_queue_count...ok
        couch_work_queue_tests:251: should_receive_first_queued_item...ok
        couch_work_queue_tests:238: should_consume_multiple_items...ok
        couch_work_queue_tests:261: should_consume_all...ok
        couch_work_queue_tests:155: 
should_block_consumer_on_dequeue_from_empty_queue...ok
        undefined
        *** instantiation of subtests failed ***
**in function couch_work_queue_tests:produce/4 
(test/couch_work_queue_tests.erl, line 363)
in call from couch_work_queue_tests:should_consume_right_item/1 
(test/couch_work_queue_tests.erl, line 182)
**error:{badmatch,timeout}

Never seen this one before.

----- Original Message -----
> From: "Joan Touzet" <[email protected]>
> To: [email protected]
> Sent: Wednesday, March 22, 2017 6:02:55 PM
> Subject: Re: Stabilizing our automated builds - help needed!
> 
> Thanks for the info Jay!
> 
> Erlangers, I still need your help addressing the remaining eunit
> failures.
> 
> -Joan
> 
> ----- Original Message -----
> > From: "Jay Doane" <[email protected]>
> > To: [email protected], "Joan Touzet" <[email protected]>
> > Sent: Monday, March 20, 2017 2:59:12 AM
> > Subject: Re: Stabilizing our automated builds - help needed!
> > 
> > On Sun, Mar 19, 2017 at 10:50 PM, Joan Touzet <[email protected]>
> > wrote:
> > 
> > >
> > > --------------------------
> > > module 'couch_log_writer_syslog_test'
> > >   couch_log_writer_syslog_test:
> > >   couch_log_writer_syslog_test_...*timed
> > > out*
> > >   undefined
> > >
> > > Not sure why this times out, can we increase the timeout maybe?
> > >
> > 
> > Another data point: I always get this same error on my mac laptop,
> > but have
> > so far been unable to identify the issue. Since nobody else (until
> > now) had
> > seen it, I assumed it was just a problem with my dev environment.
> > 
> > Jay
> > 
> 

Reply via email to