Short Introduction to This Paper

This paper characterizes self-healing software systems by surveying some of the existing work in the field. It maps the space of software self-healing capabilities and discusses the risks and limitations inherent in automatic-reaction schemes. The structure of this paper is quite clear, including "what", "why", "how" and "future directions" on self-healing systems.

- 阅读剩余部分 (Read the rest) -

Short Introduction to This Paper

This paper proposes a taxonomy for describing the problem space for self-healing systems including fault models, system responses, system completeness, and design context. It is hoped that this taxonomy will help researchers understand what aspects of the system dependability problem they are (and aren't) addressing with specific research projects.

Highlights of This Paper

Problem space model elements

- 阅读剩余部分 (Read the rest) -

Concepts

Continuous Testing

Self-healing Software

Exception Handling

Useful For Experiments

Skills

Short Introduction to This Paper

This paper investigates the concept of a "program repair bot" and present Repairnator. The Repairnator bot is an autonomous agent that constantly monitors test failures, reproduces bugs, and runs program repair tools against each reproduced bug. If a patch is found, Repairnator bot reports it to the developers. At the time of writing, Repairnator uses three different program repair systems and has been operating since February 2017. In total, it has studied 11 317 test failures over 1 609 open-source software projects hosted on GitHub, and has generated patches for 17 different bugs.

Highlights of This Paper

  • A blueprint design of a program repair bot for continuous integration (CI) test failures
  • A set of unique empirical facts about program repair and bug reproduction collected over 11 317 test failures across 1 609 software projects
  • 7 recommendations to help future authors of program repair bots

- 阅读剩余部分 (Read the rest) -

Short Introduction to This Paper

This paper gives us an introduction about how Etsy uses "GameDay" to build more confidence about their system's behavior. Specifically, it includes the discussion about 1) why apply it in production environment, 2) how to do fault injection during a GameDay exercise, 3) business justification and 4) a case, limitations and fear.

Highlights of This Paper

  • Introduction about the provisioning of a server or cloud instance from zero to production
  • Explanation about why many complex systems are largely intractable
  • Pattern about GameDay exercise, introducing the methodology of how they doing fault injection in a real company

- 阅读剩余部分 (Read the rest) -