Actions
Bug #16496
closed
StatusReportTest leads to inconsistant results
Bug #16496:
StatusReportTest leads to inconsistant results
Status:
Released
Priority:
N/A
Assignee:
Category:
Performance and scalability
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Reviewed
Fix check:
Checked
Regression:
Description
Depending on the machine on which it is executed, it takes one order of magnitude more time to finish.
That makes CI randomly red, certainly depending on the current load.
At least we need to give more time to let CI be green since it does not look like a genuine performance regression.
Updated by François ARMAND almost 6 years ago
- Status changed from New to In progress
Updated by François ARMAND almost 6 years ago
- Related to Bug #16468: Computation of ComplianceLevel generates too many objects added
Updated by François ARMAND almost 6 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/2702
Updated by François ARMAND almost 6 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|b2f444d470a5b3e5acafd2bcd37432621aebafcc.
Updated by François ARMAND almost 6 years ago
- Fix check changed from To do to Checked
Updated by Alexis Mousset over 5 years ago
- Name check changed from To do to Reviewed
Updated by Vincent MEMBRÉ over 5 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 5.0.16 which was released today.
Actions