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

Fix benchmark running on CI #35

Merged
merged 1 commit into from
Jun 29, 2020

Conversation

alexcrichton
Copy link
Member

  • Make sure the main branch is available to checkout
  • Fix collection of tests (currently zero benchmarks are run)

* Make sure the `main` branch is available to checkout
* Fix collection of tests (currently zero benchmarks are run)
Copy link
Collaborator

@Robbepop Robbepop left a comment

Choose a reason for hiding this comment

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

LGTM
Especially the new collect_test_files looks clean, thanks!
When fixing the benchmarks I didn't know whether the testsuite directory is actually required to be queried for benchmarks or not - looks like this wasn't the case according to this PR. Cannot say anything about the .github/workflow changes.

@alexcrichton
Copy link
Member Author

Hurray benchmarks are now 184100x slower! Also no worries @Robbepop :)

Gonna go ahead and merge to see the impact of #30

@alexcrichton alexcrichton merged commit 5fd8bb4 into bytecodealliance:main Jun 29, 2020
@alexcrichton alexcrichton deleted the fix-benchmarks branch June 29, 2020 16:47
fitzgen pushed a commit to fitzgen/wasm-tools that referenced this pull request Oct 21, 2020
Looks like the spec tests want a validation error, not a parse error,
when the lane is out of bounds.

Closes bytecodealliance#35
dhil pushed a commit to dhil/wasm-tools that referenced this pull request Oct 19, 2022
dhil added a commit to dhil/wasm-tools that referenced this pull request Nov 28, 2023
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.

2 participants