Age | Commit message (Collapse) | Author |
|
* egil/ensure-erl_crash.dump/OTP-10422:
test: Relax timeouts for heart_SUITE
erts: Fix crash dump write to port hack
erts: Fix lock check assertion
doc: Document ERL_CRASH_DUMP_SECONDS behaviour
test: Add test for heart restart on crash
test: Add test for heart restart on crash
erts: Change ERL_CRASH_DUMP_SECONDS behaviour
test: Refactor away ?line macros in heart_SUITE
erts: Search for heart in ports that are alive
heart: Refactor heart debugging
erts, heart: Ensure erl_crash.dump is written
|
|
Timeouts were set too narrow and timedout on slow machines
|
|
More future proof with R16
|
|
|
|
* heart reboot behaviour
* erl_crash.dump file write behaviour
|
|
* node_start_soon_after_crash tests that heart restarts
beam upon a crash and only lets beam write its crash
dump for a certain amount of time
|
|
* node_start_immediately_after_crash tests that heart restarts
beam upon a crash and will not generate a crash dump
|
|
Not setting ERL_CRASH_DUMP_SECONDS will now terminate beam
immediately on a crash without writing a crash dump file.
Setting ERL_CRASH_DUMP_SECONDS to 0 will also terminate beam
immediately on a crash without writing a crash dump file, i.e. same as not
setting ERL_CRASH_DUMP_SECONDS environment variable.
Setting ERL_CRASH_DUMP_SECONDS to a negative value will let the beam wait
indefinitely on the crash dump file being written.
Setting ERL_CRASH_DUMP_SECONDS to a positive value will let the beam wait
that many seconds on the crash dump file being written.
A positive value will set both an alarm in beam AND a heart timeout for restart
if heart is running.
This is due to the change of 'heart' behavior when 'heart' is
listening for a crash.
|
|
|
|
|
|
|
|
When a crash dump is about to be written and we have
heartbeat enabled on a system. We need time to write it
before heart explicitly kills the beam.
|
|
* egil/fix-boot_combo-test:
test: Fix smoke_test_SUITE
|
|
* lukas/erts/whitespace_nsis_fix/OTP-10481:
Fix bug when making nsis target
|
|
* Skip boot_combo tests where cannot start slave nodes
(The binary will not exist)
|
|
* lukas/erts/bucket_mask_fix/OTP-10374:
Add comment about eproviderfailedinit error
Increase sbct for win64 as block alignment is 16
|
|
|
|
|
|
* sa/dialyzer-fix-r15b02:
Fix a crash in race condition detection
Remove old untested experimental extension
Respect {plt_check,false} option when using dialyzer:run/1
Fix handling of tuple set remote types appearing in tuple sets
OTP-10464
|
|
Analysis is not always able to find the variable labels and names for any kind
of arguments passed to the ets module functions.
|
|
This extension allowed minimal detection of race conditions that were passing
through behaviour API calls, but had no tests in any suite and also caused a
crash in R15B02.
|
|
|
|
Originally reported by Joseph Wayne Norton, simplified testcase provided by Hans
Bolinder.
|
|
* egil/fix-configure-openbsd/OTP-10395:
Fix linking of shared libraries on OpenBSD
|
|
* egil/fix-missing-modules-app/OTP-10439:
tools: Add missing lcnt module to .app.src
percept: Add missing modules to .app.src
|
|
|
|
* sverk/gcc-atomic-config-bug:
erts: Fix gcc atomic bug in ethread.h
OTP-10418
|
|
|
|
|
|
* peppe/common_test/shell_mode_broken:
Fix broken interactive mode
|
|
|
|
* lukas/jinterface/whitespace_test_fix:
Do not build jinterface test if there is no jinterface
Escape whitespace in path
|
|
* lukas/erts/win32_flush_console_io/OTP-10325:
Make sure io is flushed when driver is closed
|
|
|
|
|
|
Reported-by: Matthew Dempsky
|
|
|
|
Sometime when executing an tty io operation just before
the emulator terminated, the io message would get lost.
This commit makes sure that there is no io in the fd driver
before shutting down.
|
|
A faulty #if 0 caused healthy gcc builtin atomic to be ignored.
|
|
|
|
|
|
|
|
* kenneth/topdoc/corrections2:
Fix a missing li tag plus a link to Erlide
|
|
|
|
|
|
* anders/diameter/avp_errors/OTP-10202:
Add a testcase
Fix answer-message blunder
|
|
|
|
|
|
|
|
|