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

tracetest cli and server versions mismatch problem/warning #1784

Open
sophiaxu0424 opened this issue Nov 20, 2024 · 1 comment
Open

tracetest cli and server versions mismatch problem/warning #1784

sophiaxu0424 opened this issue Nov 20, 2024 · 1 comment
Labels
question Further information is requested

Comments

@sophiaxu0424
Copy link

When enabling API observability-driven testing using
docker compose -f docker-compose-tests.yml run traceBasedTests
I am having mismatch problem/warning like below:

I've using darwin/arm64 as my platform is in tracetest/docker-compose.yaml file and the server container is up and running for now.
not sure if this warning would affect the process to see the test result?

Starting tests...
Running trace-based tests for: adservice cartservice currencyservice checkoutservice frontend emailservice paymentservice productcatalogservice recommendationservice shippingservice ...

CLI: v1.7.1
Server: v1.5.2

✖️ Version Mismatch
The CLI version and the server version are not compatible. To fix this, you'll need to make sure that both your CLI and server are using compatible versions.
We recommend upgrading both of them to the latest available version. Check out our documentation https://docs.tracetest.io/configuration/upgrade for simple instructions on how to upgrade.
Thank you for using Tracetest! We apologize for any inconvenience causedCLI: v1.7.1
Server: v1.5.2
@sophiaxu0424 sophiaxu0424 added the question Further information is requested label Nov 20, 2024
@puckpuck
Copy link
Contributor

we recommend you run trace testing using the Make target

make run-tracetesting

I just ran this command from the main branch, and it ran successfully. Can you try running that command and confirm you are still having an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants