Steps to reproduce:
It's the second time that system startup / shutdown test fails in the new GitHub workflow. AppVeyor equivalent test passes. So I think it's worth mentioning.
See https://github.com/nvaccess/nvda/actions/runs/16523998936/job/46733268125?pr=18560
The code changes in this PR are unrelated to startup / shutdown.
Actual behavior:
Sometimes system tests fail.
Expected behavior:
System tests should pass
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed on GitHub's worker.
NVDA version:
Commit bf96e2d from PR #18560, based on recent master (6e2cd91).
But after pushing an empty commit on top of it (commit 18e1e2c), the tests passed, i.e. on the same version of code.
Windows version:
? (the one in GitHub worker)
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
N/A
Have you tried any other versions of NVDA? If so, please report their behaviors.
N/A
If NVDA add-ons are disabled, is your problem still occurring?
N/A
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A
Steps to reproduce:
It's the second time that system startup / shutdown test fails in the new GitHub workflow. AppVeyor equivalent test passes. So I think it's worth mentioning.
See https://github.com/nvaccess/nvda/actions/runs/16523998936/job/46733268125?pr=18560
The code changes in this PR are unrelated to startup / shutdown.
Actual behavior:
Sometimes system tests fail.
Expected behavior:
System tests should pass
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
Installed on GitHub's worker.
NVDA version:
Commit bf96e2d from PR #18560, based on recent master (6e2cd91).
But after pushing an empty commit on top of it (commit 18e1e2c), the tests passed, i.e. on the same version of code.
Windows version:
? (the one in GitHub worker)
Name and version of other software in use when reproducing the issue:
N/A
Other information about your system:
N/A
Other questions
Does the issue still occur after restarting your computer?
N/A
Have you tried any other versions of NVDA? If so, please report their behaviors.
N/A
If NVDA add-ons are disabled, is your problem still occurring?
N/A
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
N/A