Github messages for voidlinux
 help / color / mirror / Atom feed
From: PoroCYon <PoroCYon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: kicad: update to 6.0.0
Date: Sat, 08 Jan 2022 00:10:41 +0100	[thread overview]
Message-ID: <20220107231041.aVn87f_ew4VpmI6uos51bPoXyRxDyk8auo9bseRzqRg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34917@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]

New comment by PoroCYon on void-packages repository

https://github.com/void-linux/void-packages/pull/34917#issuecomment-1007810058

Comment:
Thanks for the feedback, I've incorporated your suggestions. However, I can't seem to replicate  the test failure:

```
=> kicad-6.0.0_1: running do_check ...
[0/1] Running tests...
Test project /builddir/kicad-6.0.0/build
    Start 1: qa_python
1/8 Test #1: qa_python ........................   Passed    1.37 sec
    Start 2: qa_common
2/8 Test #2: qa_common ........................   Passed    0.04 sec
    Start 3: qa_gerbview
3/8 Test #3: qa_gerbview ......................   Passed    0.11 sec
    Start 4: qa_eeschema
4/8 Test #4: qa_eeschema ......................   Passed    0.83 sec
    Start 5: qa_sexpr
5/8 Test #5: qa_sexpr .........................   Passed    0.01 sec
    Start 6: qa_kimath
6/8 Test #6: qa_kimath ........................   Passed    0.02 sec
    Start 7: qa_pcbnew
7/8 Test #7: qa_pcbnew ........................   Passed   45.37 sec
    Start 8: qa_kicad2step
8/8 Test #8: qa_kicad2step ....................   Passed    0.17 sec

100% tests passed, 0 tests failed out of 8

Total Test time (real) =  47.93 sec
```

Maybe it's a glibc vs musl difference? I forgot to mention I'm using glibc. Either way, I'd need some help to fix this as I can't replicate it.

  parent reply	other threads:[~2022-01-07 23:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-07  2:47 [PR PATCH] " PoroCYon
2022-01-07 18:52 ` unspecd
2022-01-07 23:07 ` [PR PATCH] [Updated] " PoroCYon
2022-01-07 23:10 ` PoroCYon [this message]
2022-01-16  8:43 ` lemmi
2022-01-16  8:44 ` lemmi
2022-01-16 16:37 ` [PR PATCH] [Updated] " PoroCYon
2022-01-16 16:38 ` PoroCYon
2022-01-16 17:48 ` kicad: update to 6.0.1 PoroCYon
2022-01-16 18:35 ` [PR REVIEW] " ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 18:35 ` ericonr
2022-01-16 23:33 ` PoroCYon
2022-01-16 23:39 ` PoroCYon
2022-01-17  0:55 ` [PR PATCH] [Updated] " PoroCYon
2022-01-17  0:57 ` PoroCYon
2022-01-17  4:47 ` [PR REVIEW] " ericonr
2022-01-17 17:17 ` [PR PATCH] [Updated] " PoroCYon
2022-01-23 22:23 ` PoroCYon
2022-01-26 17:26 ` foopub
2022-01-26 17:34 ` foopub
2022-01-27  0:32 ` PoroCYon
2022-01-27  1:05 ` PoroCYon
2022-01-27 13:53 ` [PR PATCH] [Updated] " PoroCYon
2022-01-28  6:27 ` [PR PATCH] [Closed]: " ericonr
2022-01-28  8:00 ` ericonr
2022-01-29  1:12 ` foopub
2022-01-29  1:12 ` foopub

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=20220107231041.aVn87f_ew4VpmI6uos51bPoXyRxDyk8auo9bseRzqRg@z \
    --to=porocyon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    --subject='Re: kicad: update to 6.0.0' \
    /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

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).