Closed Bug 772967 Opened 9 years ago Closed 9 years ago

panda board throws an exception from sutagent in sendPing

Categories

(Testing Graveyard :: SUTAgent, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jmaher, Unassigned)

References

Details

(Whiteboard: u=panda c=ateam p=2)

This is what I see in adb logcat on my panda board:

I/System  ( 1904): libcore.io.ErrnoException: kill failed: ESRCH (No such process)
I/System  ( 1904): 	at libcore.io.Posix.kill(Native Method)
I/System  ( 1904): 	at libcore.io.ForwardingOs.kill(ForwardingOs.java:77)
I/System  ( 1904): 	at java.lang.ProcessManager$ProcessImpl.destroy(ProcessManager.java:257)
I/System  ( 1904): 	at com.mozilla.SUTAgentAndroid.service.RunCmdThread.SendPing(RunCmdThread.java:192)
I/System  ( 1904): 	at com.mozilla.SUTAgentAndroid.service.RunCmdThread.run(RunCmdThread.java:67)


We should at least reduce this so we don't have noise in the logs.
I saw this on my device as well but I didn't know what it was so I didn't bother with it.
Using bug 769428 instead to track improvements to the image.

Sorry for the noise!
Blocks: 769428
No longer blocks: android_4.0_testing
Component: General → SUTAgent
Whiteboard: u=panda c=ateam p=2
update after watcher fixes have landed:
08-08 14:30:03.148 I/Watcher ( 1805): Pinging www.mozilla.org
08-08 14:30:07.234 I/System  ( 1805): Failed to destroy process 2628
08-08 14:30:07.234 I/System  ( 1805): libcore.io.ErrnoException: kill failed: ESRCH (No such process)
08-08 14:30:07.234 I/System  ( 1805): 	at libcore.io.Posix.kill(Native Method)
08-08 14:30:07.234 I/System  ( 1805): 	at libcore.io.ForwardingOs.kill(ForwardingOs.java:77)
08-08 14:30:07.234 I/System  ( 1805): 	at java.lang.ProcessManager$ProcessImpl.destroy(ProcessManager.java:257)
08-08 14:30:07.234 I/System  ( 1805): 	at com.mozilla.watcher.WatcherService.SendPing(WatcherService.java:831)
08-08 14:30:07.234 I/System  ( 1805): 	at com.mozilla.watcher.WatcherService.access$800(WatcherService.java:46)
08-08 14:30:07.234 I/System  ( 1805): 	at com.mozilla.watcher.WatcherService$MyTime.run(WatcherService.java:907)
08-08 14:30:07.234 I/System  ( 1805): 	at java.util.Timer$TimerImpl.run(Timer.java:284)
08-08 14:30:07.234 I/Watcher ( 1805): Ping result was: 'PING bedrock-prod-zlb.vips.scl3.mozilla.com (63.245.215.20) 56(84) bytes of data.
08-08 14:30:07.234 I/Watcher ( 1805): 64 bytes from bedrock-prod-zlb.vips.scl3.mozilla.com (63.245.215.20): icmp_seq=1 ttl=45 time=97.9 ms
08-08 14:30:07.234 I/Watcher ( 1805): 64 bytes from bedrock-prod-zlb.vips.scl3.mozilla.com (63.245.215.20): icmp_seq=2 ttl=45 time=96.7 ms
08-08 14:30:07.234 I/Watcher ( 1805): 64 bytes from bedrock-prod-zlb.vips.scl3.mozilla.com (63.245.215.20): icmp_seq=3 ttl=45 time=96.2 ms
08-08 14:30:07.234 I/Watcher ( 1805): 
08-08 14:30:07.234 I/Watcher ( 1805): --- bedrock-prod-zlb.vips.scl3.mozilla.com ping statistics ---
08-08 14:30:07.234 I/Watcher ( 1805): 3 packets transmitted, 3 received, 0% packet loss, time 2007ms
08-08 14:30:07.234 I/Watcher ( 1805): rtt min/avg/max/mdev = 96.221/96.964/97.901/0.786 ms'
So I'm not sure what's going on here if you are actually using the latest agent.

This is actually a problem in the watcher (the SUTagent should no longer ping, see bug 778159). 
By default now, the watcher shouldn't ping either (see bug 779871 and https://hg.mozilla.org/mozilla-central/file/65d35a2858f6/build/mobile/sutagent/android/watcher/WatcherService.java#l905). 

Are you sure you're using the absolute latest watcher?
Pretty sure I am because you can see the watcher is outputting information about what it is doing.  Let me ensure that I am and update the bug if necessary.
we don't ping by default anymore and have no plans to ping.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.