Access rights to end test processes

[christop...@googlemail.com]

Hi everybody,

I am building and testing windows applications on windows machines.

I have a number of tests which start several processes in the background. After each of the tests I call a script to end the processes in case something went wrong end they didn't end in a proper way during the tests. This script makes use of taskkill. On my local machine everything works well. After each test all remaining processes are killed properly.

However when I run this on jenkins the taskkill seems not to work: the processes are still alive after the call and this leads to problems during the whole test run up to deadlocks.

As in the scripts the test process and kill is called directly in a row from a make environment I can't imagine where the problem is.

Is there any reason why I can't kill a process created from the same environment before? Is there a proper way to handle this on jenkins?

I am working with a client-server setup if that's important.

Many thanks for any kind of advice!

Regards,

Christoph

[Jonathan Mackenzie]

Can you find out what is going wrong? Add a call to GetLastError maybe?

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ab4ba3d4-99b1-4b48-bce8-417bb74f95den%40googlegroups.com.

[christop...@googlemail.com]

It's a script using tasklist and taskkill. There's just an errorlevel.

I got a step further: that script is searching the tasklist by filtering for the current user and that does not give a result. I am trying it without that filter during the next nightly build.

Then I'll see if I still have a problem with access rights.

[christop...@googlemail.com]

OK, latest news: the processes seem to be running as another user then the current one. When I don't preselect the tasklist output by the current user, I see my processes and killing them works.

Somewhat surprising though and hard to debug as you cant display the current user name (replaced in the output by '***').

Thanks for listening! :-)

Regards,

Christoph

[Daniel Beck]

On Thu, Jul 29, 2021 at 2:13 PM 'christop...@googlemail.com' via Jenkins Users <jenkins...@googlegroups.com> wrote:

Somewhat surprising though and hard to debug as you cant display the current user name (replaced in the output by '***').

My guess: A credential is in scope with the same username, and you're on an older version of credentials-binding plugin or haven't disabled treating that credential's username as secret.