Various test / policy file cleanups guided by cfengine lint#6115
Various test / policy file cleanups guided by cfengine lint#6115olehermanse merged 6 commits intocfengine:masterfrom
Conversation
cfengine lint generally considers empty files to be a problem, because they could be the result of a failed transfer, failed write, or similar. Thus, adding a comment here to avoid having an empty .cf file. Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>
Didn't change all of them - left the ones which seem like the test is for testing ifvarclass specifically. Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>
Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>
The test using this file was removed in: ef10f3b 13 years ago. Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>
|
@cf-bottom jenkins please |
|
Sure, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/13732/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-13732/ |
Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>
Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>
|
Waiting for Jenkins |
|
@cf-bottom jenkins |
|
Alright, I triggered a build: Jenkins: https://ci.cfengine.com/job/pr-pipeline/13742/ Packages: http://buildcache.cfengine.com/packages/testing-pr/jenkins-pr-pipeline-13742/ |
craigcomstock
left a comment
There was a problem hiding this comment.
looks fine to me. I am investigating valgrind-check failure in https://northerntech.atlassian.net/browse/ENT-13720
@craigcomstock My conclusion is that valgrind-checks failure is unrelated, because:
I will go ahead and merge this :) |
No description provided.