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

No logs are shown in the session when running tests on appium #474

Closed
TripleG opened this issue Jun 1, 2021 · 9 comments
Closed

No logs are shown in the session when running tests on appium #474

TripleG opened this issue Jun 1, 2021 · 9 comments
Labels

Comments

@TripleG
Copy link

TripleG commented Jun 1, 2021

When an appium(Android) session is completed I see no output in the Log tab, but only in the Test results. The android actor configuration has logLevel: TRACE

Any idea what could be wrong?

Test results
image

Log
image

@Naveenkumarnnk
Copy link

Hi @TripleG,

I also noticed this no logs issue while running scripts in Chrome. As far as I know, it is because of the actor and server consoles we opened. If we close them and reopen or clear the console, it would work.

This is my understanding, correct me if I am wrong.

@TripleG
Copy link
Author

TripleG commented Jun 1, 2021

Hi @Naveenkumarnnk ,

I actually haven't tried this, but I am a bit confused what you mean.
Do you mean that when running tests on Android Chrome, the server and actor consoles should not be opened, therefore server and actor must be started as "headless" processes?

@Naveenkumarnnk
Copy link

Hi @TripleG,

I mean, as we are running many tests, the server and actor console's heap memory would be full.

So, we have to clear the console or close and reopen them.

@TripleG
Copy link
Author

TripleG commented Jun 1, 2021

I am even more confused. If server and actors heap is getting filled up with time, this would mean that server and actors are not intended to be long running processes, which sounds strange to me.

Hi @adrianth , could you please take a look?

@TripleG
Copy link
Author

TripleG commented Jun 2, 2021

@adrianth, this happens not only for Android sessions, but for all(Windows Chrome for example). All logs appear in the actor console, but they don't get saved into the logs/{session-number}.log(except the initial messages which are on screenshot).

Restarting server and actor didn't help.
Regarding Windows Chrome actor: on my local(dev) machine this issue is not happening - all actor logs are correctly printed in the console and written to the .log file. Both machines(dev and prod) are Windows 10.

@adrianth
Copy link
Contributor

adrianth commented Jun 2, 2021

I investigated this issue and I found the bug that is causing it. I will correct this and will be publishing a new release with the fix. It'll take about a week, because I'd like to include a few more things in there.

@arineiza
Copy link

arineiza commented Jun 17, 2021

Hi, Adrianth. It still happens. When will the corrected version be available? Thanks.

@adrianth
Copy link
Contributor

adrianth commented Jun 17, 2021

The new release is published in beta and we're testing it as we speak. If you want to try it out, you can install it with

npm install opentest@beta -g

Please be aware that we updated a lot of dependencies (including the Appium client library to the latest version), so you shouldn't use this release in any business-critical CI pipeline yet.

@stale
Copy link

stale bot commented Oct 15, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Oct 15, 2021
@stale stale bot closed this as completed Oct 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants