Closed Bug 1100438 Opened 11 years ago Closed 11 years ago

add a requirements.txt file to talos so we can read this in while setting up in automation

Categories

(Testing :: Talos, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: jmaher)

References

Details

Attachments

(1 file)

right now our method of installing talos as a python module is not very useful since we always have version 0.0. This works ok, but with pypi caching we can run into problems. In fact with the way our mozharness script works, we clone the entire repo anyway, and make sure that talos as a package is installed. A way to reduce our duplicate installation is to clone and run from the clone (instead of a cached package and a fresh clone). To do this we can create a requirements.txt file.
This doesn't remove the old methods, but it gets us started; once this is in we can start editing the mozharness script; when that is done we can clean up the old definitions that define requirements, etc.
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Attachment #8523949 - Flags: review?(wlachance)
Comment on attachment 8523949 [details] add requirements.txt to talos (1.0) This sounds like a good step forward. If we're going to keep setup.py, I'd like to modify it to read from this file so we can stay in sync. See the web platform tests for an example of this: http://mxr.mozilla.org/mozilla-central/source/testing/web-platform/harness/setup.py#18 r+ conditional on that change being made.
Attachment #8523949 - Flags: review?(wlachance) → review+
great idea on setup.py, fixed that and it is landed; I will be deploying to a few branches in a couple of days- stay tuned!
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Blocks: 1101789
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: