aboutsummaryrefslogtreecommitdiffstats
path: root/lib/sasl/test/test_lib.hrl
AgeCommit message (Collapse)Author
2016-09-29Update sasl/test/test_lib.hrl with recent versions of kernel and stdlibSiri Hansen
"Old" versions are now taken from OTP-19.0, i.e. one major revision back from OTP-20.
2016-03-16Update sasl/test/test_lib.hrl with recent versions of kernel and stdlibSiri Hansen
"Old" versions are now taken from OTP-18.0, i.e. one major revision back from OTP-19.
2014-04-25Update sasl/test/test_lib.hrl with recent versions of kernel and stdlibSiri Hansen
2014-02-17Update sasl/test/test_lib.hrl with recent versions of kernel and stdlibSiri Hansen
2013-04-17Update "old vsn" in sasl test to R15 instead of R14 (two back from R17)Siri Hansen
2011-11-17Restart emulator before running upgrade script when erts is upgradedSiri Hansen
If the version of erts differs between two releases, the release handler automatically adds a 'restart_new_emulator' instruction to the upgrade script (relup). Earlier, this instruction was always added at the end of the upgrade script, causing the following sequence of operations during an upgrade (a bit simplified): 1. suspend processes 2. load new code 3. execute code_change functions 4. resume processes 5. restart emulator with new erts version Obviously, this caused the new code to be loaded into the old emulator and this would fail if the beam format had been changed in the new version of the emulator. To overcome this problem, this commit changes the order of the instructions, so for upgrade with changed erts version we now have: 1. restart emulator with new erts, kernel, stdlib and sasl versions, but old versions of all other applications. 2. suspend processes 3. load new code 4. execute code_change functions 5. resume processes This is implemented by creating a temporary release, including new erts, kernel, stdlib and sasl from the new release and all other applications from the old release. A new boot file for this temporary release is created, which includes a new 'apply' instruction to run release_handler:new_emulator_upgrade/2. Then the emulator is restarted using this boot file - and release_handler:new_emulator_upgrade/2 executes the rest of the upgrade script. For downgrade, the order will be as before: 1. suspend processes 2. execute code_change functions with 'down'-indication 3. load old code 4. resume processes 5. restart emulator with old erts version