Re: [PATCH qa-frontpage WIP] Add a library to parse patchwork json data

a set of functions to parse and serialize these. > > A fun experiment is to run the following script: > > (use-modules (guix-qa-frontpage patchwork patch-series)) > (use-modules (rnrs bytevectors)) > (use-modules (web client)) > (use-modules (ice-9 receive)) > (use-modules (jso

[PATCH qa-frontpage WIP] Add a library to parse patchwork json data

experiment is to run the following script: (use-modules (guix-qa-frontpage patchwork patch-series)) (use-modules (rnrs bytevectors)) (use-modules (web client)) (use-modules (ice-9 receive)) (use-modules (json)) (define patchwork-data (receive (r body) (http-get "https://patches

Re: More thoughts on Patchwork and Guix patch review/quality assurance

Hi Chris! Christopher Baines skribis: > If you're interested in using this to review patches, the place to start > is Patchwork, so visit: > > https://patchwork.cbaines.net/ > > If you want an account, please email me. Unfortunately I had to disable > registration due

More thoughts on Patchwork and Guix patch review/quality assurance

out about the results, and the builds can be prioritised by the number of packages being built for a patch series. If you're interested in using this to review patches, the place to start is Patchwork, so visit: https://patchwork.cbaines.net/ If you want an account, please email me. Unfortunately

Patchwork + the Guix Data Service for assisting with patch review

parts of reviewing Guix patches. 1: https://lists.gnu.org/archive/html/guix-devel/2020-02/msg00268.html This email is in four rough parts, some rambling, then an update on the "Current Status" of the patch review tooling I've been trying to setup, then a description of "How you ca

Re: Patchwork + automated checking and testing of patches

n]. When I then say "git am patch.mbox" it complains there is nothing in. I then have to say "git am --skip" and it goes on automatically. Could that also be the case with your patchwork-setup? Björn pgpKgl0qs4iHl.pgp Description: OpenPGP digital signature

Re: Patchwork + automated checking and testing of patches

is Git >> repository [3], and you can see the commit range here [4]. >> >> 1: https://patchwork.cbaines.net/project/guix-patches/list/?series=482 >> 2: https://laminar.cbaines.net/jobs/patchwork-test-series/826 >> 3: https://git.cbaines.net/guix/patches/log/?h=series-4

Re: Patchwork + automated checking and testing of patches

https://patchwork.cbaines.net/project/guix-patches/list/?series=482 > 2: https://laminar.cbaines.net/jobs/patchwork-test-series/826 > 3: https://git.cbaines.net/guix/patches/log/?h=series-482-version-1 > 4: > https://git.cbaines.net/guix/patches/log/?h=series-482-version-1=range=base-for-

Re: Patchwork + automated checking and testing of patches

processed here [2]. The result of applying the patches is pushed up to this Git repository [3], and you can see the commit range here [4]. 1: https://patchwork.cbaines.net/project/guix-patches/list/?series=482 2: https://laminar.cbaines.net/jobs/patchwork-test-series/826 3: https://git.cbaines.net

Re: Patchwork + automated checking and testing of patches

Hi Chris, Christopher Baines writes: > Chris Marusich writes: > >> [...] Why do you think using Jenkins wouldn't be maintainable? [...] > > Sure, I've used Jenkins in different contexts, and indeed currently use > Jenkins, so I've got some experience here. > > I'm obviously ignoring all the

Re: Patchwork + automated checking and testing of patches

Chris Marusich writes: > Hi Chris, > > This is really cool stuff! Thanks for looking into it. > > Christopher Baines writes: > >> I don't intend to do anything with Jenkins, as I think that wouldn't be >> maintainable, but I think setting up some system to check some of the >> following would

Re: Patchwork + automated checking and testing of patches

Hi Chris, This is really cool stuff! Thanks for looking into it. Christopher Baines writes: > I don't intend to do anything with Jenkins, as I think that wouldn't be > maintainable, but I think setting up some system to check some of the > following would be beneficial: I'm actually a little

Re: Patchwork + automated checking and testing of patches

Hi! Christopher Baines skribis: > This is still very much a prototype, but I think it's nearing the point > where it actually might be doing something useful. > > Currently, taking the service running the FreeDesktop fork of Patchwork, > you can go to the series page [10], and i

Re: Patchwork + automated checking and testing of patches

Christopher Baines writes: > I've now written a very rough package and service for Patchwork [4], and > managed to setup a instance here [5]. With the help of an email account > subscribed to both guix-patches and guix-commits, getmail and a couple > of scripts, it should also

Re: Patchwork + automated checking and testing of patches

Hi Christopher, Christopher Baines skribis: > So, I was trying to work out how to update a series of patches, and > asked on the Patchwork mailing list [1], and discovered there's actually > another codebase with different features [2]. This Patchwork-FDO fork > does have a pa

Re: Patchwork + automated checking and testing of patches

atches, that's definately working for some >> patches though. I don't fully understand what criteria it's using >> though, as it's comparing the commits that come through to the master >> branch, and I bet it's possible to confuse it a bit by tweaking patches >> before pushin

Re: Patchwork + automated checking and testing of patches

Gábor Boskovits writes: > I have noticed that issues.guix.info goes to 504 quite often, Ricardo said it > was because we only have one backend. So it might be a good idea to get > some infrastructure up there. WDYT? The software needs to be modified a little, e.g. to add fibers. I’ll try to

Re: Patchwork + automated checking and testing of patches

confuse it a bit by tweaking patches > > before pushing them. > > > > Regarding patch series, I don't know much about the specifics of this, > > and I don't know much about Patchwork, but just comparing a few patches > > on the older version [1], and the newer ve

Re: Patchwork + automated checking and testing of patches

it's using > though, as it's comparing the commits that come through to the master > branch, and I bet it's possible to confuse it a bit by tweaking patches > before pushing them. > > Regarding patch series, I don't know much about the specifics of this, > and I don't know mu

Re: Patchwork + automated checking and testing of patches

Ludovic Courtès writes: > Hello! > > Christopher Baines skribis: > >> ... >> >> I've now written a very rough package and service for Patchwork [4], and >> managed to setup a instance here [5]. With the help of an email account >> subscribed to b

Re: Patchwork + automated checking and testing of patches

Hello! Christopher Baines skribis: > I haven't used Patchwork [1], but it has been tried previously with Guix > [2][3]. It also seems to be a step forward in terms of taking what's > sent to the mailing list and organising it. > > 1: http://jk.ozlabs.org/projects/patchw

Re: Patchwork + automated checking and testing of patches

Tobias Geerinckx-Rice writes: > Christopher Baines wrote: >> I've now written a very rough package and service for Patchwork [4], >> and >> managed to setup a instance here [5]. With the help of an email >> account >> subscribed to both guix-patches and guix

Re: Patchwork + automated checking and testing of patches

Christopher, Christopher Baines wrote: I've now written a very rough package and service for Patchwork [4], and managed to setup a instance here [5]. With the help of an email account subscribed to both guix-patches and guix-commits, getmail and a couple of scripts, it should also collect new

Patchwork + automated checking and testing of patches

, you need some way of getting from the text sent to the mailing list to some state in a git repository. I haven't used Patchwork [1], but it has been tried previously with Guix [2][3]. It also seems to be a step forward in terms of taking what's sent to the mailing list and organising it. 1: http

Re: patchwork privileges

Hi, ng0 skribis: > Can privileges be raised or certain groups of people get the > privileges to edit patches which are not under their own email? Sorry, I have no idea. If you find something, please let me know! Ludo’.

patchwork privileges

at patchwork upstream with the name field situation. To me it looked like first- and lastname were required, however Guix does not have the requirement of a full name, just any name and some corresponding address which can be used for the commit log. If the name field is optional at patchwork

Re: Patchwork

I’ve submitted a patch to the mailing list (this time inline with “git >>> > send-mail”) and it appeared in the list. Is there any way for us to >>> > mark patches as committed via email (e.g. by commenting with something >>> > like “Pushed as cabba9e.”) or does patc

Re: Patchwork

git >> > send-mail”) and it appeared in the list. Is there any way for us to >> > mark patches as committed via email (e.g. by commenting with something >> > like “Pushed as cabba9e.”) or does patchwork figure this out >> > automatically? Or can only people with an acco

Re: Patchwork

r us to > > mark patches as committed via email (e.g. by commenting with something > > like “Pushed as cabba9e.”) or does patchwork figure this out > > automatically? Or can only people with an account change the status, > > and only on the web interface? > > That’s a good

Re: Patchwork

On 2016-05-09(10:38:38+0200), Ludovic Courtès wrote: > ng0 <n...@libertad.pw> skribis: > > > l...@gnu.org (Ludovic Courtès) writes: > > > >> Hello Guix! > >> > >> Thanks to Siddhesh Poyarekar of glibc & co., Guix patches can now be &g

Re: Patchwork

ng0 <n...@libertad.pw> skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Hello Guix! >> >> Thanks to Siddhesh Poyarekar of glibc & co., Guix patches can now be >> tracked on this Patchwork instance: >> >> http://patchwork.sourceware.org/

Re: Patchwork

l...@gnu.org (Ludovic Courtès) writes: > Hello Guix! > > Thanks to Siddhesh Poyarekar of glibc & co., Guix patches can now be > tracked on this Patchwork instance: > > http://patchwork.sourceware.org/project/guix/list/ Awesome, thanks! > Actions can be taken on the We

Re: Patchwork

“Pushed as cabba9e.”) or does patchwork figure this out > automatically? Or can only people with an account change the status, > and only on the web interface? That’s a good question! I *think* Patchwork can find out by itself by looking at the repository, but I don’t know exactly. We’ll see. :-) Ludo’.

Re: Patchwork

Ludovic Courtès <l...@gnu.org> writes: > Hello Guix! > > Thanks to Siddhesh Poyarekar of glibc & co., Guix patches can now be > tracked on this Patchwork instance: > > http://patchwork.sourceware.org/project/guix/list/ Thanks! > Actions can be taken on the W

Patchwork

Hello Guix! Thanks to Siddhesh Poyarekar of glibc & co., Guix patches can now be tracked on this Patchwork instance: http://patchwork.sourceware.org/project/guix/list/ Actions can be taken on the Web interface, provided you have an account there (I think anyone can create an acc