Closed Bug 767117 Opened 10 years ago Closed 10 years ago
jetperf needs config files
In order to be run in production, jetperf will need a production config file. It should probably also have a more developer friendly config.
By no means finished, just wanted to put up what I have before I get pulled off to something else
These seem to work for me. I'm not sure if this is adequate for production or not, but its my best first guess. I'm also proposing a test_config.py for local testing, but I don't really care if this makes it into the mozharness repo or not
Comment on attachment 642615 [details] [diff] [review] initial implementation That works. Are we going to be doing any production work on windows? If so, we need windows-specific config files as well; hopefully the existing jetperf stuff will help.
Attachment #642615 - Flags: feedback?(aki) → feedback+
(In reply to Aki Sasaki [:aki] from comment #3) > Comment on attachment 642615 [details] [diff] [review] > initial implementation > > That works. > Are we going to be doing any production work on windows? > If so, we need windows-specific config files as well; hopefully the existing > jetperf stuff will help. AFAIK, we do want to run on windows. Alex, is that correct?
(In reply to Jeff Hammel [:jhammel] from comment #4) > AFAIK, we do want to run on windows. Alex, is that correct? Yes. While not being mandatory for a first step, it sounds quite important to test on the most used platform.
This includes a windows config with parameters taken from peptest
Comment on attachment 642715 [details] [diff] [review] proposed implementation We may have to put in a pypi_url to avoid hitting pypi proper, and other buildbot/prod-related things, but this should allow us to have something to work off of.
Attachment #642715 - Flags: review?(aki) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.