Created attachment 302911 [details] perf-staging.tar.gz replicate talos buildbot master in a staging environment.
Comment on attachment 302911 [details] perf-staging.tar.gz in light of changes to nochrome status, I'm removing the review request. A new patch will be forthcoming.
Assignee: nobody → rcampbell
Priority: -- → P2
Created attachment 309228 [details] master.cfg updated master.cfg. Should reflect current reality. Configs to be copied as-needed.
Created attachment 309229 [details] [diff] [review] perf-staging2.patch included configs
Comment on attachment 309229 [details] [diff] [review] perf-staging2.patch This has the wrong set of configs (and has some configs that I've never heard of like vlad.config). I think that we need: sample.config sample.config.nogfx sample.config.nochrome fast.sample.config jss.sample.config historic_manifest.txt and to keep the blades going (those these may not strictly be necessary as I don't know if it downloads new configs per run): sample.config.win32 config-win32-pxp.py
Attachment #309229 - Flags: review?(anodelman) → review-
Also, this is still using buildsteps that check out talos per run - I thought that we'd be using something else for staging so that we can test out non-checked in talos code (or talos code that has been checked in somewhere else, or something).
As a first crack, I copied the master.cfg and just stripped out what wasn't needed. We can comment out the checkout steps to get around that. I'll repatch after landing bug 421917 and cull the extraneous configs.
also, there'll be a companion patch to this one to remove the no-longer-needed parts of the master that point to MozillaTest from the production master.
Looks like we'll only need: configs/config-win32-pxp.py configs/sample.config.win32 configs/jss.sample.config configs/sample.config and scripts/generate-tpcomponent.py which we can just copy out of the production master for now. "fast" configs are in production. I think the config-win32-pxp.py file is uploaded on each run but I'm not sure what's done with it. sample.config.win32 is modified by the PerfConfigurator so I'm pretty sure we still need it, but don't necessarily need to move it up every run.
Created attachment 309417 [details] [diff] [review] [checked in] perf-staging3.patch pruned configs directory, converted staging directory to ftp and commented cvs checkout steps.
Created attachment 309428 [details] [diff] [review] [checked in] production master.cfg pruned master.cfg. We can remove config files in a separate patch.
Attachment #309428 - Flags: review?(anodelman)
Yes, the list in comment #8 is the staging configs currently in use - my list was the complete set of staging configs. I'd like to have them all moved over so that only production configs will be in the production directory and only staging configs will live in the staging directory. I just figure that if we are moving around configs that we might as well get the full set.
Comment on attachment 309417 [details] [diff] [review] [checked in] perf-staging3.patch This looks like a pretty good first pass. We'll need to figure out how we want to get talos code onto staging machines - in this case this will work with currently up machines that already have copies of talos locally, but new machines won't run.
Attachment #309417 - Flags: review?(anodelman) → review+
Attachment #309428 - Flags: review?(anodelman) → review+
cvsci "417094 - add talos staging directory to cvs, p=me, r=anodelman" cvs commit: Examining . cvs commit: Examining configs RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/master.cfg,v done Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/master.cfg,v <-- master.cfg initial revision: 1.1 done RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/config-win32-pxp.py,v done Checking in configs/config-win32-pxp.py; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/config-win32-pxp.py,v <-- config-win32-pxp.py initial revision: 1.1 done RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/historic_manifest.txt,v done Checking in configs/historic_manifest.txt; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/historic_manifest.txt,v <-- historic_manifest.txt initial revision: 1.1 done RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/jss.sample.config,v done Checking in configs/jss.sample.config; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/jss.sample.config,v <-- jss.sample.config initial revision: 1.1 done RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/sample.config,v done Checking in configs/sample.config; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/sample.config,v <-- sample.config initial revision: 1.1 done RCS file: /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/sample.config.win32,v done Checking in configs/sample.config.win32; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/configs/sample.config.win32,v <-- sample.config.win32 initial revision: 1.1 done
Attachment #309417 - Attachment description: perf-staging3.patch → [checked in] perf-staging3.patch
Comment on attachment 309428 [details] [diff] [review] [checked in] production master.cfg Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perfmaster/master.cfg,v <-- master.cfg new revision: 1.47; previous revision: 1.46 done
Attachment #309428 - Attachment description: production master.cfg → [checked in] production master.cfg
Created attachment 309636 [details] [diff] [review] [checked in] master.cfg with installed updates Checking in master.cfg; /cvsroot/mozilla/tools/buildbot-configs/testing/talos/perf-staging/master.cfg,v <-- master.cfg new revision: 1.3; previous revision: 1.2 done
Attachment #309417 - Attachment is obsolete: true
Component: Testing → Release Engineering: Maintenance
Product: Core → mozilla.org
Whiteboard: need to apply final update to production master
Version: Trunk → other
Anything left to do here or can we close this?
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.