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

Run the "no-default-features" tests in CI #2056

Closed
Tracked by #1692
Velfi opened this issue Dec 2, 2022 · 1 comment · Fixed by #2255
Closed
Tracked by #1692

Run the "no-default-features" tests in CI #2056

Velfi opened this issue Dec 2, 2022 · 1 comment · Fixed by #2255
Labels
ops Improves our operations and release process production-readiness

Comments

@Velfi
Copy link
Contributor

Velfi commented Dec 2, 2022

I created the "no-default-features" tests as part of #2055

In order to unblock the release, we decided not to implement a new CI mechanism to run those tests in CI. However, the tests aren't very useful if we don't start doing that.

To whomever takes this on: update CI to start running integration tests that aren't associated with a specific service and that reside in their own crate.

@Velfi Velfi added the ops Improves our operations and release process label Dec 2, 2022
@jdisanti jdisanti mentioned this issue Dec 12, 2022
28 tasks
@goabv goabv assigned goabv and Velfi and unassigned goabv Dec 28, 2022
@Velfi
Copy link
Contributor Author

Velfi commented Dec 28, 2022

I spoke to the examples team about moving this into their repo and they aren't interested unless we can demonstrate the usefulness of these tests as examples.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ops Improves our operations and release process production-readiness
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants