Skip to content

Conversation

@ShahzaibIbrahim
Copy link
Contributor

Disposing the display alone is insufficient, as some tests do not create a new display and continue to use the previously set device zoom when calling DPIUtil.getDeviceZoom. This change ensures that device zoom is explicitly reset to 100 after each test, preventing unintended side effects from lingering zoom values across tests.

Disposing the display alone is insufficient, as some tests do not create
a new display and continue to use the previously set device zoom when
calling DPIUtil.getDeviceZoom. This change ensures that device zoom is
explicitly reset to 100 after each test, preventing unintended side
effects from lingering zoom values across tests.
@github-actions
Copy link
Contributor

Test Results

  118 files  ±0    118 suites  ±0   11m 4s ⏱️ +48s
4 440 tests ±0  4 418 ✅  - 2  17 💤 ±0  5 ❌ +2 
  298 runs  ±0    289 ✅  - 2   4 💤 ±0  5 ❌ +2 

For more details on these failures, see this check.

Results for commit 08344a7. ± Comparison against base commit 810cbcc.

@fedejeanne
Copy link
Member

Test failures are unrelated: #2516

@fedejeanne fedejeanne merged commit 00106b4 into eclipse-platform:master Sep 26, 2025
15 of 17 checks passed
@fedejeanne fedejeanne deleted the master-456 branch September 26, 2025 08:16
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.

Reset Device Zoom to 100 when using ResetMonitorSpecificScalingExtension

2 participants