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

[wasm-browser][tests] Fix issue with some tests exiting with no output #300

Merged
merged 1 commit into from
Aug 24, 2020

Conversation

radical
Copy link
Member

@radical radical commented Aug 21, 2020

The problem here is that these tests run very quickly, writing to the
console.log very fast, and selenium seems to not return the logs during
that time. So, when the tests are done, which is indicated by an html
element being set, we stop listening for more log messages.
And exit with the test exit code, but no output messages from the test
run.

Eg: System.Data.Common

The problem here is that these tests run very quickly, writing to the
console.log very fast, and selenium seems to not return the logs during
that time. So, when the tests are done, which is indicated by an html
element being set, we stop listening for more log messages.
And exit with the test exit code, but no output messages from the test
run.

Eg: `System.Data.Common`
@radical
Copy link
Member Author

radical commented Aug 21, 2020

/cc @directhex @akoeplinger

This might fix, or help with debugging the wasm test-browser failures.

@radical
Copy link
Member Author

radical commented Aug 21, 2020

/cc @premun

@premun
Copy link
Member

premun commented Aug 24, 2020

@radical would you happen to have example builds where I could see the problem?

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