|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Richard thanks for your very fast reply. I looked into the logcat of the Jenkins job. I compared one log of a failed build and one of a succeeded build. I saw no difference in the log. I uploaded the log for you. Maybe you see something critical. https://github.com/ITobiI/Android-Problem-Jenkins/blob/master/logcat
I looked into the /var/log/system.log too. I only noticed this:
vmhost-mac-mini.local launchctl[3904]: launchctl: Dubious ownership on file (skipping): /Library/LaunchAgents/org.jenkins-ci.plist
This is also shown at a successful build. So I think this is not the problem.
At the DiagnosticReports I don't see any log from adb or emultor64-arm. The activity log marks the emulator64-arm as not responding after a few seconds and the last system error counter increases with time. Nothing special at all messages of Console too.
I'm new at the Mac and Android world. So if you know an other log I can lock at, it would be nice you can name it.
I can't reproduce any steps to say, if I do this the build fails and if I do this the build succeeds. From my perspective, the problem is random.