Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#55822 - [meson] fails in check()
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Sunday, 01 October 2017, 08:13 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 05 January 2019, 15:41 GMT
Opened by Andreas Baumann (andreas_baumann) - Sunday, 01 October 2017, 08:13 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 05 January 2019, 15:41 GMT
|
DetailsDescription:
Running the tests fail. One test is failing because of the Java 8 to 9 update: Running java tests. Failed test during configure: 'test cases/java/1 basic' Reason: Generating the build system failed. Failed test during configure: 'test cases/java/2 subdir' Reason: Generating the build system failed. Failed test during configure: 'test cases/java/3 args' Reason: Generating the build system failed. Failed test during configure: 'test cases/java/4 inner class' Reason: Generating the build system failed. Even when using Java 8 something else is failed (was unable to find it). Additional info: * package version(s): 0.42.1-2 * config and/or log files etc. Steps to reproduce: # install either java-runtime 8 or java-runtime 9 makepkg -si |
log8
This task depends upon
Closed by Jelle van der Waa (jelly)
Saturday, 05 January 2019, 15:41 GMT
Reason for closing: Works for me
Additional comments about closing: Works in a clean chroot, which is the preferred way of building packages.
Saturday, 05 January 2019, 15:41 GMT
Reason for closing: Works for me
Additional comments about closing: Works in a clean chroot, which is the preferred way of building packages.
FAILED: valaprog@exe/unused-var.c.o
cc -Ivalaprog@exe -I. '-I../test cases/failing build/1 vala c werror' -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Werror -O0 -g -march=x86-64 -mtune=generic -O2 -fstack-protector-strong -fno-plt -D_FORTIFY_SOURCE=2 -MMD -MQ 'valaprog@exe/unused-var.c.o' -MF 'valaprog@exe/unused-var.c.o.d' -o 'valaprog@exe/unused-var.c.o' -c '../test cases/failing build/1 vala c werror/unused-var.c'
../test cases/failing build/1 vala c werror/unused-var.c:1:2: error: #warning "something" [-Werror=cpp]
#warning "something"
^~~~~~~
../test cases/failing build/1 vala c werror/unused-var.c: In function <E2><80><98>somelib<E2><80><99>:
../test cases/failing build/1 vala c werror/unused-var.c:6:7: error: unused variable <E2><80><98>unused_var<E2><80><99> [-Werror=unused-variable]
int unused_var;
^~~~~~~~~~
cc1: all warnings being treated as errors
[2/4] Compiling Vala source '../test cases/failing build/1 vala c werror/prog.vala'.
ninja: build stopped: subcommand failed.
and:
Failed test during validate: 'test cases/frameworks/14 doxygen'
Reason: Expected file usr/share/doc/spede/html/classComedy_1_1Comedian.png missing.
Expected file usr/share/doc/spede/html/classComedy_1_1Spede.png missing.
Not sure, what do do about those (they also happen on 64-bit).
I'm more worried how the vala tests suddenly stop in
ninja: build stopped: subcommand failed.