-
Notifications
You must be signed in to change notification settings - Fork 10
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 tests #472
Fix tests #472
Conversation
- Update checkout action to version v3 - Use new docker layer caching version - Simplify commands to handle docker compose shell commands - Update codecov action
Codecov Report
@@ Coverage Diff @@
## mampf-next #472 +/- ##
==============================================
+ Coverage 65.44% 66.65% +1.21%
==============================================
Files 302 311 +9
Lines 8965 9360 +395
==============================================
+ Hits 5867 6239 +372
- Misses 3098 3121 +23
... and 4 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
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.
Wow, thanks for making this work, much appreciated. After this, #441 is not needed anymore, right?
|
||
- name: Pull docker images | ||
run: docker compose pull --ignore-buildable | ||
working-directory: docker/run_cypress_tests |
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.
Maybe rename the folder to docker/run_tests
as it is not specifically for Cypress tests anymore.
Yes #441 can be closed, I cherry-picked one of your commits. |
Fix all checks. Tests are executed sequentially to utilize cache.
Please check if the PR fulfills these requirements
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: