unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: 63521@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>,
	"Nicolas Goaziou" <mail@nicolasgoaziou.fr>
Subject: [bug#63521] Request for merging "tex-team" branch
Date: Tue, 23 May 2023 14:20:04 +0100	[thread overview]
Message-ID: <87353nnpwb.fsf@cbaines.net> (raw)
In-Reply-To: <877ct0fmez.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 2426 bytes --]


Christopher Baines <mail@cbaines.net> writes:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi,
>>
>> Nicolas Goaziou <mail@nicolasgoaziou.fr> skribis:
>>
>>> Christopher Baines <mail@cbaines.net> writes:
>>>
>>>> While I realise that waiting to make changes is fustrating, I think it's
>>>> important to try and build things before merging so that the effects are
>>>> known. This is also good motivation to get more hardware helping to
>>>> build things to speed up the process.
>>>
>>> I opened the issue because the "tex-team" branch was fully built on
>>> CI, according to <https://ci.guix.gnu.org/eval/461653>.
>>>
>>> Should I have looked elsewhere before asking for the merge?
>>
>> Looking at <https://qa.guix.gnu.org/branch/tex-team>, there are 13 new
>> failures on x86_64 (178 vs. 165), but I’m not sure what they are because
>> the comparison page shows all the changed derivations (whereas we’d like
>> to see new failures only).
>>
>> How can we get that info, Chris?
>
> So, taking one step back, these numbers come from a comparison of
> tex-team and the master branch, and while that sounds sensible, because
> it's a comparison of the tips of those branches, I think some of what
> you're seeing is breakages that have happened on the master branch but
> after the last common commit.
>
>> I did find one “new” failure on the comparison page but I can’t believe
>> it’s related to changes in the branch:
>>
>>   https://data.qa.guix.gnu.org/gnu/store/a7898v4zq86vzn664g5xh0dq6s1p813k-ams-lv2-1.2.2.drv
>
> Yeah, as I say above it's possible that this has been broken on master
> and not tex-team.
>
> I'll look at getting the comparisons to happen between revisions that
> better isolate the changes on the branch, I might just initially ignore
> the hard case where the "merge base" in the Git sense isn't know by the
> data service.

I'm making some progress, I think I've changed the qa-frontpage in this
way, but unfortunately tex-team branched off master at a revision that
data.qa.guix.gnu.org hasn't got around to processing yet, so currently
there's no comparison.

Maybe the branch could be rebased or master could be merged in? If you
pick the latest commit with a green tick by it from [1], then that
should mean the data service is able to perform the comparison.

1: http://data.qa.guix.gnu.org/repository/2/branch/master

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]

  reply	other threads:[~2023-05-23 13:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 15:48 [bug#63521] Request for merging "tex-team" branch Nicolas Goaziou
2023-05-16  9:57 ` Christopher Baines
2023-05-16 12:02   ` Nicolas Goaziou
2023-05-16 12:05     ` Christopher Baines
2023-05-22 14:06     ` Ludovic Courtès
2023-05-22 14:36       ` Christopher Baines
2023-05-23 13:20         ` Christopher Baines [this message]
2023-05-24 14:36           ` Ludovic Courtès
2023-05-24 14:37           ` Ludovic Courtès
2023-05-24 17:28             ` Nicolas Goaziou
2023-05-25  9:13               ` Christopher Baines
2023-06-02  9:46                 ` Christopher Baines
2023-06-02 20:08                   ` Nicolas Goaziou
2023-06-11  9:31                     ` Christopher Baines
2023-06-11 16:18                       ` bug#63521: " Nicolas Goaziou

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=87353nnpwb.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=63521@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).