element-hq / element-hq/element-web

Tests fail in CI with error `Error: ENOSPC: no space left on device, write`

Open
#34,388 1 comment 0 reactions 0 assignees View on GitHub
A-Developer-Experience A-Testing T-Defect T-Task
Dominant language
TypeScript
Stars
13.5k
Forks
2.8k
PR merge metrics
PR metrics pending

Description

> Huh, now they are failing with:
>
> ```
> ❯ unit (chromium) src/room/timeline/event-tile/body/MediaBody/MediaBody.test.tsx (0 test)
>
> ⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯
> Error: ENOSPC: no space left on device, write
> ❯ write node:internal/fs/promises:745:8
> ❯ writeFileHandle node:internal/fs/promises:502:7
>
> ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
> Serialized Error: { errno: -28, code: 'ENOSPC', syscall: 'write' }
> ```
>
> I wonder if that is related.

_Originally posted by @richvdh in [#33189](https://github.com/element-hq/element-web/issues/33189#issuecomment-4268622771)_

Contributor guide

Open the contributing guide

Research direction

Start with the CI run and the reported unit test in src/room/timeline/event-tile/body/MediaBody/MediaBody.test.tsx. Investigate why the Chromium test run reaches ENOSPC while writing, and consider the work complete when the affected CI tests run without the no-space error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
ci-cd, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.