Skip to content
SWT Matrix Build

Avoid Rectangle allocation on every mouse move in CTabFolder #10415

Sign in to view logs

Avoid Rectangle allocation on every mouse move in CTabFolder

Avoid Rectangle allocation on every mouse move in CTabFolder #10415

Triggered via pull request April 12, 2026 11:07
@vogellavogella
synchronize #3225
vogella:topic/ctabfolder-avoid-rectangle-alloc-mousemove
Status Success
Total duration 12m 8s
Artifacts 7

maven.yml

on: pull_request
Detect changed paths
3s
Detect changed paths
Event File
4s
Event File
Matrix: Build (Linux)
Matrix: Build (macOS)
Matrix: Build (Windows)
Fit to window
Zoom out
Zoom in

Annotations

5 errors and 7 warnings
Build (macOS) (21, aarch64) / build
Device is disposed
Build (macOS) (21, aarch64) / build
Device is disposed
Build (Linux) (21, gtk3, x11) / build
Device is disposed
Build (macOS) (21, x86_64) / build
Device is disposed
Build (macOS) (21, x86_64) / build
Device is disposed
Detect changed paths
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: petermetz/paths-filter@5ee2f5d4cf5d7bdd998a314a42da307e2ae1639d. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (macOS) (21, aarch64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (Linux) (21, gtk4, x11) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (Linux) (21, gtk3, x11) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (macOS) (21, x86_64) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (Linux) (21, gtk4, wayland) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Build (Windows) (21) / build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: stCarolas/setup-maven@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Event File
3.92 KB
sha256:3d5ba6174291696281aa260baca535c2eb8396e88b98b3eaf600fa8a1c5cb136
test-results-cocoa.macosx.aarch64---java21
115 KB
sha256:1609418bd42c2b8736375232a43da954b2eb9bd78164c5c4b458588517747dec
test-results-cocoa.macosx.x86_64---java21
116 KB
sha256:45c0f4c517cab3a6353769237c0e8462b1196e51b1feaefa03febd8de0741fc6
test-results-gtk.linux.x86_64-gtk3-x11-java21
137 KB
sha256:7fda63d66b9306d6271fa0ad9d5ebcd01692616f7c2e907f6ca8ef3c9786ec57
test-results-gtk.linux.x86_64-gtk4-wayland-java21
130 KB
sha256:010f090147586f7368f32221122aa35af8736d44d8f936ea6c84272974841b6d
test-results-gtk.linux.x86_64-gtk4-x11-java21
129 KB
sha256:4fe66fcdeecde9814660c31b4590dc3d03ac505a379dad47e1f4399746f38da1
test-results-win32.win32.x86_64---java21
150 KB
sha256:c0cab503f5955257827bbf7ccfeaa139969b5cd43562e3e66234e0242ffc25d7