Age | Commit message (Collapse) | Author |
|
On a computer which is fast, but with timers with low resolution,
the measured time for an empty queue could be zero, which could
cause the test case to fail.
Add a calibration function to scale up the amount the amount of
work so that the measured time will not be lower than 50 ms.
|
|
|
|
* msantos/tftp-wrap-block-counter/PR-965:
tftp: support transfer of files > 65535 blocks
|
|
* maint:
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.
|
|
test_server:start_node does no longer add the test_server path to the
new node, since the needed code is present in the default path. This
caused two test cases in code_SUITE to fail.
code_SUITE:mult_lib_roots: Expected the test_server path to be first
in the code path. This check is removed.
code_SUITE:bad_erl_libs: Started a node with "-env ERL_LIBS ",
i.e. not giving any value to the ERL_LIBS variable. This test
succeeded by accident, since the combination with arguments set by
test_server_node.erl and by slave.erl caused the node start to work,
and no further checks were present in the test. This part of the test
case is now removed.
|
|
test_server_sup:crash_dump_dir() is expected to return {ok,Dir}, but
if there was no test framework set, then it would return just 'ok'. To
avoid crash, the function will no returm {ok,Cwd} if no framework is
set.
|
|
* bjorn/compiler/binary-comprehensions/OTP-13289:
Generalize bit string comprehensions
|
|
* bjorn/remove-test_server/OTP-12705:
Remove multiple inclusion of ct.hrl
otp_SUITE: Remove handling of test_server application
Correct common_test.app.src
|
|
* egil/basedir-directories/OTP-13392:
stdlib: Add filename:basedir/2,3
stdlib: Use parallel groups in filename_SUITE
stdlib: Remove ?line macros in filename_SUITE
|
|
|
|
|
|
|
|
|
|
* legoscia/tls_ipv6_dist:
Add inet6_tls_dist, for TLS distribution over IPv6
Conflicts:
lib/ssl/src/ssl_tls_dist_proxy.erl
OTP-13391
|
|
|
|
* ia/inets/httpd-gracefull-error/OTP-13389:
inets: No error reports for expected termination
|
|
|
|
* siri/ct_netconfc/log-open-close/OTP-13386:
Log open and close of netconf connections
|
|
* siri/appups-19.0:
Update appups in kernel, stdlib and sasl for OTP-19
|
|
|
|
* siri/ct_release_test/remove-test_server:
Remove application test_server from ct_release_test
|
|
* ia/public_key/missinig-nl/OTP-13381:
public_key: An encapsulated PEM header shall be followed by a blank line
|
|
|
|
* siri/crashdump-dir/OTP-13388:
Set dir for slave node's erl_crash.dump
|
|
|
|
This was earlier filename:dirname(code:which(test_server)). On
Microsoft Windows, this pointed to a directory under c:/Program Files,
and in later versions this directory is no longer writable. The
framework (common_test) log dir is now used instead.
|
|
Since test_server is no longer an own application, it shall not be
added to the releases create by ct_release_test.
|
|
* sverk/master/halt-INT_MIN:
erts: Make erlang:halt() accept bignums as Status
erts: Change erl_exit into erts_exit
kernel: Remove calls to erl_exit
|
|
OTP-13251
* sverk/halt-INT_MIN:
erts: Make erlang:halt() accept bignums as Status
erts: Change erl_exit into erts_exit
kernel: Remove calls to erl_exit
|
|
|
|
* msantos/epmd-IPv6-node-reg2/PR-864/OTP-13364:
epmd: support IPv6 node registration
|
|
The expression in a bit string comprehension is limited to a
literal bit string expression. That is, the following code
is legal:
<< <<X>> || X <- List >>
but not this code:
<< foo(X) || X <- List >>
The limitation is annoying. For one thing, tools that transform
the abstract format must be careful not to produce code such as:
<< begin
%% Some instrumentation code.
<<X>>
end || X <- List >>
One reason for the limitation could be that we'll get
reduce/reduce conflicts if we try to allow an arbitrary
expression in a bit string comprehension:
binary_comprehension -> '<<' expr '||' lc_exprs '>>' :
{bc,?anno('$1'),'$2','$4'}.
Unfortunately, there does not seem to be an easy way to work
around that problem. The best we can do is to allow 'expr_max'
expressions (as in the binary syntax):
binary_comprehension -> '<<' expr_max '||' lc_exprs '>>' :
{bc,?anno('$1'),'$2','$4'}.
That will work, but functions calls must be enclosed in
parentheses:
<< (foo(X)) || X <- List >>
|
|
If synced callbacks arrive early before the return value from
init had been synced to proc_lib. The callbacks where ignored.
Added a short timeout to avoid the scheduling raise but we don't want
block the wxe_server in case of deadlock in init, so sleep for a short
while and check again, and drop the callback when init takes to long.
|
|
|
|
|
|
Commit 4cf832f1ad163f5b25dd8a6f2d314c169c23c82f erroneously removed
logging of open and close of netconf connections. This is now
corrected.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OTP-13164 more efficient peer lookup
OTP-13342 remote watchdog transition into state SUSPECT
|
|
RFC 1421 Privacy Enhancement for Electronic Mail February 1993
Encapsulated Message
Pre-Encapsulation Boundary (Pre-EB)
-----BEGIN PRIVACY-ENHANCED MESSAGE-----
Encapsulated Header Portion
(Contains encryption control fields inserted in plaintext.
Examples include "DEK-Info:" and "Key-Info:".
Note that, although these control fields have line-oriented
representations similar to RFC 822 header fields, the set
of fields valid in this context is disjoint from those used
in RFC 822 processing.)
Blank Line
(Separates Encapsulated Header from subsequent
Encapsulated Text Portion)
Encapsulated Text Portion
(Contains message data encoded as specified in Section 4.3.)
Post-Encapsulation Boundary (Post-EB)
-----END PRIVACY-ENHANCED MESSAGE-----
|
|
|
|
|