From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Leo Famulari <leo@famulari.name>
Cc: "40031@debbugs.gnu.org" <40031@debbugs.gnu.org>
Subject: bug#40031: OpenScad Test errors
Date: Thu, 12 Mar 2020 12:03:51 +0000 [thread overview]
Message-ID: <49ouC9nRCLekpgO0n2l-KGx5ytBXMNBMC-YBp80CGL86C_FM1W97u7NOtPhrofi_Z5yvfqXlw27-HbtK2gqPOjFgdsav-L85B1lna6S1GiI=@elenq.tech> (raw)
In-Reply-To: <20200311225144.GB22532@jasmine.lan>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, March 11, 2020 10:51 PM, Leo Famulari <leo@famulari.name> wrote:
> On Wed, Mar 11, 2020 at 08:48:43PM +0000, Ekaitz Zarraga wrote:
>
> > Hi,
> > My installation of GuixSD fails to install OpenSCAD.
> > Running `guix environment --pure --ad-hoc openscad` fails with the errors I attach.
> > Can you reproduce or is it just a problem with my installation?
> > Ideas about how can I correct this?
>
> Try running it again the build with --keep-failed and then looking in
> the build directory for test suite logs. There is not much to go on in
> the build log you sent.
I made it.
I opened the folder and it's compiled and it runs pretty well.
The tests have the following errors which are exclusively related with the test tooling, in my opinion.
```
Unable to open a connection to the X server.
DISPLAY=:1
Can't create OpenGL OffscreenView. Code: -1.
Error: openscad failed with return code 1
Test time = 0.06 sec
```
The tests compare the *image* of what it's supposed to render OpenSCAD with some already rendered images.
The problem is it's trying to access a screen and it's unable to do it.
There's `xvfb` for X testing but it's like it's not working.
Ideas?
Thanks!
next prev parent reply other threads:[~2020-03-12 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 20:48 bug#40031: OpenScad Test errors Ekaitz Zarraga
2020-03-11 22:51 ` Leo Famulari
2020-03-12 12:03 ` Ekaitz Zarraga [this message]
2020-03-20 18:06 ` Marius Bakke
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='49ouC9nRCLekpgO0n2l-KGx5ytBXMNBMC-YBp80CGL86C_FM1W97u7NOtPhrofi_Z5yvfqXlw27-HbtK2gqPOjFgdsav-L85B1lna6S1GiI=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=40031@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).