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

BrowserStack Local process doesnt been killed properly. #7

Open
ezwanharun opened this issue Jul 5, 2018 · 3 comments
Open

BrowserStack Local process doesnt been killed properly. #7

ezwanharun opened this issue Jul 5, 2018 · 3 comments

Comments

@ezwanharun
Copy link

I noticed that the browserstack local connection process doesnt been killed properly after the bamboo job is done / finish executing some test against the browserstack. As attached image, the process seem like been added each time the bamboo job been triggered and leave the old one. This will cost the process redundant even thought it was idle.

Browerstack plugin version : 1.0.4
Bamboo version : 6.5

screen shot 2018-07-05 at 4 16 57 pm

@ezwanharun
Copy link
Author

any thought @mohitmun @pulkitsharma07 ?

@pulkitsharma07
Copy link
Contributor

Hi @ezwanharun , can you provide details regarding the environment where the bamboo job is running ? What OS are you using ?

@ezwanharun
Copy link
Author

There is two separate issue in here and #8 where that ticket is mainly for only specific bamboo job should start/trigger the Browserstack Local plugin and not all available Bamboo job.

OS: debian 9.3
bamboo : 6.5

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