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

test: unskip passing setContent test #648

Closed
wants to merge 1 commit into from

Conversation

yury-s
Copy link
Member

@yury-s yury-s commented Jan 25, 2020

No description provided.

@yury-s yury-s changed the title test(webkit): unskip passing setContent test test: unskip passing setContent test Jan 25, 2020
@pavelfeldman
Copy link
Member

It was just skipped for being flaky, so I guess we can't do that!

@yury-s
Copy link
Member Author

yury-s commented Jan 25, 2020

If it's flaky, we should fix it, not skip. It passed a few iterations for me.

@@ -534,7 +534,7 @@ module.exports.describe = function({testRunner, expect, headless, playwright, FF
const result = await page.content();
expect(result).toBe(expectedOutput);
});
it.skip(FFOX || WEBKIT)('should not confuse with previous navigation', async({page, server}) => {
it('should not confuse with previous navigation', async({page, server}) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

This reliably does not work with .repeat(100) and -j 10 on my mac. I spent two hours trying to make it work on WebKit, and it seems like we don't always get load event after setContent. I'll keep digging.

@yury-s yury-s closed this Jan 27, 2020
@yury-s yury-s deleted the enable-test branch January 28, 2020 00:54
sand4rt pushed a commit to sand4rt/playwright that referenced this pull request Dec 21, 2022
sand4rt pushed a commit to sand4rt/playwright that referenced this pull request Dec 21, 2022
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