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

[Regression] Improve reliability for DNS-SD change #1040

Closed
youngbupark opened this issue Apr 3, 2024 · 5 comments
Closed

[Regression] Improve reliability for DNS-SD change #1040

youngbupark opened this issue Apr 3, 2024 · 5 comments
Labels
bug Something is broken or not working as expected flaky-test Flaky functional/unit tests triaged This item has been triaged by project maintainers and is in the backlog

Comments

@youngbupark
Copy link
Contributor

youngbupark commented Apr 3, 2024

Problem

This is the regression bug after we merge this PR to use DNS-SD.

We have to fix the tests, so that it works with new DNS-SD based eshop.
Since we removed HTTPRoutes, there is more parallelization and the deployment is ready after a few seconds of printing out the success message.
The tests always pass the second time.

Web application is ready: http://localhost/
Error text: "Failed to load resource: the server responded with a status of 404 (Not Found)"
Error text: "Failed to load resource: the server responded with a status of 404 (Not Found)"
Error text: "Failed to load resource: the server responded with a status of 500 (Internal Server Error)"
Error text: "[2024-03-23T15:50:44.663Z] Error: Failed to complete negotiation with the server: Error"
Error text: "[2024-03-23T15:50:44.666Z] Error: Failed to start the connection: Error"
Error text: "Failed to load resource: net::ERR_NAME_NOT_RESOLVED"

Related issues

#1022
#1025
#1021

AB#11694

@youngbupark
Copy link
Contributor Author

@nithyatsu I created the separate issue for the regression after we removing httproute.

@youngbupark youngbupark changed the title Improve reliability for DNS-SD change [Regression] Improve reliability for DNS-SD change Apr 3, 2024
@youngbupark youngbupark added bug Something is broken or not working as expected flaky-test Flaky functional/unit tests labels Apr 3, 2024
@sylvainsf
Copy link

@nithyatsu Can you please look into this?

@sylvainsf sylvainsf added the triaged This item has been triaged by project maintainers and is in the backlog label Apr 4, 2024
@nithyatsu
Copy link
Contributor

I am looking into this, but I don't seem to have permissions to assign the issue to myself @sylvainsf

@nithyatsu
Copy link
Contributor

This seemed like a regression to me initially, but it is not, since I see the same issue logged by @vinayada1 sometime last year november. #885 @youngbupark @sylvainsf

@willdavsmith
Copy link
Contributor

Closing in favor of #885

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken or not working as expected flaky-test Flaky functional/unit tests triaged This item has been triaged by project maintainers and is in the backlog
Projects
None yet
Development

No branches or pull requests

4 participants