Skip to content

ci: introduce riot, use it to run tracer tests #1737

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

Merged
merged 6 commits into from
Oct 23, 2020
Merged

Conversation

Kyle-Verhoog
Copy link
Member

This PR introduces the usage of riot for running tests starting with the tracer
tests.

@Kyle-Verhoog Kyle-Verhoog added the changelog/no-changelog A changelog entry is not required for this PR. label Oct 20, 2020
@Kyle-Verhoog Kyle-Verhoog marked this pull request as ready for review October 20, 2020 03:22
@Kyle-Verhoog Kyle-Verhoog requested a review from a team as a code owner October 20, 2020 03:22
Copy link
Contributor

@majorgreys majorgreys left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧨

@Kyle-Verhoog Kyle-Verhoog merged commit bbc2343 into master Oct 23, 2020
@Kyle-Verhoog Kyle-Verhoog deleted the kyle-verhoog/riot branch October 23, 2020 01:42
Czechh added a commit that referenced this pull request Oct 23, 2020
…nvocations

* master:
  ci: introduce riot, use it to run tracer tests (#1737)
  fix(django): add check for instrument view mro (#1744)
  fix: snapshot decorator for pytest fixtures (#1743)
  tests(logging): don't test warn (#1738)
  feat(flask): store request headers (#1735)
  ci: fix deploy_master (#1739)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog A changelog entry is not required for this PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants