Skip to content
This repository was archived by the owner on Jul 12, 2022. It is now read-only.

Improved CI to avoid 'killed signal' error #497

Closed
lucasdittrichzup opened this issue Sep 4, 2020 · 0 comments · Fixed by #503
Closed

Improved CI to avoid 'killed signal' error #497

lucasdittrichzup opened this issue Sep 4, 2020 · 0 comments · Fixed by #503
Assignees
@lucasdittrichzup
Labels
🔨 improvement Improvement in features ✔️ ready-for-review ready for review
Milestone
2.0.5

Comments

@lucasdittrichzup
Copy link
Contributor

What would you like to be added:
The CI intermittently presents a killed signal error when running the lint job. After some research, it was realized that it is a common problem in the community and the orientation is to add the machine resources explicitly through the resource_class property.

Why is this needed:
To avoid breaking the pipeline by the killed signal error.
@lucasdittrichzup lucasdittrichzup added the 🔨 improvement Improvement in features label Sep 4, 2020
@lucasdittrichzup lucasdittrichzup added this to the 2.0.5 milestone Sep 4, 2020
@lucasdittrichzup lucasdittrichzup self-assigned this Sep 4, 2020
This was linked to pull requests Sep 4, 2020
Improved CI to avoid 'killed signal' error #500
Closed
Improved CI to avoid 'killed signal' error #503
Merged
@brunasilvazup brunasilvazup added the ✔️ ready-for-review ready for review label Sep 8, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@lucasdittrichzup lucasdittrichzup

Labels
🔨 improvement Improvement in features ✔️ ready-for-review ready for review
Projects
None yet
Milestone
2.0.5
2 participants
@brunasilvazup @lucasdittrichzup