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

Sets Origin.Port to fix "port already in use" error that occurs occas… #1044

Closed

Conversation

turetske
Copy link
Collaborator

@turetske turetske commented Apr 3, 2024

…ionally in S3 Origin tests

@turetske turetske requested a review from jhiemstrawisc April 3, 2024 21:30
@turetske turetske force-pushed the fix-flaky-s3-origin-test branch from e286476 to 83017e5 Compare April 3, 2024 21:59
@bbockelm
Copy link
Collaborator

bbockelm commented Apr 5, 2024

Did the wrong branch get force pushed here? It doesn't seem like the code changes match the PR title.

@turetske
Copy link
Collaborator Author

turetske commented Apr 5, 2024

Did the wrong branch get force pushed here? It doesn't seem like the code changes match the PR title.

This was two issues. One, after realizing it was a more complex issue than the port change and that broke everything more, we decided to remove the virtual mode test (since it wasn't really serving a purpose right now) and I didn't update the description AND it looks like a rebase off of main went funky. I'll repair it today.

@turetske turetske closed this Apr 5, 2024
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.

3 participants