test: fix broken tests, for #5813 #6232
Merged
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
|
Download the artifacts for this pull request:
See Testing a PR.
|
rfay
approved these changes
May 22, 2024
|
I think we have trouble with Rancher and Colima as well. People wonder how we spend all our time as software developers :) |
|
Restarted a number of tests. Note that Colima has had a version update which was not supposed to affect anything, but it's updated via brew on all 3 arm64 machines. |
|
Thanks for being so smart to create this branch on ddev/ddev so we can properly solve this problems. If it's OK, let's fix all 3 things here in this PR. |
stasadev
force-pushed
the
20240522_stasadev_fix_windows_test
branch
from
c757830
to
ae1d7be
Compare
stasadev
changed the title
jonesrussell
pushed a commit
to jonesrussell/ddev
that referenced
this pull request
Jun 9, 2024
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.
The Issue
Buildkite error:
How This PR Solves The Issue
The error is a result of my refactoring in:
I thought the path would look like
/c/Users/..., but it isC:\Users\...Manual Testing Instructions
Automated Testing Overview
Related Issue Link(s)
Release/Deployment Notes