Actions
Bug #15248
closedqa tests in ncf does not fail if there is an error in the tests
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
Description
We are only keeping the latest exit satus of the tests, which is pylint.
We should add a set -e as easy fix
Updated by Félix DALLIDET over 5 years ago
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
Updated by Félix DALLIDET over 5 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Alexis Mousset
- Pull Request set to https://github.com/Normation/ncf/pull/1022
Updated by Félix DALLIDET over 5 years ago
- Subject changed from qa tests in ncf does not fails if there is an error in the tests to qa tests in ncf does not fail if there is an error in the tests
Updated by Félix DALLIDET over 5 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset b3c45b880520196fabb9b43190feecff6117603d.
Updated by Vincent MEMBRÉ over 5 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.13 which was released today.
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category changed from Packaging to Packaging
Actions