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

"Error POSTing DOM" happening regularly #235

Closed
krasnoukhov opened this issue Sep 23, 2020 · 3 comments
Closed

"Error POSTing DOM" happening regularly #235

krasnoukhov opened this issue Sep 23, 2020 · 3 comments

Comments

@krasnoukhov
Copy link
Contributor

Thanks to the merge of #234 we've been able to upgrade to the most recent Percy stack. However, I've noticed that our builds fail to create all snapshots with the log message originating here:

https://github.com/percy/ember-percy/blob/40cb769830e5688238c34ffa7b9f03b2d9e53d15/addon-test-support/%40percy/ember/index.js#L137

The message is like this:

LOG: [percy] Error POSTing DOM, disabling: TypeError: Failed to fetch

This happened 3-4 times already on different builds since yesterday, including the baseline builds. This makes things really problematic since it results in "bad" baseline build, which in turn results in a lot of diffs for branch builds.

Here's a most recent example: https://percy.io/simplepractice/simplepractice/builds/7002777

Not sure where that error is coming from (percy agent?) but perhaps this addon can add a retry logic of sorts? Any update would be appreciated.

@krasnoukhov
Copy link
Contributor Author

Any update on this? Still happening regularly.

@wwilsman
Copy link
Contributor

wwilsman commented Oct 7, 2020

Hey @krasnoukhov!

Are there any other logs in the browser console when you see that error? According to search results, that error comes from fetch when there is something up with the response and it seems like it is typically cors related. The local percy server uses a cors middleware to accept all requests, so I wonder what may be happening in your case.

@krasnoukhov
Copy link
Contributor Author

Thanks for the reply. Seems like this happens when agent is not running due to this message:

Warning: Skipping visual tests. PERCY_TOKEN was not provided

We have some conditions around PERCY_TOKEN which flake sometimes so that's the culprit. Sorry for the trouble

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

No branches or pull requests

2 participants