Actions
action #88837
openSeparate out style checks into a dedicated environment
Status:
New
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
QA (public, currently private due to #173521) - future
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
Updated by livdywan almost 4 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