Skip to content

[rqd] Add windows support#2165

Draft
DiegoTavares wants to merge 14 commits intoAcademySoftwareFoundation:masterfrom
DiegoTavares:rust_rqd_windows
Draft

[rqd] Add windows support#2165
DiegoTavares wants to merge 14 commits intoAcademySoftwareFoundation:masterfrom
DiegoTavares:rust_rqd_windows

Conversation

@DiegoTavares
Copy link
Collaborator

First take at implementing windows support for rqd. The goal was to have feature parity, but I
wasn't able to find a Windows tool to emulate taskset and allocate processes to threads. So this
stands as the only feature not available for windows.

First take at implementing windows support for rqd. The goal was to have feature parity, but I
wasn't able to find a Windows tool to emulate taskset and allocate processes to threads. So this
stands as the only feature not available for windows.
@DiegoTavares
Copy link
Collaborator Author

Caveat: I currently don't have a windows environment to test this on. I'm relying on the Rust unit tests on github as my only quality assurance.

I need a volunteer to test this on a real environment and report bugs.

…for interface binding

Provide Windows-specific get_ip_for_interface implementation that
returns an error if binding by interface name is requested, since
this feature is unsupported on Windows. Add corresponding tests.
…ion tests

- Adjust test code to handle Windows binary naming and commands
- Load machine resource files conditionally for Unix-based tests
- Add Windows PowerShell memory_fork.cmd test script
- Mark frame execution and related tests as Unix-only where appropriate
- Add comment on run_as_user config option availability on Unix systems only
Use a function to wait for openrqd to open its gRPC port before
proceeding, ensuring tests do not start too early and improving
reliability and speed of the integration tests.
…indows

- Refactor integration tests to normalize paths for Windows compatibility
- Correct Rust RQD docs to reflect Windows support status as available
Use ephemeral free ports for gRPC servers instead of fixed ports to avoid conflicts.
Serialize integration tests with a global mutex to prevent parallel execution issues.
Replace fixed hostnames with "127.0.0.1" for consistency.
@DiegoTavares
Copy link
Collaborator Author

@lithorus or @KernAttila do you guys have a Windows machine on hand to give the rust/rqd a spin and report back if you find any errors?

@lithorus
Copy link
Collaborator

@lithorus or @KernAttila do you guys have a Windows machine on hand to give the rust/rqd a spin and report back if you find any errors?

I'm affraid I don't have one.

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.

2 participants