Skip to content

[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

Merged
merged 7 commits into from
May 23, 2025

Conversation

crobert-1
Copy link
Contributor

@crobert-1 crobert-1 commented May 23, 2025

Description:

Ansible tests on Windows recently started failing with VERR_NO_LOW_MEMORY and VERR_NO_CONT_MEMORY errors. This was not caused by any change in our repository, the likely culprit is the GitHub workflow doing apt 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.

  • Increase memory allocated to Vagrant boxes from 4GB to 8GB
  • Switch Vagrant boxes being used for Windows 2016 and Windows 2019. The Vagrant boxes being used hadn't changed, but could not pass testing with current apt and python dependencies.
  • Address VirtualBox failures by clearing cache as noted in bug links.

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
Copy link

codecov bot commented May 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.86%. Comparing base (6dff418) to head (9948aaf).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@crobert-1 crobert-1 force-pushed the ansible_cherry_picked branch from 21f1f19 to 90ee27f Compare May 23, 2025 18:43
@crobert-1 crobert-1 marked this pull request as ready for review May 23, 2025 20:51
@crobert-1 crobert-1 requested review from a team as code owners May 23, 2025 20:51
- name: free after clean cache
run: |
free -h

Copy link
Contributor

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?

Copy link
Contributor Author

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 👍

@crobert-1 crobert-1 merged commit dd4fb76 into signalfx:main May 23, 2025
94 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators May 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants