| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
| |
This reverts commit d4e4511b19f4126d9271a6e3a8fa2eb716da7e85.
|
| | |
|
| | |
|
| |\
| |
| | |
Remove --enable-sanitizers configure options
|
| | |
| |
| |
| |
| |
| | |
Motivation:
An untested broken feature.
Can easily be enabled by setting CFLAGS and LDFLAGS.
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The <c>size/1</c> BIF is not optimized by the JIT, and its use can
result in worse types for Dialyzer.
When one knows that the value being tested must be a tuple,
<c>tuple_size/1</c> should always be preferred.
When one knows that the value being tested must be a binary,
<c>byte_size/1</c> should be preferred. However, <c>byte_size/1</c> also
accepts a bitstring (rounding up size to a whole number of bytes), so
one must make sure that the call to <c>byte_size/</c> is preceded by a
call to <c>is_binary/1</c> to ensure that bitstrings are rejected. Note
that the compiler removes redundant calls to <c>is_binary/1</c>, so if
one is not sure whether previous code had made sure that the argument is
a binary, it does not harm to add an <c>is_binary/1</c> test immediately
before the call to <c>byte_size/1</c>.
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tweaked the meas tool to be less verbose during a
test (suite) run.
OTP-18298
|
| | | | |
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
* bmk/megaco/20220926/test_tweaking/25.0:
[megaco|test|mess] Another test case using try-tc
[megaco|test|mess] Use try-tc for test case
[megaco|test|mib] Minor adjustment of the traffic case
|
| | | | |
|
| | | | |
|
| | |/ |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
"Magically" wrap'ed error in such a way that the
test wrapper themselves did not detect that an error
had occured (and therefor could not do checks).
|
| | | | |
|
| |\ \ \
| |/ /
|/| | |
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | |
| | |
| | |
| | | |
OTP-18179
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* 'deterministic-build' of https://github.com/TD5/otp:
make: Allow OTP to be built deterministically
compiler: Make test_lib robust to +deterministic
compiler: Make compiler forward +determinsitic flag to epp
compiler: Make yecc respect +deterministic
compiler: Make leex respect +deterministic
compiler: Make asn1ct_gen respect +deterministic
compiler: Make EPP respect +deterministic
OTP-18165
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add a --enable-deterministic-build to the configure script,
which sets ERL_DETERMINISTIC=yes throughout the relevant
Makefiles, which then invoke the relevant build stages with the
+deterministic option.
This addresses absolute paths being included in generated .erl files
and compiled .beam files that resulted in builds from different source
directories generating different artefacts (which is a component of the
issue in erlang#4482).
I think it would make sense to make this the default at some stage, but
I've put the change behind a flag for now to decouple
making deterministic OTP builds possible from making them the default.
Having +deterministic set results in compiler options being
removed from the module info for modules where this options was used.
This may have other implications for users of OTP.
For tests themselves, +determinism is not set, since many test cases
depend on accessing the test module's compilation options, or other
features not available in deterministic mode, in order to configure
themselves. For tests of the determinism feature specifically,
+deterministic must be explicitly passed to the compiler within the
relevant test cases.
|
| |\ \ \ |
|
| | | |/
| |/|
| | |
| | | |
Tweaked the condition for running test case.
|
| |/ /
| |
| |
| |
| |
| | |
Tweaked a couple of test cases in the pending-limit test suite.
The point is to 'catch' when we fail to start nodes, and skip
tc in those cases (instead of crashing and failing).
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|