Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

ginkgo-project / ginkgo Public

Notifications You must be signed in to change notification settings
Fork 94
Star 435

Code
Issues 108
Pull requests 37
Discussions
Actions
Projects 1
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Allow passing matrix filename as benchmark input#1387

Merged

upsj merged 6 commits intodevelopginkgo-project/ginkgo:developfrom benchmark_matrix_inputginkgo-project/ginkgo:benchmark_matrix_inputCopy head branch name to clipboard

Aug 17, 2023

+624-36

Conversation Commits6 (6)Checks Files changed

Commits

Commits on Aug 17, 2023

allow passing matrix filename as benchmark input
upsj
committed
add -input_matrix flag
upsj
committed
test -input_matrix flag
upsj
committed
use absolute path
upsj
committed
review updates

committed
escape file path using rapidJSON
upsj
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.