Re: Failed to build in QA

2023-11-29 Thread Attila Lendvai
> > The other issue with the v4 series is that Patchwork has got confused > > and only picked out the first of the v4 patches. The threading also > > looks weird to me in my email client, but I'm not quite sure why. How > > did you send the v4 patches? > > > I sent them with git send-mail but I als

Re: Failed to build in QA

2023-11-29 Thread reza.housse...@gmail.com
>There's two issues, one is the machine running Patchwork is low on disk >space, and that keeps stopping new messages being processed. I've >resolved that for now. Thanks! >The other issue with the v4 series is that Patchwork has got confused >and only picked out the first of the v4 patches. T

Re: Failed to build in QA

2023-11-29 Thread Christopher Baines
Reza Housseini writes: > Hi Christopher > > I submitted a new revision to the issue, but the QA link shows > > Issue not found > This could mean the issue does not exist, it has no patches or has > been closed. > > do you know what the problem is here? There's two issues, one is the machine run

Re: Failed to build in QA

2023-11-29 Thread Reza Housseini
Hi Christopher I submitted a new revision to the issue, but the QA link shows Issue not found This could mean the issue does not exist, it has no patches or has been closed. do you know what the problem is here? Thanks for your help, Best, Reza

Re: Failed to build in QA

2023-10-20 Thread reza.housse...@gmail.com
On October 9, 2023 12:40:40 PM UTC, Reza Housseini wrote: >> This is probably down to a top level circular dependency. In particular, >> trying to paraview to compute the version to form part of the >> native-search-path at the top level causes problems. > >I'm wondering why it builds fine locall

Re: Failed to build in QA

2023-10-10 Thread Christopher Baines
Reza Housseini writes: >> This is probably down to a top level circular dependency. In particular, >> trying to paraview to compute the version to form part of the >> native-search-path at the top level causes problems. > > I'm wondering why it builds fine locally but causes problems in QA > hav

Re: Failed to build in QA

2023-10-09 Thread Reza Housseini
This is probably down to a top level circular dependency. In particular, trying to paraview to compute the version to form part of the native-search-path at the top level causes problems. I'm wondering why it builds fine locally but causes problems in QA have you any pointers what might be the

Re: Failed to build in QA

2023-10-06 Thread Christopher Baines
"reza.housse...@gmail.com" writes: > On October 5, 2023 10:49:06 AM GMT+02:00, Christopher Baines > wrote: >> >>"reza.housse...@gmail.com" writes: >> >>> I submitted an issue to guix. But QA refuses to build it [1]. I have >>> no clue what the problem is, can anyone shed light on a possible >

Re: Failed to build in QA

2023-10-05 Thread reza.housse...@gmail.com
On October 5, 2023 10:49:06 AM GMT+02:00, Christopher Baines wrote: > >"reza.housse...@gmail.com" writes: > >> I submitted an issue to guix. But QA refuses to build it [1]. I have >> no clue what the problem is, can anyone shed light on a possible >> resolution? > >You pretty much found the prob

Re: Failed to build in QA

2023-10-05 Thread Development of GNU Guix and the GNU System distribution.
On 2023-10-05 at 09:49+01:00, Christopher Baines wrote: > I've triggered QA to reapply the patches now (by deleting the > issue-66262 branch), so hopefully things will work better this time. Could you try the same for https://qa.guix.gnu.org/issue/64222? It's stuck at unknown and that's why everyo

Re: Failed to build in QA

2023-10-05 Thread Christopher Baines
"reza.housse...@gmail.com" writes: > I submitted an issue to guix. But QA refuses to build it [1]. I have > no clue what the problem is, can anyone shed light on a possible > resolution? You pretty much found the problem, the relevant line on the page you linked to is: [ 6/ 50] loading...