News for hackers. Stuff that matters.
Re:The tragedy of 100% code coverage (2016) by ReligiousFlames on Tuesday May 09, 2017 @01:15AM (#14297886)
This is what I love about the design and operational philosophy of the Erlang/OTP evironment: the trickier class of harder-to-test/reproduce transient/timing pre-defensive-coding issues can sometimes be resolved automagically under supervision trees restarting said Erlang process. Log the stacktrace as a failure to maybe be fixed and move on. That's in addition to a robust soft-realtime, SMP VM which allows remote, live debugging.
Re:The tragedy of 100% code coverage (2016) by d6e on Tuesday May 09, 2017 @02:50PM (#14302826)
As a newbie to Erlang, how does Erlang handle this case better for a service than a Python process which logs and restarts on failure? Also, this runtime testing strategy doesn't handle cases where you have other systems depending on that Erlang code path being successful, does it?.