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

Use staging server for gz_TEST #412

Closed
wants to merge 1 commit into from

Conversation

azeey
Copy link
Contributor

@azeey azeey commented Apr 9, 2024

🦟 Bug fix

Summary

This test has lately been timing out more frequently. Switching to the staging server should hopefully help.

Checklist

  • Signed all commits for DCO
  • Added tests
  • Updated documentation (as needed)
  • Updated migration guide (as needed)
  • Consider updating Python bindings (if the library has them)
  • codecheck passed (See contributing)
  • All tests passed (See test coverage)
  • While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Signed-off-by: Addisu Z. Taddese <[email protected]>
@azeey azeey requested a review from nkoenig as a code owner April 9, 2024 19:32
@github-actions github-actions bot added the 🏯 fortress Ignition Fortress label Apr 9, 2024
@nkoenig
Copy link
Contributor

nkoenig commented Apr 29, 2024

I'm going to close this. The timeout was due to a high number of DB connections from Gazebo11.

@nkoenig nkoenig closed this Apr 29, 2024
@azeey azeey deleted the use_staging branch April 29, 2024 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏯 fortress Ignition Fortress
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

2 participants