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

fix(shorebird_cli): flaky windows failure due to pkg:archive #1906

Merged
merged 3 commits into from
Apr 16, 2024

Conversation

felangel
Copy link
Contributor

Description

Type of Change

  • ✨ New feature (non-breaking change which adds functionality)
  • 🛠️ Bug fix (non-breaking change which fixes an issue)
  • ❌ Breaking change (fix or feature that would cause existing functionality to change)
  • 🧹 Code refactor
  • ✅ Build configuration change
  • 📝 Documentation
  • 🗑️ Chore

Copy link

codecov bot commented Apr 16, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (4fd3214) to head (6a325f3).
Report is 4 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1906   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          174       174           
  Lines         5476      5476           
=========================================
  Hits          5476      5476           
Flag Coverage Δ
shorebird_cli 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines +12 to +19
# We're using a specific commit because the latest published version (3.4.10)
# does not include a sync close API for ZipFileEncoder.
# https://github.com/brendan-duncan/archive/commit/94bf62410e9a073451bda0d851a07e8b8863bde4
# This was causing a flaky test on windows when using `shorebird preview`
# https://github.com/shorebirdtech/shorebird/issues/1902
archive:
git:
url: https://github.com/brendan-duncan/archive
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe leave a TODO here noting that we should switch away from a specific commit once a release containing the API we need is published

# https://github.com/shorebirdtech/shorebird/issues/1902
archive:
git:
url: https://github.com/brendan-duncan/archive
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit since this might be exaggerated concerns: Usually when I stumble in cases like this, I tend to fork the repo under a org that I have control, just to be safe that this commit will not vanish.

I know the odds of that happening is not much though, but it don't hurt to be overzealous haha

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I thought about that but it seemed like overkill. Ideally we'll move away from this as soon as the next version is published.

@felangel felangel merged commit 2972919 into main Apr 16, 2024
1 check passed
@felangel felangel deleted the fix/shorebird-cli-flaky-windows-failure branch April 16, 2024 18:38
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.

tests: flaky windows preview test
3 participants