Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

Simulate failures of the Testing Infrastructure #3

Closed
12 tasks
victorb opened this issue Jan 29, 2017 · 1 comment
Closed
12 tasks

Simulate failures of the Testing Infrastructure #3

victorb opened this issue Jan 29, 2017 · 1 comment

Comments

@victorb
Copy link
Collaborator

victorb commented Jan 29, 2017 •
edited
Loading

Description

To make sure we can quickly restart jenkins and workers, and that the alerts are working, we'd like to have simulated failures we can use as testing.

Acceptance Criteria

  • Can simulate failure easily
  • Simulated failures happens on a regular interval
  • When failures happen, we get alerted

Tasks

  • Find way to kill Jenkins master
  • Find way to kill workers one-per-one or randomly
  • Decide interval of simulated failures
  • Make sure that alerts are triggered
  • Be able to simulate different failures
    • Full hdd
    • Was OOM killed
    • (Random process kill?)
    • Loosing connectivity with internet backbone

Dependencies

Depends on #1
Depends on #2
Depends on #8
@victorb victorb mentioned this issue Jan 29, 2017
Closed
5 tasks
@Kubuxu Kubuxu removed the ready label Mar 2, 2017
@victorb victorb removed the sprint label Oct 6, 2017
@victorb
Copy link
Collaborator Author

victorb commented Aug 13, 2018

This issue was moved to ipfs-inactive/dev-team-enablement#76

@victorb victorb mentioned this issue Aug 13, 2018
Open
12 tasks
@victorb victorb closed this as completed Aug 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@victorb @Kubuxu