Re: [PATCH Cuirass 1/4] specification: Ensure name is a symbol.

Hi, On Mon, 17 Jun 2024 at 15:16, Ludovic Courtès wrote: > statically-typed language programmers would be > right to laugh at us here, I admit Nah because the new feature is really nice! :-) Thanks. But it remembers me one of our first in-person discussion back then on

Re: bug#69456: Cuirass 1.2.0-2.7bcd3d0 (and manual): latest install image not available for download (wrong URL?)

Hello, Giovanni Biscuolo skribis: > IMO there is a bug in the CI UI > > Tanguy LE CARROUR writes: > >> In order to test the latest installer, I went to the "latest download" >> page [1] and clicked on "x86_64-linux" under "GNU Guix System on Linux" >> and ended up on an error page [2]: >> >> ""

Re: [PATCH Cuirass v2] cuirass: Fix handling of SPECIFICATION-NAME.

Romain GARBAGE skribis: > Fixes a regression introduced in > 1da873b0e23eceb3c239dd6dc6781debf23bec63, where the NAME field of the > SPECIFICATION record type is forced to be a symbol as stated by the > documentation. > > * src/cuirass/base.scm (jobset-registry): Handle SPECI

[PATCH Cuirass v2] cuirass: Fix handling of SPECIFICATION-NAME.

Fixes a regression introduced in 1da873b0e23eceb3c239dd6dc6781debf23bec63, where the NAME field of the SPECIFICATION record type is forced to be a symbol as stated by the documentation. * src/cuirass/base.scm (jobset-registry): Handle SPECIFICATION-NAME as a symbol. * src/cuirass/http.scm (body

Re: [PATCH Cuirass] cuirass: Fix handling of SPECIFICATION-NAME.

On Mon Jun 17, 2024 at 3:42 PM CEST, Ludovic Courtès wrote: > Hi! Hi Ludo' ! > Romain GARBAGE skribis: > > [...] > > * src/cuirass/base.scm: Handle SPECIFICATION-NAME as a symbol. > > * src/cuirass/http.scm: Handle SPECIFICATION-NAME as a symbol. > > * src/

Re: [PATCH Cuirass] cuirass: Fix handling of SPECIFICATION-NAME.

Hi! Romain GARBAGE skribis: > Fixes a regression introduced in > 1da873b0e23eceb3c239dd6dc6781debf23bec63, where the NAME field of the > SPECIFICATION record type is forced to be a symbol as stated by the > documentation. Yay, that was fast! > * src/cuirass/base.scm: Handle SPE

Re: pico.css in Cuirass

Ludovic Courtès writes: >> The last thing I started working on was to use the HTML5 "progress" >> element instead of using custom div + bootstrap JS. With pico.css we >> can drop most classes and a lot of nested divs. Currently, though, it >> all looks very messy. > > Do I get it right that thi

Re: [PATCH Cuirass 1/4] specification: Ensure name is a symbol.

Hi, Ludovic Courtès skribis: > I’ve applied the whole series to Cuirass: > > 81d2530 * http: Add /admin/gitlab/event. > 10cf59f * gitlab: Add module for Gitlab JSON objects definition. > 1da873b * specification: Ensure name is a symbol. After doing some more testing,

Re: [PATCH] cuirass: check for null on specification edition page.

Hi, Jaming skribis: > From a5a99b1a7f930614bd88cadfe7a3470805403d48 Mon Sep 17 00:00:00 2001 > From: Justin Martin > Date: Sun, 9 Jun 2024 11:20:25 -0400 > Subject: [PATCH] cuirass: check for null on specification edition page. > > * src/static/js/cuirass.js: check '.r

[PATCH Cuirass] cuirass: Fix handling of SPECIFICATION-NAME.

Fixes a regression introduced in 1da873b0e23eceb3c239dd6dc6781debf23bec63, where the NAME field of the SPECIFICATION record type is forced to be a symbol as stated by the documentation. * src/cuirass/base.scm: Handle SPECIFICATION-NAME as a symbol. * src/cuirass/http.scm: Handle SPECIFICATION

[PATCH Cuirass 4/4] http: Add tests for Gitlab API.

/http.scm +++ b/tests/http.scm @@ -21,6 +21,7 @@ (use-modules (cuirass http) (cuirass database) + (cuirass gitlab) (cuirass specification) (cuirass utils) (tests common) @@ -41,6 +42,9 @@ (call-with-values (lambda () (http-get uri

[PATCH Cuirass 1/4] specification: Ensure name is a symbol.

* src/cuirass/specification.scm (ensure-symbol): New variable. (specification)[name]: Ensure name is a symbol. * tests/database.scm: Fix test. --- src/cuirass/specification.scm | 11 ++- tests/database.scm| 2 +- 2 files changed, 11 insertions(+), 2 deletions(-) diff --git a

[PATCH Cuirass 2/4] gitlab: Add module for Gitlab JSON objects definition.

* Makefile.am: Add src/cuirass/gitlab.scm. * src/cuirass/gitlab.scm: Add and record types. (gitlab-merge-request->specification): New variable. --- Makefile.am| 1 + src/cuirass/gitlab.scm | 95 ++ 2 files changed, 96 insertions(+) cre

[PATCH Cuirass 0/4] Add preliminary support for Gitlab webhooks

Gitlab JSON objects definition. http: Add /admin/gitlab/event. http: Add tests for Gitlab API. Makefile.am | 1 + src/cuirass/gitlab.scm| 95 +++ src/cuirass/http.scm | 88 src/cuirass

Re: [PATCH Cuirass 1/4] specification: Ensure name is a symbol.

Hi Romain, I’ve applied the whole series to Cuirass: 81d2530 * http: Add /admin/gitlab/event. 10cf59f * gitlab: Add module for Gitlab JSON objects definition. 1da873b * specification: Ensure name is a symbol. I took the liberty to merge the commit that adds test with the one that defines

[PATCH] cuirass: check for null on specification edition page.

>From a5a99b1a7f930614bd88cadfe7a3470805403d48 Mon Sep 17 00:00:00 2001 From: Justin Martin Date: Sun, 9 Jun 2024 11:20:25 -0400 Subject: [PATCH] cuirass: check for null on specification edition page. * src/static/js/cuirass.js: check '.remove-channel' for null. --- src/static/js/c

Re: [PATCH 0/1] Possible fix of the Cuirass build with the latest Guix

Hi, Rodion Goritskov skribis: > Got some problems due to the change re-exports in (guix utils). > Also, should I send patches for Cuirass here or to the guix-patches? Good catch! I see that Maxim fixed these issues just recently; it should be fine now. Thanks, Ludo’.

[PATCH 0/1] Possible fix of the Cuirass build with the latest Guix

Got some problems due to the change re-exports in (guix utils). Also, should I send patches for Cuirass here or to the guix-patches? Rodion Goritskov (1): remote-server: Fix guix modules selects src/cuirass/scripts/remote-server.scm | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions

Re: cuirass building and deployment

i will report more, for now you can see there are thousands of build errors tryign to bootstrap http://34.41.82.208:8080/eval/7?status=failed On Sun, Mar 24, 2024, 07:27 Ludovic Courtès wrote: > Hi, > > Jim Dupont skribis: > > > have been struggling to deploy cuirass on a

Re: cuirass building and deployment

Hi, Jim Dupont skribis: > have been struggling to deploy cuirass on a gcp cluster. > I was able to install it manually on one machine and use it from guix > talking to postgres and nginx running in ubuntu. the shepherd wont build or > install, needs more love. > I have gotten t

cuirass building and deployment

Hi team, have been struggling to deploy cuirass on a gcp cluster. I was able to install it manually on one machine and use it from guix talking to postgres and nginx running in ubuntu. the shepherd wont build or install, needs more love. I have gotten to finally build on guix and can export the

Re: Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html

On 2024-03-12 23:22, Mark H Weaver wrote: Simon Tournier writes: [...] AFAIK, Hydra is now down. IIRC, Mark was in charge. Mark? Yes, our instance of Hydra was retired many years ago. I agree that it makes sense to remove it from . Thanks

Re: Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html

I am Jing Luo, a new member from the GNU webmaster team. I noticed that >> gnu.org has a page on "GNU Development Resources" [1], which has a >> section about "Hydra: Continuous builds and portability testing". As I >> know, Guix now uses Cuirass for CI. The

Re: Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html

cuirass it would boil down to these questions: - what is cuirass? how does it work? - how can other GNU packages use ci.guix? (if they can) [...] -- Jing Luo About me: https://jing.rocks/about/ PGP Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC signature.asc Description: OpenPGP

Re: Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html

hat > gnu.org has a page on "GNU Development Resources" [1], which has a > section about "Hydra: Continuous builds and portability testing". As I > know, Guix now uses Cuirass for CI. The text [1] has not been updated > since 2012. Would anyone on this list be inter

Cuirass 1.2.0-2.7bcd3d0 (and manual): latest install image not available for download (wrong URL?)

Hello Tanguy, IMO there is a bug in the CI UI Tanguy LE CARROUR writes: > In order to test the latest installer, I went to the "latest download" > page [1] and clicked on "x86_64-linux" under "GNU Guix System on Linux" > and ended up on an error page [2]: > > """ > {"error":"Could not find the

Re: [Cuirass] JavaScript work

Janneke Nieuwenhuizen writes: > I'm wondering though what the net gain of minification is > with current bandwiths. On the few sites that I use javascript on I just > ship the preferred readable code. JavaScript libraries can weigh several megabytes unminified. With minification applied to t

Re: [Cuirass] JavaScript work

Hi, Ricardo Wurmus skribis: > I noticed that Cuirass bundles minified JavaScript. I’ve started a new > branch that replaces the minified JavaScript with readable source code > and minifies the files as part of the build. > > I also tried to remove the need for jQuery, at l

Re: [Cuirass] JavaScript work

Hi, Ricardo Wurmus writes: > Hi, > > I noticed that Cuirass bundles minified JavaScript. I’ve started a new > branch that replaces the minified JavaScript with readable source code > and minifies the files as part of the build. > > I also tried to remove the need for jQ

Re: [Cuirass] JavaScript work

Ricardo Wurmus writes: > I noticed that Cuirass bundles minified JavaScript. I’ve started a new > branch that replaces the minified JavaScript with readable source code > and minifies the files as part of the build. Yay for that. I'm wondering though what the net gain of minifi

[Cuirass] JavaScript work

Hi, I noticed that Cuirass bundles minified JavaScript. I’ve started a new branch that replaces the minified JavaScript with readable source code and minifies the files as part of the build. I also tried to remove the need for jQuery, at least in our own JavaScript code. (Datatables.js still

Introduce Cuirass and remove Hydra on https://www.gnu.org/software/devel.html

Hi Guix, I am Jing Luo, a new member from the GNU webmaster team. I noticed that gnu.org has a page on "GNU Development Resources" [1], which has a section about "Hydra: Continuous builds and portability testing". As I know, Guix now uses Cuirass for CI. The text [1]

[cuirass] Typo?

Hi, In (cuirass base) there is this definition: --8<---cut here---start->8--- (define (exception-reporter . results) "Return an exception handler that reports the exception on the error port and returns the values RESULTS." (lambda (key .

Re: Cuirass 1.2.0 released

On 10/30/23 10:42 AM, Ludovic Courtès wrote: Hello Guix! It’s a bit of a non-event since we’ve been packaging and using snapshots of Cuirass all along, but nevertheless, I’m totally thrilled to announce that Cuirass 1.2.0 is out! Congratulations! It might be my holiday project this year to

Cuirass 1.2.0 released

Hello Guix! It’s a bit of a non-event since we’ve been packaging and using snapshots of Cuirass all along, but nevertheless, I’m totally thrilled to announce that Cuirass 1.2.0 is out! https://guix.gnu.org/en/cuirass/ Changes since 1.1.0 (excerpt from the ‘NEWS’ file): ** Core

Re: [PATCH cuirass] doc: Fix remaining evaluation hook example.

Hello, vicvbcun writes: > This is a follow-up to commit 0b63c3b6989af77d4e1c9a98dd25c8f26b37d930. > > * doc/cuirass.texi (Triggering an Evaluation): Fix URL in example. Also applied! -- Thanks, Maxim

[PATCH cuirass] doc: Fix remaining evaluation hook example.

This is a follow-up to commit 0b63c3b6989af77d4e1c9a98dd25c8f26b37d930. * doc/cuirass.texi (Triggering an Evaluation): Fix URL in example. --- It seems that it has been copy-pasted in the meantime :). doc/cuirass.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/cuirass

Re: [PATCH cuirass] doc: Fix evaluation hook URL example.

Hi, vicvbcun writes: > * doc/cuirass.texi (Invocation): Fix URL in the example of the push hook. > --- > doc/cuirass.texi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/doc/cuirass.texi b/doc/cuirass.texi > index 69c58f7..00f00c1 100644 > --- a/doc/cuirass.texi > +++ b

[PATCH cuirass] doc: Fix evaluation hook URL example.

* doc/cuirass.texi (Invocation): Fix URL in the example of the push hook. --- doc/cuirass.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/cuirass.texi b/doc/cuirass.texi index 69c58f7..00f00c1 100644 --- a/doc/cuirass.texi +++ b/doc/cuirass.texi @@ -561,7 +561,7 @@ exa

Re: Cuirass upgrade on ci.guix

Hi Ludo, On Mon, 02 Oct 2023 at 23:46, Ludovic Courtès wrote: > A few hours ago I deployed current Cuirass on ci.guix and its build > machines. The expected benefits are: Really cool! Thank you! > As a bonus, we may finally get native GNU/Hurd builds again, via the > childhurd

Re: Cuirass upgrade on ci.guix

Hey, > 1. Better throughput. I fixed a bug that would lead “workers” to > eventually get ignored by ‘cuirass remote-server’, meaning they > would become idle until either the server or the worker is > restarted¹. Wow, that's a nice catch! > 2. Evaluat

Re: Cuirass upgrade on ci.guix

Ludovic Courtès writes: Hi Ludo! > A few hours ago I deployed current Cuirass on ci.guix and its build > machines. The expected benefits are: Thank you for this (often seemingly) unthankful work! > As a bonus, we may finally get native GNU/Hurd builds again, via the > childhurd

Cuirass upgrade on ci.guix

Hello Guix! A few hours ago I deployed current Cuirass on ci.guix and its build machines. The expected benefits are: 1. Better throughput. I fixed a bug that would lead “workers” to eventually get ignored by ‘cuirass remote-server’, meaning they would become idle until either the

Re: Cuirass actors

On Thu, Sep 14, 2023 at 11:31 AM Ludovic Courtès wrote: > > Hi! > > "Thompson, David" skribis: > > > I'm curious to hear more about your inter-process transport needs! > > I’d like to have actors running in separate processes on the same > machine. I wouldn’t want them to communicate over Tor or

Re: Cuirass actors

Simon Tournier skribis: > IIUC, the current two “builder” backend are: > > + local ’guix-daemon’: the queue of derivations is processed using one >strategy – the one implemented in C++, > > + ’cuirass remote-server’: the queue of derivations is processed using >

Re: Cuirass actors

Hi! "Thompson, David" skribis: > I'm curious to hear more about your inter-process transport needs! I’d like to have actors running in separate processes on the same machine. I wouldn’t want them to communicate over Tor or TCP+TLS; rather, I’d like them to use AF_UNIX sockets, “abstract socket

Re: Cuirass actors

Hey Ludo, On Wed, Sep 13, 2023 at 5:08 PM Ludovic Courtès wrote: > > With this actor split, one could implement another “builder” backend, > for instance one that talks to a Build Coordinator process. It’s also > obviously close to the programming model encouraged by Goblins, which > should make

Re: Cuirass actors

remote build delegates builds to > 'cuirass remote-server'. [...] > With this actor split, one could implement another “builder” backend, > for instance one that talks to a Build Coordinator process. IIUC, the current two “builder” backend are: + local ’guix-daemon’:

Cuirass actors

Hello Guix! My (useful? misguided? questionable?) quest around Cuirass has led me closer to some of the goals mentioned in my previous message¹ and in the ‘TODO’ file². The ‘wip-actors’ branch³, which I plan to merge soon, splits activities of the ‘cuirass register’ process among several actors

Re: News from Cuirass

Hello! Felix Lechner skribis: > On Sun, Jul 16, 2023 at 6:53 AM Ludovic Courtès wrote: >> >> Cuirass now uses a database >> connection pool > > That is super exciting! In another implementation the pooling code > comes with the database interface [1]

Re: News from Cuirass

Hi Ludovic, On Sun, Jul 16, 2023 at 6:53 AM Ludovic Courtès wrote: > > Cuirass now uses a database > connection pool That is super exciting! In another implementation the pooling code comes with the database interface [1] which makes it available more broadly. Could the poo

News from Cuirass

Hello Guix! A couple of months ago, I found myself working on hot fixes for Cuirass, whose repository had been gathering dust for months. One thing leads to another, and I’ve worked on a few improvements recently: • Guile-Squee (interface to PostgreSQL) now cooperates with Fibers, meaning

Cuirass package build timeouts and max-silent-time [was Re: Merging branch wip-haskell]

On Wed, Mar 08, 2023 at 08:31:33PM +0100, Lars-Dominik Braun wrote: > Hello Felix, > > > I see build failures [1] for Ghc 9.2.5 in the Cuirass job set [2] for > > my own feature branch. [3] They are caused by a one-hour timeout. Did > > you folks figure out how to ext

Re: rust-team cuirass build

Efraim Flashner writes: > The Rust Team has been hard at work updating the rust compiler and a > number of rust packages. We've tested a number of packages¹ to ensure > that everything looks okay. > > Quick stats for the branch: > 404 commits by 4 people. > 181 packages updated > 50 packages remo

Re: [PATCH] Cuirass: Complete IPv6 support

On Sat, Mar 4, 2023, at 03:12, Christopher Baines wrote: > Leo Famulari writes: > >> On Wed, Mar 01, 2023 at 12:34:08AM -0800, Ryan Sundberg wrote: >>> Hello Guix hackers, >>> >>> I have implemented IPv6 support for Cuirass in the attached patchset. &

Re: [PATCH] Cuirass: Complete IPv6 support

Leo Famulari writes: > On Wed, Mar 01, 2023 at 12:34:08AM -0800, Ryan Sundberg wrote: >> Hello Guix hackers, >> >> I have implemented IPv6 support for Cuirass in the attached patchset. >> This has been tested on a multi-node cluster running Cuirass over IPv6 >>

Re: [PATCH] Cuirass: Complete IPv6 support

On Wed, Mar 01, 2023 at 12:34:08AM -0800, Ryan Sundberg wrote: > Hello Guix hackers, > > I have implemented IPv6 support for Cuirass in the attached patchset. > This has been tested on a multi-node cluster running Cuirass over IPv6 > with some real builds. It should maintain

rust-team cuirass build

The Rust Team has been hard at work updating the rust compiler and a number of rust packages. We've tested a number of packages¹ to ensure that everything looks okay. Real world testing has occurred on x86_64 and has started on riscv64 but we'd like to request that a job be added to cui

[PATCH] Cuirass: Complete IPv6 support

Hello Guix hackers, I have implemented IPv6 support for Cuirass in the attached patchset. This has been tested on a multi-node cluster running Cuirass over IPv6 with some real builds. It should maintain full backwards compatibility with the default IPv4, only enabling IPv6 when given the

cuirass manual not found

on the cuirass web page, https://guix.gnu.org/cuirass/ the link to the cuirass manual, https://guix.gnu.org/cuirass/manual/, leads to a 404 not found error

Re: Questions about Cuirass

On 30-10-2022 13:50, James Hobson wrote: Sorry for not getting back to you. Looks promising! I wish I could release everything under a free license. Baby steps though! I’ve managed to release a few things under LGPL since I started! That’s 100% more than before! Sounds good. But anyway.

Re: Questions about Cuirass

having to rebuild the entire guix package set? We don’t have so many build >> machines, especially not for armv7. > > You can tell Cuirass to only build a selection of packages (and their > dependencies), by using a manifest, then not all of Guix is compiled but only > what's

Re: Questions about Cuirass

have so many build machines, especially not for armv7. You can tell Cuirass to only build a selection of packages (and their dependencies), by using a manifest, then not all of Guix is compiled but only what's necessary for your particular purpose. Also, your Cuirass instance still needs a

Questions about Cuirass

for armv7. Question 2 Does cuirass garbage collect? Or is that done through guix gc? We would need to host the binary packages for maybe 3 revisions at a time in this air gapped server. Question 3 Our software is sadly proprietary. Is there a way for guix build to selectively unpack and patch

Re: Cuirass and SQL

this one file and that’s >> it. > > Exactly! :-) > > If we use guile-dbi, it should be possible to support both sqlite and > postgresql. Popular projects like Nextcloud do allow the user to choose > their preferred database system. But, then again, Cuirass is built for > ver

Re: Cuirass and SQL

xactly! :-) If we use guile-dbi, it should be possible to support both sqlite and postgresql. Popular projects like Nextcloud do allow the user to choose their preferred database system. But, then again, Cuirass is built for very large scale. So, perhaps it is best to not try and also cover t

Re: Cuirass and SQL

Hi, Arun Isaac skribis: >> Initially, Cuirass was using SQLite but then switched [1] to >> PostgreSQL. The main reason is scalability. > > Ah, I see. I didn't know that. Years before, Hydra (https://nixos.org/hydra) also dropped its SQLite backend in favor of PostgreS

Re: Cuirass and SQL

On Fri, 27 May 2022, zimoun wrote: > Initially, Cuirass was using SQLite but then switched [1] to > PostgreSQL. The main reason is scalability. Make sens for the main CI used by Guix or for an organization. > I do not know if it is a technically doable to have two SQL backends and

Re: Cuirass and SQL

On Fri, 27 May 2022 11:06:24 +0200 zimoun wrote: Hi Guixers, Here is the video recording from today: https://archive.org/details/guix-forge-arun-isaac-may-28-2022 enjoy, jgart https://whereis.xn--q9jyb4c/

Re: Cuirass and SQL

> For simplicity in a single-system deployment I recommend running > postgres in "trust" mode and listen on a local unix socket rather than > exposing it to the network. This allows you to use the same access > control for Postgres that you'd use for an sqlite3 db file: file > permissions. This

Re: Cuirass and SQL

--- Original Message --- On Saturday, May 28th, 2022 at 8:45 AM, Arun Isaac wrote: > There's still the complexity of backing up a PostgreSQL > database How much easier is sqlite3? I host a Postgres server on DigitalOcean with automatic db backup. I've had to restore, it's easy and it

Re: Cuirass and SQL

Hi zimoun, > Initially, Cuirass was using SQLite but then switched [1] to > PostgreSQL. The main reason is scalability. Ah, I see. I didn't know that. > I do not know if it is a technically doable to have two SQL backends and > let the user pick the one they prefer. Fo

Re: Cuirass and SQL

For any cuirass-curious readers, I want to say I deployed it on Linode a week ago and its been one of the most "just works" out-of-the-box tools in the guix arsenal that I've encountered. It was really easy and painless to get going, and makes "pinning" milestone syste

Cuirass and SQL

Hi, On jeu., 26 mai 2022 at 00:24, Arun Isaac wrote: >> Quick question about guix-forge. Why laminar instead of cuirass as >> the CI? > > Two reasons: > > - Cuirass requires a PostgreSQL database, but I wanted guix-forge to be > as stateless as possible and defin

[BUG] Cuirass seems stuck in a loop.

Hello Guix! I've a strange behaviour using Cuirass. * Symptoms #+begin_example $ cat /var/log/cuirass.log … 2022-02-22T16:18:17 Fetching channels for spec

Re: cuirass schedules aarch64 jobs on x86_64?

Ricardo Wurmus writes: > We have a lot of aarch64 failures that I’m manually restarting and or > building on the honeycomb machines on my desk. > > Here’s one of them that fails in Cuirass: > > https://ci.guix.gnu.org/build/323991/details I reconfigured all of the buil

cuirass schedules aarch64 jobs on x86_64?

We have a lot of aarch64 failures that I’m manually restarting and or building on the honeycomb machines on my desk. Here’s one of them that fails in Cuirass: https://ci.guix.gnu.org/build/323991/details And here’s the associated log: --8<---cut here---st

Re: Could someone please restart this Cuirass build?

Em quinta-feira, 13 de janeiro de 2022, às 15:41:49 -03, Tobias Geerinckx- Rice escreveu: > Thiago Jung Bauermann 写道： > > > Therefore, could someone please restart this Cuirass build? > > Done. Thank you! -- Thanks, Thiago

Re: Could someone please restart this Cuirass build?

Thiago Jung Bauermann 写道： Therefore, could someone please restart this Cuirass build? Done. Kind regards, T G-R signature.asc Description: PGP signature

Could someone please restart this Cuirass build?

s to fail because of missing dependencies. Therefore, could someone please restart this Cuirass build? -- Thanks, Thiago

Re: branch master updated: services: cuirass: Add a no-publish argument.

Hey, > So I’d suggest turning that into ‘publish?’, defaulting to #t. Yeah, you're completely right, I reversed the logic with: cfd2442488971420289a12d5ca8f07816e1149bf. Thanks, Mathieu

Re: branch master updated: services: cuirass: Add a no-publish argument.

Hi! guix-comm...@gnu.org skribis: > commit d128c6fd33f46ec4e2d0ef352d20a858c377bf6f > Author: Mathieu Othacehe > AuthorDate: Thu Aug 12 12:58:34 2021 +0200 > > services: cuirass: Add a no-publish argument. > > * gnu/services/cuirass.scm (): Add a &g

Re: Cuirass job names and package variants

rsion, > > > and thus the same job name. Apparently Cuirass only takes the > > > first > > > job > > > with a given name into account and dismisses subsequent ones. > > > > > > What would be a good way to address this, either in Cuirass or in &g

Re: Cuirass job names and package variants

Leo Prikler skribis: > Am Freitag, den 25.06.2021, 13:44 +0200 schrieb Ludovic Courtès: [...] >> However, variants of a given package have the same package >> name/version, >> and thus the same job name. Apparently Cuirass only takes the first >> job >> w

Re: Cuirass job names and package variants

Am Freitag, den 25.06.2021, 13:44 +0200 schrieb Ludovic Courtès: > Hello! > > Cuirass support in (gnu ci) computes job names as a function of > package > names (the ‘job-name’ procedure). I wanted to build several package > variants using ‘--with-input’, which I expre

Cuirass job names and package variants

Hello! Cuirass support in (gnu ci) computes job names as a function of package names (the ‘job-name’ procedure). I wanted to build several package variants using ‘--with-input’, which I expressed in a manifest: https://gitlab.inria.fr/guix-hpc/guix-hpc/-/blob/master/manifest#L33-50 However

Re: Cuirass 1.1 released

Hi! Mathieu Othacehe skribis: > We are pleased to announce the release of Cuirass 1.1. > > This is the second official release of Cuirass, the GNU Guix continuous > integration software. For the last six months, this project has been > funded through the NGI0 PET Fund, a fund

Re: Cuirass 1.1 released

On Sun, Jun 13, 2021 at 12:59:55PM +0200, Mathieu Othacehe wrote: > We are pleased to announce the release of Cuirass 1.1. > > This is the second official release of Cuirass, the GNU Guix continuous > integration software. For the last six months, this project has been > funded t

Cuirass 1.1 released

We are pleased to announce the release of Cuirass 1.1. This is the second official release of Cuirass, the GNU Guix continuous integration software. For the last six months, this project has been funded through the NGI0 PET Fund, a fund established by NLNet[1]. Thanks to this support, Cuirass

Re: Cuirass badges

Hey Ludo, > This is not yet deployed in the current ‘cuirass’ package, right? Yes it is :) For instance, to get the badge of the guix-hpc specification at https://guix.bordeaux.inria.fr, you can use the following URL: https://guix.bordeaux.inria.fr/jobset/guix-hpc/badge.svg. There are s

Haskell update (was: Release 1.2.1: Cuirass failed to build Haskell 179 packages)

On Tue, Mar 23 2021, zimoun wrote: >> Maybe its time to update to a newer Stackage LTS release? :) > > Well, I do not know if it possible to do so before the next release. > IMHO, let focus on what remains for the next release and let upgrade the > Stackage LTS after. Any updates on this? I mana

Re: Cuirass badges

Hi! Mathieu Othacehe skribis: > Cuirass is now able to generate badges like any respectable CI > system. For instance: > > * https://ci.guix.gnu.org/jobset/master/badge generates a badge showing > the percentage of successful jobs for the master specification. Fanciness. :

Re: Cuirass badges

Hey Luis, > And the source file: > > https://luis-felipe.gitlab.io/media/2021/05/cuirass-badges-proposal-2021-05-28.svg > > I think I like d and d*. Wooh, that's great! I updated Cuirass to use the d badge proposal. Many thanks for your help, Mathieu

Re: Cuirass badges

On Fri, May 28, 2021 at 07:24:50PM +, Luis Felipe wrote: > Here's my initial proposal: > > https://luis-felipe.gitlab.io/media/2021/05/cuirass-badges-proposal-2021-05-28.png Wow! > And the source file: > > https://luis-felipe.gitlab.io/media/2021/05/cuirass-badges-

Re: Cuirass badges

On Friday, May 28, 2021 4:49 PM, Luis Felipe wrote: > On Friday, May 28, 2021 1:10 PM, Mathieu Othacehe othac...@gnu.org wrote: > > > Hello, > > Cuirass is now able to generate badges like any respectable CI > > system. For instance: > > > > - https:/

Re: Cuirass badges

On Friday, May 28, 2021 1:10 PM, Mathieu Othacehe wrote: > Hello, > > Cuirass is now able to generate badges like any respectable CI > system. For instance: > > - https://ci.guix.gnu.org/jobset/master/badge generates a badge showing > the percentage of successfu

Cuirass badges

Hello, Cuirass is now able to generate badges like any respectable CI system. For instance: * https://ci.guix.gnu.org/jobset/master/badge generates a badge showing the percentage of successful jobs for the master specification. * https://ci.guix.gnu.org/jobset/guix/badge generates a badge

Re: Cuirass accessibility

Hi Mathieu, Mathieu Othacehe skribis: > I have made the report public here[3]. Although I have already applied a > bunch of accessibility related fixes, there's still some work left. The > report if full of interesting teachings, and if some people want to join > me, they are more than welcome :

Re: Cuirass accessibility

On Thursday, May 13, 2021 7:07 PM, Mathieu Othacehe wrote: > Hello, > > As part of the Cuirass NLNet grant[1], the website at > https://ci.guix.gnu.org has been audited by the Accessibility > Foundation[2]. That's nice. > I have made the report public here[3]. Although

Cuirass accessibility

Hello, As part of the Cuirass NLNet grant[1], the website at https://ci.guix.gnu.org has been audited by the Accessibility Foundation[2]. I have made the report public here[3]. Although I have already applied a bunch of accessibility related fixes, there's still some work left. The repo

  1   2   3   4   5   >