Skip to content

Print environment info on tests start #2175

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
Merged
merged 1 commit into from
Jul 15, 2022
Merged

Print environment info on tests start #2175

merged 1 commit into from
Jul 15, 2022
+26 −0

Conversation

JimBobSquarePants
Copy link
Member

Prerequisites

  • I have written a descriptive pull-request title
  • I have verified that there are no overlapping pull-requests open
  • I have verified that I am following the existing coding patterns and practice as demonstrated in the repository. These follow strict Stylecop rules 👮.
  • I have provided test coverage for my change (where applicable)

Description

Uses the BenchMarkDotNet tooling to print out environment information before running any tests.

Should be helpful figuring out what is happening with #2117 and #2173 (comment)

environment diagnostic output

Sorry, something went wrong.

@JimBobSquarePants JimBobSquarePants mentioned this pull request Jul 14, 2022
Merged
4 tasks
brianpopow
brianpopow approved these changes Jul 14, 2022
View reviewed changes
Copy link
Collaborator

@brianpopow brianpopow left a comment

Choose a reason for hiding this comment

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

Good idea, I think this can help with the above issues.

@JimBobSquarePants JimBobSquarePants merged commit 6f20d94 into main Jul 15, 2022
@JimBobSquarePants JimBobSquarePants deleted the js/test-environment-info branch July 15, 2022 04:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@brianpopow brianpopow

Assignees
No one assigned
Labels
unit tests
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@JimBobSquarePants @brianpopow