diff options
author | Björn Gustavsson <[email protected]> | 2016-03-03 13:43:04 +0100 |
---|---|---|
committer | Björn Gustavsson <[email protected]> | 2016-03-03 13:50:26 +0100 |
commit | 5560415efb7cf2d361f63525bf599c5303c78f32 (patch) | |
tree | 6902ea94ab534e13cda5740bb0487a0157c78bb9 /lib/asn1/test/asn1.spec | |
parent | 9020ce9ab8347a781d4f761a1389bec4fd2bb468 (diff) | |
download | otp-5560415efb7cf2d361f63525bf599c5303c78f32.tar.gz otp-5560415efb7cf2d361f63525bf599c5303c78f32.tar.bz2 otp-5560415efb7cf2d361f63525bf599c5303c78f32.zip |
asn1_SUITE_value: Don't test the LDAP module
asn1ct:test(Mod) will generate sample values for data types
in an ASN.1 modules. The following definition from LDAP
can cause problems for asn1ct:test/1:
Filter ::= CHOICE {
and [0] SET SIZE (1..MAX) OF filter Filter,
or [1] SET SIZE (1..MAX) OF filter Filter,
not [2] Filter,
equalityMatch [3] AttributeValueAssertion,
substrings [4] SubstringFilter,
greaterOrEqual [5] AttributeValueAssertion,
lessOrEqual [6] AttributeValueAssertion,
present [7] AttributeDescription,
approxMatch [8] AttributeValueAssertion,
extensibleMatch [9] MatchingRuleAssertion,
... }
If we were unlucky (which we were on some computers), the construction
of sample values would not terminate.
Eliminate the problem for now by not testing the LDAP module. This
workaround should be removed when we have added some limitation to the
recursion in asn1ct_value when generating values.
Diffstat (limited to 'lib/asn1/test/asn1.spec')
0 files changed, 0 insertions, 0 deletions