Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1020356 > unrolled thread

Bug#963409: kakoune: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2

Started byPeter Pentchev <roam@ringlet.net>
First post2020-08-03 13:30 +0200
Last post2020-08-03 13:30 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#963409: kakoune: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 Peter Pentchev <roam@ringlet.net> - 2020-08-03 13:30 +0200

#1020356 — Bug#963409: kakoune: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2

FromPeter Pentchev <roam@ringlet.net>
Date2020-08-03 13:30 +0200
SubjectBug#963409: kakoune: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2
Message-ID<AzGPf-2oN-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

package src:kakoune
fixed 963409 2020.01.16-2
thanks

On Sun, Jun 21, 2020 at 10:10:07PM +0200, Lucas Nussbaum wrote:
> Source: kakoune
> Version: 2020.01.16-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200620 ftbfs-bullseye
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.

Hi,

Somewhat belatedly, thanks for this rebuild!

Back when you filed the
bug, I could easily reproduce it in an unstable chroot, but I could not
reproduce it in a testing one, so I put it off for a while. Later,
after another GCC 10 snapshot made its way into experimental and
unstable, it turned out that I cannot reproduce it any more,
witnessed by kakoune/2020.01.16-2 having been built successfully almost
everywhere, except a somewhat expected failure on the Hurd (that I will
look into one of these days; I do try to get my packages to build there,
too) and a weird one on sh4 that I will investigate soon. However,
neither of these failures is anything similar to the internal failure
during the test run that was seen before.

So once again, thanks for filing this, but I believe that it may have
been something more likely related to GCC than to Kakoune. Of course,
it is possible that Kakoune does something weird that uncovered it, but
still, it seems to build now...

G'luck,
Peter

-- 
Peter Pentchev  roam@ringlet.net roam@debian.org pp@storpool.com
PGP key:        http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13

[toc] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web