mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jan Schlicht (JIRA)" <>
Subject [jira] [Commented] (MESOS-3082) Perf related tests rely on 'cycles' which might not always be present.
Date Fri, 08 Jan 2016 16:20:40 GMT


Jan Schlicht commented on MESOS-3082:

Tests trying to sample using perf with the 'cycles' value can cause failures of other tests
if run on a virtual machine that does not support _CPU performance counters_. E.g. running
{{sudo ./bin/ --gtest_filter="*ROOT_CGROUPS_Sample"}} will fail and sometimes
keep a child process running. This process will block some cgroups from being removed. This
affects all test processes that are run afterwards that try to clean up some cgroups before
being run (mostly {{ROOT_CGROUPS_*}}).

I'd suggest to disable these test if in a virtual machine without _CPU performance counters_.

> Perf related tests rely on 'cycles' which might not always be present.
> ----------------------------------------------------------------------
>                 Key: MESOS-3082
>                 URL:
>             Project: Mesos
>          Issue Type: Bug
>         Environment: Ubuntu 14.04 (in a virtual machine)
>            Reporter: Benjamin Hindman
>              Labels: mesosphere
> When running the tests on Ubuntu 14.04 the 'cycles' value collected by perf is always
0, meaning certain tests always fail. These lines in the test have been commented out for
now and a TODO has been attached which links to this JIRA issue, since the solution is unclear.
In particular, 'cycles' might not properly be counted because it is a hardware counter and
this particular machine was a virtual machine. Either way, we should determine the best events
to collect from perf in either VM or physical settings.

This message was sent by Atlassian JIRA

View raw message