-
Trying to get percy running on my local machine. Things seem to be set as I can see in logs that percy has started and snapshot is taken. But after that, I am not able to see my snapshots on the percy portal. The builds are in "Receiving build" state. They are stuck there. I am following java-selenium turorial from here: https://docs.percy.io/docs/java-selenium I see these: But I do not see any of these: [percy] Created build #1: https://percy.io/[your-project] [percy] Stopping percy... Am I missing something? |
Beta Was this translation helpful? Give feedback.
Replies: 11 comments
-
Build url for reference: https://percy.io/56bc5714/percytest2/builds/11532147 |
Beta Was this translation helpful? Give feedback.
-
Hey @nirav1516! Would you be able to share the full build logs? My guess is an exception happened during the test run, exiting the process. Hard to tell without full log output, though. Adding |
Beta Was this translation helpful? Give feedback.
-
The test is successful. I do not see any error in the test. In fact it generates expected results. Only thing which is not working is percy snapshot. If running percy with java requires special set up, the documentation should be more detailed. There is not enough documentation available I guess. The docs are very high level. Wanted to run this with verbose again and now I see 500 internal server error without any reason or showing any proper error cause [percy:config] Found config file: .percy.yml (0ms) |
Beta Was this translation helpful? Give feedback.
-
Looks like there was a bug shipped in the API that returned a 500 error. We deployed a fix 👍🏼 |
Beta Was this translation helpful? Give feedback.
-
Thanks for the update. I can start the server now. But the 'Receiving Build' state is still there. I am pasting verbose logs for your reference. I am doing this POC for my org to use percy as a visual testing tool. Would love to get more help to get going so we can proceed with a tool that works seemlessly.
|
Beta Was this translation helpful? Give feedback.
-
Would you be able to provide the full logs for the full test run? I don't see any issues in those logs that are provided. |
Beta Was this translation helpful? Give feedback.
-
Hello @Robdel12 This is the entire percy logs. It abruptly ends after "Finalizing snapshot" step. I do not see none of these when I run it with SDK. So, there is some issue for sure. If you tell me specifically what logs(other than percy) you are looking for, I can see what I can do. |
Beta Was this translation helpful? Give feedback.
-
Hey @nirav1516! I'm looking for the full test logs. Everything from |
Beta Was this translation helpful? Give feedback.
-
This issue is stale because it has been open for more than 14 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
Beta Was this translation helpful? Give feedback.
-
Hi @Robdel12 We could resolve the issue by removing a "node kill" step in our framework. Here are the logs for the issue
Seems like percy works asynchronously. Is it possible of it to work synchronously so that once the control goes out of percy snapshot, it can be assumed to be done. |
Beta Was this translation helpful? Give feedback.
-
Hey @nirav1516! If there's a process in your maven build that kills all node processes, it won't work with Percy. Percy is a parent process to your test command. When you run |
Beta Was this translation helpful? Give feedback.
Hey @nirav1516! If there's a process in your maven build that kills all node processes, it won't work with Percy. Percy is a parent process to your test command. When you run
percy exec -- mvn test
(or whatever the subcommand topercy exec
is),mvn test
is spawned by@percy/cli
. Killing Node processes means Percy will always be stopped at that point in the script. And how abrupt it is, Percy's CLI has no time to clean up the sub process & finalize the Percy build.