From: Gigahawk <Gigahawk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: PrusaSlicer: update to 2.4.0.
Date: Wed, 19 Jan 2022 11:47:27 +0100 [thread overview]
Message-ID: <20220119104727.7ch6fDqVHxZ7L5exSCEO_sBIqz8-G_rQ-IwGLYA-Uks@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35105@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2687 bytes --]
New comment by Gigahawk on void-packages repository
https://github.com/void-linux/void-packages/pull/35105#issuecomment-1016257406
Comment:
The build errors for i686 I assume have to do with the `icu` stuff still being in the backlog:
```
[/tsutil/creststn/TestBinaryCollationData]
*Note* some errors are data-loading related. If the data used is not the
stock ICU data (i.e some have been added or removed), consider using
the '-w' option to turn these errors into warnings.
Elapsed Time: 00:00:16.417
make[2]: *** [Makefile:98: check-local] Error 1
make[2]: Leaving directory '/builddir/icu/source/test/cintltst'
-------------
| *** FAILING TEST SUMMARY FOR: intltest
TestGetSize
ResourceBundleTest
utility
| *** END FAILING TEST SUMMARY FOR: intltest
-------------
| *** FAILING TEST SUMMARY FOR: cintltst
/tsutil/crestst/TestGetSize
/tsutil/creststn/TestNewTypes
/tsutil/creststn/TestBinaryCollationData
| *** END FAILING TEST SUMMARY FOR: cintltst
---------------
ALL TESTS SUMMARY:
ok: testdata iotest
===== ERRS: intltest cintltst
make[1]: *** [Makefile:91: check-recursive] Error 1
make[1]: Leaving directory '/builddir/icu/source/test'
make: *** [Makefile:153: check-recursive] Error 2
=> ERROR: icu-70.1_1: do_check: '${make_cmd} ${make_check_args} ${make_check_target}' exited with 2
=> ERROR: in do_check() at common/build-style/gnu-configure.sh:33
Error: Process completed with exit code 1.
```
I'm not sure what to make of the x86_64-musl errors, it looks like a test is failing (presumably due to differences between musl and glibc)
```
Testing Mutable priority queue - first pop
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
libslic3r_tests is a Catch v2.13.6 host application.
Run with -? for options
-------------------------------------------------------------------------------
Mutable priority queue - first pop
-------------------------------------------------------------------------------
/builddir/PrusaSlicer-version_2.4.0/tests/libslic3r/test_mutable_priority_queue.cpp:343
...............................................................................
/builddir/PrusaSlicer-version_2.4.0/tests/libslic3r/test_mutable_priority_queue.cpp:367: FAILED:
CHECK( valid )
with expansion:
false
Testing Mutable priority queue complex
Passed in 0.005678 [seconds]
```
It looks like this test is either new or failing as of this new version, running CI against 2.3.0 doesn't produce any problems
https://github.com/Gigahawk/void-packages/runs/4865799953?check_suite_focus=true
next prev parent reply other threads:[~2022-01-19 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 10:22 [PR PATCH] " Gigahawk
2022-01-19 8:04 ` [PR PATCH] [Updated] " Gigahawk
2022-01-19 8:06 ` Gigahawk
2022-01-19 8:09 ` [PR REVIEW] " Gigahawk
2022-01-19 9:43 ` Gigahawk
2022-01-19 10:47 ` Gigahawk [this message]
2022-01-28 7:53 ` ericonr
2022-01-28 7:53 ` [PR PATCH] [Closed]: " ericonr
-- strict thread matches above, loose matches on Subject: below --
2022-01-07 17:06 [PR PATCH] " Gottox
2022-01-28 7:53 ` ericonr
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=20220119104727.7ch6fDqVHxZ7L5exSCEO_sBIqz8-G_rQ-IwGLYA-Uks@z \
--to=gigahawk@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).