Age | Commit message (Collapse) | Author |
|
* maint:
Fix etp-ets-tables
Fix node refc test for free processes hanging around
Enhanced node refc bookkeeping
Fix node container refc tests of ETS
Fix node refc test of external data
Node container refc test for persistent terms
Include persistent term storage in node/dist refc check
Fix node refc test for system message queue
|
|
* rickard/node-refc-tests-22:
Fix etp-ets-tables
Fix node refc test for free processes hanging around
Enhanced node refc bookkeeping
Fix node container refc tests of ETS
Fix node refc test of external data
Node container refc test for persistent terms
Include persistent term storage in node/dist refc check
Fix node refc test for system message queue
|
|
|
|
|
|
|
|
|
|
|
|
* rickard/node-refc-tests-21:
Node container refc test for persistent terms
Include persistent term storage in node/dist refc check
Fix node refc test for system message queue
|
|
|
|
|
|
* rickard/node-refc-tests-20:
Fix node refc test for system message queue
|
|
|
|
|
|
The functions io:columns() and io:rows() only worked correctly inside
interactive erlang shells before this fix. These functions returned
{error,enotsup} before this fix even if stdout and stdin were
connected to a terminal when they were invoked from an escript or a
program started with e.g., `erl -noshell`.
This commit fixes issue ERL-717.
|
|
|
|
|
|
|
|
|
|
Extend the "checks" for faulty gcc (found another platform
with the same problem (Old SLES 11).
Also tweaked the multicast test a bit.
|
|
* john/erts/merge-fd-file-info/OTP-15956:
file: allow read_file_info on file descriptors
|
|
|
|
Needed to do some tweaking to make the tool work with IPv6 sockets.
Also found and corrected some unrelated bugs in the tool.
OTP-15897
|
|
"Due to" cut-and-paste, a number of IPv6 test cases was missing
the condition fun for validating IPv6 support (which caused
a couple of IPv6 test cases to fail on platforms not supporting IPv6).
OTP-15897
|
|
OTP-15897
|
|
OTP-15897
|
|
OTP-15897
|
|
OTP-15897
|
|
* rickard/test-fixes-21:
Fix unstable test dump_SUITE:signal_abort
Fix unstable node_container_SUITE:magic_ref test
Fix unstable node_container_SUITE:node_controller_refc test
Fix unstable tests process_SUITE:no_priority_inversion{,2}
|
|
OTP-15897
|
|
OTP-15897
|
|
The nif code expects the socket address to be "complete",
that is all fields must exist. This was not the case for
a couple of functions, sendto, sendmsg and connect.
What was mssing was a call to 'ensure_sockaddr'.
Test: 1) Add a condition function to test if IPv6 is available
and works.
2) Needed to adjust a test case (actually a common function
used in several test cases) since the socket address
data type has two optional fields, which we do not
initiate (when sending), but the nif-code does fill in.
OTP-15897
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* maint:
Refine test cases
Remove test code that fails on Windows
|
|
* raimo/udp-send-TOS/OTP-15422:
Refine test cases
Remove test code that fails on Windows
|
|
|
|
|
|
* maint:
Fix unstable test dump_SUITE:signal_abort
Fix unstable node_container_SUITE:magic_ref test
Fix unstable node_container_SUITE:node_controller_refc test
Fix unstable tests process_SUITE:no_priority_inversion{,2}
|
|
* rickard/test-fixes-21:
Fix unstable test dump_SUITE:signal_abort
Fix unstable node_container_SUITE:magic_ref test
Fix unstable node_container_SUITE:node_controller_refc test
Fix unstable tests process_SUITE:no_priority_inversion{,2}
|
|
Sometimes processes have not had the time to spread
from one scheduler. Force spread by using the undocumented
'scheduler' option.
|
|
* rickard/test-fixes-20:
Fix unstable node_container_SUITE:magic_ref test
Fix unstable node_container_SUITE:node_controller_refc test
Fix unstable tests process_SUITE:no_priority_inversion{,2}
|
|
|
|
|
|
Sometimes processes have not had the time to spread
from one scheduler. Force spread by using the undocumented
'scheduler' option.
|
|
* sverker/hash-improve-shrink:
erts: Tweak hash shrink limit
erts: Improve hash shrinking
|
|
* Only shrink when we can remove one segment and still remain
below 50% table load.
* Only shrink down to two table segments. It just leads to a lot of
potentially "unnecessary" rehashing to have a chance of getting rid
of the last extra segment before the last delete op. I don't think
it's worth it.
|