vdirsyncer tests using hypothesis

  • Open
  • quality assurance status badge
Details
One participant
  • Efraim Flashner
Owner
unassigned
Submitted by
Efraim Flashner
Severity
normal
E
E
Efraim Flashner wrote on 28 Apr 2019 21:07
(address . bug-guix@gnu.org)
20190428190729.GB3104@macbook41
There are regularly two tests for vdirsyncer which fail when I build it
on my machine. I've resorted to running 'until guix build --no-grafts
vdirsyncer; do sleep 5; done', but this doesn't seem like a good
solution.

=================================== FAILURES ===================================
_________________________________ test_fuzzing _________________________________
tests/unit/test_metasync.py:129: in test_fuzzing
a=metadata, b=metadata,
E hypothesis.errors.FailedHealthCheck: Data generation is extremely slow: Only produced 4 valid examples in 1.01 seconds (1 invalid ones and 0 exceeded maximum size). Try decreasing size of the data you're generating (with e.g.max_size or max_leaves parameters).
E See https://hypothesis.readthedocs.io/en/latest/healthchecks.htmlfor more information about this. If you want to disable just this health check, add HealthCheck.too_slow to the suppress_health_check settings for this test.

Does anyone know how to work with hypothesis to fix this problem?


--
Efraim Flashner <efraim@flashner.co.il> ????? ?????
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEoov0DD5VE3JmLRT3Qarn3Mo9g1EFAlzF+fAACgkQQarn3Mo9
g1HqFw/+NQEMp/Ml7fGlJEEOITa+FlhJkkDAY/kw4Hk7GIu5fkn1JLGvkm67qEoh
eVBQZfLcak2QcC0khoS5y3qLy5wypGrtdnKQ4LEHSbhc7HsgcdSSR9+GMZF1qtze
LUhl/rdDwNoxfSDrGYhmYonMvPzGFlSDpy6Ih6dfdrIQeUNLv3TpPxz9/xAKPho+
9rO/ryfwyD5F0gg/yTqNNNKC64eDohm00OHQ8symFh1J5VxilPrwOrcEMeylqfLv
tEHzlaWG0mFxZrcs6GVN+yIvDla8XeeGgqZp/Rvsgm4CG8IGZGmQITxTqaz6GGfb
Y7IiX+NTtGVPcoyedboKAZgmjy+f8gNMaWO2Ajhi2SnCAIT7hsGAuTxFcDZUIgiV
C8IgjuljNXdx8mdOvJXIX4Z2T8KPtTTFkMfRjc+iej+VBa2ryj7e3SyyP4Iq6WQy
chrx5n7T0TZI/jDgFX/cn4gfU8aFPTOCWb/JBnRdLBHWA0dj3yLGst0ms29k1+pD
RrE2pQyPcZD3vyLiJzvydrSNzJcs0BgfOL/qnCZc5whop4Zcu8s4QtW0zgb9x5in
Rnm/lU4racs7iitvngAQnFgzJ+iEr9JPjFY+YFSuq9gmlKUfKYm9EwvVfbG5pRp1
Nony3kGqSa2SDy1vefQF00rua5ofcDonZFQuCMGh9NViQNLDU84=
=AeeV
-----END PGP SIGNATURE-----


?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 35477@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 35477
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch