AlarmdIT.testPersistManyAlarmsAtOnce() test ordering issue?

Description

This test had an intermittent failure in one of my branches. It looks like an alarm has been left in the database between executions or possibly an ActiveMQ message has been replayed from disk just before the test executed.

Bamboo log:

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Jesse White March 21, 2016 at 8:48 AM

To my knowledge, this hasn't reoccurred since I applied the patch.

Jesse White March 10, 2016 at 11:48 PM

I'm unable to reproduce this locally, but I've attempted to fix it with ddd28650977d0778ca4c4646de9a8c02fdd91523.

If this does reoccur, we will have more details as to which alarms are present in the table.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created March 8, 2016 at 10:02 PM
Updated March 21, 2016 at 8:48 AM
Resolved March 21, 2016 at 8:48 AM