Closed Bug 1113273 Opened 10 years ago Closed 10 years ago

talos determines the sourcestamp and other binary specific information during ffsetup, this could be done earlier in the harness

Categories

(Testing :: Talos, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: jmaher)

References

Details

Attachments

(1 file)

Inside of talos we start running a test and the first thing we do is create a fresh profile and initialize it.  During this specific process we parse the revision, sourcestamp, etc. from the binary.

We end up doing this for each test we run in the test run, in most jobs we run this is done 3+ times, in some jobs it is done 6 times.

we can move this to run_tests.py where much of the browser_config setup is done.  

This seems like a cleaner place to do this and it allows us to use the source stamp for logging or other decisions if we choose to at any point during the test run.
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Attachment #8538657 - Flags: review?(wlachance)
Comment on attachment 8538657 [details] [diff] [review]
move mozversion data extraction to run_tests.py from ffsetup.py (1.0)

Review of attachment 8538657 [details] [diff] [review]:
-----------------------------------------------------------------

Makes sense, thanks!
Attachment #8538657 - Flags: review?(wlachance) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: