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

Pr25 fix intermittent non zero return code #26

Merged
merged 9 commits into from
Jun 17, 2022

Conversation

ctorgalson
Copy link
Owner

Includes fies for intermittend non-zero return code, hopefully fixes tests.

danoost and others added 3 commits June 16, 2022 16:39
`head` occasionally closes the pipe before `vim --version` finishes writing to it, causing the command to fail with return code 141 (exit due to SIGPIPE). An explicit `test` for code 141 ignores that without squashing other errors.
Fix intermittent non-zero return code
@ctorgalson ctorgalson self-assigned this Jun 16, 2022
@ctorgalson
Copy link
Owner Author

The tests actually run now. H/t to @robertdebock and @stefangweichinger for their work in stefangweichinger/ansible-rclone#105.

Not all of them pass, but that's on me :)

… in CI

- Re: pr25-fix-intermittent-non-zero-return-code
- Re: pr25-fix-intermittent-non-zero-return-code
- Re: pr25-fix-intermittent-non-zero-return-code
- Re: pr25-fix-intermittent-non-zero-return-code
- Re: pr25-fix-intermittent-non-zero-return-code
- Since the last release, we've been handling all file operations *as* a certain
  user, so we can rely on that to ensure the group and mode are set in line with
  the system's configuration.
- We're still testing for group since (in the context of the tests) a group that
  is NOT identical to vim_owner is a sign that something's gone wrong with some
  task's become and become_user settings.
- Re: pr25-fix-intermittent-non-zero-return-code
@ctorgalson ctorgalson merged commit efb7d82 into master Jun 17, 2022
@ctorgalson ctorgalson deleted the pr25-fix-intermittent-non-zero-return-code branch June 17, 2022 08:46
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

Successfully merging this pull request may close these issues.

2 participants