| Age | Commit message (Collapse) | Author |
|---|
|
Line numbering of erlang files that were not correctly indented could
be wrong after coverting to html with erl2html2:convert/[2,3]. This has
been corrected.
This commit also fixes the following:
* There are now link targets for each line and not only for each 10th
line - meaning that links from test logs are now to the exact line,
and not to the last number for which N rem 10 == 0.
* there will only be one link target per function, i.e. the faulty
link targets for function clauses are removed.
* link targets for function now includes the arity (e.g. func/1 has a
link target "func-1")
And some tests are added.
|
|
|
|
* siri/common_test/ct_netconfc-close-problems:
[common_test] Allow server to terminate netconf session before rpc-reply
[common_test] Ensure process down after ct_netconf:close_session
|
|
test_server_h will now recognize info_reports written by ct connection
handlers (according to the description in cth_conn_log) and ignore
them as they will be completely handled by by ct_conn_log_h.
Earlier test_server_h would print a tag (testcase name) before
forwarding the report to error_logger_tty_h. This would cause lots of
tags in the log with no info report following (since
error_logger_tty_h did not handle them).
|
|
* vd/jinterface_epmd_localhost:
OtpEpmd.lokupNames() may hang if network is badly configured
OTP-10579
|
|
OTP-10570
ct_netconfc:close_session sometimes returned {error,closed} because
the ssh connection was closed (from the server side) before the
rpc-reply was received by the client. This is normal and can not be
helped. It has been corrected so the return will be 'ok' in this case.
Other error situations will still give {error,Reason}.
|
|
OTP-10510
When starting a named netconf connection directly after stopping one
with the same name, it sometimes failed with 'connection_exists'. This
has been corrected.
|
|
Conflicts:
lib/ssl/src/ssl_connection.erl
|
|
* ia/ssl/terminate-handling/OTP-10574:
ssl: Make sure that the ssl connection process will not hang in terminate function.
ssl: Add default values to emulated socket options in internal record
|
|
function.
Avoid doing gen_tcp/inet socket operations in terminate if socket
is already closed. Call gen_tcp:recv/3 in the "data delivery workaround"
to avoid hanging.
|
|
The absence of the active default values could cause a process leak
|
|
* maint:
Fix compiler crash for binary matching and a complicated guard
|
|
* bjorn/compiler/binary-matching/OTP-10567:
Fix compiler crash for binary matching and a complicated guard
|
|
|
|
* maint:
Ssh appup modifications
Updated appup for ssh
Bumped revision
Removed some testing variables
ssh_opts is now a proper list
After auth rsa and dsa passwords is set to undefined
Removing the password after auth
|
|
* fredrik/ssh-password-conf/OTP-10511:
Ssh appup modifications
Updated appup for ssh
Bumped revision
Removed some testing variables
ssh_opts is now a proper list
After auth rsa and dsa passwords is set to undefined
Removing the password after auth
|
|
|
|
* maint:
Fix bug where require of same name at same config would return name in use
|
|
|
|
* upstream/maint:
ssl: Do not use gen_fsm:sync_send_all_state_event/3 timeout
|
|
The gen_fsm:sync_send_all_state_event/3 timout is a client side timeout.
If timeouts are needed we want them to be server side timeouts.
|
|
* maint:
Doc for quiet_mode
SSH quiet mode
|
|
* fredrik/ssh-quiet-mode/OTP-10429:
Doc for quiet_mode
SSH quiet mode
|
|
|
|
|
|
* bjorn/ct/minor-corrections:
test_server_io: Correct a few comments
Handle ct:abort_current_testcase/1 when executing parallel groups
Make sure that "Cover analysing..." is written to stdout
Make sure that "Testing..." is not written if testing has finished
|
|
* bjorn/test_server/remove-remote-target-support:
Remove stale support for remote target nodes
|
|
The support for remote target nodes has not worked in a long time.
We are unlikely to ever need remot target node support and if
we'll need it will be easier to start over from scratch.
|
|
|
|
* anders/diameter/upgrade/OTP-10550:
Allow for no diameter on remote node in connection guard
|
|
* anders/diameter/peer_mapping/OTP-10470:
Document peer_ref() service_info
Use peer_ref() service_info in traffic suite
Add service_info for a peer_ref()
|
|
* anders/diameter/shared_transport/OTP-10443:
Use multiple connections in traffic suite
Implement service_opt() restrict_connections
Document service_opt() restrict_connections
|
|
* anders/diameter/sequence_masks/OTP-10445:
Redo watchdog test suite
Update/clarify some comments
Add reopen message from watchdog
Add options service_info
Add diameter_reg:wait/1
Clarify diameter_transport doc
Remove pre-OTP configure support
Remove obsolete make target
Use sequence masks in test suites
Implement sequence masks
Document sequence masks
|
|
Since the support for parameterized modules will be removed in R16,
we should not use them in test cases.
|
|
Since the support for parameterized modules will be removed in R16,
we should not use them in test cases.
|
|
|
|
|
|
ct:abort_current_testcase/1 (which is a wrapper for the function
with the same name in test_server_ctrl) would not work as expected
when a group with parallel test cases was executing. Essentially,
the abort_current_testcase message would be ignored until the group
has finished and would then abort the end_per_group testcase for
the group.
Since there is no unique current testcase when a parallel group is
executing, we must handle the abort_current_testcase message and
return an error tuple.
Also fix the bug that test_server_ctrl:abort_current_testcase/1
would always return 'ok'.
|
|
If it is written with io:fwrite/2 it will be written to
the unexpected_io log, where it will not be of any use.
|
|
When writing messages to stdout, all messages are prefixed with
"Testing" followed by the name of the test suite. We don't want
to write that prefix if testing has stopped.
|
|
|
|
'user_timetrap_error' was not detected during any "conf init function"
except init_per_suite, so if e.g. init_per_group failed with
user_timetrap_error, then the test cases in the group would not be
skipped. This has been corrected.
|
|
Earlier, #st.config was set to undefined when entering this loop. Then
it was updated when the test case itself started. This means that if
the test case process crashed during test case initiation, the parent
process would not know the Config.
This commit saves the initial Config value in the parent process
(run_test_case_msgloop/1) from the start.
|
|
Commit c4375a62cfaabfd8de757f59714623ba1a8cb915 added a parallel
group, but incorrectly, so no test cases at all were run in
receive_SUITE.
|
|
The compiler would crash when attempting to compile a function
head that did binary matching and had a complex expression using
'andalso' and 'not'.
Noticed-by: José Valim
|
|
|
|
|
|
|
|
|
|
|
