Summary: | sci-libs/vtk-9.0.3-r4: failed (test phase) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joonas Niilola <juippis> |
Component: | Current packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kripton, proxy-maint, waebbl-gentoo |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 829841 | ||
Attachments: |
build.log
vtk-9.0.3-r4-LastTest.log |
Description
Joonas Niilola
2022-04-25 13:48:46 UTC
Created attachment 774509 [details]
vtk-9.0.3-r4-LastTest.log
Only about one third of the tests are passing. I wonder, how to fix this. Upstream build system testing seems not to be made for downstream testing inside a sandbox, with downloading files, a target VTKData to build extra data files, which I wasn't be able to get it build properly. Maybe the feature from EAPI 8 to allow downloading of files in certain circumstances can help with that? If I read and understood your comment right, then yes, maybe you can work it through the new available features. I don't really know if EAPI-8 is needed since you can already bypass the network sandbox in test phase via ALLOW_TEST="network" variable in your make.conf (env/test.conf). You also could pre-download the test cases, but I fear that'll require a lot of modifications to the ebuild. So maybe let's try with ALLOW_TEST="network" first? Oh and you do need these in the _ebuild_ too: PROPERTIES="test_network" RESTRICT="test" I can try these changes. Yet, they are just a small bit of the issues. v9.1.0 has all cases and needed data in a downloadable tarball, but still many tests fail with our setup. If you look at their dashboard[1], most of their tests pass. Maybe this points to some misconfiguration with the ebuild as well, i.e. USE flag combinations which might not play well together, but are not strictly forbidden by upstream. While preparing for packaging v9.1.0, I tried building and testing from a git checkout, which resulted in lesser test fails than the ebuild shows. I was even thinking of restricting test until that has been solved. [1] https://open.cdash.org/index.php?project=VTK The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0167fc77186716079471d895b32b2283ca8b7fc4 commit 0167fc77186716079471d895b32b2283ca8b7fc4 Author: Paul Zander <negril.nx+gentoo@gmail.com> AuthorDate: 2023-07-06 14:26:47 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-01-10 12:41:01 +0000 sci-libs/vtk: add 9.3.0 Closes: https://bugs.gentoo.org/918898 Closes: https://bugs.gentoo.org/909520 Closes: https://bugs.gentoo.org/909380 Closes: https://bugs.gentoo.org/908874 Closes: https://bugs.gentoo.org/906264 Closes: https://bugs.gentoo.org/906075 Closes: https://bugs.gentoo.org/887505 Closes: https://bugs.gentoo.org/840776 Closes: https://bugs.gentoo.org/835659 Signed-off-by: Paul Zander <negril.nx+gentoo@gmail.com> Closes: https://github.com/gentoo/gentoo/pull/34432 Signed-off-by: Sam James <sam@gentoo.org> sci-libs/vtk/Manifest | 6 + sci-libs/vtk/files/vtk-9.2.5-pegtl-3.x.patch | 136 +++ ...ix-Java-error-with-integer-enum-overloads.patch | 51 ++ sci-libs/vtk/files/vtk-9.3.0-java.patch | 11 + sci-libs/vtk/files/vtk-9.3.0-opencascade.patch | 17 + sci-libs/vtk/files/vtk-9.3.0-pdal-2.6.0.patch | 77 ++ .../vtk-9.3.0-too-many-initializer-values.patch | 20 + sci-libs/vtk/metadata.xml | 1 + sci-libs/vtk/vtk-9.3.0.ebuild | 909 +++++++++++++++++++++ 9 files changed, 1228 insertions(+) |