-
Notifications
You must be signed in to change notification settings - Fork 190
chore: use go build constraint #289
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #289 +/- ##
==========================================
- Coverage 54.68% 52.74% -1.94%
==========================================
Files 9 9
Lines 673 673
==========================================
- Hits 368 355 -13
- Misses 262 271 +9
- Partials 43 47 +4 ☔ View full report in Codecov by Sentry. |
|
@thaJeztah I just noticed that this would solve #277 as well |
pass/pass.go
Outdated
| @@ -1,3 +1,6 @@ | |||
| //go:build linux || darwin | |||
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.
slightly on the fence on this one; I think the code in this repo works fine on any platform (if there's a pass binary to shell out to?)
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.
agree, switched to unix.
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.
actually !windows looks better.
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.
So for the pass helper; I guess the thing I was wondering here was that;
- the code in this repository (the helper itself) is basically platform-agnostic (including Windows)
- the "only" limitation we have for testing is that we don't have a
passbinary on Windows - so, wondering if we should actually exclude it on Windows?
- (but indeed, we can't currently run the tests, as those depend on a
passbinary) - ^^ do we know if there's an implementation of the
passbinary for windows?
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.
It looks like there's at least one implementation (although last release is really old; https://github.com/mbos/Pass4Win)
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.
Tried to install Pass4Win in ci but binary is not named pass.exe 😣 https://github.com/docker/docker-credential-helpers/actions/runs/5110526809/jobs/9186513917#step:9:8
So disable tests for windows in the meantime. Let me know if you prefer a specific tag like exclude_pass_tests that would be just set in CI.
8bc3973 to
239923b
Compare
2791d66 to
a031c52
Compare
|
Look like it timed out or so 😔 |
399b954 to
492a7b1
Compare
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
492a7b1 to
72391b3
Compare
|
@thaJeztah PTAL when you can 🙏, would like to rebase #288 |
thaJeztah
left a comment
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.
LGTM
fixes #176
Switch to go build constraint. This allows to run tests against the right architecture. Errors in
passtests are now properly handled.