From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [tracking] List of currently failing builds
Date: Sat, 03 Sep 2022 20:07:20 +0200 [thread overview]
Message-ID: <20220903180720.udsptNn_EDwSDPVGMnHMJmo2REgeH_AUETsuQdFIT0s@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39083@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39083#issuecomment-1236174503
Comment:
> Also when trying to get a useful build log from failing go packages, you probably want to set XBPS_MAKEJOBS=1 so that the error is the last log message (or close to it). Multiple jobs typically causes the error to get lost in the shuffle of logs.
I am aware of that, but I don't really want to go through all of the logs and manually find the issue in the logs. Some of the logs might not be useful, but people can build it manually. This is with -j20 :).
> Maybe just remove go-languageserver?
feel free to open a PR
next prev parent reply other threads:[~2022-09-03 18:07 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 9:46 [ISSUE] " paper42
2022-09-03 9:47 ` paper42
2022-09-03 12:06 ` sgn
2022-09-03 12:06 ` sgn
2022-09-03 16:31 ` CameronNemo
2022-09-03 16:33 ` CameronNemo
2022-09-03 16:37 ` CameronNemo
2022-09-03 16:40 ` CameronNemo
2022-09-03 17:04 ` oreo639
2022-09-03 17:08 ` oreo639
2022-09-03 17:35 ` oreo639
2022-09-03 17:42 ` oreo639
2022-09-03 18:02 ` oreo639
2022-09-03 18:07 ` paper42 [this message]
2022-09-03 18:08 ` paper42
2022-09-03 18:18 ` paper42
2022-09-04 8:57 ` sgn
2022-09-04 14:30 ` sgn
2022-09-04 15:15 ` sgn
2022-09-04 15:24 ` sgn
2022-09-04 18:04 ` sgn
2022-09-05 15:59 ` classabbyamp
2022-09-05 15:59 ` classabbyamp
2022-09-06 15:11 ` mtboehlke
2022-09-06 16:33 ` paper42
2022-09-06 16:33 ` paper42
2022-09-07 10:32 ` paper42
2022-09-22 14:29 ` mtboehlke
2022-09-29 16:05 ` TeddyDD
2022-09-29 18:41 ` paper42
2022-09-29 19:34 ` paper42
2022-09-29 19:38 ` paper42
2022-10-02 20:56 ` motorto
2022-10-05 8:07 ` paper42
2022-10-08 21:12 ` paper42
2022-10-08 21:13 ` paper42
2022-10-08 21:13 ` paper42
2022-10-08 21:14 ` paper42
2022-10-08 21:14 ` paper42
2022-10-08 21:15 ` paper42
2022-10-08 21:30 ` paper42
2022-10-08 21:31 ` paper42
2022-11-17 14:32 ` tranzystorek-io
2022-11-26 18:35 ` kruceter
2022-11-26 21:14 ` kruceter
2022-11-30 17:53 ` kruceter
2022-12-04 16:39 ` kruceter
2022-12-25 18:13 ` mhmdanas
2022-12-25 18:32 ` kruceter
2022-12-25 18:38 ` CameronNemo
2022-12-25 20:29 ` mhmdanas
2022-12-25 20:29 ` mhmdanas
2022-12-25 20:30 ` mhmdanas
2022-12-25 20:32 ` mhmdanas
2022-12-25 20:33 ` mhmdanas
2022-12-25 20:43 ` mhmdanas
2022-12-25 20:43 ` mhmdanas
2023-01-06 12:26 ` kruceter
2023-01-21 19:52 ` r-ricci
2023-02-09 21:23 ` dkwo
2023-02-15 1:48 ` dkwo
2023-04-03 13:21 ` zlice
2023-04-03 13:35 ` zlice
2023-04-03 14:25 ` zlice
2023-04-18 20:37 ` mhmdanas
2023-04-19 21:32 ` mhmdanas
2023-07-25 19:20 ` dkwo
2023-07-25 20:12 ` TeddyDD
2023-07-25 20:33 ` dkwo
2023-07-25 21:47 ` TeddyDD
2023-07-26 5:29 ` TeddyDD
2023-10-21 11:13 ` motorto
2023-10-21 13:06 ` zlice
2023-10-21 17:12 ` motorto
2023-11-10 20:26 ` vfx1b
2023-11-10 22:09 ` vfx1b
2023-11-10 22:15 ` classabbyamp
2023-11-13 16:47 ` vfx1b
2023-11-14 13:39 ` zlice
2023-11-14 13:40 ` zlice
2023-11-14 13:41 ` zlice
2024-03-23 16:17 ` adigitoleo
2024-03-23 17:22 ` leahneukirchen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220903180720.udsptNn_EDwSDPVGMnHMJmo2REgeH_AUETsuQdFIT0s@z \
--to=paper42@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).