Project

General

Profile

Actions

action #88837

open

Separate out style checks into a dedicated environment

Added by livdywan over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
Start date:
2021-02-19
Due date:
% Done:

0%

Estimated time:

Description

Observation

Especially in the context of CI, perltidy and other style checks can get mixed up with cache failures or other test failures.

Suggestion

  • Run perltidy separate from other tests
  • Run style checks in a smaller environment where the general cached isn't used
  • Consider style checks in general here, although tidy might be seen as the most prominent one to look out for

Related issues 1 (1 open0 closed)

Related to openQA Project - action #73309: every time a direct dependency is updated in Factory our CI jobs fail until the package is updatedWorkable2020-10-13

Actions
Actions #1

Updated by livdywan over 3 years ago

  • Related to action #73309: every time a direct dependency is updated in Factory our CI jobs fail until the package is updated added
Actions #2

Updated by okurz over 3 years ago

  • Target version set to future
Actions

Also available in: Atom PDF