patches to stop scheduling tests via buildbot on macosx

RESOLVED INVALID

Status

Release Engineering
General Automation
RESOLVED INVALID
8 months ago
8 months ago

People

(Reporter: kmoir, Assigned: spacurar)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 obsolete attachments)

(Reporter)

Description

8 months ago
similar to bug 1353376, but for tests.  Again, we could try it on a project branch to start.

You could start working on these patches now even though we're not ready to work on them yet.
(Reporter)

Updated

8 months ago
Assignee: nobody → spacurar
(Assignee)

Comment 1

8 months ago
Created attachment 8860945 [details] [diff] [review]
bug_1358566_stop-scheduling-tests-via-buildbot-on-macosx.patch

I disabled both opt and debug tests.
Attachment #8860945 - Flags: review?(kmoir)
(Assignee)

Comment 2

8 months ago
Created attachment 8860946 [details]
diff_stop-scheduling-tests-via-buildbot-on-macosx
(Reporter)

Comment 3

8 months ago
Comment on attachment 8860945 [details] [diff] [review]
bug_1358566_stop-scheduling-tests-via-buildbot-on-macosx.patch

Looking again at the patches in bug 1358566

https://reviewboard.mozilla.org/r/132416/diff/1#index_header

this will disable the sendchanges for opt and talos changes in mozharness scripts

and this will ride the trains.  So I don't think we need to do anything on the buildbot side to disable tests. 

We want the builders to remain there so they can run the tests on buildbot bridge.
i.e. scheduled on taskcluster but run on buildbot.

So I apologize for the confusion.  This bug is not needed.
Attachment #8860945 - Flags: review?(kmoir)
(Assignee)

Comment 4

8 months ago
It's ok, no problem. I was also wondering how it will work with this patch. I was thinking I missed something this whole time. 
I will mark the patch as obsolete.
(Assignee)

Updated

8 months ago
Attachment #8860946 - Attachment is obsolete: true
(Assignee)

Updated

8 months ago
Attachment #8860945 - Attachment is obsolete: true
(Reporter)

Updated

8 months ago
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.