Open Bug 1680484 Opened 5 years ago Updated 7 months ago

Upload the geckodriver.log file as artifact for the jobs

Categories

(Testing :: Raptor, task, P3)

Default
task

Tracking

(Not tracked)

People

(Reporter: alexandrui, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Whiteboard: [fxp])

Upload the geckodriver.log file as artifact for the jobs as to provide more information for investigations.

Note that Selenium stores it in the current working directory by default. So it should be easy to do.

Component: Performance → Raptor

Hi Alex :)
May I ask you about this task for some advice?
I'd like to see the geckodriver.log.
When I ran a command (i.e, ./mach raptor --browsertime -t amazon), I couldn't see geckodriver log and find any log file.
How can I check the geckodriver log or file?

Flags: needinfo?(aionescu)

Hey Jun, I'm going to redirect the question to :whimboo :)

Flags: needinfo?(aionescu) → needinfo?(hskupin)

(In reply to Greg Mierzwinski [:sparky] from comment #3)

Hey Jun, I'm going to redirect the question to :whimboo :)

Greg, I don't know about the Raptor browsertime jobs which I'm not involved in. Usually we just log stdout so that all the geckodriver logging appears next to the Firefox logs. If that's not what is done for Raptor you might wanna change, or setup the job to upload the geckodriver.log file.

Flags: needinfo?(hskupin) → needinfo?(gmierz2)

Thanks for the context :whimboo. This bug is for uploading the artifact in CI, but Jun is having a hard time finding any geckodriver.log file locally. Is there a pref we have to change to get this log file output and would you know if there's a default location for it?

Flags: needinfo?(gmierz2) → needinfo?(hskupin)

Ah, that wasn't clear in the last needinfo. So actually geckodriver doesn't create a log file (bug 1611003) yet at all but writes all the output to stdout. So all its output will indeed be part of the default log in CI.

Flags: needinfo?(hskupin)
Whiteboard: [fxp]
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.