From: "brettg@posteo.net" <brettg@posteo.net>
To: Alex Kost <alezost@gmail.com>, Oleg Pykhalov <go.wigust@gmail.com>
Cc: 33854@debbugs.gnu.org
Subject: bug#33854: StumpWM build failing.
Date: Tue, 08 Jan 2019 02:14:01 -0600 [thread overview]
Message-ID: <nl0n2ohpveo44hislvnffgv4.1546935177979@email.lge.com> (raw)
In-Reply-To: <4he7fjmurtf2cvitjem4snh3.1545600224075@email.lge.com>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
Just following up here, I returned from vacation and this is still failing. I will dig around after the jet lag settles, but does anybody have any information on this error? It seems to be related to sbcl.
Sent from my Sprint Phone.
------ Original message------From: Alex KostDate: Tue, Dec 25, 2018 7:50 PMTo: Oleg Pykhalov;Cc: 33854@debbugs.gnu.org;Subject:bug#33854: StumpWM build failing.
Alex Kost (2018-12-24 18:01 +0300) wrote:
> Oleg Pykhalov (2018-12-24 09:10 +0300) wrote:
>
>> Hi,
>>
>> Thank you for notice this.
>>
>> "brettg@posteo.net" writes:
>>
>>> Hi all, StumpWM is failing to build on my machine. Can anybody
>>> replicate this? […]
>>
>> The build farm can https://ci.guix.info/build/721131
>
> Actually it can't since the build status is "1" which means "failed".
Oops, I'm sorry. Initially I thought that you meant "build farm can
build it", but now I see you meant "build farm can reproduce the fail" :-)
--
Alex
[-- Attachment #2: Type: text/html, Size: 1814 bytes --]
next prev parent reply other threads:[~2019-01-08 8:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 21:25 bug#33854: StumpWM build failing brettg
2018-12-24 6:10 ` Oleg Pykhalov
2018-12-24 10:59 ` Boris A. Dekshteyn
2018-12-24 15:01 ` Alex Kost
2018-12-24 15:09 ` Alex Kost
2018-12-24 17:35 ` Oleg Pykhalov
2019-01-08 8:14 ` brettg [this message]
2019-01-09 15:08 ` brettg
2020-06-11 4:13 ` Royce Strange
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=nl0n2ohpveo44hislvnffgv4.1546935177979@email.lge.com \
--to=brettg@posteo.net \
--cc=33854@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=go.wigust@gmail.com \
/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).