Age | Commit message (Collapse) | Author |
|
The ssh application is not installed on all test hosts. Catching the
call to ssh:start/0 allows the the netconf tests to be nicely skipped
if ssh does not exist.
|
|
* siri/cuddle-master:
Add short sleep when killing slave nodes
[ct test] Do reload_config instead of get_config
|
|
* peppe/common_test/OTP-13615:
Fix problem with incorrect type of timestamps
OTP-13615
|
|
OTP-13615
|
|
The test case config_dynamic_SUITE:test_localtime_update sometimes
failed on slow machines, since the initial value of 'localtime' is
fetched with ct:get_config instead of ct:reload_config. The value is
then from the test run start, not from the time of the ct:get_config
call. This is now corrected.
|
|
* siri/cuddle-master:
[ct test] Wait for event receiver to be unregistered
[ct test] Flush messages from old client after close in telnet server
[ct test] Use monitor instead of ct:sleep
[ct test] Check that crypto is loaded, or skip netconf tests
[ct test] Reduce amount of data in netconfc1_SUITE:get_a_lot
|
|
To avoid badarg when two tests are run within the same test case.
|
|
Since the same erlang process is used for subsequent telnet
connections, messages from old clients must be flushed after close.
|
|
ct_gen_conn_SUITE_data/conn_SUITE.erl uses a lot of ct:sleep(100) when
waiting for processes to exit. This commit removes all the sleeps and
introducess monitor instead.
|
|
Tests for ct_netconfc are failed instead of skipped if crypto can not
be loaded. This is now corrected.
|
|
This test case often fails with table_trans_timeout in the netconf
server (ns.erl) on slow machines. The amount of data was originally
reduced by commit 976214f8d738d4852348496df79f84264d899aba, but was
faulty reverted by commit 171d7e2a161ef9270240aff0fa15a285df21c1ef. It
is now reduced again...
|
|
* peppe/common_test/log_tests:
Write suite that tests the API for printing to log
|
|
* peppe/common_test/fix_failing_tests:
Make sure test node shuts down before skipping suite
Measure file i/o overhead and skip test if the speed is too slow
Skip test cases if cover or debug is running
|
|
|
|
|
|
|
|
* siri/cuddle-master:
Change ct:sleep to timer:sleep where scaling is not wanted
Don't generate ssh key files in netconf client test
Ignore data received in break mode in test telnet_server
Wait for process to die before next call
Retry ct_telnet:get_data if no data is received after short wait
Don't throw rest of line when NOP is received in test telnet_server
Change ct:sleep to timer:sleep in telnet_server
|
|
|
|
|
|
Generating the dsa files can be very slow on some machines. Use
hardcoded files instead.
|
|
The only command handled in break mode is 'q' = 'quit break
mode'. Other data would earlier cause a function_clause
exception. Other data could e.g. be a NOP poll (keep alive). To fix
the problem, any data received in break mode, except 'q', will now be
ignored.
|
|
ct_telnet_own_server_SUITE:large_string tests that the client can
receive a chopped up string. To make sure the right thing is tested, a
SHORT timer is used before calling ct_telnet:get_data, but on some
slow machines the the timer is too short to allow data to be
received. To overcome this, the test now re-tries ct_telnet:get_data a
few times before giving up.
|
|
If telnet command NOP (No Operation) was received in the same tcp
package as other data, then the rest of the data would be regarded
further telnet commands (to proceed IAC, Interprete As Command) and
would never get to telnet_server:do_handle_data/2.
This is now corrected.
|
|
Conflicts:
OTP_VERSION
lib/common_test/test/ct_hooks_SUITE_data/cth/tests/ct_update_config_SUITE.erl
lib/common_test/vsn.mk
|
|
The telnet_server is run on the main test node which will scale and
multiply timers on some test hosts. The other side of the telnet test
(the client) is run on the slave, which does not inherit timer scaling
and multiplication. Therefore, it is better to use timer:sleep in the
server.
|
|
* siri/cuddle-master:
Extend timer in test
Update crashdump_viewer_SUITE with new release numbers
Set longer timetrap when creating dsa files
Check that ssh application exists before starting netconf tests
Improve error control when starting ssh in netconf test
|
|
* peppe/ct_misc_18_patches:
Add flag/option for disabling the character escaping functionality
Fix bug using the wrong lists search function
Fix bug with clashing timestamp values
Fix problem with stylesheet tags getting escaped
Skip pre/post test IO suite if cover or debug is running
Tweak pre_post_io test case to run without failing
Fix various log related problems
|
|
|
|
OTP-13535
The return value of ct:get_timetrap_info/0 has been modified.
|
|
|
|
|
|
ct_netconfc_SUITE ->
netconfc1_SUITE:close_while_waiting_for_chunked_data fails every now
and then with {error,timeout} instead of {error,closed}. To overcome
this, the timeout value in the failing call is now extended.
|
|
... in test for ct_netconfc.
|
|
On some test machines, crypto or ssh applications do not
exist. ct_netconfc_SUITE only checked for crypto, causing failed
instead of skipped test case when ssh does not exist.
|
|
|
|
|
|
|
|
* peppe/common_test/misc_18.3_bugfixes:
Fix minor issues with escaping characters
OTP-13003
|
|
OTP-13003
|
|
Conflicts:
lib/common_test/test/Makefile
|
|
* siri/test-ct_release_test/OTP-13390:
Remove upgrade tests from stdlib_SUITE
Add test of ct_release_test
|
|
The ct_release_test module provides support for testing
upgrade/code_change of one or more applications within the Erlang/OTP
product. This commit adds tests to the common_test/test directory.
|
|
|
|
|
|
|
|
|
|
|
|
The netconf client in common_test was earlier very restrictive as to
which ssh options the user could set. This is now changed, and any ssh
option is now allowed. The netconf client will simply pass on any
option, which it does not recognize, to ssh.
|
|
Conflicts:
OTP_VERSION
|
|
If a ssh package contained more than one netconf end tag, then the
second end tag was never detected in ct_netconfc:handle_data. Instead
it was included in the XML data given to the xmerl parser, which then
failed with reason "\"]]>\" is not allowed in content".
This problem was introduced by OTP-13007.
|