Age | Commit message (Collapse) | Author |
|
groups.
|
|
|
|
1. ct:timetrap(infinity) not supported.
2. Previous set timetrap for a test case is not cancelled by new one.
|
|
|
|
init_per_testcase.
|
|
|
|
1. Allow empty group to be specified without generating an error.
2. Sort out potential problem with unnecessary call to delete_subs/2.
|
|
|
|
|
|
|
|
|
|
leader process.
|
|
|
|
|
|
* ia/ssl/doc-fixes:
Added missing path validation error to documentation
|
|
|
|
* ia/public_key/test-suite-update:
Created common test groups and temporary skipped pkits_SUITE as the conformance tests suite certificates has expired.
|
|
conformance tests suite certificates has expired.
New conformance tests uses another format to save certificates so
we need to implement PKCS-12 support.
CRL tests are commented out as the CRL support is not included
in the main development yet.
|
|
* maint-r14:
Prepare release
Update framwork backwards compatability check to use TEST_SERVER_FRAMEWORK as it should and not the Module
Export ct_framework:end_tc/3 for backwards compatability reasons
Update end_tc framework calls to check the name of the framework module instead of the return value of the call
|
|
|
|
* lukas/common_test/ct_hooks_compat_maint/OTP-9200:
Update framwork backwards compatability check to use TEST_SERVER_FRAMEWORK as it should and not the Module
Export ct_framework:end_tc/3 for backwards compatability reasons
Update end_tc framework calls to check the name of the framework module instead of the return value of the call
|
|
as it should and not the Module
|
|
|
|
instead of the return value of the call
|
|
* ia/ssl/prepare-for-release:
Prepare for release
|
|
|
|
* ia/public_key/prepare-for-release:
Prepare for release
|
|
|
|
* ta/dialyzer-doc:
dialyzer/doc: synchronize manual.txt and dialyzer.xml
dialyzer/doc: fix whitespace errors
dialyzer/doc: use consistent colons in type specs
OTP-9226
|
|
* ms/heart-rem-garbage-append:
heart: remove garbage appended to heart command
OTP-9224
|
|
* bjorn/compiler/coverage:
bs_match_SUITE: Improve coverage of beam_bsm
beam_bsm: Eliminate uncovered line in warning generation
match_SUITE: Cover a clause in beam_dead:forward/4
beam_dead: Remove uncovered special case handling of empty blocks
beam_dead: Remove uncovered clauses in binary matching optimization
beam_dead: Remove uncoverable case clause in update_value_dict/3
beam_dead: Remove code that cannot be covered in forward/4
record_SUITE: Cover optimization of is_record/3 in beam_type
compiler tests: Reinstate ?MODULE macro in calls to test_lib:recompile/1
|
|
Conflicts:
erts/vsn.mk
|
|
* hw/fix-epmd-perror:
Fix epmd's dbg_perror() output
OTP-9223
|
|
* mh/eunit-surefire-reports:
Increase depth of error messages in Eunit Surefire reports
OTP-9220
|
|
* sa/dialyzer-invalid-spec-fix:
Fix crash related with the contract blame assignment patch
OTP-9219
|
|
* gc/gen-format-status-improvements:
Fix format_status bug for unregistered gen_event processes
Conflicts:
lib/stdlib/test/gen_event_SUITE.erl
OTP-9218
|
|
* bjorn/erts/remove-init_get_args-doc/OTP-9209:
Remove documentation for non-existent init:get_args/0
|
|
|
|
In warning_translate_label/2, gb_trees:lookup/2 is called
to translate from the entry label for a function to its name.
Since the gb_tree has an entry for all functions in the module,
there is no way that the lookup can fail unless there is a
serious bug.
Therefore, use gb_trees:get/2 so that an exception and an
internal compiler error will be generated if the lookup would
ever fail.
|
|
|
|
There is never any empty blocks when beam_dead is invoked.
Even if there were, they will be removed a little bit later in
forward/4.
|
|
In the optimization of binary matching, it seems that two clauses
cannot never be reached. Removing the clauses is safe, since that
would only mean that an opportunity for an optimization is lost
|
|
Because the code generator (v3_codegen) would not include the
same value more than once in a select_val/3 instruction and
because a label can only be referenced by one select_val/3
instruction, there is no way that the correct value could already
be in the gb_tree. (Even if it could happen, this change is
safe because only opportunity for an optimization would be missed;
incorrect code would not be generated.)
|
|
Since the optimizations in forward/4 already depends on some
assumptions on how code is generated anyway, document the
assumptions in a comment and remove the uncoverable code.
|
|
Since the introduction of improved record optimizations in
1858cb81391d2bce29b4b7620574ca60128cebf7 and
470c91d43eae54f63661645acbce4b92d73287cc, the optimization of
a is_record/3 call with a known correct type in
beam_type:simplify_basic_1/3 has not been covered.
|
|
In 3d0f4a3085f11389e5b22d10f96f0cbf08c9337f (an update to conform
with common_test), in all test_lib:recompile(?MODULE) calls, ?MODULE
was changed to the actual name of the module. That would cause
test_lib:recompile/1 to compile the module with the incorrect
compiler options in cloned modules such as record_no_opt_SUITE,
causing worse coverage.
|
|
|
|
|
|
|
|
|