|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
Maybe we could use the e10s project branch if it's not longer needed, or set up a new one. I don't know what is the process for this but it would be a huge help to prevent regressions and new tests that are not e10s-multi compatible.
Ryan, this was your idea many months ago, and we all think it would be awesome. Could you help us with setting it up or do you know who else we could ask for help?
Here are some potentially useful pages about project branches: https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches
I'd be open to using Ash for this. Can we discuss after this week's e10s standup?
(In reply to J. Ryan Stinnett [:jryans] (use ni?) from comment #2) > Here are some potentially useful pages about project branches: > > https://wiki.mozilla.org/ReleaseEngineering:ProjectBranchPlanning > https://wiki.mozilla.org/ReleaseEngineering/DisposableProjectBranches Thanks! (In reply to Ryan VanderMeulen [:RyanVM] from comment #3) > I'd be open to using Ash for this. Can we discuss after this week's e10s > standup? Yes, that sounds perfect.
This is the bug we should use to turn on e10s-multi on Ash. Ryan, do you want to write the patches or at least point me to what I need to look for to do this? You mentioned that there are a few places to patch.
Summary: [e10s-multi] Project branch for e10s-multi until we can turn it on on nightly → [e10s-multi] Use Ash for e10s-multi continuous integration testing
I've pushed the above patch to ash, marking this as FIXED. We should aim to get Ash green again ASAP.
Assignee: nobody → mrbkap
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.