From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id GPoWGJpnPGboOQAAe85BDQ:P1 (envelope-from ) for ; Thu, 09 May 2024 08:05:14 +0200 Received: from aspmx1.migadu.com ([2001:41d0:303:e16b::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id GPoWGJpnPGboOQAAe85BDQ (envelope-from ) for ; Thu, 09 May 2024 08:05:14 +0200 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b="Hu2hVX/h"; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1715234714; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=e4JLomms2RpFuT43osTtdXJXXN9Zmo5vJrEt0QVjBNM=; b=ksDsoa+UnGAGcopGKQaFqDwQ4CzjZaxgrlhGHK/MCi4eMJb9qSjXlcoAA9ZiOInahu8OF+ hecPJcA/9dIf9f32IU7TpmSlsqiUNAetFHR3y1Myt/EtoUUe7UwgmoC7+Ktp9vfvNsrEHq RWhZZ5xY5NPcsW0n8+/SEk6EOk4tqXkLcMYIRATfqhSt3PeAHqj+oB3KD/mzqB7l0CMJL/ vVMc+4lu21FlTgUCM/ZRr/9+mw5wHzpdnhEMXkS8PnoXhXrN2ecWJEOP7VjtjdmL2g8z32 56bPwkFc7wst6lZmZhbyz7PRBzZ5pgxZYhYbBJrsfL5llsHwChbWgp2cagCxQQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b="Hu2hVX/h"; spf=pass (aspmx1.migadu.com: domain of "guix-devel-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="guix-devel-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1715234714; a=rsa-sha256; cv=none; b=hmQZqt6+zussVTmkyAAwiXazrzBOTpt8YlrDHzkPghJqhI/hBvYOv1QoMyMsZ8Fvx+Efd+ cHYEs5TJz0pJ6+UJZOlMkdGJIw8ReUz6FS+XFL+tNMX5PASoUpUlHbiUXmNo5ujqmIwsUX mVBn2KUvsg4EsHBJ7bW/PDRHVmLFmvruia3OJOh6aE4AI4iM0Hlk6BEeMGcOzRoSlhL0uX MJ2fcAQiuehlUwA1E/YKpCADGOdWVh+WM9zq3eMB1vgUYcGKuh/I+fStj8y2XmmyLbJnyc iF9rvGHZRQaZFKUFlZfWiv67EuR47w6GvOlaT5KqgxmmVvnQmAD6jj9+pIGbaA== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 08C3315AB5 for ; Thu, 9 May 2024 08:05:14 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1s4wtc-0000mC-A8; Thu, 09 May 2024 02:04:48 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1s4wtY-0000lu-QK for guix-devel@gnu.org; Thu, 09 May 2024 02:04:46 -0400 Received: from mail-wm1-x32c.google.com ([2a00:1450:4864:20::32c]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1s4wtV-0003Ux-8M; Thu, 09 May 2024 02:04:44 -0400 Received: by mail-wm1-x32c.google.com with SMTP id 5b1f17b1804b1-41ba1ba55e9so4360715e9.3; Wed, 08 May 2024 23:04:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1715234678; x=1715839478; darn=gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=e4JLomms2RpFuT43osTtdXJXXN9Zmo5vJrEt0QVjBNM=; b=Hu2hVX/hZuxGC8C9Z0T7ZBvPXRLeLlxJfRwaQVq9xCorMUluzdBejPi7ZmWxkHOO5l HgL+jphNsIHG/46ht7V0AvmRxFbYFonb6tHdkJCK9q3GESvSsbyI0bBGaF4p7hmm5Chm zFjNhXK3zvcjrR/c8fyCHaQjwewPqfSARmpVOX0B/6hN58N3eHjRmm8fdt/u3tins5v6 QTdGa9dMDcgVXRV+SRvYQH7LxhERSFl1Pf5cjyUOhFA3QX8EkAb43BAKI0K+OIaFFMrz /8OSQIj1KObq6f7Rmm7a4cDrIma6IyA5RCptzWR4UD24xPmN5GWmeV0mqlX5ucO6HX06 awPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715234678; x=1715839478; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=e4JLomms2RpFuT43osTtdXJXXN9Zmo5vJrEt0QVjBNM=; b=UY4sKt48PLndi1HvYj8RFlpt5Fdck87d28p6Pavo32rMZqJBn5tLdCFrJcHhZrrYsV /1UFhOEU5Uc/XsvqkmRnk3b9SztcRCIKrdgprAHXKSygPf8Txrq4jCZmPz/1kTtCagmM rikPas6cGFlLahcqGOMieCilMg0IDlb0F8q0Opy8m7zvkOWcHQuYVy6ZeZvmpKgpumip MJDWbaDR37cpmoysGW79BmC3nuvZM+vqPTkNzMFX1qY9AL8EuO9+dNbeoiCLn/ySiaDc Zw4SBl6lCQaDvbWm5/LPbQq2ppBuMQFD6r5BnmlrvkMhRd/0SzTfYLeLOtIJeDLQN2Dl twgg== X-Forwarded-Encrypted: i=1; AJvYcCV+h/r+WYWiiIjkUI3oX73S3fWPi8pjoSrdcsP0h8APQ5bI+AGUaw32XXvVkPBoWlKI6hVYIoZFEOAQ0kM= X-Gm-Message-State: AOJu0YybvfUKuYMWFH41/mo7mxqZUVolKRQDMN5qQPt+cqGR0YqWaQKr nGDPeBniN81OOyVPat5EA7JeQ2DxtlbTvB/A9A+mrpMDMPMHFelNaOGH+ogyBjxS//JQN8ussDV w6PcFXAGGl3vvJXJkEr2v4oWFCPQ= X-Google-Smtp-Source: AGHT+IGqeuPy9eiAkX+R6qtmWQ9Dep+BYb0ZExLnUQbFqaNC4XDWSAFjuhrDzShUNImedlisN1rz2MmRgCDNwxOO4KI= X-Received: by 2002:a05:600c:1913:b0:41a:b961:9495 with SMTP id 5b1f17b1804b1-41f719d5e9amr32641955e9.25.1715234677990; Wed, 08 May 2024 23:04:37 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Ashvith Shetty Date: Thu, 9 May 2024 11:34:26 +0530 Message-ID: Subject: Re: `make check` fails when trying to build from Git To: Steve George Cc: guix-devel@gnu.org, =?UTF-8?Q?Ludovic_Court=C3=A8s?= Content-Type: multipart/alternative; boundary="000000000000b02c420617ff3184" Received-SPF: pass client-ip=2a00:1450:4864:20::32c; envelope-from=ashvithshetty10@gmail.com; helo=mail-wm1-x32c.google.com X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: guix-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+larch=yhetil.org@gnu.org Sender: guix-devel-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -9.71 X-Spam-Score: -9.71 X-Migadu-Queue-Id: 08C3315AB5 X-Migadu-Scanner: mx13.migadu.com X-TUID: MjJCbOxjLrip --000000000000b02c420617ff3184 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable (Sorry for replying again, but since my message wasn't reaching to gnu-devel for others to see, I'm trying this again, this time, hopefully it should reach others) Hello Steve, Yes, you're right about that - I am on the master branch. Should I switch to a different commit? Maybe the ones listed in `git tag --list`? On Mon, 6 May, 2024, 15:23 Ashvith Shetty, wrote: > Hello Steve, yes, you're right about that - I am on the master branch. > Should I switch to a different commit? Maybe the ones listed in `git tag > --list`? For my first patch, I wanted to create multiple package variants > of NodeJS. similar to how it was done for Zig. I was wondering if those > errors can affect them. > > On Sun, May 5, 2024 at 3:53=E2=80=AFPM Steve George = wrote: > >> >> On 4 May, Ashvith Shetty wrote: >> > I've been looking forward to contributing some packages to Guix, but s= o >> > far, I've not been able to figure out from the manual, so I'm going >> through >> > the entire Contributing >> > >> section. >> > >> > So far, after the `guix shell -D guix -CPW` command, I've reached the >> `make >> > check` part, where the tests fail. What logs should I share, so that I >> can >> > make it easier for people to check out the issue that's stopping me fr= om >> > progressing? >> (...) >> >> Hi Ashvith - are you building the master branch with a recent checkout? >> >> I also get some FAILS, but not as many as you. >> >> You can probably continue and if the ./pre-inst-env guix command works >> then you can continue to package. >> >> The manual has a section on how to investigate the test failures: if you >> have alook at those there may be clues and you can create issues with a >> proper log at that point. >> >> Best, >> >> Steve / Futurile >> >> >> >> --000000000000b02c420617ff3184 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
(Sorry for replying again, but since my message wasn&#= 39;t reaching to gnu-devel for others to see, I'm trying this again, th= is time, hopefully it should reach others)

Hello Steve,
Y= es, you're right about that - I am on the master branch. Should I switc= h to a different commit? Maybe the ones listed in `git tag --list`?=C2=A0

On Mon, 6 May, 2024, 15:23 Ashvith Shetty, <ashvithshetty= 10@gmail.com> wrote:
Hello Steve, yes, you're right about that - I am on the = master branch. Should I switch to a different commit? Maybe the ones listed= in `git tag --list`? For my first patch, I wanted to create multiple packa= ge variants of NodeJS. similar to how it was done for Zig. I was wondering = if those errors can affect them.

On Sun, May 5, 2024 at 3:53=E2=80= =AFPM Steve George <steve@futurile.net> wrote:

On=C2=A0 4 May, Ashvith Shetty wrote:
> I've been looking forward to contributing some packages to Guix, b= ut so
> far, I've not been able to figure out from the manual, so I'm = going through
> the entire Contributing
> <https= ://guix.gnu.org/manual/devel/en/html_node/Contributing.html> section= .
>
> So far, after the `guix shell -D guix -CPW` command, I've reached = the `make
> check` part, where the tests fail. What logs should I share, so that I= can
> make it easier for people to check out the issue that's stopping m= e from
> progressing?
(...)

Hi Ashvith - are you building the master branch with a recent checkout?

I also get some FAILS, but not as many as you.

You can probably continue and if the ./pre-inst-env guix command works then= you can continue to package.

The manual has a section on how to investigate the test failures: if you ha= ve alook at those there may be clues and you can create issues with a prope= r log at that point.

Best,

Steve / Futurile



--000000000000b02c420617ff3184--