Re: Failed to build in QA
> > 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 also noticed that the order got > mixed up in issues.guix.gnu.org, no idea how this happened... i also see this every once in a while. i guess it's because the SMTP server-farm receives mutliple emails in close proximity, and they end up reaching debbugs in a different order. -- • attila lendvai • PGP: 963F 5D5F 45C7 DFCD 0A39 -- “In matters of conscience, the law of majority has no place.” — Mahatma Gandhi (1869–1948)
Re: Failed to build in QA
>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. 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 also noticed that the order got mixed up in issues.guix.gnu.org, no idea how this happened...
Re: Failed to build in QA
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 running Patchwork is low on disk space, and that keeps stopping new messages being processed. I've resolved that for now. 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? Thanks, Chris signature.asc Description: PGP signature
Re: Failed to build in QA
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
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 locally but causes problems in QA have you >any pointers what might be the difference? > >> Making openfoam have LD_LIBRARY_PATH as a search path seems like the >> incorrect use of search paths though, since you're searching for >> something in the same package. Replacing this with wrapping would be an >> improvement, although still I'm unsure why LD_LIBRARY_PATH would need >> setting in this case >Hmm maybe you are right, will try to wrap the binaries instead... I removed the search-path but it still fails to build, I cannot make sense of the error message...
Re: Failed to build in QA
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 > have you any pointers what might be the difference? You should be able to reproduce this locally, I see the issue when running make. signature.asc Description: PGP signature
Re: Failed to build in QA
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 difference? Making openfoam have LD_LIBRARY_PATH as a search path seems like the incorrect use of search paths though, since you're searching for something in the same package. Replacing this with wrapping would be an improvement, although still I'm unsure why LD_LIBRARY_PATH would need setting in this case Hmm maybe you are right, will try to wrap the binaries instead... OpenPGP_0xC375C6AF05125C52.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
Re: Failed to build in QA
"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 >>> resolution? >> >>You pretty much found the problem, the relevant line on the page you >>linked to is: >> >>[ 6/ 50] loading... 24.0% of 25 filesbuilder for >>`/gnu/store/qhvpjfn3d9cwz5zxadblbnbqa92a8i27-guix-cli-core.drv' failed due to >>signal 11 (Segmentation fault) >> >>So the data service wasn't able to build Guix. This probably isn't due >>to your changes, and it doesn't happen very often, so the thing to do >>here is just retry. >> >>I've triggered QA to reapply the patches now (by deleting the >>issue-66262 branch), so hopefully things will work better this time. >> >>Thanks, >> >>Chris > > Thanks very much, it seems to have worked, but now it's stuck with > paraview undefined symbol, although the necessary module > (gnu/packages/image-processing) is imported? 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. Making openfoam have LD_LIBRARY_PATH as a search path seems like the incorrect use of search paths though, since you're searching for something in the same package. Replacing this with wrapping would be an improvement, although still I'm unsure why LD_LIBRARY_PATH would need setting in this case. signature.asc Description: PGP signature
Re: Failed to build in QA
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 problem, the relevant line on the page you >linked to is: > >[ 6/ 50] loading...24.0% of 25 filesbuilder for >`/gnu/store/qhvpjfn3d9cwz5zxadblbnbqa92a8i27-guix-cli-core.drv' failed due to >signal 11 (Segmentation fault) > >So the data service wasn't able to build Guix. This probably isn't due >to your changes, and it doesn't happen very often, so the thing to do >here is just retry. > >I've triggered QA to reapply the patches now (by deleting the >issue-66262 branch), so hopefully things will work better this time. > >Thanks, > >Chris Thanks very much, it seems to have worked, but now it's stuck with paraview undefined symbol, although the necessary module (gnu/packages/image-processing) is imported? -- Sent from /e/ Mail.
Re: Failed to build in QA
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 everyone ghosted it despite me pinging on IRC every other week in the last few months. signature.asc Description: PGP signature
Re: Failed to build in QA
"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... 24.0% of 25 filesbuilder for `/gnu/store/qhvpjfn3d9cwz5zxadblbnbqa92a8i27-guix-cli-core.drv' failed due to signal 11 (Segmentation fault) So the data service wasn't able to build Guix. This probably isn't due to your changes, and it doesn't happen very often, so the thing to do here is just retry. I've triggered QA to reapply the patches now (by deleting the issue-66262 branch), so hopefully things will work better this time. Thanks, Chris signature.asc Description: PGP signature
Failed to build in QA
Hi list 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? Best, Reza [1] https://data.qa.guix.gnu.org/job/49591#bottom -- Sent from /e/ Mail.
