-
Notifications
You must be signed in to change notification settings - Fork 247
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
Client session uninitialized when running tests #1991
Comments
When did this start to fail? Where does this output come from:
What are you using to run the tests? There should not be anything special with next minor, all my pipelines works normally |
Same machine, same setup, same code. Basically I am looking for any ideas how we can find out what the problem is?
This is a pipeline using ALOps
Not sure if I understand the question, but we are using ALOps in an Azure pipeline here |
My assumption is that this is an ALOps problem. |
It was caused by Rapidstart imports or at least we could solve it removing the import |
PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
Running tests in a container fails because "Warm-up Client Context" and "Create Client Context" fail
Scripts used to create container and cause the issue
We are using bcch for creating images, but not to create the containers, but here are the environment variables and other settings when starting the container
Full output of scripts
Container start
Log for running of the tests:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
does it happen all the time?
So far it looks like we only get this for nextMinor
did it use to work?
Yes
The text was updated successfully, but these errors were encountered: