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

ci: Update spectests branch - skipping tests for post-1.0 features #836

Merged
merged 1 commit into from
Jun 23, 2022

Conversation

gumb0
Copy link
Collaborator

@gumb0 gumb0 commented Jun 22, 2022

Simpler alternative to #750

Branch with new tests: wasmx/wasm-spec#4

@codecov
Copy link

codecov bot commented Jun 22, 2022

Codecov Report

Merging #836 (70a85d5) into master (8f379dc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #836   +/-   ##
=======================================
  Coverage   99.27%   99.27%           
=======================================
  Files          88       88           
  Lines       13296    13296           
=======================================
  Hits        13199    13199           
  Misses         97       97           
Flag Coverage Δ
rust 98.37% <ø> (ø)
spectests 89.92% <ø> (ø)
unittests 99.22% <ø> (ø)
unittests-32 99.32% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@axic
Copy link
Member

axic commented Jun 22, 2022

Looks good to me, this skips that monster commit. Should date the tag though.

@gumb0 gumb0 force-pushed the update-spectests-0.8.0-simple branch from e5dd2c2 to 3865d76 Compare June 23, 2022 12:57
@gumb0 gumb0 force-pushed the update-spectests-0.8.0-simple branch from 3865d76 to 70a85d5 Compare June 23, 2022 13:28
@gumb0 gumb0 marked this pull request as ready for review June 23, 2022 13:32
@gumb0 gumb0 requested review from chfast and axic June 23, 2022 13:55
@gumb0 gumb0 merged commit 5638d05 into master Jun 23, 2022
@gumb0 gumb0 deleted the update-spectests-0.8.0-simple branch June 23, 2022 15:12
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.

3 participants