Skip to content

Conversation

@robF8
Copy link
Contributor

@robF8 robF8 commented Apr 1, 2020

  • Sleeping device when waiting for workload to end was causing workload
    to occasionally freeze. Changed device sleep to host sleep.
  • Panda dataframe.ix() is deprecated so changed to .loc()

* Sleeping device when waiting for workload to end was causing workload
  to freeze. Changed device sleep to host sleep.

* Panda dataframe.ix() is deprecated so changed to .loc()
@setrofim
Copy link
Contributor

setrofim commented Apr 2, 2020

The sleep on target is quite deliberate -- this allows the workload to be used with simulations, where on-target time might proceed at very different rate from wall-clock time. Could you provided a bit more detail regarding the freezes you're encountering when waiting on target? E.g. is it target specific? does the workload actually freeze, or is it running but the sleep not returning? or does the entire target crash for some reason? etc.

@robF8
Copy link
Contributor Author

robF8 commented Apr 28, 2020

It happens on quite a few of the devices, reproducible 100% on a mate20 and pixel 4. I thought it was the sleep not returning properly but now not so sure. The workload just seems to hang after stop_event.set() and self.join() is called in JankbenchRunMonitor::stop() and the logcat stream process isn't being terminated.

@marcbonnici
Copy link
Contributor

A few things to check:

  • Is there anything abnormal in the logcat for the device that may indicate the problem?
  • Is this a locally connected device?
  • Are you able to set a breakpoint to determine where the code is getting stuck?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants