Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helix work item failures due to failure to find xharness-event-processor.py #400

Closed
3 tasks
jkoritzinsky opened this issue Jul 19, 2023 · 1 comment
Closed
3 tasks

Comments

@jkoritzinsky
Copy link
Member

jkoritzinsky commented Jul 19, 2023

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=345368

Build leg reported

chrome-DebuggerTests.BreakpointTests.WorkItemExecution

Pull Request

dotnet/runtime#89128

Known issue core information

Fill out the known issue JSON section by following the step by step documentation on how to create a known issue

 {
    "ErrorMessage" : "python: can't open file '/root/helix/work/workitem/u/xharness-event-processor.py': [Errno 2] No such file or directory",
    "BuildRetry": false,
    "ErrorPattern": "",
    "ExcludeConsoleLog": false
 }

@dotnet/dnceng

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

Additional information about the issue reported

No response

Report

Build Definition Test Pull Request
345837 dotnet/runtime Workloads-NoWebcil-Wasm.Build.Tests.NonWasmTemplateBuildTests.WorkItemExecution dotnet/runtime#89225
345767 dotnet/runtime chrome-DebuggerTests.BreakpointTests.WorkItemExecution dotnet/runtime#89204
345670 dotnet/runtime PayloadGroup0.WorkItemExecution dotnet/runtime#89217
345630 dotnet/runtime chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution dotnet/runtime#88838
345563 dotnet/runtime chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution
345466 dotnet/runtime Wasm.Build.Tests.Blazor.BuildPublishTests.BlazorBuildRunTest dotnet/runtime#89151
345368 dotnet/runtime chrome-DebuggerTests.BreakpointTests.WorkItemExecution dotnet/runtime#89128
345298 dotnet/runtime chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution dotnet/runtime#89147
344749 dotnet/runtime chrome-DebuggerTests.BreakpointTests.WorkItemExecution dotnet/runtime#88910
344910 dotnet/runtime Workloads-Wasm.Build.NativeRebuild.Tests.OptimizationFlagChangeTests.WorkItemExecution dotnet/runtime#89081
344851 dotnet/runtime chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution dotnet/runtime#89147
344737 dotnet/runtime chrome-DebuggerTests.GetPropertiesTests.WorkItemExecution dotnet/runtime#87865
344591 dotnet/runtime chrome-DebuggerTests.GetPropertiesTests.WorkItemExecution dotnet/runtime#89162
344683 dotnet/runtime chrome-DebuggerTests.EvaluateOnCallFrameTests.WorkItemExecution
344254 dotnet/runtime chrome-DebuggerTests.BreakpointTests.WorkItemExecution dotnet/runtime#89142
344334 dotnet/runtime DebuggerTests.CallFunctionOnTests.DebuggerTests.CallFunctionOnTests.RunOnInvalidCfoId dotnet/runtime#89139

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
14 16 16

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=345368
Error message validated: python: can't open file '/root/helix/work/workitem/u/xharness-event-processor.py': [Errno 2] No such file or directory
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 7/19/2023 11:12:46 PM UTC

@premun
Copy link
Member

premun commented Jul 20, 2023

@jkoritzinsky this error does not break the job. The problem is a bit above:

The active test run was aborted. Reason: Test host process crashed
Results File: /root/helix/work/workitem/uploads/xharness-output/logs/testResults.trx

Passed!  - Failed:     0, Passed:    69, Skipped:     0, Total:    69, Duration: 6 m 13 s - DebuggerTestSuite.dll (net8.0)
Test Run Aborted.
artifacts: /root/helix/work/workitem/uploads/xharness-output
+ export _commandExitCode=1

The error later is ignored

@premun premun closed this as completed Jul 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants