Skip to content

Conversation

@Cellule
Copy link
Contributor

@Cellule Cellule commented Oct 24, 2016

Do not run Wasm tests in Razzle at this time. Will reenable once we stabilize our spec implementation.
Re-enable f32 test that was disabled because of razzle issue.


This change is Reviewable

…tabilize our spec implementation.

Re-enable f32 test that was disabled because of razzle issue.
Copy link
Contributor

@dilijev dilijev left a comment

Choose a reason for hiding this comment

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

Looks good.

<compile-flags>-on:Wasm</compile-flags>
</default>
</test>
-->
Copy link
Contributor

Choose a reason for hiding this comment

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

Re-enabling the test f32.js as part of this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It was disabled for razzle, since I am disabling the whole folder for razzle, I wanted to ake the chance to reenable it before I forget

@dilijev
Copy link
Contributor

dilijev commented Oct 24, 2016

Signed off. Good to merge.

@chakrabot chakrabot merged commit 251385c into chakra-core:master Oct 25, 2016
chakrabot pushed a commit that referenced this pull request Oct 25, 2016
Merge pull request #1816 from Cellule:users/micfer/wasm/test

Do not run Wasm tests in Razzle at this time. Will reenable once we stabilize our spec implementation.
Re-enable f32 test that was disabled because of razzle issue.
@Cellule Cellule deleted the users/micfer/wasm/test branch October 25, 2016 00:07
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.

4 participants