Skip to content

HttpStress is broken on Windows (CAP_SYS_PTRACE) #76045

@antonfirsov

Description

@antonfirsov

CI runs are broken since 9/22, need to check local runs.

https://dev.azure.com/dnceng-public/public/_build/results?buildId=26259&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=abae1f68-3c73-5bff-491f-f2b908580ce6

Creating httpstress_server_1 ... error
ERROR: for httpstress_server_1  Cannot create container for service server: invalid CapAdd: unknown capability: "CAP_SYS_PTRACE"
ERROR: for server  Cannot create container for service server: invalid CapAdd: unknown capability: "CAP_SYS_PTRACE"

Edit (pasting comment from below):

I cannot reproduce this locally. dotnet/dnceng was there any change around 9/22 that may have affected

  • the NetCore-Public pool -OR-
  • the 1es-windows-2022-open image -OR-
  • the stress/http.yml pipeline
    ?

Seeing an error about CAP_SYS_PTRACE on Windows is super esoteric.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions