I'm finding these are getting lost in the noise, it would be great when filing test issue tickets to 'git blame' the code and figure out who to notify to fix the test. Could you do that here?
On Fri, Mar 18, 2016 at 3:55 PM, Neil Conway (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/MESOS-4984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Neil Conway updated MESOS-4984: > ------------------------------- > Labels: flaky-test mesosphere tech-debt (was: flaky-test mesosphere) > > > MasterTest.SlavesEndpointTwoSlaves is flaky > > ------------------------------------------- > > > > Key: MESOS-4984 > > URL: https://issues.apache.org/jira/browse/MESOS-4984 > > Project: Mesos > > Issue Type: Bug > > Components: tests > > Reporter: Neil Conway > > Labels: flaky-test, mesosphere, tech-debt > > Attachments: slaves_endpoint_flaky_4984_verbose_log.txt > > > > > > Observed on Arch Linux with GCC 6, running in a virtualbox VM: > > [ RUN ] MasterTest.SlavesEndpointTwoSlaves > > /mesos-2/src/tests/master_tests.cpp:1710: Failure > > Value of: array.get().values.size() > > Actual: 1 > > Expected: 2u > > Which is: 2 > > [ FAILED ] MasterTest.SlavesEndpointTwoSlaves (86 ms) > > Seems to fail non-deterministically, perhaps more often when there is > concurrent CPU load on the machine. > > > > -- > This message was sent by Atlassian JIRA > (v6.3.4#6332) >
