Closed NAVFreak closed 2 years ago
Since you disable the taskscheduler, I think it's cause by something else, like background sessions (startsession) that was started during a testrun.. .
I have searched through my entire workspace and there is no startsession nowhere or other background jobs. I'm not sure that the taskscheduler is inactive. The only thing i see is:
*** Overrule 'EnableTaskScheduler': TRUE
"docker" create --env accept_eula=Y --env accept_outdated=Y --restart no --label TFSBuild=Order Nordic_8580 myimage:sandbox-***0.4.443***3.45688-se-***0.0.***7763.3***87dev-ltsc***0***9
Is there a way to make sure it is not loaded?
The most anoying is that this is happening to me in several pipelines. The only workaround solutions that I have found is to rename the testobject in some pipelines and in some it doesn't work. This stops my entire pipeline cause of failing tests
I think we found it - i didn't notice it, but the developer pointed me to the wrong usage of the "taskscheduler" input in the yaml:
So it's either "keep", "enable" or "disable".
Can you try that?
Tip: use the DevOps pipeline editor: it has intellisense ;-)
It worked! 🥳 Yeah I have definately made a note to myself to start use intellisense in the devops pipeline editor. That could have saved me a lot of hours of googling if I had used it earlier 🙈
Describe the bug I can't run a certain test scenario in my ALOps pipeline. After googling the error I found this dialoge with waldo and Freddy which seems to have the same error and it is because the task scheduler is running.
My error:
So now I try to disable the task scheduler in the pipeline. I found out there is an option which I think I can use for this.
Is this correct to inactivate the taskscheduler?
the used yaml If it looks weird it's because I have pasted most of it from different template files
the output Also the complete output is necessary for us to see what is going on. Also use backtics: Out from ALOPS Start Docker and ALOPS Run test suite
Expected behavior I expect the task scheduler to be inactivated to see if this is the reason to my problem. If you have any other suggestion please suggest them.