Perf is specific to the kernel version and different versions have different flags and output formats. Specifically, the code requires a kernel release >= 2.6.39 but you're running a 2.6.32 kernel: your version of perf is not currently supported and you should skip those tests. The only effect of this is that you cannot use the optional perf_event isolator.
On Mon, Jun 1, 2015 at 5:03 PM, Qian Zhang <[email protected]> wrote: > Thanks Haosdent and Ian. > > But in my machine, I already have perf installed, so I am not sure why > those test cases still failed. > # rpm -qa | grep perf > perf-2.6.32-431.el6.x86_64 > # which perf > /usr/bin/perf > > And can you please let me know why my example C++ framework works as > normal? I see the following message: > Task 0 is in state TASK_LOST > Aborting because task 0 is in unexpected state TASK_LOST with reason 1 > from source 1 with message 'Executor terminated' > It seems task is in an unexpected state, right? And after > "./src/test-framework --master=127.0.0.1:5050" is executed, I ran "echo > $?", and its output is 1 which means something wrong, otherwise "echo $?" > should output 0, right? > > >
