Project

General

Profile

Actions
Copy link

Bug #15248

closed

qa tests in ncf does not fail if there is an error in the tests

Added by Félix DALLIDET over 5 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
Alexis Mousset
Category:
Packaging
Target version:
5.0.13
Pull Request:
https://github.com/Normation/ncf/pull...
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

Actions
Copy link
 #1

Updated by Félix DALLIDET over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Félix DALLIDET
Actions
Copy link
 #2

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
Actions
Copy link
 #3

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
Actions
Copy link
 #4

Updated by Félix DALLIDET over 5 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:b3c45b880520196fabb9b43190feecff6117603d.

Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 5 years ago

  • Fix check changed from To do to Checked
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 5.0.13 which was released today.

Actions
Copy link
 #7

Updated by Alexis Mousset over 2 years ago

  • Project changed from 41 to Rudder
  • Category changed from Packaging to Packaging
Actions
Copy link

Also available in: Atom PDF