Re: Trees closed, no ETA for reopening until cloud issues fixed
On Tuesday, February 28, 2017 at 10:37:13 AM UTC-8, Sebastian Hengst wrote: > Hi, > > at the moment, there is major internet outage affecting cloud services > like Amazon's AWS. > > Because the release automation infrastructure depends on that, we had to > close the trees and you won't be able to push. At the moment, it's not > possible to say when trees will be reopened. Treeherder doesn't show > that trees are closed because this had to be done internally. > > https://bugzilla.mozilla.org/show_bug.cgi?id=1343293 tracks the tree > closure. > > Thank you for your patience. > > Sebastian At this point, most trees are reopened. Mozilla-inbound is the only one still closed a I'm cleaning up failures that are trickling in as Treeherder catches up on processing finished jobs. I expect to be done in the next hour or so and then reopen mozilla-inbound. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Trees closed, no ETA for reopening until cloud issues fixed
On Tuesday, February 28, 2017 at 6:07:30 PM UTC-8, KWierso wrote: > On Tuesday, February 28, 2017 at 10:37:13 AM UTC-8, Sebastian Hengst wrote: > > Hi, > > > > at the moment, there is major internet outage affecting cloud services > > like Amazon's AWS. > > > > Because the release automation infrastructure depends on that, we had to > > close the trees and you won't be able to push. At the moment, it's not > > possible to say when trees will be reopened. Treeherder doesn't show > > that trees are closed because this had to be done internally. > > > > https://bugzilla.mozilla.org/show_bug.cgi?id=1343293 tracks the tree > > closure. > > > > Thank you for your patience. > > > > Sebastian > > At this point, most trees are reopened. Mozilla-inbound is the only one still > closed a I'm cleaning up failures that are trickling in as Treeherder catches > up on processing finished jobs. I expect to be done in the next hour or so > and then reopen mozilla-inbound. I reopened inbound. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
./mach try empty
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 builds or tests. Once pushed, you can sign in to Treeherder and manually add whatever jobs you'd like via Treeherder's "Add New Jobs" button in the per-push menu. The tryserver wiki page[1] has a section showing how to manually add jobs to a push, with some pictures, if it's helpful. You'll need to be on a somewhat recent checkout of mozilla-central, and it wouldn't hurt to run `./mach mercurial-setup --update` again, though I don't believe that's strictly necessary. Enjoy, Wes 1. https://wiki.mozilla.org/ReleaseEngineering/TryServer#Scheduling_jobs_with_Treeherder ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: PSA: Cancel your old Try pushes
On Friday, April 15, 2016 at 5:11:55 PM UTC-7, Xidorn Quan wrote: > On Sat, Apr 16, 2016 at 1:47 AM, Ryan VanderMeulen < > rvandermeu...@mozilla.com> wrote: > > > I'm sure most of you have experienced the pain of long backlogs on Try > > (Windows in particular). While we'd all love to have larger pools of test > > machines (and our Ops people are actively working on improving that!), one > > often-overlooked thing people can do to help with the backlog Right Now is > > to cancel pending jobs on pushes they no longer need (i.e. newer push to > > Try, broken patch, already pushed to inbound, etc). > > > > Treeherder makes it easy to do this - just hit the little circle with an X > > icon on the right hand side adjacent to the "XX% - Y in progress" text > > along the top bar of the push. You will be prompted whether you really want > > to cancel all jobs on the push. Just hit OK and you're done. > > > > Killing off unnecessary jobs can have a significant impact on wait times > > and backlog, so your consideration is greatly appreciated! > > > > Can we probably provide an additional banner on the top of the treeherder > which shows all try pushes one has pushed in progress? I suppose it would > make people easier to find and switch between their own try pushes, and > also make it more convenient to cancel old pushes they no longer need > without adding much annoyance. > > - Xidorn There's a Treeherder bug on file for providing a view like that. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Tree Closures due to Bug 1286942 Buildbot DB Issues
On Friday, July 15, 2016 at 2:59:55 AM UTC-7, Carsten Book wrote: > Hi, > > we currently have a complete tree closure due to Buildbot DB Issues. > > The Teams working on resolving this issue and the Tracking Bug is: > https://bugzilla.mozilla.org/show_bug.cgi?id=1286942 > > There is no ETA yet for reopening. > > Thanks for your patience. > > - Tomcat > > P.S. one way to get patches checked-in automatically would be using > MozReview and Autoland to push it when then tree reopens. Just to close the loop here, the DB issues were resolved this morning. Trees remained mostly closed while the usual post-extended-closure backlog cleared up. All trees were re-opened this afternoon. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: How do I file a bug?
On Thursday, October 4, 2018 at 5:14:53 PM UTC-7, fantasai wrote: > On 10/04/2018 04:26 PM, Steve Fink wrote: > > On 10/04/2018 03:45 PM, fantasai wrote: > >> Start here, at Mozilla's home page: > >> https://www.mozilla.org/ > >> > >> Give me steps to reproduce to find instructions for filing > >> a bug against Firefox. Ditto for up-to-date instructions > >> for building the source and submitting a patch. > >> > >> (Don't send me links to the instructions; I'm cheating by > >> asking here already. Walk me through the process of > >> discovering how I can contribute to Mozilla and make the > >> world a better place. I wouldn't be here if I hadn't > >> already walked that path 19 years ago, but I can't find it > >> anymore so I need some help.) > > > > I tried it out, and did better than I expected on my first run-through: > > [...] > > I'm impressed! Want to take a stab at finding patch-submission > instructions? :D > > > I agree that a nice path from www.mozilla.org would be beneficial, > > especially for promoting the volunteer aspect of the project. > > We've got a lot of highly-produced (read: expensive) material > promoting the volunteer aspect of Mozilla: >https://www.mozilla.org/en-US/contribute/ > But afaict none of it actually leads to a viable path towards > actually becoming a technical contributor... > > From my discussions with staff at Mozilla, the people actually > working with volunteers (like QA and l10n) find this very > frustrating, but the people whose job it is to connect volunteers > to opportunities to contribute don't think it's useful, important, > or in some cases even a good idea to fix this problem. I don't > know how to break through that resistance, and I find it very > demoralizing that there even is any. :( > > I'm also disconnected enough from Mozilla the last few years > that I've no idea where up-to-date documentation on this stuff > would live. If I ever manage to dig myself out of the backlog > of spec work enough to write a patch, I'd like to know where > to look! > > Fwiw, here's how I arrived at becoming a technical contributor: >https://web.archive.org/web/2125153750/http://www.mozilla.org:80/ > > https://web.archive.org/web/2301043132/http://www.mozilla.org:80/get-involved.html > > https://web.archive.org/web/2302035824/http://www.mozilla.org:80/quality/bug-writing-guidelines.html > > https://web.archive.org/web/2304015940/http://www.mozilla.org:80/newlayout/bugathon.html > > “One of the things that people seem to like best about the > existing content on mozilla.org is that it is written by people, > for people, without bluster or self-promotion.” > -- jwz, Mozilla Documentation Style Guide, 1999 > > ~fantasai I would say adding a link to https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines (or maybe https://support.mozilla.org/en-US/kb/contributors-guide-writing-good-bug ) in the "More links" section at the bottom of https://www.mozilla.org/en-US/contribute/ would go a long way toward having a better onboarding experience for filing bugs. https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/How_to_Submit_a_Patch would be the patch for patch submission. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Deprecation notice - change to Treeherder's jobdetail API
On Friday, April 10, 2020 at 11:08:14 AM UTC-7, Sarah Clements wrote: > Otherwise, this is the API: > https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task//runs/0/artifacts > <-- for all artifacts or with `/` to select just one specific > artifact. Just as a side note, that "0" in the URL can sometimes be "1" or a higher integer if the job had failed in a way that made taskcluster automatically retry/rerun the job. (It's the [runId] or [retryId] mentioned up-thread) ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
