Closed magnetophon closed 6 years ago
Can you try to run that test by hand, ie. lib/parser/test-utils --verbose
?
@djcb Odd: when I run the test by hand it passes (the above is from inside the pkg build). Must be a NixOS thing. I'll ask there.
Thanks.
Hmm, doubt it's a NixOS thing... are you able to isolate the exact test that fails?
How should I do that?
What does lib/parser/test-suite.log
say?
@peterhoeg how do I read that?
When I run the tests from nix-shell
, they pass.
nix-build -K -A mu $(pwd)
- this will leave the build directory behind for you to inspect.
@peterhoeg Thanks.
That command didn't work here, but this one did:
nix-build -K -E 'with import <nixpkgs> {}; callPackage ./default.nix {}'
.
Unfortunately the log isn't very helpful without --verbose
, and I don't know how to pass that.
=======================================
mu 1.0: lib/parser/test-suite.log
=======================================
# TOTAL: 3
# PASS: 2
# SKIP: 0
# XFAIL: 0
# FAIL: 1
# XPASS: 0
# ERROR: 0
.. contents:: :depth: 2
FAIL: test-utils
================
/utils/date-basic: **
ERROR:test-utils.cc:51:void test_cases(const CaseVec&, ProcFunc): 'casus.expected == res' should be TRUE
FAIL test-utils (exit status: 134)
Can you check if adding something equivalent to tzdata
to nixpkg's check dependencies can help?
In Void Linux, with this new check deps, the test is passed inside chroot environment.
Because the test code use "Europe/Helsinki" as timezone, I think we should change it to "+0200" or something equivalent?
Thanks @sgn. Upgrading to 1.4.1 also seemed to have done the trick.
When I try to build version 1.0 on NixOS, a test fails: