| Age | Commit message (Collapse) | Author |
|---|
|
* maint:
Fix bug where require of same name at same config would return name in use
|
|
* lukas/common_test/multi_require_bug/OTP-10572:
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
|
|
* ia/ssl/gen-fsm-timout/OTP-10569:
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
|
|
* maint:
Fix binary append exceptions
|
|
* bjorn/erts/binary-append/OTP-10524:
Fix binary append exceptions
|
|
|
|
* 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
|
|
* bjorn/stdlib/eliminate-param-module-use:
dict_SUITE: Eliminate use of parameterized modules
sets_SUITE: Eliminate use of parameterized modules
|
|
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.
|
|
* siri/user_timetrap-group-test/OTP-10018:
[common_test] Add tests for user timetraps in groups
[test_server] Skip test cases if init_per_group fails in user timetrap
[test_server] Add Config to run_test_case_msgloop/1 from the start
|
|
|
|
'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.
|
|
* anders/diameter/patch/R15B02/OTP-10555:
vsn -> 1.2.1
Update appup for OTP-10461/10550
Allow for no diameter on remote node in connection guard
Add missing clause for peer failover
|
|
|
|
|
|
anders/diameter/patch/R15B02/OTP-10555
* anders/diameter/patch/R15B02/upgrade/OTP-10550:
Allow for no diameter on remote node in connection guard
|
|
anders/diameter/patch/R15B02/OTP-10555
* anders/diameter/patch/R15B02/failover_error/OTP-10461:
Add missing clause for peer failover
|
|
|
|
|
|
The guard is against a connection to a given peer already existing but
fails if diameter is not running on a remote node.
Note that the guard itself is to be made configurable in R15B03
(OTP-10493) to allow multiple connections per peer.
|
|
* fredrik/ssh-use-options-alg/OTP-10498:
Option to ssh:connect {pref_public_key_algs, list()} where you can give the algorithms you want to use
|
|
Code such as the following should cause an exception:
Bin = <<0:1>>,
<<Bin/binary,...>>
(Because the "binary" type implies that the binary must have a
size in bits that is a multiple of 8.)
Depending on the binary, either no exception was thrown or the
wrong exception was thrown (because c_p->freason was not set).
Noticed-by: Adam Rutkowski
|
|
The guard is against a connection to a given peer already existing but
fails if diameter is not running on a remote node.
Note that the guard itself is to be made configurable in R15B03
(OTP-10493) to allow multiple connections per peer.
|
|
|
|
|
|
This allows a diameter_app callback to retrieve the corresponding
configuration as passed to diameter:add_transport/2.
|
|
|
|
|
|
Configuration will allow relaxation of the guard against multiple
transport connections to the same peer.
|
