Age | Commit message (Collapse) | Author |
|
It is bad practice to use an arbitrary string as a format
string for io:format(), since it could contain a '~' character
which could trigger a badarg exception. Therefore, replace all
io:format/3 calls that looks like:
io:format(Fd, String, [])
with:
io:put_chars(Fd, String)
|
|
The Format string argument for io:format() is not documented
to accept an iolist, so we should not depend on it.
Also, it is bad practice to use an arbitrary string as a format
string for io:format(), since it could contain a '~' character
which could trigger a badarg exception.
Fix both problems at the same time by using io:put_chars() to
display the iolist.
|
|
Add newlines to the same io function call,
so that concurrent io always starts at a new line.
|
|
* bjorn/kernel/global-resolve-function-fix/OTP-10419:
global: Allow "tuple funs" as resolve functions
|
|
If a severe error occurs in test_server (e.g. failing to write to
log files), test_server would terminate without commont_test knowing
about it. Since ct_run can now return an exit code, it is important
that common_test is aware of severe problem so that it can indicate
that an error has occurred.
|
|
|
|
If it is not possible for test_server_ctrl:start_log_file/0 to
create the log file directory or log files, then stop_extra_tools/1
(called from init_tester/10) is also likely to crash and hide the
original error reason. That will be confusing to the user.
Therefore, catch the call to stop_extra_tools/1.
|
|
Commit de7e01c958ff7c9e6da4034a53567a30a4ae5792 removed support for
tuple funs. To still allow resolve functions for
global:{re_}register_name/3 to be specified as {M,F}, we'll need to
translate {M,F} to an external fun.
Also update the documentation to mention that the use of {M,F} to
specify a resolve function is deprecated, and to add a recommendation
to use an external fun.
|
|
The rel specification now dictates the order in which included and
used applications are loaded/started by the boot file. If the
applications are not specified in the rel spec, then the order from
the .app file is used. This was a bug earlier reported on systools,
and is now also implemented in reltool.
Example:
If a .app file specified
{applications,[x,y]}
{included_applications,[b,c]}
And the reltool.config has
{rel, "myrel", "1.0", [a,y,x,c,b]}
Then the boot file will load/start y before x and c before b. Earlier
x would always be started before y and b always before c due to the
order in the .app file.
|
|
Two adjacent * used as a single pattern will match
all files and zero or more directories and subdirectories.
|
|
* bjorn/stdlib/filelib-wildcard/OTP-6874:
Fix filelib:wildcard/2
|
|
If a 'rel' spec in the reltool config does not contain all
applications that are listed as {applications,Applications} in a .app
file, then these applications are autmatically added when creating the
.rel file.
For 'included_applications', the behaviour was not the same. I.e. if a
'rel' spec in the reltool config did not contain all applications that
are listed as {included_applications,InclApplications} in a .app file,
then reltool would fail with reason "Undefined applications" when
creating the .rel file. This has been corrected, so both
'applications' and 'included_applications' are now automatically added
if not already in the 'rel' spec.
I.e. for an application 'z', if z.app contains
{applications,[stdlib,kernel,x]}
{included_applications,[y]}
then reltool configuration
{rel, "myrel", "1.0", [z]}
will cause the same .rel file as
{rel, "myrel", "1.0", [stdlib,kernel,x,y,z]}
|
|
* siri/dont-allow-modvsn-in-app-file/OTP-10417:
Don't allow {Mod,Vsn} in modules list in .app file
|
|
It was possible to insert {Mod::atom(),Vsn::term()} instead of
Mod::atom() in the modules list in a .app file. This was not visible
in the documentation of .app files, but it was visible in the
documentation of application:load/[1,2] (where the .app file term can
be used directly as first argument).
The Vsn part was never used, so this possibility has now been removed.
|
|
|
|
|
|
* siri/sasl/dont_destroy_test_dir/OTP-10394:
Skip release_handler test related to symlinks on windows
|
|
The erl.ini file generated by reltool:install/2 faulty pointed out
$ROOT/bin as Bindir. This is now changed to $ROOT/erts-Vsn/bin. Also,
backslashes in erl.ini needed to be escaped.
|
|
filelib:wildcard("some/relative/path/*.beam", Path) would fail to
match any file. That is, filelib:wildcard/2 would not work if the
first component of the pattern did not contain any wildcard
characters.
Noticed-by: Samuel Rivas
|
|
|
|
* siri/sasl/dont_destroy_test_dir/OTP-10394:
Make sure release_handler_SUITE does not mess up sasl test directory
|
|
According to documentation it should be allowed to set
incl_cond=include|exclude|derived, but if set to derived on module
level, reltool_server would crash. This has been corrected.
|
|
* ia/public_key/ssh_decode-comment-issue/OTP-9361:
public_key: ssh_decode now handles comments, at the end of the line, containing withespaces correctly
|
|
* ia/public_key-missing-sha224/OTP-9362:
public_key: Add missing references to sha224 and sha384
|
|
release_handler_SUITE:otp_9864 deleted parts of the
release_handler_SUITE_data directory so the test suite could not be
executed twice without re-installation. This has been corrected.
|
|
|
|
|
|
* siri/stdlib/escript_SUITE/OTP-10393:
Extend watchdog, and add report_error option to compile:file in escript_SUITE
|
|
* maint:
Do not build jinterface test if there is no jinterface
Escape whitespace in path
|
|
* lukas/jinterface/whitespace_test_fix:
Do not build jinterface test if there is no jinterface
Escape whitespace in path
|
|
|
|
|
|
|
|
|
|
|
|
containing withespaces correctly
|
|
* siri/sasl/rb_SUITE/OTP-10387:
Fix rb_SUITE failing tests
|
|
* siri/runtime_tools/remove-inviso-rest:
Remove all traces of inviso application from runtime_tools
|
|
1. escript_SUITE:create_and_extract sometimes fails with timetrap
timeout on solars. Watchdog is extended to avoid this.
2. escript_SUITE:archive_scritp sometimes fails with compilation
error. Option 'report_errors' is added to compile:file in order to get
more information.
|
|
The R15B02 release
|
|
Some tests in rb_SUITE failed every now and then depending on timing:
1. sometimes SASL printouts from cth_log_redirect were captured in
addition to expected printouts
2. sometimes test supervisor and server were not completely stopped
before next test case was started
This has been corrected.
|
|
Rests of inviso was still in runtime_tools.app.src and
runtime_tools_sup.erl. This has been removed. A test of
application:start/stop is also added to runtime_tools_SUITE.
|
|
|
|
|
|
|
|
|
|
* anders/diameter/avp_errors/OTP-10202:
Add a testcase
Fix answer-message blunder
|
|
|
|
|
|
Conflicts:
lib/diameter/autoconf/vxworks/sed.general
xcomp/README.md
|