Skip to content

[9.3](backport #48904) x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT_FOUND in reserved-name test#48907

Merged
efd6 merged 1 commit into9.3from
mergify/bp/9.3/pr-48904
Feb 17, 2026
Merged

[9.3](backport #48904) x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT_FOUND in reserved-name test#48907
efd6 merged 1 commit into9.3from
mergify/bp/9.3/pr-48904

Conversation

@mergify
Copy link
Copy Markdown
Contributor

@mergify mergify bot commented Feb 17, 2026

Proposed commit message

x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT_FOUND in 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.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works. Where relevant, I have used the stresstest.sh script to run them under stress conditions and race detector to verify their stability.
  • I have added an entry in ./changelog/fragments using the changelog tool.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #48904 done by [Mergify](https://mergify.com).

@efd6 @mergify
x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT_FOUND i…
4c24fc0 
…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)
@mergify mergify bot added the backport label Feb 17, 2026
@mergify mergify bot requested a review from a team as a code owner February 17, 2026 22:16
@mergify mergify bot added the backport label Feb 17, 2026
@mergify mergify bot assigned efd6 Feb 17, 2026
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 17, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Feb 17, 2026

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@github-actions github-actions bot added Filebeat Filebeat flaky-test Unstable or unreliable test cases. bugfix Team:Security-Service Integrations Security Service Integrations Team labels Feb 17, 2026
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Feb 17, 2026
@elasticmachine
Copy link
Copy Markdown
Contributor

elasticmachine commented Feb 17, 2026

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

@efd6 efd6 merged commit 9a7e5f9 into 9.3 Feb 17, 2026
23 checks passed
@efd6 efd6 deleted the mergify/bp/9.3/pr-48904 branch February 17, 2026 23:45
belimawr added a commit to belimawr/beats that referenced this pull request Feb 18, 2026
@belimawr
Revert "x-pack/filebeat/input/internal/httplog: accept ERROR_PATH_NOT…
1c1cc40 
…_FOUND in reserved-name test (elastic#48904) (elastic#48907)"

This reverts commit 9a7e5f9.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@efd6 efd6 efd6 approved these changes

Assignees

@efd6 efd6

Labels

backport bugfix Filebeat Filebeat flaky-test Unstable or unreliable test cases. Team:Security-Service Integrations Security Service Integrations Team

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@elasticmachine @efd6