serf package (guix dependency) tests fail

  • Done
  • quality assurance status badge
Details
3 participants
  • Leo Famulari
  • Maxim Cournoyer
  • Marius Bakke
Owner
unassigned
Submitted by
Maxim Cournoyer
Severity
normal
M
M
Maxim Cournoyer wrote on 26 Apr 2017 23:18
(name . bug-guix)(address . bug-guix@gnu.org)
CAN-vT6SND3qZrte0pu3o98U-+LFFfDnzV7CgBdMZKZPp0-ZXzw@mail.gmail.com
Hello Guix!

While attempting to "guix environment guix" after doing a "git pull"
in my guix checkout (master), it attempted to build many packages
(bash, gcc, etc.) and failed building `serf' due to test failures:

............F.FFF.FFF.FF.FFFFF...................................

There were 14 failures:
1) test_ssl_trust_rootca: test/test_util.c:438: expected <0> but was <120199>
2) test_ssl_certificate_chain_with_anchor: test/test_util.c:438:
expected <0> but was <120199>
3) test_ssl_certificate_chain_all_from_server: test/test_util.c:438:
expected <0> but was <120199>
4) test_ssl_no_servercert_callback_allok: test/test_util.c:438:
expected <0> but was <120170>
5) test_ssl_large_response: test/test_util.c:438: expected <0> but was <120170>
6) test_ssl_large_request: test/test_util.c:438: expected <0> but was <120170>
7) test_ssl_client_certificate: test/test_util.c:438: expected <0> but
was <120170>
8) test_ssl_future_server_cert: test/test_util.c:438: expected <0> but
was <120199>
9) test_setup_ssltunnel: test/test_util.c:438: expected <0> but was <120170>
10) test_ssltunnel_basic_auth: test/test_context.c:2116: expected <0>
but was <120170>
11) test_ssltunnel_basic_auth_server_has_keepalive_off:
test/test_context.c:2116: expected <0> but was <120170>
12) test_ssltunnel_basic_auth_proxy_has_keepalive_off:
test/test_context.c:2116: expected <0> but was <120170>
13) test_ssltunnel_basic_auth_proxy_close_conn_on_200resp:
test/test_context.c:2116: expected <0> but was <120170>
14) test_ssltunnel_digest_auth: test/test_util.c:438: expected <0> but
was <120170>

!!!FAILURES!!!
Runs: 65 Passes: 51 Fails: 14

== Testing test/testcases/simple.response ==
== Testing test/testcases/chunked.response ==
== Testing test/testcases/deflate.response ==
== Testing test/testcases/chunked-trailers.response ==
== Testing test/testcases/chunked-empty.response ==
== Running the unit tests ==
ERROR: test(s) failed in test_all
scons: *** [check] Error 1
scons: building terminated because of errors.
phase `check' failed after 51.6 seconds
builder for `/gnu/store/sgavfd7s3f4xixvfhdqb2nn77fvbf63q-serf-1.3.8.drv'
failed with exit code 1
@ build-failed /gnu/store/sgavfd7s3f4xixvfhdqb2nn77fvbf63q-serf-1.3.8.drv
- 1 builder for
`/gnu/store/sgavfd7s3f4xixvfhdqb2nn77fvbf63q-serf-1.3.8.drv' failed
with exit code 1
guix build: error: build failed: build of
`/gnu/store/sgavfd7s3f4xixvfhdqb2nn77fvbf63q-serf-1.3.8.drv' failed

This particular output was triggered by runnnig "guix build --check
serf" on a foreign distro, but I also had serf test failures on
GuixSD.

Maxim
M
M
Marius Bakke wrote on 27 Apr 2017 15:54
87bmric5x6.fsf@fastmail.com
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:

Toggle quote (37 lines)
> Hello Guix!
>
> While attempting to "guix environment guix" after doing a "git pull"
> in my guix checkout (master), it attempted to build many packages
> (bash, gcc, etc.) and failed building `serf' due to test failures:
>
> ............F.FFF.FFF.FF.FFFFF...................................
>
> There were 14 failures:
> 1) test_ssl_trust_rootca: test/test_util.c:438: expected <0> but was <120199>
> 2) test_ssl_certificate_chain_with_anchor: test/test_util.c:438:
> expected <0> but was <120199>
> 3) test_ssl_certificate_chain_all_from_server: test/test_util.c:438:
> expected <0> but was <120199>
> 4) test_ssl_no_servercert_callback_allok: test/test_util.c:438:
> expected <0> but was <120170>
> 5) test_ssl_large_response: test/test_util.c:438: expected <0> but was <120170>
> 6) test_ssl_large_request: test/test_util.c:438: expected <0> but was <120170>
> 7) test_ssl_client_certificate: test/test_util.c:438: expected <0> but
> was <120170>
> 8) test_ssl_future_server_cert: test/test_util.c:438: expected <0> but
> was <120199>
> 9) test_setup_ssltunnel: test/test_util.c:438: expected <0> but was <120170>
> 10) test_ssltunnel_basic_auth: test/test_context.c:2116: expected <0>
> but was <120170>
> 11) test_ssltunnel_basic_auth_server_has_keepalive_off:
> test/test_context.c:2116: expected <0> but was <120170>
> 12) test_ssltunnel_basic_auth_proxy_has_keepalive_off:
> test/test_context.c:2116: expected <0> but was <120170>
> 13) test_ssltunnel_basic_auth_proxy_close_conn_on_200resp:
> test/test_context.c:2116: expected <0> but was <120170>
> 14) test_ssltunnel_digest_auth: test/test_util.c:438: expected <0> but
> was <120170>
>
> !!!FAILURES!!!
> Runs: 65 Passes: 51 Fails: 14

The SSL certificates in "test/server" expired 18/04.


I'll try to port this patch, but "viewvc" can't give binary diffs, so
will have to clone it locally first.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkB+AYACgkQoqBt8qM6
VPqhPgf/Qgm19j4uWg96CwilOgTvmInBdQoQa30LP+2Einz7C6OBHoKh6isj+P52
CzwwEwJcbd4JaQrM2QZHrbuRyYzJNzM8bxh6UuJ9SZQgVfORUqG6Hz2iwTJ5mGWi
waULi+JCW0qNCSkfq2LZrcOUMlNQT//dgGCiht//4A7h62PnzLXmNtTO9RuE0fFA
/zXIPew43gHmdBS8+JNan2WjOqDM9cUstivtwkuO3G+erblNCtplRDUpFFEgKGPR
LpRlY6TQgXt9Ru9eRBpNvr3TyP5rT/1I+Gzlsf6Ukx7yr2k57KjODe5ARylzkng4
KM5t5w5Gi0zH+CSZwJ7H/U9ZfZ4a2Q==
=V6Qw
-----END PGP SIGNATURE-----

M
M
Marius Bakke wrote on 27 Apr 2017 16:19
878tmmc4rd.fsf@fastmail.com
Marius Bakke <mbakke@fastmail.com> writes:

Toggle quote (46 lines)
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hello Guix!
>>
>> While attempting to "guix environment guix" after doing a "git pull"
>> in my guix checkout (master), it attempted to build many packages
>> (bash, gcc, etc.) and failed building `serf' due to test failures:
>>
>> ............F.FFF.FFF.FF.FFFFF...................................
>>
>> There were 14 failures:
>> 1) test_ssl_trust_rootca: test/test_util.c:438: expected <0> but was <120199>
>> 2) test_ssl_certificate_chain_with_anchor: test/test_util.c:438:
>> expected <0> but was <120199>
>> 3) test_ssl_certificate_chain_all_from_server: test/test_util.c:438:
>> expected <0> but was <120199>
>> 4) test_ssl_no_servercert_callback_allok: test/test_util.c:438:
>> expected <0> but was <120170>
>> 5) test_ssl_large_response: test/test_util.c:438: expected <0> but was <120170>
>> 6) test_ssl_large_request: test/test_util.c:438: expected <0> but was <120170>
>> 7) test_ssl_client_certificate: test/test_util.c:438: expected <0> but
>> was <120170>
>> 8) test_ssl_future_server_cert: test/test_util.c:438: expected <0> but
>> was <120199>
>> 9) test_setup_ssltunnel: test/test_util.c:438: expected <0> but was <120170>
>> 10) test_ssltunnel_basic_auth: test/test_context.c:2116: expected <0>
>> but was <120170>
>> 11) test_ssltunnel_basic_auth_server_has_keepalive_off:
>> test/test_context.c:2116: expected <0> but was <120170>
>> 12) test_ssltunnel_basic_auth_proxy_has_keepalive_off:
>> test/test_context.c:2116: expected <0> but was <120170>
>> 13) test_ssltunnel_basic_auth_proxy_close_conn_on_200resp:
>> test/test_context.c:2116: expected <0> but was <120170>
>> 14) test_ssltunnel_digest_auth: test/test_util.c:438: expected <0> but
>> was <120170>
>>
>> !!!FAILURES!!!
>> Runs: 65 Passes: 51 Fails: 14
>
> The SSL certificates in "test/server" expired 18/04.
>
> https://svn.apache.org/viewvc?view=revision&revision=1792234
>
> I'll try to port this patch, but "viewvc" can't give binary diffs, so
> will have to clone it locally first.

Apparently "patch" does not yet support binary diffs either:

patching file test/test_buckets.c
Hunk #1 succeeded at 1232 (offset -91 lines).
patching file test/server/serfcacert.pem
File test/server/serfclientcert.p12: git binary diffs are not supported.
patching file test/server/serfrootcacert.pem
patching file test/server/serfserver_expired_cert.pem
patching file test/server/serfserver_future_cert.pem
patching file test/server/serfservercert.pem
patching file test/server/serfserverkey.pem
source is under 'serf-1.3.8'
applying '/gnu/store/qbh97afjjgkn332f8ncn6k8pg74wfc8w-serf-comment-style-fix.patch'...
applying '/gnu/store/vk533j8s56nhlzz2hnqn853xb9yl6b6y-serf-update-test-certificates.patch'...
builder for `/gnu/store/3kcz9as8i986fxqj368n6cg3k7nhj7cq-serf-1.3.8.tar.xz.drv' failed to produce output path `/gnu/store/n4479kx0qx8rblzqnwgxg7jnp1x1xyjh-serf-1.3.8.tar.xz'

I'll try to run `git apply` in a phase instead, although that will
almost double the reverse dependencies of "git".
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkB/eYACgkQoqBt8qM6
VPpIIQgAlViBBjMmwKkvFWGJ0gm2PyNixswM71BRBZsbIHP5xrA8IIQiL7jKVbj4
5c7HfnSEYCixhWYkEShOHw1qjlU2VZ8z996hDTYNm3IjiNuA8tDKnPggHUp8Aqb8
Y1uitQMyPqU/6tN3J9/JyDvJXrZiqQjIAz8rRGpS7vkKPYUH4tTEyyPxzfb0jEc6
pUKgOdYO9C4ruMwv6PKQpvuB7OW6I1LEHqManNj2nHtXRa2k5atFPCiy9CVdcZim
tJZnC07w8XOyqHd1XPEFZWyyz04ErpAiU/pC1DPVUMF/O5V9E2ub4e1AACpZVbeo
nqu1wJi6OmdtvXKQBRqhrZ2rFTwqpg==
=Q+g9
-----END PGP SIGNATURE-----

M
M
Marius Bakke wrote on 27 Apr 2017 16:39
8760hpdidj.fsf@fastmail.com
Marius Bakke <mbakke@fastmail.com> writes:

Toggle quote (67 lines)
> Marius Bakke <mbakke@fastmail.com> writes:
>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>
>>> Hello Guix!
>>>
>>> While attempting to "guix environment guix" after doing a "git pull"
>>> in my guix checkout (master), it attempted to build many packages
>>> (bash, gcc, etc.) and failed building `serf' due to test failures:
>>>
>>> ............F.FFF.FFF.FF.FFFFF...................................
>>>
>>> There were 14 failures:
>>> 1) test_ssl_trust_rootca: test/test_util.c:438: expected <0> but was <120199>
>>> 2) test_ssl_certificate_chain_with_anchor: test/test_util.c:438:
>>> expected <0> but was <120199>
>>> 3) test_ssl_certificate_chain_all_from_server: test/test_util.c:438:
>>> expected <0> but was <120199>
>>> 4) test_ssl_no_servercert_callback_allok: test/test_util.c:438:
>>> expected <0> but was <120170>
>>> 5) test_ssl_large_response: test/test_util.c:438: expected <0> but was <120170>
>>> 6) test_ssl_large_request: test/test_util.c:438: expected <0> but was <120170>
>>> 7) test_ssl_client_certificate: test/test_util.c:438: expected <0> but
>>> was <120170>
>>> 8) test_ssl_future_server_cert: test/test_util.c:438: expected <0> but
>>> was <120199>
>>> 9) test_setup_ssltunnel: test/test_util.c:438: expected <0> but was <120170>
>>> 10) test_ssltunnel_basic_auth: test/test_context.c:2116: expected <0>
>>> but was <120170>
>>> 11) test_ssltunnel_basic_auth_server_has_keepalive_off:
>>> test/test_context.c:2116: expected <0> but was <120170>
>>> 12) test_ssltunnel_basic_auth_proxy_has_keepalive_off:
>>> test/test_context.c:2116: expected <0> but was <120170>
>>> 13) test_ssltunnel_basic_auth_proxy_close_conn_on_200resp:
>>> test/test_context.c:2116: expected <0> but was <120170>
>>> 14) test_ssltunnel_digest_auth: test/test_util.c:438: expected <0> but
>>> was <120170>
>>>
>>> !!!FAILURES!!!
>>> Runs: 65 Passes: 51 Fails: 14
>>
>> The SSL certificates in "test/server" expired 18/04.
>>
>> https://svn.apache.org/viewvc?view=revision&revision=1792234
>>
>> I'll try to port this patch, but "viewvc" can't give binary diffs, so
>> will have to clone it locally first.
>
> Apparently "patch" does not yet support binary diffs either:
>
> patching file test/test_buckets.c
> Hunk #1 succeeded at 1232 (offset -91 lines).
> patching file test/server/serfcacert.pem
> File test/server/serfclientcert.p12: git binary diffs are not supported.
> patching file test/server/serfrootcacert.pem
> patching file test/server/serfserver_expired_cert.pem
> patching file test/server/serfserver_future_cert.pem
> patching file test/server/serfservercert.pem
> patching file test/server/serfserverkey.pem
> source is under 'serf-1.3.8'
> applying '/gnu/store/qbh97afjjgkn332f8ncn6k8pg74wfc8w-serf-comment-style-fix.patch'...
> applying '/gnu/store/vk533j8s56nhlzz2hnqn853xb9yl6b6y-serf-update-test-certificates.patch'...
> builder for `/gnu/store/3kcz9as8i986fxqj368n6cg3k7nhj7cq-serf-1.3.8.tar.xz.drv' failed to produce output path `/gnu/store/n4479kx0qx8rblzqnwgxg7jnp1x1xyjh-serf-1.3.8.tar.xz'
>
> I'll try to run `git apply` in a phase instead, although that will
> almost double the reverse dependencies of "git".

Never mind, "serf" is already a dependency of git (through
"subversion"), so this did not work very well..

Perhaps we could have a "git-minimal" for cases like this? I suppose
that could be useful for "git-fetch" as well. I'll give that a go
shortly, unless there are better suggestions.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkCArgACgkQoqBt8qM6
VPqehwf/ZrPRuj9LMYGV1VaNUk4L56CWNIrnoeUIw41wBVeSTop4e7T/gZx8MGHi
FW/I84yE0m+tdZ0znPMdOeLZvhejl2dUGxHDcA1Iw1+yGxuqGbn0CsL/bR4ke+Ac
t9SgwfQf8dpdH8MXZAVzImQcz9HNEz6y7DPqH7jnKlD31W9f1k2Z5sBJAyaLifHU
ReHsDMF7EDFoG/qnSw1GSf9TYWRPP/Bk+btml4V4FwJAAiaiKTdCQSebz/YujxBp
2Vs+TZUDPSwzmZ5CL3yfN+0S3WJuVDsKKc+5mkhBMfJ0XdTh+NlLuNB/H4fetLx6
4ka55f/3ukuNnFzOnCQOZ9MSWT2gXg==
=MUgr
-----END PGP SIGNATURE-----

L
L
Leo Famulari wrote on 27 Apr 2017 16:58
(name . Marius Bakke)(address . mbakke@fastmail.com)
20170427145817.GA32045@jasmine
On Thu, Apr 27, 2017 at 04:19:18PM +0200, Marius Bakke wrote:
Toggle quote (7 lines)
> Apparently "patch" does not yet support binary diffs either:
>
> patching file test/test_buckets.c
> Hunk #1 succeeded at 1232 (offset -91 lines).
> patching file test/server/serfcacert.pem
> File test/server/serfclientcert.p12: git binary diffs are not supported.

Perhaps we should avoid using binary patches in Guix, but I think you
could use a patch with a binary diff by passing '--binary' to
(patch-flags). I haven't tested it, however.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlkCBwYACgkQJkb6MLrK
fwjDFw//dC3ZHyR8TD3D2SJPEAbrhMTstLWQPId1QYDniVFrWoFRbEaYMkbMNr41
W+tP3F6K+nH9F5n88KnYygJSQf3J5AzrLnLlGdpFvTkf+K5F3jZnIFezRR/Zdqp3
fAO6DxHWVxZeUF6BdqmxqZBiBi14RaScwHpfY4JPPRWdV0gfHBwubqIsqZZ2YZeN
w4cMwyCP99iA9lYo9I7BcVJrTx5WMZggSk8rJCGtHxALdF2ws62k8J5nCAjKswRx
NyJ8OdLq4h//k9JGJCdsNHh5N6HxhIDDDm/UnNByn38DY7q4RPGwdqQfnxMeuAbW
MXxXJOVsvD2Snv0Z5Qlxth0ewkWiaSKabcqhJQR82i33fjOOsCqSJZXFQbmUN5D4
7/CK/nallhDHBtjeYlXVSgjlrlTjclwykfh8/3Zh8naaJcaBhNnucGh1x7l4GPqH
LoTKDaYqSCw45FjB1fkz7gMlRE3jzMAWBcUsjgE6orgsh/IqEJoD6EGaY9uIgKEi
bevhunGgZRFruv5Gh8cgRwbvi689z9E1lzbPclVnOCkutjyza6UWHjkgRbcc850h
ixD55a3bFTxpCwUMf1dfYuwAXPV3t1stR+JZdRBXQxnoIXGmx8N96lDWuSz4gjsn
diZKan6UDQVGFZtjUrL/PpDtBe3AIZSZtDMpxnzHQMzGIVqr7xg=
=l5+g
-----END PGP SIGNATURE-----


L
L
Leo Famulari wrote on 27 Apr 2017 17:04
(name . Marius Bakke)(address . mbakke@fastmail.com)
20170427150443.GB32045@jasmine
On Thu, Apr 27, 2017 at 03:54:13PM +0200, Marius Bakke wrote:
Toggle quote (8 lines)
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> >
> > While attempting to "guix environment guix" after doing a "git pull"
> > in my guix checkout (master), it attempted to build many packages
> > (bash, gcc, etc.) and failed building `serf' due to test failures:
> >
> > ............F.FFF.FFF.FF.FFFFF...................................

[...]

Toggle quote (5 lines)
> > !!!FAILURES!!!
> > Runs: 65 Passes: 51 Fails: 14
>
> The SSL certificates in "test/server" expired 18/04.

Terrible! This invalidates the entire dependency tree based on serf. In
effect, it enforces an expiration date on these packages.

Toggle quote (2 lines)
Rather than using this workaround, which will stop working 2018-09-19,
we should disable this test. We should also file an upstream bug asking
them to fudge the date in their tests, so that we can run this test
suite forever. GnuTLS uses this technique with the 'datefudge' tool.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlkCCIsACgkQJkb6MLrK
fwjaoA//Y2G6hkBeh4xnd9ka0SR+r2ZGG/4S61mx7C5jIraZhZrIVD/+NNSkJv+t
O1g8em3uoODmnI1TFs3XY1tRsmTZJttdLpG2/kZ9AZLLFtfF1hmkzuj4ZEfjr/Mn
2Xnzf5W+JpVA4hEDynFFqxBNdztnEr1fjjI/1KrNbZ+Yh2oTqk5pISnwbl8AuiAx
eq0bjBdx/2NxkWIUPsqAzovIXLqgO1CQ64vzvta+4VleoTX4MrwZyHQ/Q5W2/Ycu
NIVRWm8Hk9h8JRZiJuOdW2uZVBfx+lkllI9/pyM+zOcfpgcRJhwjH5H8l1oigvCV
SNDJ72D5FoQ8kyxO0Xz29CZaf82s6s3FqWtCUVs4R2afEEI6swyP2h/dKbK4fjLI
xrQRIG4nOib3JIzVuq075riE87sKklPJrQrzX6AK2AiQqFw2h3fhmG0Q1C2ZIRS/
Z5EiP7TipmF0xEDEhfJ+m1hv00yvzYnzUnwgN9QtYudhEXboZvsHdM6YgwsEGZhL
wzFZh3xyDKCqAP794RUZ8xa3fik6a3YQkghUzjRcGdmFFItjPguhEXHrk4pAXMot
eIivXO34BrZkI9hjAxa7zUQan+yAFWFwM0xxm/Qjcw1IrdBxJ+bSeWjAFt3dCjVx
urj2QFJHzVCdiuopQ1alml1xnddixkBYYBW+nYJ0Tjkov2TtmdE=
=KoXj
-----END PGP SIGNATURE-----


M
M
Marius Bakke wrote on 27 Apr 2017 17:16
(name . Leo Famulari)(address . leo@famulari.name)
8737ctdgp1.fsf@fastmail.com
Leo Famulari <leo@famulari.name> writes:

Toggle quote (19 lines)
> On Thu, Apr 27, 2017 at 03:54:13PM +0200, Marius Bakke wrote:
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> >
>> > While attempting to "guix environment guix" after doing a "git pull"
>> > in my guix checkout (master), it attempted to build many packages
>> > (bash, gcc, etc.) and failed building `serf' due to test failures:
>> >
>> > ............F.FFF.FFF.FF.FFFFF...................................
>
> [...]
>
>> > !!!FAILURES!!!
>> > Runs: 65 Passes: 51 Fails: 14
>>
>> The SSL certificates in "test/server" expired 18/04.
>
> Terrible! This invalidates the entire dependency tree based on serf. In
> effect, it enforces an expiration date on these packages.

Good point. We should definitely avoid this.

Toggle quote (7 lines)
>
> Rather than using this workaround, which will stop working 2018-09-19,
> we should disable this test. We should also file an upstream bug asking
> them to fudge the date in their tests, so that we can run this test
> suite forever. GnuTLS uses this technique with the 'datefudge' tool.

Interesting, I was not aware of "datefudge".

I'll disable these tests for now and create an upstream issue once I've
learned more about the datefudge tool.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkCCzoACgkQoqBt8qM6
VPoSlAgA1Wa3EMIvAmn3GYWBu06ASXUkU99ULV3HmdmH6CvDTLAwYqFAjKPxyo7+
K1cGbrCeGPCfMdFE/KmT6fQKtTNJewdVXqen9iW+ehRtkc+tMXV+bkp8EFdfEdly
RzB09f18Tk6rjM/B5S5ukRPAnIdQFu8xkNMU8v/BRKd+ip+M4XJRnBAndcZzHjVF
ZJbq+9XMbetXvE850qdMuIeUZN9HrpkYX/G7zIU3BJWHt3K0IIPOK6lKnRKu9Pz2
TfuFuc/8yfVFtNK9T7ULNJqg8UUy2vXBUC3JW2G2Q7rsDUcfI6EaJdWgaYLj+Rjl
cvZHLH/IxHDI44NrKrwLovBT03fBNw==
=PXeO
-----END PGP SIGNATURE-----

M
M
Marius Bakke wrote on 27 Apr 2017 18:01
(name . Leo Famulari)(address . leo@famulari.name)
87zif1c00w.fsf@fastmail.com
Marius Bakke <mbakke@fastmail.com> writes:
Toggle quote (13 lines)
> Leo Famulari <leo@famulari.name> writes:
>>> https://svn.apache.org/viewvc?view=revision&revision=1792234
>>
>> Rather than using this workaround, which will stop working 2018-09-19,
>> we should disable this test. We should also file an upstream bug asking
>> them to fudge the date in their tests, so that we can run this test
>> suite forever. GnuTLS uses this technique with the 'datefudge' tool.
>
> Interesting, I was not aware of "datefudge".
>
> I'll disable these tests for now and create an upstream issue once I've
> learned more about the datefudge tool.

I disabled these tests in decb4c26fa1c748b118e33495d5493d84a6ca6c9 and
also pushed an update for 1.3.9.

Leaving this bug open until the upstream issue is created so it can be
added here as a reference.
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkCFd8ACgkQoqBt8qM6
VPqRPwf/S8697G+ZP/YDE1vheNC6Aofz/HoEpnm6/GzPHxNkyzf5120esXawSGVN
KFlr350BDgGNGuGwbhT78Uzl6kj0IqI+l7KRMKPwXqAtXXvGjlb2VA3gRQhn+sJW
/P5O73jO4+bDADaqG3ipguAI17IYolaWo3MzTSJAzC8XBw+OM7f2yl7RGOVdZiqd
nTPVdec17bLE/yGkd+9Bg3AMK1n8rermA26kF9nzkUIwub/qj0HAL70BWyUc93Vs
x9tBWHYNsDVTNC3EOaK3kmA+GBNWu7+jbrrYCRYNIBYOHJAaoB9e97JBUyXyDX+s
ATqpOuIm60oddbyDbnm6pqfK1eGRQg==
=TOD8
-----END PGP SIGNATURE-----

M
M
Maxim Cournoyer wrote on 27 Apr 2017 19:13
(address . 26671@debbugs.gnu.org)
A99D015D-C513-47D2-8969-2D92289261C5@gmail.com
On April 27, 2017 9:01:35 AM PDT, Marius Bakke <mbakke@fastmail.com> wrote:
Toggle quote (23 lines)
>Marius Bakke <mbakke@fastmail.com> writes:
>> Leo Famulari <leo@famulari.name> writes:
>>>> https://svn.apache.org/viewvc?view=revision&revision=1792234
>>>
>>> Rather than using this workaround, which will stop working
>2018-09-19,
>>> we should disable this test. We should also file an upstream bug
>asking
>>> them to fudge the date in their tests, so that we can run this test
>>> suite forever. GnuTLS uses this technique with the 'datefudge' tool.
>>
>> Interesting, I was not aware of "datefudge".
>>
>> I'll disable these tests for now and create an upstream issue once
>I've
>> learned more about the datefudge tool.
>
>I disabled these tests in decb4c26fa1c748b118e33495d5493d84a6ca6c9 and
>also pushed an update for 1.3.9.
>
>Leaving this bug open until the upstream issue is created so it can be
>added here as a reference.

Thanks! :)
M
M
Marius Bakke wrote on 8 May 2017 13:46
(name . Leo Famulari)(address . leo@famulari.name)
87a86ny3k7.fsf@fastmail.com
Marius Bakke <mbakke@fastmail.com> writes:

Toggle quote (3 lines)
> Leaving this bug open until the upstream issue is created so it can be
> added here as a reference.

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAlkQWngACgkQoqBt8qM6
VPonvQgAqvWMhfVNVCpGqu22UErwZOGAwHluKy4uccSpRoL7M5pw9w8xH7zyqpI+
YgETPO71mMNTfZ5W5vD/zQje475lgfXAMWXF52TZODpaEs4IFsY0+uHozguoaDio
/tY/G3lt9viAfl7MfepmHjZHrcHHmhVxzYA0ujkPjDjY0O10MGmUwqAQ+oJKAeBf
vrH6Thfq3d3JW2bP232NNB3tLYvLYRCV5jWg9C+Pnt6vP+LejzzFRH0Oqq3B4VP0
sSW1Y66JLH1XHviIRXm97x5BfYYHTCgaWwVwpnHNoieCIgrRB1L5R1mgyi63gd0+
yHYxWhbZMTT7rHs+Ie2o41w4TAFTOQ==
=LRgi
-----END PGP SIGNATURE-----

Closed
?