1008848 - Add shutdown times of the application to the report

Status: RESOLVED WONTFIX

(Testing Graveyard :: Mozmill, defect)

Description

[Henrik Skupin [:whimboo][⌚️UTC+1]]

It would be good to know about the shutdown times of Firefox while running Mozmill tests. That way we could add them to our logs, beside each restart of Firefox. Those could be used later to determine shutdown slowness. This looks important especially because of the known regressions in Firefox 29.0, which are bug 1005958, bug 966469 and bug 985655.

As what I have seen is that the shutdown time is saved inside the profile as Telemetry.ShutdownTime.txt (implemented via bug 753461). Using it, and attaching it to the correct restart test result should be simply, but it will be harder to manager when the profile gets reset. So our process handling might also need an update, so that we might have to wait for an update of that file, before continuing with the next test.

Comment 1

[Rishabh Roy]

can i work on this bug ?

Comment 2

[Rishabh Roy]

(In reply to Henrik Skupin (:whimboo) from comment #0)
> It would be good to know about the shutdown times of Firefox while running
> Mozmill tests. That way we could add them to our logs, beside each restart
> of Firefox. Those could be used later to determine shutdown slowness. This
> looks important especially because of the known regressions in Firefox 29.0,
> which are bug 1005958, bug 966469 and bug 985655.
> 
> As what I have seen is that the shutdown time is saved inside the profile as
> Telemetry.ShutdownTime.txt (implemented via bug 753461). Using it, and
> attaching it to the correct restart test result should be simply, but it
> will be harder to manager when the profile gets reset. So our process
> handling might also need an update, so that we might have to wait for an
> update of that file, before continuing with the next test.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Absolutely! You are welcome to work on it.

Just to add to my last comment, we should not enable telemetry here. This is a feature we have disabled because we want to avoid that statistics are getting sent. Instead we should use the endModule event or something around the appquit observer (both located in frame.js) as time to start measuring the shutdown. On the python side we will have to wait for the process to end. For the latter you might want to wait until the patch on bug 975068 has been landed, which will happen hopefully the next two days.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

No work has happened here in the last three months. So I'm going to unassign you.

Also Mozmill will reach its end of life soon. We are currently working on getting all the tests for Firefox ported to Marionette. For status updates please see bug 1080766.