data.qa.guix.gnu.org/QA Upgrade

Hey, Over the last month there's been work to move data.qa.guix.gnu.org from a Hetzner VM that I was renting to hydra-guix-130, a server hosted at the MDC. This new server has about 6x the amount of memory and many more cores. All of the moving is now finished, and I've also started to try and op

Re: Why does `system reconfigure` need to `pull`?

45mg <45mg.wri...@gmail.com> writes: > So I've just installed Guix System on my main machine, and right off the > bat, I want to thank everyone here for spending their time on this > amazing project. While there have been a few pain points (expect some > (minor) patches, hopefully!), the feeling o

Re: packages.guix.gnu.org down

"Ian Eure" writes: > Hi Guixers, > > Looks like https://packages.guix.gnu.org/ has been returning 504 errors for a > few weeks. > > Any idea when it'll be back? Looks like it's working currently. I noticed some issues with data.guix.gnu.org (which packages.guix.gnu.org uses) and cleaned things

Re: work-in-progress team branches

Maxim Cournoyer writes: > Hi, > > Christopher Baines writes: > > [...] > >>>> Hm. So is the intention that the moment a branch is created, it is >>>> expected to be in a good shape to be merged? >>> >>> [..] >>> >>

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Janneke Nieuwenhuizen writes: > Christopher Baines writes: > > [cc: Efraim] > >> Janneke Nieuwenhuizen writes: >> >>> Maxim Cournoyer writes: >>> >>>> Sorry for reviving a 14 weeks old thread, I'm still catching up >

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Janneke Nieuwenhuizen writes: > Maxim Cournoyer writes: > >> Sorry for reviving a 14 weeks old thread, I'm still catching up >> post-move :-). > > Ah that explains why I missed this... > >> Christopher Baines writes: >> >> [...] >> >

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Maxim Cournoyer writes: > Hi Chris, > > Sorry for reviving a 14 weeks old thread, I'm still catching up > post-move :-). No worries, I hope move things are going well. > Christopher Baines writes: > > [...] > >>> The manual currently says it goes to &#

Re: Guix Data Service: Dump files missing (?)

Luis Felipe writes: > I'd like to get familiar with the Guix Data Service locally, but I > haven't been able to set up the database because there's no dump files > available in the URLs indicated in the README. > > For example, https://data.guix.gnu.org/dumps loads correctly but lists > no dumps.

Re: Upgrading Guix packages website in Guix infrastructure

Luis Felipe writes: > On 4/11/24 22:12, Ludovic Courtès wrote: >> Hello, >> >> Luis Felipe skribis: >> >>> Hi guix, >>> >>> The software behind https://packages.guix.gnu.org/, Guix Packages >>> Website,¹ has been updated with the following changes: >> Yay! >> >> Could you send a patch against th

Persistent heap usage when computing derivations

Hey, I've been putting some more time and money in to trying to get the QA data service (data.qa.guix.gnu.org) to perform better recently, but unfortunately I haven't been having much success. I've been trying to parallelise more and while I think this should speed things up, butI'm having to red

Re: Default postgresql version

Christopher Baines writes: > Andreas Enge writes: > >> Am Tue, Oct 29, 2024 at 12:42:32PM +0100 schrieb Andreas Enge: >>> I have restarted nginx and nar-herder (just an educated guess), but >>> to no avail. >> >> I think the problem is further

Re: Default postgresql version

Andreas Enge writes: > Am Tue, Oct 29, 2024 at 12:42:32PM +0100 schrieb Andreas Enge: >> I have restarted nginx and nar-herder (just an educated guess), but >> to no avail. > > I think the problem is further upstream, in the place where the nars are > actually stored (hatysa). When I download a f

Re: Status of python-team branch

Sharlatan Hellseher writes: > Hi, > > I may volunteer myself to that > - rebase on current master > - resolve conflicts > - apply pending patches from issues > - push for testing > - merge to master > > Is anyone interested in rebasing the branch? Are you still looking at rebasing python-team?

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Vagrant Cascadian writes: > On 2024-09-06, Ludovic Courtès wrote: >> Simon Tournier skribis: >> >>> In this picture of “merge train”, the CI workload and world rebuilds >>> will increase, no? >>> >>> Consider the two teams: science and this new core-packages. Then >>> science takes care of open

zh-CN or zh-cn for the Guix manual URL?

Hey, It seems like the simple change I made to remove the endless possibilities for manual URLs [1] has had some unintended consequences. 1: https://git.savannah.gnu.org/cgit/guix/maintenance.git/commit/?id=3de9f2119371038650045946ba6e7de6e90f68e5 Some have been fixed, but the links from the we

Re: core-update scope

Andy Tai writes: > Hi, shall changes to non-core packages like ffmpeg still be in the > scope of core-updates? > > ffmpeg, for example, is no where near the core of the GNU system like > glibc, but still it is widely dependent upon. But it would make no > sense to have a ffmpeg-team because it

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Christopher Baines writes: >> The manual currently says it goes to 'staging' [1], and that this will >> be merged within six weeks. Is this actually true? I don't see any >> sign of it on Guix' git [2], and an unsure if the manual is out of >>

Re: ‘core-updates’ is gone; long live ‘core-packages-team’!

Is this actually true? I don't see any > sign of it on Guix' git [2], and an unsure if the manual is out of > sync with the branches workflow. > > While 'staging' seems like it could have similar difficulties to > core-updates if it gets out of hand. The alternati

Re: Request for assistance maintaining LibreWolf

Ian Eure writes: >> We've had for many months a feature in QA [1] where people can mark >> patches as being reviewed and looking like they're ready to be >> merged, >> which is personally what I hope will mitigate this feeling of "I >> cannot >> help you since I don't have commit access", because

Re: Request for assistance maintaining LibreWolf

Sergio Pastor Pérez writes: > I cannot help you since I don't have commit access. But I want to thank > you for your hard work, I'm currently using your package. > > I can only echo your frustration since I also have some patches ready to > be merged that seem to be forgotten. As it has been disc

Re: Static hosting of substitutes

Ian Eure writes: > I’d like to provide substitutes for packages in my personal channel. > The ideal setup for this would be for a machine on my internal net to > perform the builds, then upload the results to another system on the > open internet. That could be a machine running a web server poi

Re: qa.guix delays in processing patches

Philip McGrath writes: > Hi Chris, > > On 6/19/24 09:50, Christopher Baines wrote: >> Ludovic Courtès writes: >>> >>> It’s unclear to me why issues are sometimes seemingly not picked up. >>> Chris, do you have more insight into this? >> QA just

Re: Our mips64el support is really really dead

Efraim Flashner writes: > Three initial bits about Guix's support for mips64el: > 1. We stopped producing a standalone installer for mips64el before the > 1.0 release, which means it's been years since anyone has been able to > install it without help. Actually, 0.12 was the last version¹, back i

Re: ‘core-updates’ rebased: testing needed!

Ludovic Courtès writes: > 宋文武 skribis: > >> Hello, there are 399 build failed which only on core-updates if I count >> it correctly (1 at the end of each line come from ci status, I think 2 >> are for dependencies failed), the 4xx are build number, which can be >> used as "https://ci.guix.gn

Starting a Quality Assurance Meeting/Team/Sociocracy circle

Hey! Following on from the governance discussion at the Guix Days earlier this year, I'm not sure what progress has been made. I'd still like to get the QA stuff in to a more sustainable state, whether that means shutting things down or moving the services to be run by the project/Guix Foundation

Re: Cleaning up branches on savannah

Christopher Baines writes: > The following branches all seem to have commits that haven't made it to > master yet, although I haven't checked if the changes were applied but > just with different commit ids. > > - gnuzilla-updates > - go-team > - haskell-team

Re: Cleaning up branches on savannah

Mark H Weaver writes: > Hi Christopher, > > Christopher Baines writes: > >> I think the easy process change is to delete the gnuzilla-updates branch >> once you've pushed the chagnes to master. That should make it clearer >> that there's effectively n

Re: qa.guix delays in processing patches

Ludovic Courtès writes: > Hi Philip, > > "Philip McGrath" skribis: > >> For some reason QA still doesn't seem to be working for >> https://issues.guix.gnu.org/71203 (a Racket update I sent on May >> 26), which I suspect may be related to this. Could someone take a >> look? >> >> The page at http

Re: issues.guix.gnu.org certificate expired

Andy Tai writes: > trying to connect to is using Firefox, Firefox says: > > > Did Not Connect: Potential Security Issue > > Firefox detected an issue and did not continue to issues.guix.gnu.org. > The website is either misconfigured or your computer clock is set to > the wrong time. > > It’s

Re: 07/13: gnu: go-gopkg-in-cheggaaa-pb-v1: Rename to go-github-com-cheggaaa-pb.

Sharlatan Hellseher writes: > Hi Christopher, > > I've pushed changes fixing it > . Awesome, thanks! Chris signature.asc Description: PGP signature

Re: 07/13: gnu: go-gopkg-in-cheggaaa-pb-v1: Rename to go-github-com-cheggaaa-pb.

guix-comm...@gnu.org writes: > sharlatan pushed a commit to branch master > in repository guix. > > commit 2ef0e4bce1f5b4c3b59cfa944e971a3f31afd2d2 > Author: Artyom V. Poptsov > AuthorDate: Sat Jun 8 14:44:06 2024 +0300 > > gnu: go-gopkg-in-cheggaaa-pb-v1: Rename to go-github-com-cheggaaa-pb.

Re: package submission, unit test failures on Guix QA... policies?

Andy Tai writes: > Hi, I have a patch submission that builds fine (in the GNU Guix sense, > that is, unit tests run and pass) locally but fails on Guix QA due to > unit tests failing. > > I suspect that the failures are due to the build machine (or machines) > as plain x86-64 PC (fine as build se

Re: branch core-updates updated (c8c6883398 -> 0e06c9697a)

Efraim Flashner writes: > On Sun, Jun 09, 2024 at 10:46:10AM +0100, Christopher Baines wrote: >> guix-comm...@gnu.org writes: >> >> > efraim pushed a change to branch core-updates >> > in repository guix. >> > >> > from c8c6883398

Re: branch core-updates updated (c8c6883398 -> 0e06c9697a)

guix-comm...@gnu.org writes: > efraim pushed a change to branch core-updates > in repository guix. > > from c8c6883398 gnu: dico: Add libxcrypt dependency. > new 9804f8c149 gnu: coeurl: Update to 0.3.1. > new 51c7b6d76f gnu: font-gnu-freefont: Build with newer fontforge. > new 0

Re: Cleaning up branches on savannah

Mark H Weaver writes: > Christopher Baines writes: > >> There are quite a few branches on savannah, and it would be nice to >> remove them if they're unnecessary, at least because that will prompt >> the QA data service to delete the data, saving on disk space. >

Cleaning up branches on savannah

Hey, There are quite a few branches on savannah, and it would be nice to remove them if they're unnecessary, at least because that will prompt the QA data service to delete the data, saving on disk space. I'm ignoring all the version-* and wip-* branches, which leaves the following sets of branch

Changes to managing branches

Hey! I've now merged the most recent batch [1] of changes to the process for managing patches and branches. There was a previous thread on guix-devel discussing the changes here [2]. 1: https://issues.guix.gnu.org/70549 2: https://lists.gnu.org/archive/html/guix-devel/2024-04/msg00247.html The m

How to test fixed output derivations in the bordeaux build farm?

Hey! I'd like to do more testing of fixed output derivations, both in general and for patches/branches via QA. In particular, it would be useful to test specific operations in the derivation, e.g. downloading just from upstream. Being able to control this is also necessary to prevent the bordeaux

Re: Scheduling a new release?

Christina O'Donnell writes: > On 08/05/2024 14:01, Christopher Baines wrote: >> I think it would be nice to have a new release, and indeed release more >> often, I think the way to get there is for less things to be broken >> between releases, such that releasing tak

Re: branch master updated (2bea3f2562 -> 6745d692d4)

Ricardo Wurmus writes: >> These changes from r-updates have effectively jumped the queue past >> those on the core-updates and gnome-team branches, and since there was >> never a "Request for merging" issue opened [1], the bordeaux build farm >> is going to be delayed in building gnome-team as it

Re: branch master updated (2bea3f2562 -> 6745d692d4)

guix-comm...@gnu.org writes: > rekado pushed a change to branch master > in repository guix. > > from 2bea3f2562 gnu: kubo: Unbundle go-cidutil, go-log and go-ipfs-util. > new 79c2b32337 gnu: r-with-tests: Update to 4.4.0. ... > new 5ad635ec49 gnu: r-job: Update to 0.3.1. > ne

Re: Scheduling a new release?

Simon Tournier writes: > Here or there, we have bugs as: > > https://issues.guix.gnu.org/70659 > https://issues.guix.gnu.org/70726 > > And our answer looks like: > > > Additionally, I strongly advise upgrading guix-daemon, as noted in > the > > bug report above. > > Well,

Re: Hackathon: fix build errors on the "master" branch.

Efraim Flashner writes: > On Mon, Apr 29, 2024 at 04:52:29PM +0200, Ricardo Wurmus wrote: >> Hi Guix, >> >> for the past weeks the "master" branch has been in pretty poor state >> according to ci.guix.gnu.org. It keeps hovering at around 56% progress, >> which is a far cry from the 80+% we used

Re: Managing patches and branches, retrospective and futher changes?

Andreas Enge writes: > Hello, > > Am Wed, Apr 24, 2024 at 02:21:56PM +0100 schrieb Christopher Baines: >> Let me know if you have any thoughts or questions! > > in this part: > +@item > +Minimise the changes on master that are missing on the branch prior to > +m

Re: Managing patches and branches, retrospective and futher changes?

Steve George writes: > I think we should strongly recommend against long-running unmerged branches. > > Perhaps there could be a recommendation to merge every 3 months. My hope is that with these process changes, we won't end up with long-running branches. Maybe we could add a recommendation, b

Managing patches and branches, retrospective and futher changes?

Hey! Almost a year ago, the branching strategy was changed [1][2]. 1: https://issues.guix.gnu.org/63459 2: https://lists.gnu.org/archive/html/guix-devel/2023-06/msg00024.html I think these changes have gone OK, we've had ~27 [3] branches merged in this manor and I think looking back these change

Re: Status of ‘core-updates’

Ludovic Courtès writes: > What’s the status of ‘core-updates’? What are the areas where help is > needed? > > I know a lot has happened since the last update¹, which is roughly when > I dropped the ball due to other commitments, but I’m not sure where we > are now. I haven't really been followi

Re: Error handling when 'guix substitute' dies

Ludovic Courtès writes: > Hi, > > Philip McGrath skribis: > >> I don't know if the root cause is related, but this reminded me of >> some networking errors I sometimes get accessing substitutes. I had >> the luck (good or bad?) to get an example while building >>

Re: Emacs and Gnome branches are merged now

Liliana Marie Prikler writes: > I've now pushed the merge commits for both emacs-team and gnome-team. Thank you to everyone involved in getting these changes through :D > If you have a weak machine, PLEASE DO NOT PULL IMMEDIATELY AND WAIT FOR > CI TO CATCH UP! Despite efforts to prebuild thin

Re: March update on bordeaux.guix.gnu.org

Ludovic Courtès writes: > Hi! > > Christopher Baines skribis: > >> Related to this, I've added options to the nar-herder to help change the >> TTL being used, and reduced the TTL for bordeaux.guix.gnu.org to 10 >> minutes (from 180 days) [4]. This will at le

March update on bordeaux.guix.gnu.org

Hey! I'm think the last update I sent out was back in April 2023 [1], but it's coming up to 3 years since bordeaux was added as a default substitute server [2]. It's scary how much time has passed! 1: https://lists.gnu.org/archive/html/guix-devel/2023-04/msg00319.html 2: https://guix.gnu.org/en/

Re: qa.guix.gnu.org: Returns a plain Guile error for a merged issue

"Artyom V. Poptsov" writes: > Hello, > > I just found out that Guix QA returns a plain Guile error message when I > try to open an issue that was merged: > https://qa.guix.gnu.org/issue/69654 > > The error looks like this: > > An error occurred > > Sorry about that! > wrong-type-arg > > #fWron

Re: Concerns/questions around Software Heritage Archive

MSavoritias writes: > On 3/16/24 19:50, Christopher Baines wrote: >> Ian Eure writes: >> >>> Hi Guixy people, >>> >>> I’d never heard of SWH before I started hacking on Guix last fall, and >>> it struck me as rather a good idea. However, I’

Re: Concerns/questions around Software Heritage Archive

Ian Eure writes: > Hi Guixy people, > > I’d never heard of SWH before I started hacking on Guix last fall, and > it struck me as rather a good idea. However, I’ve seen some things > lately which have soured me on them. > > They appear to be using the archive to build LLMs: > https://www.softwar

Re: February update on the Guile guix-daemon

Ludovic Courtès writes: > Christopher Baines skribis: > >> - Then there's the big areas to work on next: >> >>- I think I'm going to need to use thread pools for SQLite operations >> in the daemon, as the build coordinator does. > > I th

February update on the Guile guix-daemon

Hey! Here's an overdue update on rewriting the Guix daemon in Guile, following on from the earlier thread on guix-devel [1] and the blog post [2]. 1: https://lists.gnu.org/archive/html/guix-devel/2023-09/msg00328.html 2: https://guix.gnu.org/en/blog/2023/a-build-daemon-in-guile/ Unfortunately I

Re: Guix Days: Patch flow discussion

Clément Lassieur writes: > On Fri, Feb 16 2024, Andreas Enge wrote: > >> Am Fri, Feb 16, 2024 at 11:56:50AM +0100 schrieb Clément Lassieur: >>> Would it makes sense to have a "does-not-apply" tag too? >> >> Should this not appear in the QA page, assuming that once all the new >> issues are close

Re: QA is back, who wants to review patches?

Vivien Kraus writes: > Hello Chris, > > Le vendredi 09 février 2024 à 10:44 +, Christopher Baines a écrit : >> Let me know if you have any comments or questions! > > Thank you for all your work on QA. > > I can’t help but notice QA is missing

Re: QA is back, who wants to review patches?

Vivien Kraus writes: > Dear QA wizards, > > Le vendredi 09 février 2024 à 10:44 +, Christopher Baines a écrit : >> You just need to not be involved (so you can't review your >> own patches) > > I interpret this as it’s OK to review patches if you asked fo

Re: QA is back, who wants to review patches?

Andreas Enge writes: > I see a few "Failed to process revision", for instance here: >https://qa.guix.gnu.org/issue/68778 > While I am not sure why, these look like transient (?) build failures, > at least failures not related to the patch in question. What is there to do? Long term it would

Re: QA is back, who wants to review patches?

Tanguy LE CARROUR writes: > Hi Chris, > > First of, thanks (again) for everything that you’ve done with QA! > It looks great! > > > Quoting Christopher Baines (2024-02-09 11:44:11) >> Let me know if you have any comments or questions! > > Unfortunately, I ha

QA is back, who wants to review patches?

Hey! After substitute availability taking a bit of a dive recently, the bordeaux build farm has finally caught back up and QA is back submitting builds for packages changed by patches. QA also has a feature to allow easily tagging patches (issues) as having been reviewed and ready to merge (revie

Re: Collecting Guix talks at FOSDEM

Steve George writes: > Hi, > > Did anyone take a photo of the discussion whiteboard? > > And/or anyone get a photo of the room generally that could be used in > the blog post? Be nice to have a visual ... I took a picture of the infrastructure discussion whiteboard: https://www.cbaines.net/gui

Re: Meeting in Brussels on Wednesday night?

Ludovic Courtès writes: > To those traveling to Brussels tomorrow: who’s in to meet in our lair, > namely Au Bon Vieux Temps, on Wednesday evening/night? :-) > > > https://www.openstreetmap.org/?mlat=50.84832&mlon=4.35237#map=20/50.84832/4.35237&layers=Y > > I should be able to be there arou

Re: [Guix-europe-sac] Shutting down qa.guix?

Andreas Enge writes: > Am Sat, Dec 09, 2023 at 11:54:59AM +0100 schrieb Ludovic Courtès: >> I think this underlines a collective failure to get our act together. > > indeed, and besides what Simon mentioned about the bank situation I think > there was a certain lack of consistency between decidi

December/January update on QA and related things

Hey, I sent out the last update [1] back near the start of December. 1: https://lists.gnu.org/archive/html/guix-devel/2023-12/msg00021.html In summary, QA has been not really working since mid December as data.qa.guix.gnu.org wasn't keeping up with processing revisions for patches and branches.

Re: Performance of computing cross derivations

Ludovic Courtès writes: > Christopher Baines skribis: > >> I think you're right, while I send some other changes in #68266, I think >> it's this change around make-rust-sysroot that has pretty much all the >> effects on performance. >> >> I thin

Re: Performance of computing cross derivations

Efraim Flashner writes: > [[PGP Signed Part:Signature made by expired key 41AAE7DCCA3D8351 Efraim > Flashner ]] > On Fri, Jan 05, 2024 at 04:41:14PM +, Christopher Baines wrote: >> >> Ludovic Courtès writes: >> >> > Hi, >> > >> > Chr

Re: Performance of computing cross derivations

Ludovic Courtès writes: > Hi, > > Christopher Baines skribis: > >> When asked by the data service, it seems to take Guix around 3 minutes >> to compute cross derivations for all packages (to a single >> target). Here's a simple script that replicates t

Re: Shutting down qa.guix?

Maxim Cournoyer writes: > Hi, > > Christopher Baines writes: > >> Tobias Geerinckx-Rice writes: >> >>> Christopher Baines 写道： >>>> it's not the most cost effective setup >>> >>> Has this been explained in more detail before

Re: Shutting down qa.guix?

Tobias Geerinckx-Rice writes: > Christopher Baines 写道： >> it's not the most cost effective setup > > Has this been explained in more detail before? Probably not, beid is currently a CPX51 Hetzner cloud server costing €65.33 a month. This has been useful as it's enab

Re: Shutting down qa.guix?

Ludovic Courtès writes: > Hello, > > Christopher Baines skribis: > >> I am still planning to shutdown data.qa.guix.gnu.org and >> QA which depends on it within the next couple of weeks. I do hope it can >> return some point though, and hopefully sooner rather

Re: Discontinuing data.guix.gnu.org?

Ludovic Courtès writes: > Hello! > > Christopher Baines skribis: > >> As previously set out, I'm planning to stop hosting the data service >> instances this year. While I would like to stop hosting the server for >> data.guix.gnu.org, > > I forgot th

November/December update on qa.guix.gnu.org and related things

Hey! Not much has changed since the last update. There's a new "waiting for builds" status, I tweaked some code around build cancelation, I put in place a mitigation for #67194 affecting the build coordinator, and did some investigation of the hurd locale issue (#67507). As previously set out, I'

RISC-V builds and substitutes

Hey, I have a RISC-V board that is hooked up to the bordeaux build farm, and there is another board connected, although there's some issues with the connection/agent. 1 to 2 boards though isn't enough to get good substitute availability and build packages for patches and branches though. There's

Re: Failed to build in QA

Reza Housseini writes: > Hi Christopher > > I submitted a new revision to the issue, but the QA link shows > > Issue not found > This could mean the issue does not exist, it has no patches or has > been closed. > > do you know what the problem is here? There's two issues, one is the machine run

Re: mesa-updates: call for patches

John Kehayias writes: > Hi everyone, > > Update below: > > On Sun, Nov 05, 2023 at 11:47 PM, John Kehayias wrote: > [snippy snip snip] >>> >>> Happy to! Substitutes will eventually become available, but there's >>> quite a few builds to be done. This takes care of some ungrafts and >>> updates w

Re: Patch Review Flow

"jgart" writes: > Does anyone follow this workflow for reviewing patches? > > git clone https://git.guix-patches.cbaines.net/guix-patches/ > git checkout issue-x > git format-patch ... > # then in the development checkout of Guix: > git am ...; make; ./pre-inst-env guix build > > Should we d

Re: Reproducible Builds 2023 in Hamburg

Christopher Baines writes: > Hey! > > This event is now finished! Efraim and Julien and I had a discussion > about Guix things relating to Reproducible Builds and there are some > notes available here [1]. > > 1: https://reproducible-builds.org/events/hamburg2023/guix-todo/

Reproducible Builds 2023 in Hamburg

Hey! This event is now finished! Efraim and Julien and I had a discussion about Guix things relating to Reproducible Builds and there are some notes available here [1]. 1: https://reproducible-builds.org/events/hamburg2023/guix-todo/ Maybe the others can mention what things they've been looking

Re: August/November update on qa.guix.gnu.org and related things

Suhail writes: > "Christopher Baines" writes: > >> There isn't much documentation for QA > > Understood. > > Is the preferred place to ask questions regd the QA service this mailing > list? Yep. >> I think it's fair to say that these shou

Re: August/November update on qa.guix.gnu.org and related things

Suhail writes: > Christopher Baines writes: > >> - The README is published at https://qa.guix.gnu.org/README > > The README seems more focused on task planning and TODO items than > explaining how to use the qa.guix.gnu.org website. Could you please > provide a

August/November update on qa.guix.gnu.org and related things

Hey, The last update I sent out was back in July [1]. 1: https://lists.gnu.org/archive/html/guix-devel/2023-07/msg00144.html There have been quite a few changes over the last few months, here's a summary of the changes: - QA now stores when it's submitted builds for a issue/branch and cance

Performance of computing cross derivations

Hey! When asked by the data service, it seems to take Guix around 3 minutes to compute cross derivations for all packages (to a single target). Here's a simple script that replicates this: (use-modules (srfi srfi-34) (gnu packages) (guix grafts) (gui

Re: branch master updated: gnu: Add passff.

guix-comm...@gnu.org writes: > This is an automated email from the git hooks/post-receive script. > > snape pushed a commit to branch master > in repository guix. > > The following commit(s) were added to refs/heads/master by this push: > new 6c894b7a1a gnu: Add passff. > 6c894b7a1a is descr

Re: [PATCH qa-frontpage] Apply incoming patches onto the correct feature branch

Christopher Baines writes: > Vivien Kraus writes: > >> It seems that the only available information of the feature branch is >> in the patch name. >> --- >> >> Hello guix! >> >> Thank you for making the QA tool. It seems to me that feature branc

Re: How to send revision patches to old issues in DEBBUGS so Guix QA can look at them?

Andy Tai writes: > Hi, per Chris's recent comments, Guix QA only looks at (a window of) > recently created issues due to storage space limitations, which is > understandable. > > However, if I have update (package definition) patches to not very > recent issues, such as some stale issues sitting

Re: [PATCH] web: Include merged_with in graphql .

Arun Isaac writes: >> Sorry, I missed this patch. I will apply it tonight. > > Done! > > https://git.savannah.gnu.org/cgit/guix/mumi.git/commit/?id=a89c5109963de0b5fd1f500ed2e2ede47728fdb4 > https://git.savannah.gnu.org/cgit/guix/mumi.git/commit/?id=025fc600f1cb4c73042bf920aee3e07d5fb9c53a > > I

Re: Guix Data Service can now poll for new revisions/branches

Maxim Cournoyer writes: > Hi Christopher, > > Christopher Baines writes: > >> Hey, >> >> As has happened before in the past, at the moment we're not getting >> emails to guix-commits for the main guix.git repository. This impacts >> the data ser

Re: [PATCH] web: Include merged_with in graphql .

Simon Tournier writes: > Hi, > > Out of my curiosity, is this patch > > On Tue, 26 Sep 2023 at 09:59, Christopher Baines wrote: >> * mumi/web/graphql.scm (): Include merged_with. >> --- >> mumi/web/graphql.scm | 12 +++- >> 1 file changed, 11 ins

Re: Failed to build in QA

Reza Housseini writes: >> This is probably down to a top level circular dependency. In particular, >> trying to paraview to compute the version to form part of the >> native-search-path at the top level causes problems. > > I'm wondering why it builds fine locally but causes problems in QA > hav

Re: Guix QA "Unable to apply patches"

Andy Tai writes: > Hi, for one of my package patches, Guix QA shows > > "Unable to apply patches" > > in https://qa.guix.gnu.org/issue/63095 > > even though I double checked the patch applies cleanly on the current > head of the master branch. > > Guix QA shows no hint as what the failure is (no

Guix Data Service can now poll for new revisions/branches

Hey, As has happened before in the past, at the moment we're not getting emails to guix-commits for the main guix.git repository. This impacts the data service instances as they use these emails to know when there are new revisions to process. I've now added the ability to configure the data serv

Re: Failed to build in QA

"reza.housse...@gmail.com" writes: > On October 5, 2023 10:49:06 AM GMT+02:00, Christopher Baines > wrote: >> >>"reza.housse...@gmail.com" writes: >> >>> I submitted an issue to guix. But QA refuses to build it [1]. I have >>> no

Re: Failed to build in QA

"reza.housse...@gmail.com" writes: > I submitted an issue to guix. But QA refuses to build it [1]. I have > no clue what the problem is, can anyone shed light on a possible > resolution? You pretty much found the problem, the relevant line on the page you linked to is: [ 6/ 50] loading...

Re: Guix related things in Germany at the end of October/start of November

Efraim Flashner writes: > [[PGP Signed Part:Signature made by expired key 41AAE7DCCA3D8351 Efraim > Flashner ]] > On Thu, Sep 28, 2023 at 11:58:10PM +0200, Ricardo Wurmus wrote: >> >> Christopher Baines writes: >> >> > PackagingCon [1] is happening

Re: [workflow] Automatically close bug report when a patch is committed

Giovanni Biscuolo writes: > [[PGP Signed Part:Signature made by expired key D37D0EA7CECC3912 Giovanni > Biscuolo (Xelera) ]] > Hi, > > Giovanni Biscuolo writes: > > [...] > The first thing we need is a server side git post-receive hook on Savannah, I've opened the sr#110928 support r

Re: Process for reviewing patches as someone without commit access

Christopher Baines writes: > I've been reviewing the list of ideas on and around QA ([1]) recently, > and got thinking again about how to support people without commit access > reviewing patches. Obviously you don't need commit access to review > patches, but where I thin

[PATCH] web: Include merged_with in graphql .

* mumi/web/graphql.scm (): Include merged_with. --- mumi/web/graphql.scm | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/mumi/web/graphql.scm b/mumi/web/graphql.scm index 6dcb8ce..2c7c676 100644 --- a/mumi/web/graphql.scm +++ b/mumi/web/graphql.scm @@ -69,7 +69,17

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

Vivien Kraus writes: > Hi! > > Here is a small library that exports 3 types: > − is the collection of metadata that is present > in the square brackets in the patch names; > − is an individual item of the patch series; > − is a whole series of patches; > > And a set of functions to parse an

  1   2   3   4   5   6   7   8   9   >