Closed Bug 916989 Opened 9 years ago Closed 8 years ago

Run eideticker on firefoxos builds at least nightly in an automated manner

Categories

(Testing Graveyard :: Eideticker, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: wlach, Assigned: wlach)

References

Details

(Keywords: perf, Whiteboard: [c=automation p= s=2014.02.14 u=])

This metabug is meant to track everything related to our Q3 Eideticker goal for FirefoxOS:

"Create a set (at least 2) of tests for b2g Eideticker to measure user perceived application startup and scrolling performance, and run on a daily basis"

(yes I should have filed this earlier... but better late than never)
Depends on: 879192
Status: NEW → ASSIGNED
Keywords: perf
Whiteboard: [c=automation p= s= u=]
Hey Dave, I know you managed to get this set up in the London office just before the holidays... what more needs to be done to get this reporting to eideticker.mozilla.org? Is it just a matter of ssh keys?
Flags: needinfo?(dave.hunt)
The laptop is in the London office and I've successfully triggered tests on it. The CI system will need several updates based on recent changes in Eideticker but they should be fairly straight-forward. Publishing the reports *should* work so long as the networking is setup as expected, but there are currently a couple of complications.

1. I cannot get remote access to the laptop. It has a fixed IP of 10.246.24.39 and a hostname of eideticker-london.corp.lon1.mozilla.com, but I am unable to reach this on any of my VPN configurations. I was able to successfully reach it in December shortly after setting it up, and I have been reassured that it is still up and responding within the office.

2. I cannot (easily) get local access to the laptop. My wife is expecting our second child any day, and I'd rather not be 2 hours away if it all kicks off. Also, after the event I will be taking two weeks paternity leave, which is likely to delay this further.

3. The London desktop support guy is no longer the London desktop support guy, and there's no replacement. This makes troubleshooting the network issues much harder. I'm currently talking to jlin in #servicedesk to see if we can get this running.
Flags: needinfo?(dave.hunt)
I'm now able to access the eideticker-london node remotely (solution was to route all traffic over VPN) and am working on getting the CI running again.
This is now running in the London office and currently reporting to http://people.mozilla.org/~dhunt/eideticker-ci-dashboard/b2g.inari.mozilla-central.master.tests/ with the patches applied from bug 960063 and bug 960530.
Depends on: 960530
We now have a system reporting to http://eideticker.mozilla.org/b2g

It doesn't run every test we'd like it to, but we have startup metrics going at least.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Priority: -- → P2
Whiteboard: [c=automation p= s= u=] → [c=automation p= s=2014.02.14 u=]
Product: Testing → Testing Graveyard
You need to log in before you can comment on or make changes to this bug.