-
Notifications
You must be signed in to change notification settings - Fork 166
[chore][ansible] Fix failing Windows tests #6246
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
Conversation
Set python action version use working 2022 box for 2019, StefanScherer/windows_2016, increase memory and set python deps Clean cache fix vagrant box versions set valid versions for vagrant boxes Different requirements.txt files for different ansible versions Use StefanScherer/windows_2019 for 2019
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6246 +/- ##
==========================================
+ Coverage 44.82% 44.86% +0.03%
==========================================
Files 390 390
Lines 26983 26983
==========================================
+ Hits 12096 12106 +10
+ Misses 14017 14009 -8
+ Partials 870 868 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
21f1f19
to
90ee27f
Compare
- name: free after clean cache | ||
run: | | ||
free -h | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit;
Shall we add a debug flag to display this info if needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about it but I'm thinking of keeping it for now. My thought process is that with flaky failures we ideally want this output when it fails, as it may pass the next time when it's run with debugging.
I'd be happy to remove in the future if it's too much noise or use a debug flag if you disagree 👍
Description:
Ansible tests on Windows recently started failing with
VERR_NO_LOW_MEMORY
andVERR_NO_CONT_MEMORY
errors. This was not caused by any change in our repository, the likely culprit is the GitHub workflow doingapt update
and picking up new dependencies that broke the vagrant box configurations being used. The changes included here are the minimal changes required to reduce flakiness and get Windows tests passing again.apt
andpython
dependencies.