Enable Talos on the Electrolysis branch

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
8 years ago
4 years ago

People

(Reporter: Benjamin Smedberg, Assigned: lsblakk)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments, 2 obsolete attachments)

(Reporter)

Description

8 years ago
When we started the Electrolysis branch builds there was no point in running Talos on them. Now we're more stable I'd like to start running Talos on these builds on all three desktop platforms. It is not important to run Talos on any mobile platforms at this point (if Talos even exists for any mobile platforms, I'm not clear on that).
Component: Release Engineering → Release Engineering: Future
(Reporter)

Comment 1

8 years ago
jford, what does the "future" marking mean here? I was told when e10s was created that adding Talos in the future would be really quick and easy.
(In reply to comment #1)
> jford, what does the "future" marking mean here? I was told when e10s was
> created that adding Talos in the future would be really quick and easy.

jhford was triaging this, as no-one else had time to deal with this today. I'll take it for now, and thumb-wrestle with lsblakk and anodelman on Monday to see who can deal with this. 

Original comment still stands, yes, this should be easy to enable on this branch. 

Note: we are talking here about enabling the pre-existing talos suites. This is unrelated to the new multi-process talos suites you were asking about elsewhere and which have yet to be written afaik.
Assignee: nobody → joduinn
Component: Release Engineering: Future → Release Engineering
OS: Windows NT → All
(Assignee)

Comment 3

8 years ago
Created attachment 408143 [details] [diff] [review]
Add electrolysis branch to talos config.py
Attachment #408143 - Flags: review?(anodelman)
(Reporter)

Comment 4

8 years ago
Yes, existing Talos to match mozilla-central, the other work will come later.
(In reply to comment #4)
> Yes, existing Talos to match mozilla-central, the other work will come later.

Perfect. This we can do quickly, in fact Lukas already has patch up for review.
Assignee: joduinn → lsblakk
Attachment #408143 - Flags: review?(anodelman) → review+
Tested in staging?
(Assignee)

Comment 7

8 years ago
Created attachment 408424 [details] [diff] [review]
Add electrolysis branch to talos config.py in staging

Will test this in staging on next downtime.
(Assignee)

Comment 8

8 years ago
Created attachment 410357 [details] [diff] [review]
Add electrolysis branch to talos config.py in staging

This is the current patch that I ran in staging today. The linux builds have the libstdc++ mismatch at the moment:

mozqa@qm-ref-ubuntu:~/talos-slave/talos-data$ ./firefox/firefox
./firefox/firefox-bin: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.10' not found (required by ./firefox/libxul.so)
Attachment #408424 - Attachment is obsolete: true
(Reporter)

Comment 9

8 years ago
Yes. I don't think that should necessarily block putting this into production.
Created attachment 410400 [details] [diff] [review]
Enables talos for electrolysis on staging and production
Attachment #410400 - Flags: review?(anodelman)
We're going to schedule a downtime for this coming Monday, providing the 3.6 release gets the go ahead, and this will get turned on at that time.
Attachment #410400 - Flags: review?(anodelman) → review+
Downtime update - this Wednesday at 8am PST.
Created attachment 411550 [details] [diff] [review]
Turn on talos for Electrolysis with V8 and SVG Opacity

so this one is now queued up behind turning on V8 (bug 506772) and SVG opacity (bug 524089)
Attachment #410400 - Attachment is obsolete: true
Attachment #411550 - Flags: review?(anodelman)
Attachment #411550 - Flags: review?(anodelman) → review+
Comment on attachment 411550 [details] [diff] [review]
Turn on talos for Electrolysis with V8 and SVG Opacity

http://hg.mozilla.org/build/buildbot-configs/rev/645d3e06adf3
Attachment #411550 - Flags: checked-in+
Switched this on today, closing.
Status: NEW → RESOLVED
Last Resolved: 8 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.