x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT_FOUND in reserved-name test#48904
Merged
efd6 merged 1 commit intoelastic:mainfrom Feb 17, 2026
Merged
x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT_FOUND in reserved-name test#48904efd6 merged 1 commit intoelastic:mainfrom
efd6 merged 1 commit intoelastic:mainfrom
Conversation
…n reserved-name test Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both.
Contributor
🤖 GitHub commentsJust comment with:
|
belimawr
approved these changes
Feb 17, 2026
andrewkroh
approved these changes
Feb 17, 2026
Contributor
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
mergify bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
…n reserved-name test (#48904) Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both. (cherry picked from commit c0b005f)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
…n reserved-name test (#48904) Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both. (cherry picked from commit c0b005f)
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Feb 17, 2026
…n reserved-name test (#48904) Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both. (cherry picked from commit c0b005f)
6 tasks
efd6
added a commit
that referenced
this pull request
Feb 17, 2026
…n reserved-name test (#48904) (#48905) Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both. (cherry picked from commit c0b005f) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
efd6
added a commit
that referenced
this pull request
Feb 17, 2026
…n reserved-name test (#48904) (#48906) Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both. (cherry picked from commit c0b005f) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
efd6
added a commit
that referenced
this pull request
Feb 17, 2026
…n reserved-name test (#48904) (#48907) Windows 11 changed how reserved DOS device names (AUX, PRN, etc.) are resolved. On Windows 10 the path is redirected to the device, producing ERROR_DIRECTORY. On Windows 11 the device name interception happens differently and some builds return ERROR_PATH_NOT_FOUND instead. Accept either error so the test passes on both. (cherry picked from commit c0b005f) Co-authored-by: Dan Kortschak <dan.kortschak@elastic.co>
belimawr
added a commit
to belimawr/beats
that referenced
this pull request
Feb 18, 2026
…_FOUND in reserved-name test (elastic#48904) (elastic#48907)" This reverts commit 9a7e5f9.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed commit message
Checklist
stresstest.shscript to run them under stress conditions and race detector to verify their stability../changelog/fragmentsusing the changelog tool.Disruptive User Impact
Author's Checklist
How to test this PR locally
Related issues
The system cannot find the path specified.; want The directory name is invalid.#48902Use cases
Screenshots
Logs