How to handle patches for openqa_fedora in Pagure ?
Hello Adam, I saw you copied the git trees of openqa from Bitbucket to Pagure as per ticket T863 (1) What is the way to submit patches on openqa_fedora in Pagure ? Are there fork and pull-request functionality in Pagure ? or do I have to handle in another place my changes and submit patches by email ? (1) https://phab.qa.fedoraproject.org/T863 -- Michel Normand ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: How to handle patches for openqa_fedora in Pagure ?
Up to this point, we were using Phabricator (https://phab.qa.fedoraproject.org/) for code reviews, but it is kinda hard to set up. As far as I know, we don't have openQA repos in Pagure yet, but we will have soon, so if you don't want to install arcanist (cli tool for submitting to Phab), just wait until moving to Pagure is over and submit your pull request here (yes, there is fork/pull-request functionality in Pagure). Jan ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: New ExecDB
There's not been a huge amount of effort put to this - I've had other priorities ever since, but I can get back on it, if you feel it's the time to do it. The only code to work in that direction is here: https://bitbucket.org/fedoraqa/execdb/branch/feature/pony where I only basically started on removing the tight coupling between execdb and buildbot, and then I went on trying to figure out what's in this thread. On Tue, Jan 10, 2017 at 6:57 AM, Tim Flink wrote: > On Fri, 21 Oct 2016 13:16:04 +0200 > Josef Skladanka wrote: > > > So, after a long discussion, we arrived to this solution. > > > > We will clearly split up the "who to notify" part, and "should we > > re-schedule" part of the proposal. The party to notify will be stored > > in the `notify` field, with `taskotron, task, unknown` options. > > Initially any crashes in `shell` or `python` directive, during > > formula parsing, and when installing the packages specified in the > > formula's environment will be sent to task maintainers, every other > > crash to taskotron maintainer. That covers what I initially wanted > > from the multiple crashed states. > > > > On top of that, we feel that having an information on "what went > > wrong" is important, and we'd like to have as much detail as > > possible, but on the other hand we don't want the re-scheduling logic > > to be too complicated. We agreed on using a `cause` field, with > > `minion, task, network, libtaskotron, unknown` options, and storing > > any other details in a key-value store. We will likely just > > re-schedule any crashed task anyway, at the beginning, but this > > allows us to hoard some data, and make more informed decision later > > on. On top of that, the `fatal` flag can be set, to say that it is > > not necessary to reschedule, as the crash is unlikely to be fixed by > > that. > > > > This allows us to keep the re-scheduling logic rather simple, and most > > imporantly decoupled from the parts that just report what went wrong. > > How far did you end up getting on this? > > Tim > > ___ > qa-devel mailing list -- qa-devel@lists.fedoraproject.org > To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org > > ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: Task Result Dashboards
On Wed, Jan 11, 2017 at 11:42:32PM -0700, Tim Flink wrote: > The motivation is to enable more complex visualizations of results. If > we're interested in the current state of all ruby packages or all > python packages it's not all that easy to see that at a glance with our > current resultsdb interfaces. > > I can also see having a dashboard for all critpath packages or all > packages needed for building a livecd being a useful thing to render Oh, I see. Cool. This seems like it could be very useful for Modularity — one dashboard for each module. -- Matthew Miller Fedora Project Leader ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: How to handle patches for openqa_fedora in Pagure ?
On Thu, 2017-01-12 at 09:11 +0100, Normand wrote: > Hello Adam, > I saw you copied the git trees of openqa from Bitbucket to Pagure as per > ticket T863 (1) I didn't - it must have been garretraziel, if it's been done. > What is the way to submit patches on openqa_fedora in Pagure ? > Are there fork and pull-request functionality in Pagure ? > or do I have to handle in another place my changes and submit patches by > email ? I think for now we're sticking with the Phabricator-based process rather than switching to Pagure's PR / issue tracking. For now for these repos we're just using Pagure as a git host. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
Re: How to handle patches for openqa_fedora in Pagure ?
On Thu, 2017-01-12 at 08:29 -0800, Adam Williamson wrote: > On Thu, 2017-01-12 at 09:11 +0100, Normand wrote: > > Hello Adam, > > I saw you copied the git trees of openqa from Bitbucket to Pagure as per > > ticket T863 (1) > > I didn't - it must have been garretraziel, if it's been done. > > > What is the way to submit patches on openqa_fedora in Pagure ? > > Are there fork and pull-request functionality in Pagure ? > > or do I have to handle in another place my changes and submit patches by > > email ? > > I think for now we're sticking with the Phabricator-based process > rather than switching to Pagure's PR / issue tracking. For now for > these repos we're just using Pagure as a git host. To harmonize with Jan's answer: I'm certainly fine with switching from Phabricator to Pagure for openQA issue and PR tracking if we want to do that too, I just wasn't sure it was part of the plan :) -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net ___ qa-devel mailing list -- qa-devel@lists.fedoraproject.org To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org
