unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: Nigko Yerden <nigko.yerden@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: What does it mean when patch disappears from qa.guix.gnu.org patches list?
Date: Tue, 28 May 2024 15:12:36 +0100	[thread overview]
Message-ID: <a4nhvygqkqrgavhnk32z5dnkpqyhswv3vtvi3hgdxfqez2h5h2@hf33p2k6xug3> (raw)
In-Reply-To: <501e32a8-6ced-42c4-a0c7-e2364e777040@gmail.com>

Hi,

Generally it means:

1. Issue has been applied - check issues.guix.gnu.org and generally the committer will have left a note saying when it was committed and closing the issue.

2. If not, then it could be a failure of the QA system. Sometimes QA has to be reset and so issues are skipped over. To check if it's been processed go the URL: 

    https://qa.guix.gnu.org/issue/NNNN

    https://qa.guix.gnu.org/issue/70341

I get an error about wrong-type-arg - I don't know what that means but clearly something has gone wrong.

The last traffic on it was someone talking about a typo, you could reroll the patch (fix the typo) and try resubmitting it to the queue.

Thanks,

Steve / Futurile


On 27 May, Nigko Yerden wrote:
> Hello Guix!
> 
> Recently the patch https://issues.guix.gnu.org/70341 has completely
> disappeared from https://qa.guix.gnu.org/patches? list of patches
> under consideration. I would like to know what does it mean? The patch
> was considered inappropriate and rejected? Or some kind of error
> in patch processing occurred?
> 
> Regards,
> Nigko
> 


      reply	other threads:[~2024-05-30 22:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-27  4:32 What does it mean when patch disappears from qa.guix.gnu.org patches list? Nigko Yerden
2024-05-28 14:12 ` Steve George [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4nhvygqkqrgavhnk32z5dnkpqyhswv3vtvi3hgdxfqez2h5h2@hf33p2k6xug3 \
    --to=steve@futurile.net \
    --cc=guix-devel@gnu.org \
    --cc=nigko.yerden@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).