-
-
Notifications
You must be signed in to change notification settings - Fork 176
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 failing GitHub Actions CI #475
Open
beau-witter
wants to merge
92
commits into
vexx32:main
Choose a base branch
from
beau-witter:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Remove more unnecessary references to pesterinfo file Remove unused dependencies file Adjust version of Pester in readme
Also show what is located in $env:PROJECTROOT/PSKoans and what is in $env:BUILTMODULEPATH
GitHub env acts differently when set in the yml
Also adds printout of all env variables
It seems that scripts need to have their environment variables passed in from the actions yaml
Also clean up some of the unused debugging Flattens if/else now that I know which var is the correct one
Also add some output statements for clarity
Also, store the calculated path variable for use in later copying
I am trying to understand how the env variables sometime pass in correct and sometimes are only seemingly visible (when viewing the action output) but not when trying to reference them in code.
Accidentally using powershell syntax instead of github actions
Also corrects all remaining variable references
Fix test results path so the entire workspace is not packaged Upload code coverage results revert publish job to as it was
Based on https://github.com/EnricoMi/publish-unit-test-result-action/blob/v2.4.1/README.md#github-action-to-publish-test-results Also add new workflow to support this
May still be a good idea to update to a non-deprecated action for publishing test results
This reverts commit 405b8fb.
This reverts commit ec1ec3c.
Also try to output code coverage results for extra information (why does code coverage state 0% when it should currently be around 8%?)
Also remove passthru and adjust output to detailed
Just the Tests folder for where to run from Just the PSKoans folder for where the source files are.
This should allow Code Coverage to more directly link tests to their respective files Also chang the variable in the KoanValidation tests to actually print
Also demote output back to Normal from Detailed
Also commented out suspected unneccesary step in the Test job
Also remove sanity debug output
Remove unneccesary docs inclusion in tests
Bump download-artifact to v3 to dismiss warning
I also added a new workflow called ".github/workflows/unit-test-results.yml" that is meant to display the actual code coverage results due to limitations of generating reports on fork PRs as described here: https://github.com/marketplace/actions/publish-test-results#support-fork-repositories-and-dependabot-branches |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Attempts to fix the failing github actions based on the error message.
Context
The GitHub Actions CI appears to be failing and based on following up on the error message, this change should help.
Changes
Checklist