-
-
Notifications
You must be signed in to change notification settings - Fork 6
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
Build failures on nightly #14
Comments
Hi @rfay , I compared some other add-on tests and I saw that we are using here For all other add-on I looked at, this is I guess this is probably not the root cause but I modified into Maybe we could add temporary some verbosity to debug by adding a secret |
I've had this problem with repositories as well, and haven't sorted it out. Repos created? by someone else don't send me their failures. I guess maybe it's something we could open an issue about. Certainly baffles me. You can debug this on Github hardware by going to https://github.com/ddev/ddev-mongo/actions/workflows/tests.yml and clicking the button in the upper right "Run Workflow" and check "Debug with tmate". It will let you ssh into the machine and see what actually happens. I guess there's inadequate docs on that approach. ![]() |
However, as we see, the test ran OK for you and the nightly worked last night :( I guess we just need more output from the test to understand what's happened. |
Yes, it fails only sometimes. To debug this, I added another tmate session step that will be available only in case of failure. I also increase the frequency of the cron so that failure should happen more frequently. If I'm here during a failed test, I will debug with tmate and try some [EDIT]: damned, I was able to enter in a failed workflow : https://github.com/ddev/ddev-mongo/actions/runs/5873818472/job/15927617320 but, as the bats teardown is deleting all the project ( Do you have any idea of what we should looking as the project and files have been removed by the teardown method ? Maybe I can just create a |
Just remove the teardown for now I'd say. It properly tears everything down at the start, so it doesn't do any harm. Thanks for chasing this! |
Removing the teardown gives some progress but, as the following test (install from release) is run after a failed one, some content are wiped and we are loosing information. By the way, I saw the original error was (https://github.com/ddev/ddev-mongo/actions/runs/5875221214/job/15931158670#step:11:14) :
And when I went in the tmate session I ran
But this is maybe the log after the second test... Finally, I created a specific debug action with only the "install from directory" test and will run it manually to see if I can understand more. |
With the new specific debug action, (result of
No idea why but this is a beginning. |
Maybe related: mongo-express/mongo-express-docker#39 |
Hi @rfay , it seems that adding Will let test running for some days to see if it is ok. It seems that for some reason, |
Wow, nice work. I'll bet that it has to do with healthcheck. ddev-mongo has one, ddev-mongo/docker-compose.mongo.yaml Lines 28 to 30 in 57fe742
But mongo-express has a I guess a wait in start is not the biggest problem for a gui element here. Congrats on the great work on this. |
Solved by 6651175 |
@julienloizelet would you mind taking a look and seeing if you can sort out why nightlies are failing from directory? I'm not sure why the run doesn't give us a bit more info. Seems to fail on
ddev restart
, https://github.com/ddev/ddev-mongo/actions/runs/5853744817/job/15875363058The text was updated successfully, but these errors were encountered: