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

test: Skip Fish test if not installed #1463

Merged
merged 1 commit into from
Jan 29, 2023

Conversation

hyperupcall
Copy link
Contributor

Summary

In the same style as #1423 and #1422, this only runs Fish tests if Fish is installed

Partially addresses #465 (part of the WSL errors are Fish not installed errors, even if the error isn't WSL-specific)

@hyperupcall hyperupcall requested a review from a team as a code owner January 29, 2023 01:34
Copy link
Contributor

@jthegedus jthegedus left a comment

Choose a reason for hiding this comment

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

Approving because we have this with the other types of Shells, however, I don't think this contributes to the linked WSL issues because we aren't actually running test cases in a WSL environment (something I do want to address once WSL2 can be run properly in GitHub CI).

Thanks!

@jthegedus
Copy link
Contributor

One of my concerns with code like this is it can potentially mask other issues. For instance, suppose that our CI env changes and doesn't properly install Fish, how will we be notified of this error.

Perhaps this check itself can be wrapped in a way that they aren't run during CI environments.

Another PR that ensures these tests are only skipped in non-CI environments would be ideal.

@jthegedus jthegedus merged commit aa0abfa into asdf-vm:master Jan 29, 2023
@hyperupcall hyperupcall deleted the fish-improvement branch January 29, 2023 01:52
@hyperupcall
Copy link
Contributor Author

That is a good point - a PR to ensure that the test if always ran in CI would prevent masking errors

@Stratus3D
Copy link
Member

One of my concerns with code like this is it can potentially mask other issues. For instance, suppose that our CI env changes and doesn't properly install Fish, how will we be notified of this error.

Yeah, that's a really good point. I'd prefer explicit DISABLE_FISH flags for envs that don't have Fish available

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.

None yet

3 participants