Github messages for voidlinux
 help / color / mirror / Atom feed
From: tjkirch <tjkirch@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: file: update to 5.43.
Date: Sun, 09 Oct 2022 01:56:29 +0200	[thread overview]
Message-ID: <20221008235629.9Z-sc_TUPKZJeexAOou5IrdujUBSeYcRB8jK7YLJXHc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39825@inbox.vuxu.org>

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

New comment by tjkirch on void-packages repository

https://github.com/void-linux/void-packages/pull/39825#issuecomment-1272415328

Comment:
x86-64 musl unit tests failed with:
```
2022-10-08T23:42:25.2927150Z Running test: ../tests/dsd64-dsf.testfile
2022-10-08T23:42:25.3031608Z ../tests/dsd64-dsf.testfile: DSD Stream File, mono, simple-rate, 1 bit, 141184 samples
2022-10-08T23:42:25.3032087Z lt-test: ERROR: result was (len 57)
2022-10-08T23:42:25.3032524Z DSD Stream File, mono, simple-rate, 1 bit, 141184 samples
2022-10-08T23:42:25.3032828Z expected (len 94)
2022-10-08T23:42:25.3033193Z DSF audio bitstream data, 1 bit, mono, "DSD 64" 2822400 Hz, no compression, ID3 version 2.3.0
```

I haven't figured out yet how to run unit tests during a cross build with xbps-src, so I'm not sure if this is reproducible.  I don't seem to have the ability to rerun CI checks.

  reply	other threads:[~2022-10-08 23:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 23:41 [PR PATCH] " tjkirch
2022-10-08 23:56 ` tjkirch [this message]
2022-10-09  0:17 ` paper42
2022-10-09  0:48 ` tjkirch
2022-10-09  4:21 ` tjkirch
2022-10-09  5:42 ` tjkirch
2022-10-09 22:07 ` tjkirch
2022-10-09 22:07 ` [PR PATCH] [Closed]: " tjkirch
2022-10-09 22:07 ` tjkirch
2022-12-09 17:47 [PR PATCH] " mhmdanas
2022-12-09 18:14 ` mhmdanas

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=20221008235629.9Z-sc_TUPKZJeexAOou5IrdujUBSeYcRB8jK7YLJXHc@z \
    --to=tjkirch@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).