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

Allow for asynchronousness in span processing in test #45963

Merged
merged 1 commit into from
Jan 30, 2025

Conversation

holly-cummins
Copy link
Contributor

Resolves #45955

@holly-cummins
Copy link
Contributor Author

What do you think of this, @brunobat? One of my goals with https://github.com/orgs/quarkusio/projects/30 is that it shouldn't be necessary to change any tests, and this changes a test. But I think I have a plausible explanation for why my changes expose a problem that's actually a test issue?

This comment has been minimized.

@holly-cummins holly-cummins changed the title Allow for asynchronousness in span processing Allow for asynchronousness in span processing in test Jan 29, 2025
@holly-cummins holly-cummins force-pushed the allow-asynchronous-otel branch from b64220f to 2c7889e Compare January 30, 2025 09:05
Copy link

quarkus-bot bot commented Jan 30, 2025

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 2c7889e.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

@gsmet gsmet requested a review from brunobat January 30, 2025 10:10
@geoand geoand merged commit 199ce85 into quarkusio:main Jan 30, 2025
20 checks passed
@quarkus-bot quarkus-bot bot added this to the 3.19 - main milestone Jan 30, 2025
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.

Tests in opentelemetry-reactive project are sensitive to execution order
3 participants