-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Bug] Running e2e tests (playwright) on mac close app function is not closing app properly #160
Comments
I have found quite good looking, in a way of problematic, description and possible solution to a problem here: |
Also a quick dirty solution in the meantime would be to reboot the machine as the last command on the script. When the machine is started after the reboot there are no popups. This solution will not fix this issue but will unblock us for scheduled the execution of the pipeline. Specially if this can not be addressed right now and this may hit all the e2e for any extension we want to test. WDYT? |
if that works, no problem. |
shouldn't be logging out the user enough? |
Not sure, but the point is, if you reboot the underlying deliverest logic will wait until the machines comes up so you dont have to log in and log out (as that would require probably to move the user password somehow to the script) And as pre requisite target hosts have auto login set up so you do not need to take care of nothing just add the reboot cmd on your script |
Might have been fixed by podman-desktop/podman-desktop#7803 |
I am still seeing the problematic pop ups. But we might now know the place to tackle in development mode in order to avoid this windows being shown on every test run on mac. |
When running the playwright e2e tests on MacOS when the app is closed in between tests somehow the system has a problem on how the app is closed and a popup is showing.
This is preventing new executions of pipelines which are based on
goax
as it will use the forefront app to install Podman, but the forefront app is now this warning popup.Ideally the e2e execution should leave the environment as it was before execution.
The text was updated successfully, but these errors were encountered: