| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* derek121/eunit-doc-additions:
Add mention of ?assertNotMatch and ?assertNotEqual
|
|
* vladdu/eunit_unicode_OTP11660:
OTP-11660: make eunit unicode safe
|
|
These two macros are defined in eunit.hrl, but are missing in this
documentation.
|
|
|
|
All output from eunit is unicode, including the surefire XML files.
|
|
|
|
OTP-12200
* matwey/makefile:
Cleanup parse_transform modules in eunit
Cleanup behaviour modules in ssl
Cleanup behaviour modules in ssh
Fix a typo in clean section of otp_mibs makefile
|
|
* lemenkov/install_additional_headers/OTP-12197:
Install internal hrl files when necessary
|
|
|
|
|
|
Sometimes we install *.erl files. Some these files include a private
*.hrl files, so in order to make these *.erl files usable we have to
install these private includes as well.
Signed-off-by: Peter Lemenkov <[email protected]>
|
|
Parse_transform modules were not cleanuped.
|
|
is_function/2 looks present since at least OTP R13B03, so the change
shall not undermine running eunit on older versions of Erlang.
This commit is only refactoring - it contains no functional changes.
|
|
|
|
Most dependencies introduced are exactly the dependencies to other
applications found by xref. That is, there might be real dependencies
missing. There might also be pure debug dependencies listed that
probably should be removed. Each application has to be manually
inspected in order to ensure that all real dependencies are listed.
All dependencies introduced are to application versions used in
OTP 17.0. This since the previously used version scheme wasn't
designed for this, and in order to minimize the work of introducing
the dependencies.
|
|
Ensure all are "normal" versions according to the new version scheme
introduced in OTP 17.0
|
|
* hb/dialyzer/deprecate_types/OTP-10342:
Deprecate pre-defined built-in types
|
|
Add the mentioned test suites for *all* library and touched
non-library applications.
|
|
The types array(), dict(), digraph(), gb_set(), gb_tree(), queue(),
set(), and tid() have been deprecated. They will be removed in OTP 18.0.
Instead the types array:array(), dict:dict(), digraph:graph(),
gb_set:set(), gb_tree:tree(), queue:queue(), sets:set(), and ets:tid()
can be used. (Note: it has always been necessary to use ets:tid().)
It is allowed in OTP 17.0 to locally re-define the types array(), dict(),
and so on.
New types array:array/1, dict:dict/2, gb_sets:set/1, gb_trees:tree/2,
queue:queue/1, and sets:set/1 have been added.
|
|
As discussed in issue #240 *all* OTP library applications use the '.*'
wildcard as up and down version. This makes library applications
always up- and downgradeable. Using the wildcard version obsoletes
all maintenance tasks regarding library applications' appup files.
Additionally, it prevents upgrade problems caused by automatically
included application dependencies when using reltool to create
releases. Missing copyright headers are now consistently present.
|
|
The R16B03 release
Conflicts:
lib/sasl/vsn.mk
|
|
|
|
|
|
|
|
|
|
This is to avoid outputting something like "\"%\f" instead of [34,37,12] in the XML.
|
|
|
|
A io_request in eunit reuturns wrong value when it receive getopts or
get_geometry request.
|
|
The R16B02 release
Conflicts:
lib/sasl/vsn.mk
|
|
|
|
|
|
This makes typos such as missing commas between two assertions
(e.g. ?assert(true) ?assert(true)) syntax errors instead of silently
compiling and failing with a badfun error at runtime.
This won't break any existing code as parenthesed expressions and blocks
have the same precedence and none of these macros can be used as patterns.
|
|
|
|
|
|
|
|
|
|
|
|
* nox/enable-silent-rules/OTP-10726:
Implement ./otp_build configure --enable-silent-rules
|
|
With silent rules, the output of make is less verbose and compilation
warnings are easier to spot. Silent rules are disabled by default and
can be disabled or enabled at will by make V=0 and make V=1.
|
|
|
|
|
|
|
|
|
|
|
|
An error during fixture setup means that some tests could not be run,
and therefore needs to be highlighted in the test report. Likewise, a
cleanup failure is often a problem that needs to be looked into.
Since setup and cleanup are not part of any single test in Eunit's
view, I include them as phantom test cases in the report whenever they
fail.
|
|
|
|
|
|
|
|
|
