[bug#73515] Request for merging "qt-team" branch

[bug#73515] Request for merging "qt-team" branch

[Z572]

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


Hi! qt-team have this following updates:
- qt5 5.15.10 -> 5.15.15
- qt6 6.6.3 -> 6.7.2
- libvpx 1.12.0 -> 1.14.1
- abseil-cpp 20230802.1 -> 20240722.0
- add re2-next, icu4c-75, python-setuptools-scm-next
- qtconnectivity rename to qtconnectivity-5 and add qtconnectivity qt6
- qtcharts rename to qtcharts-5 and add qtcharts qt6

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

[bug#73515] Ready to merge qt-team branch?

[Steve George]

Hi Z572,

You're next in the merge queue according to the list [0], are you ready to merge?

Looks like a rebase is needed as QA is saying it can't process it:

https://qa.guix.gnu.org/branch/qt-team

I'm assuming this is partially why CI's substitutes available is so bad.

Steve / Futurile

[0] https://qa.guix.gnu.org/

[bug#73515] Ready to merge qt-team branch?

[Christopher Baines]

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

Steve George <steve@futurile.net> writes:

> You're next in the merge queue according to the list [0], are you ready to merge?
>
> Looks like a rebase is needed as QA is saying it can't process it:
>
> https://qa.guix.gnu.org/branch/qt-team

The QA data service has processed the tip of qt-team, that's how it's
able to provide substitute information.

Also, looks like it's based on 3dc63f8ca7af8d4fee32a03c206b571896a3a70a
which is a few days old, so I'm guessing it was rebased a couple of days
ago.

The qa-frontpage has just finished canceling all the old builds that I
guess were submitted prior to the rebase, so hopefully some builds will
start happening soon.

> I'm assuming this is partially why CI's substitutes available is so bad.

I think CI has substitute availability comparable with master, which
seems good to me at least regarding the merge of qt-team, it's bordeaux
which is further behind.

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

[bug#73515] Ready to merge qt-team branch?

[Steve George]

On 11 Nov, Christopher Baines wrote:
> Steve George <steve@futurile.net> writes:
(...) 
> The QA data service has processed the tip of qt-team, that's how it's
> able to provide substitute information.
> 
> Also, looks like it's based on 3dc63f8ca7af8d4fee32a03c206b571896a3a70a
> which is a few days old, so I'm guessing it was rebased a couple of days
> ago.
> 
> The qa-frontpage has just finished canceling all the old builds that I
> guess were submitted prior to the rebase, so hopefully some builds will
> start happening soon.
> 
> > I'm assuming this is partially why CI's substitutes available is so bad.
> 
> I think CI has substitute availability comparable with master, which
> seems good to me at least regarding the merge of qt-team, it's bordeaux
> which is further behind.

Ah! thanks for the explanation Chris.

What's a reasonable level to wait for before a branch is merged? Master is at 96% on CI, and 92% on bordeaux right, so should we wait for the QT branch to get to the same point? And, is there a rule of thumb for the other architectures?

Steve

[bug#73515] Ready to merge qt-team branch?

[Z572]

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

Steve George <steve@futurile.net> writes:

> Hi Z572,
>
> You're next in the merge queue according to the list [0], are you ready to merge?
>
> Looks like a rebase is needed as QA is saying it can't process it:
>
> https://qa.guix.gnu.org/branch/qt-team
>
> I'm assuming this is partially why CI's substitutes available is so bad.

The other day I rebase to the latest commit, but qa doesn't seem to have
handled Merge base yet. and ci.guix's qt-team seems to work very slowly,
the submitted package will take a long time to start.

>
> Steve / Futurile
>
> [0] https://qa.guix.gnu.org/

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

[bug#73515] Request for merging "qt-team" branch

[Ludovic Courtès]

Hi,

Z572 <zhengjunjie@iscas.ac.cn> skribis:

> The other day I rebase to the latest commit, but qa doesn't seem to have
> handled Merge base yet. and ci.guix's qt-team seems to work very slowly,
> the submitted package will take a long time to start.

<https://ci.guix.gnu.org/jobset/qt-team> is at 75% across all
architectures; for reference, ‘master’ is at 78% (meaning that x86 is
above 90% and aarch64 is very low).

I would say it’s enough to make an informed decision as to whether to
merge.

WDYT?

Thanks,
Ludo’.

bug#73515: Request for merging "qt-team" branch

[Zheng Junjie]

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

Ludovic Courtès <ludo@gnu.org> writes:

> Hi,
>
> Z572 <zhengjunjie@iscas.ac.cn> skribis:
>
>> The other day I rebase to the latest commit, but qa doesn't seem to have
>> handled Merge base yet. and ci.guix's qt-team seems to work very slowly,
>> the submitted package will take a long time to start.
>
> <https://ci.guix.gnu.org/jobset/qt-team> is at 75% across all
> architectures; for reference, ‘master’ is at 78% (meaning that x86 is
> above 90% and aarch64 is very low).
>
> I would say it’s enough to make an informed decision as to whether to
> merge.

Yes, the other day I was waiting for bordeaux to build qt-team's aarch64 architecture.

Now I have pushed qt-team to master

Closed this issue.

>
> WDYT?
>
> Thanks,
> Ludo’.

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