Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shellcheck failing on fedora32 #80

Open
deepshikhaaa opened this issue Mar 11, 2021 · 7 comments
Open

shellcheck failing on fedora32 #80

deepshikhaaa opened this issue Mar 11, 2021 · 7 comments
Assignees

Comments

@deepshikhaaa
Copy link
Member

No description provided.

@deepshikhaaa
Copy link
Member Author

deepshikhaaa commented Mar 11, 2021

shellcheck was not installed on community cage fedora builders and the job did not fail when there was no shellcheck. We need to have a proper check for the same.

And now since the AWS fedora builders have shellcheck https://github.com/gluster/gluster.org_ansible_configuration/blob/c0e209a3151c470dd6e953d7df154986e53bd0ba/roles/jenkins_builder/tasks/pkgs_job_shellcheck.yml and the inventory https://github.com/gluster/gluster.org_ansible_configuration/blob/4f8e7eda1e4e965ba63216af0bd602a55c6c2237/hosts#L46 , it started failing.

@deepshikhaaa
Copy link
Member Author

Already discussed on the same #53

@mscherer
Copy link
Collaborator

It fail because we have warnings/errors. So the job is working in that it detect what is supposed to be detected (which it didn't before). I would suggest we make it non blocking or something since there is no fast/clear path toward a resolution (like, do we want to fix the 2M of warning ?)

@amarts
Copy link
Member

amarts commented Mar 11, 2021

Lets start with 'non-blocking' mode to start with! We can decide how to resolve it eventually!

@deepshikhaaa
Copy link
Member Author

I have removed the shellcheck job from the list of jobs to pass before merging.

@pranithk
Copy link
Member

I have removed the shellcheck job from the list of jobs to pass before merging.

@deepshikhaaa Is this change deployed? I just did recheck smoke on gluster/glusterfs#2259 and it still failed.

@deepshikhaaa
Copy link
Member Author

@pranithk The issue you linked here is missing the approval from reviewers. shellcheck is not blocking the merge here.

@amarts @mscherer I am not sure how to deal with a situation where we might miss out on the new shellcheck related errors. Any suggestions?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants