*tl;dr:* Taskcluster, the platform supporting Firefox CI, will be moving to
a new hosting environment during the tree-closing window at the end of
September. This is a major change and upgrade to the platform, but may
cause some bumps along the way.
Taskcluster is in the midst of a few migrations
*tl;dr:* Taskcluster, the platform supporting Firefox CI, will be moving to
a new hosting environment during the tree-closing window at the end of
September. This is a major change and upgrade to the platform, but may
cause some bumps along the way.
Taskcluster is in the midst of a few migrations
@tomprince reminds me that it's important to note these changes were
uplifted to the release branches, so pushing release branches to try should
continue to work without any issue.
Dustin
On Mon, Mar 11, 2019 at 6:33 PM Dustin Mitchell wrote:
> I am in the process of landing
&
I am in the process of landing
https://bugzilla.mozilla.org/show_bug.cgi?id=1526979
which changes the way we trigger decision tasks to make them more
predictable and debuggable.
In the process, I landed the necessary in-tree support in
https://phabricator.services.mozilla.com/D18288
https://
We have been working on a new approach to configuring the Firefox-CI
installation of Taskcluster to suit Firefox's needs. If you've ever needed
a scope assigned to a repository, wondered why your project branch wasn't
getting builds, or couldn't figure out what instance type a worker uses,
this is
Firefox has an extensive performance testing framework, called Talos
https://wiki.mozilla.org/Buildbot/Talos might be a good place to start.
Dustin
2017-11-17 10:02 GMT-05:00 :
> Hello,
>
> I would like to test Firefox browser performance test - using default
> settings and using customized se
I think we should question the assumption that writing
source-code-level documentation is a good activity for newcomers to
the codebase.
Documentation is usually best written by someone with a deep
understanding of what is being documented, not by someone new to the
project. And this documentatio
This is awesome, thanks Wes!
Dustin
2017-09-26 16:16 GMT-04:00 KWierso :
> I've recently landed a new way to push things to the tryserver. With `./mach
> try empty`, mach will just push whatever commits you're working on to try,
> without prompting you for anything and without scheduling any bu
This is awesome, thanks Wes!
Dustin
2017-09-26 16:16 GMT-04:00 KWierso :
> I've recently landed a new way to push things to the tryserver. With `./mach
> try empty`, mach will just push whatever commits you're working on to try,
> without prompting you for anything and without scheduling any bu
2017-09-14 18:32 GMT-04:00 Botond Ballo :
> I think "-p all" is still useful for "T pushes" (and it sounds like
> build jobs aren't the main concern resource-wise).
Correct -- all builds are in AWS.
I'd like to steer this away from "What legacy syntax should we use
instead?" and "How should we tw
And if there are any unexpected-visible tasks, we stand ready to fix
that either in the tier settings or during Treeherder ingestion. Let
us know.
Dustin
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev
2017-09-03 13:51 GMT-04:00 William Lachance :
> There's also the "retrigger job with extra options" action which you can
> trigger directly from treeherder, that lets you set the environment,
> preferences, and a few other things:
>
> https://wlach.github.io/blog/2017/04/easier-reproduction-of-inte
Oops, the profile is from a *different* random github page from my
history, sorry for any confusion.
2017-09-03 12:40 GMT-04:00 Dustin Mitchell :
> I just reproduced it with a random page from my history:
> https://github.com/taskcluster/taskcluster-cli/issues/49. Any github
> page wil
I just reproduced it with a random page from my history:
https://github.com/taskcluster/taskcluster-cli/issues/49. Any github
page will do, and it seems to have to do with caching. if I delete
today's history, I can reproduce. And with a repro recipe, I can
capture a profile -- https://perfht.ml
That general mechanism is open-ended, though -- fuzzy is just one
interface to it. The possibilities for shortcuts, purpose-specific
commands, and automation are enormous.
https://firefox-source-docs.mozilla.org/taskcluster/taskcluster/try.html
Dustin
2017-09-02 23:04 GMT-04:00 Andrew Halbersta
I haven't distinguished between those two options -- I was making the
point that Ghostery isn't (exclusively) to blame. Yes, it's that test
pilot.
The flashes (just saw another a moment ago) are on github.com.
Dustin
2017-09-01 17:01 GMT-04:00 Boris Zbarsky :
> On 9/1/1
I can narrow that bisection down to two sets: [test-pilot] and [].
Dustin
2017-09-01 9:54 GMT-04:00 Boris Zbarsky :
> On 9/1/17 7:02 AM, Gervase Markham wrote:
>>
>> Restarting with no extensions causes my browser to feel a whole lot
>> faster (I'd love to know why that is, but that's a separate
I've seen it a few times now since this thread began. I had Ghostery
installed but removed it a few days ago. I only have whimsy
(disabled) and test pilot installed.
Dustin
2017-08-31 15:00 GMT-04:00 Michael Froman :
>
>> On Aug 31, 2017, at 1:08 PM, Boris Zbarsky wrote:
>>
>> The symptoms yo
I've been seeing this, too, often on github pages. I do not have
stylo enabled per about:support ("false (disabled by default)").
Dustin
2017-08-31 13:45 GMT-04:00 Chris Peterson :
> Gerv, do you have Stylo enabled? Even if you did not flip the pref
> (layout.css.servo.enabled), you might be in
This was a huge project full of detailed requirements and challenges,
and an important step in the taskcluster migration. Congratulations
to everyone who worked so hard to make it happen!
Dustin
___
dev-platform mailing list
dev-platform@lists.mozilla.o
Nice work -- what a milestone!
Dustin
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
Just to follow up, we've determined that the `-t all` issue was
bustage from something that landed yesterday. It's fixed now.
Dustin
2017-05-13 15:04 GMT-04:00 Matthew N. :
> On 5/13/17 11:31 AM, Dustin Mitchell wrote:
>>
>> Specifically, -t for e10s talos doesn'
Specifically, -t for e10s talos doesn't work. Non-e10s talos works
fine (but then, e10s talos are the interesting perf numbers..)
>From the look of it, this has been broken since mid-March, but was
only recently reported. Note that issues like this are now fixable by
anyone who can write a patch
Yep, this caused problems in automation (we ended up setting
I_PREFER_A_SUBOPTIMAL_MERCURIAL_EXPERIENCE_THANK_YOu or whatever the
env var was). I agree that a quick warn-and-continue would be fine.
Dustin
2017-05-12 15:23 GMT-04:00 Eric Rahm :
> Didn't it somehow cause builds to fail? A gentle r
I think many of the concerned people were flagged for r? on bug
1286075, but for everyone else, it's landed in inbound today.
If you haven't mucked around with the configuration of which
TaskCluster tasks run for pushes, and how they run, then you can tune
out now.
If you have a project that I've
If you have worked on adding or modifying the gecko tasks that run in
taskcluster, heads up!
I've just pushed a patchset to bug 1286075 which will dramatically
change how tasks are configured. Change for the better, of course!
Please see the bug for the details, but the general idea is that task
Admin Assigned: jhford
Impact to service: Some TaskCluster worker types had backlogs of 30-60
minutes, including taskcluster-images jobs which must run before
builds can begin. Trees are closed, preventing further check-ins.
Start Date/Time: 2016-08-23 07:12:00 PDT
Bug: https://bugzilla.mozilla
> BTW, starting yesterday, there was a "TaskClusterRobot" comment on my m-i
> push on GitHub with message "TaskCluster: @upsuper does not have permission
> to trigger tasks." [1][2]
This was due to an unfortunate interaction of the mirroring of gecko
to github, and the taskcluster-github component
28 matches
Mail list logo
