Skip to content

test(nuxt): Pin the nuxt-4 e2e MongoDB image to 8.0 - #25557

Merged
logaretm merged 1 commit into
developfrom
awad/pin-nuxt-4-mongo
Oct 20, 2026
Merged

logaretm merged 1 commit into
developfrom
awad/pin-nuxt-4-mongo

Conversation

@logaretm

Copy link
Copy Markdown
Member

The nuxt-4 e2e jobs keep failing because the mongo:8 container goes unhealthy about 10s after it starts, fixed by pinning the image to mongo:8.0 and printing the container logs when setup fails so the next failure shows why.

Comment on lines +16 to +17
execSync('docker compose logs --tail 50', { cwd: __dirname, stdio: 'inherit' });
throw error;

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shows why the image went down, if it does.

@s1gr1d s1gr1d left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also pin it for the other nuxt E2E tests e.g. nuxt-5 (also uses mongo:8)

@logaretm
logaretm marked this pull request as ready for review October 20, 2026 13:57
@logaretm
logaretm merged commit 62a794d into develop Oct 20, 2026
75 of 77 checks passed
@logaretm
logaretm deleted the awad/pin-nuxt-4-mongo branch October 20, 2026 13:57
s1gr1d added a commit that referenced this pull request Oct 20, 2026
Same fix as #25557, applied to nuxt-5. It failed the same way on #25552
(`container e2e-tests-nuxt-5-mongo is unhealthy`)

The floating `mongo:8` tag moved to 8.3 on 2026-10-17. On CI the
container goes unhealthy some seconds after start. That is much earlier
than the healthcheck retries allow, so the server process exits, and
Docker then reports the container as unhealthy. If setup fails again,
the container logs now print, so we can see why mongod exits.
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

Successfully merging this pull request may close these issues.

3 participants