[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Deployment with running test will fail #1823

Closed
1 task done
kigawas opened this issue Jul 15, 2024 · 3 comments
Closed
1 task done

[Bug]: Deployment with running test will fail #1823

kigawas opened this issue Jul 15, 2024 · 3 comments
Labels
S-Triage Awaiting decision for what to do T-Bug Something isn't working

Comments

@kigawas
Copy link
kigawas commented Jul 15, 2024

What happened?

Deploy with test cargo shuttle deploy will fail with:

2024-07-16T01:56:22.974+09:00 [Deployer]  INFO shuttle_proto::_runtime_client: connecting runtime client
2024-07-16T01:56:29.975+09:00 [Deployer]  INFO Entering Crashed state
2024-07-16T01:56:29.975+09:00 [Deployer]  INFO Cleaning up startup crashed deployment
2024-07-16T01:56:29.975+09:00 [Deployer] ERROR shuttle_deployer::deployment::run: {error="Failed to get runtime: failed to start shuttle runtime"} Service startup encountered an error

Deployment crashed

Run the following for more details

cargo shuttle logs 1daab0f7-ed00-4392-9c76-1373e214f083

--no-test is fine

Version

v0.46.0

Which operating system(s) are you seeing the problem on?

In deployment

Which CPU architectures are you seeing the problem on?

In deployment

Relevant log output

See above

Duplicate declaration

  • I have searched the issues and there are none like this.
@kigawas kigawas added S-Triage Awaiting decision for what to do T-Bug Something isn't working labels Jul 15, 2024
@kigawas kigawas changed the title [Bug]: Run test before deployment will fail [Bug]: Deployment with running test will fail Jul 15, 2024
@joshua-mo-143
Copy link
Member

Hi, are you using any tests in your application? Shuttle will try to run tests by default if there are any.

A common cause of failure might be that you're trying to use something like testcontainers that spins up dev containers locally, which the Shuttle environment currently can't do (and will therefore invalidate the tests).

@kigawas
Copy link
Author
kigawas commented Jul 19, 2024

There should be no test containers, just axum routers

@jonaro00
Copy link
Member

Closing since the new shuttle.dev builder will not run tests by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
S-Triage Awaiting decision for what to do T-Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kigawas @jonaro00 @joshua-mo-143