| Age | Commit message (Collapse) | Author |
|---|
|
`beam_asm` would encode `{literal,[]}`, `{literal,erlang}`, and
`{literal,42}` in a less efficient way than the equivalent values
`nil`, `{atom,erlang}`, and `{integer,42}`. That would increase the
size of BEAM files and could increase the loaded code size. It would
probably not harm performance, because `literal` was only used this
way in code that generates `badmatch` and `case_clause` exceptions.
|
|
|
|
|
|
For the parent commit as a diameter 2.2 patch.
|
|
Commit d9d918b2 added a gen_server whose purpose is to keep track of
visible nodes on which diameter_dist:attach/1 has been called to
register a node as a handler of incoming Diameter requests when
diameter_dist:route_session/2 is configured as spawn_opt MFA. The server
contacts visible nodes at init in order to request information, but
instead of monitoring visible to also be able to request information at
nodeup, it monitored on all nodes, resulting in gen_server casts even to
hidden nodes.
Monitor only on visible nodes since a hidden node may not be able to
deal with the new message.
|
|
into sverker/maint-21/doc-big-creation-tags/OTP-15766
|
|
|
|
|
|
|
|
During a garbage collection, there could have been an overflow
in the old virtual heap.
|
|
Make sure that the instruction pointer is correct for a garbing
process in a crash dump.
|
|
Wait a little after to make sure that fun holding process to
complete its termination.
|
|
According to the comment, this rule was only needed when communication
with R7B nodes was supported.
|
|
With the new compiler in OTP 22, we have to use more options to
turn off optimizations.
This commit also skips the match_huge_int/1 test case in the
unoptimized clone of the bs_match_int module because it could
crash on memory-constrained computers.
|
|
* maint:
Updated OTP version
Prepare release
# Conflicts:
# OTP_VERSION
# make/otp_version_tickets_in_merge
|
|
* maint-21:
Updated OTP version
Prepare release
# Conflicts:
# make/otp_version_tickets
|
|
Since `dummy_result/1` returns integers (i.e. `0`) not floats, `util/0,1` specs should account for that.
|
|
For the notify_started02 test case we (now) try estimate how
long we should wait for completion (based on the time of the
first iteration). On slow machines, it takes longer to start and
stop the manager, so adjust the total timeout accordingly.
|
|
|
|
|
|
* lukas/erl_interface/depend-fix/OTP-15757:
erl_interface: Generate dependencies at compile time
|
|
* lukas/erts/fix-fd-driver-select/OTP-15753:
erts: Fix sys_driver to correctly deselect fds
|
|
* sverker/crypto/bcmp-memcmp-fix/OTP-15750:
crypto: Fix link error on windows
|
|
* rickard/ts-find-ubuntu-inst/OTP-15716:
Find installed OTP for Ubuntu
|
|
* maint:
ssh: Present peername for accept_callback fun also for Sockets
ssh: Add ssh_channel:init/1
|
|
* maint-21:
ssh: Present peername for accept_callback fun also for Sockets
ssh: Add ssh_channel:init/1
|
|
* hans/ssh/accept_callback_socket/OTP-15763:
ssh: Present peername for accept_callback fun also for Sockets
|
|
* hans/ssh/ssh_channel-init/OTP-15762:
ssh: Add ssh_channel:init/1
|
|
* ingela/ssl/cipher-suite-conversions:
ssl: Add functions to convert between diffrent cipher suite formats
|
|
* bjorn/erts/measure-process_main/OTP-15620:
Add benchmark
Add erts_debug:interpreter_size/0
|
|
|
|
Atomic elements such as atoms, '{}', '[]', and '<<>>' are output on
the same line in types, structs, lists, &c.
In particular types can be more compact, and easier to read.
A space is output after comma in tuples, to be more consistent.
|
|
* hasse/stdlib/erl_pp_quoted_atom_types/OTP-15756:
stdlib: Add option 'quote_singleton_atom_types' to erl_pp
|
|
The new option can be used by Dialyzer, which has traditionally quoted
singleton atom types.
The OTP team has decided not to use the convention in OTP
documentation, at least not for now. That is why the option is needed.
EDoc does not use the new option.
Syntax Tools does not have a similar option.
|
|
* peterdmv/ssl/dtls-fix:
ssl: Fix faulty match of Socket in handle_info/3
Change-Id: Ied8228b8f2eb88e50a47fc101331d7913fdb1de6
|
|
|
|
1) A test case failed due to the times retreived by
get(snmpEngineTime) reported to large time diffs
(this is basically a sanity check).
Added some more info about time(s) to see if there
are some "gaps" somewhere.
The problem occurred on a slow Virtial Machine.
2) A previous (failing) test case failed to cleanup after
itself (see above), which caused later test cases to fail.
Specifically, the app top supervisor was not terminated,
which caused the start agent function to fail (basically
already_started).
|
|
Added common (formated) timestamp function(s). Made use of
these in the verbosity module (for debug printouts) and in
the test suite(s).
I also *think* I found the cause for some if the test case
failures (timeouts).
For v3 (agent) test cases the test manager makes use of parts
of the agent code: snmp_framework_mib and snmp_user_based_sm_mib.
And since they store their data in snmpa_local_db, that also
needs to be running.
And this was the problem (I think). On some (slow) machines,
the snmpa_local_db process from the *previous* test case
might still be running when the we tried to start it. That meant
that no new snmpa_local_db was started. Instead the old one,
still running but terminating, was retain. For a while. Until
it actually finally stopped. So the next operation towards
snmpa_local_db, insert, simply hanged until the process
terminated.
This in combination with the fact that the packet server process,
which was started using proc_lib, previously called init_ack
before this init was actually done, could actually start and then
at a much later time hang because some operation timed out
(the packet server was hanging).
Yuckety yuck-yuck.
|
|
Improved test printouts (more with timestamps), also
fixed the printouts of the (fake) local-db start
result printout.
Also updated the copyright end-dates.
|
|
Handle when the agent test manager starts the fake local-db
and that process is already running (for some reason).
|
|
The agent test manager had a bug during start that could
potentially cause deadlock, but atleast could cause test
cases to fail because of timeouts. The test manager
(actually the "packet server") used proc_lib to start the
process but it called the init_ack function before the init
was actually complete. This was only a problem for v3 cases
(where it did a bunch of further inits, including starting
the local-db process).
Also did debug/verbosity tweaking. Added a bunch of debug
(verbosity) printouts for the agent test manager "packet server"
during v3 init. Also made sure we could distinguish the
"normal" local-db from the one used by the test manager
(this is done by using a new short-name).
|
|
The EXPECT printouts has been improved. Partly by
including a timestamp.
|
|
Improve debug (verbose) printouts when a get/get-next/get-bulk/set
request fails (first by printing at level log instead of trace
and secondly by also printing the original operation result
when the operation fails).
|
|
The test manager used in the agent tests has been tweaked
in order to increase the readability (both of the code
and the output).
|
|
Improved the test manager printouts to make it easier to
diagnose problems...
|
|
|
|
|
|
|
|
Fix dtls_connection:handle_info/3 to correctly match the Socket
in static_env.
Change-Id: Iddaad0514c2413abac6d9a06292556e07acc7729
|
|
|
