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

[wasm][debugger] Failing test - DebuggerTests.CallFunctionOnTests.CheckVSCodeTestFunction1 #95950

Closed
radical opened this issue Dec 13, 2023 · 1 comment · Fixed by #95955
Closed
Assignees
Labels
arch-wasm WebAssembly architecture area-Debugger-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab

Comments

@radical
Copy link
Member

radical commented Dec 13, 2023

Hit on #95832

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=494540
Build error leg or test failing: DebuggerTests.CallFunctionOnTests.DebuggerTests.CallFunctionOnTests.CheckVSCodeTestFunction1
Pull request: https://github.com/dotnet/runtime.git/pull/95832

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "cfo-res.*Value for json property named description didn't match",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
 Assert.Equal() Failure: [[cfo-res] Value for json property named description didn't match.]
 
 Expected: Array(10)
 Actual:   Array 
 Expected: {
   "type": "object",
   "className": "Array",
   "description": "Array(10)",
   "subtype": "array"
 } 
 Actual: {
   "type": "object",
   "className": "Array",
   "description": "Array",
   "objectId": "5084384295708308525.1.9"
 }

The actual object is missing the subtype, which might be because something went wrong. This is for a js object, so it isn't controlled by our debug proxy. If it isn't an error then we should update the test. That could be tested by checking some contents of the array.

Update: CheckVSCodeTestFunction2 passes though.

cc @ilonatommy

Report

Summary

24-Hour Hit Count 7-Day Hit Count 1-Month Count
0 0 0
@radical radical added arch-wasm WebAssembly architecture blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' area-Debugger-mono Known Build Error Use this to report build issues in the .NET Helix tab labels Dec 13, 2023
@ghost
Copy link

ghost commented Dec 13, 2023

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Hit on #95832

Build Information

Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=494540
Build error leg or test failing: DebuggerTests.CallFunctionOnTests.DebuggerTests.CallFunctionOnTests.CheckVSCodeTestFunction1
Pull request: https://github.com/dotnet/runtime.git/pull/95832

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "",
  "ErrorPattern": "cfo-res.*Value for json property named description didn't match",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}
 Assert.Equal() Failure: [[cfo-res] Value for json property named description didn't match.]
 
 Expected: Array(10)
 Actual:   Array 
 Expected: {
   "type": "object",
   "className": "Array",
   "description": "Array(10)",
   "subtype": "array"
 } 
 Actual: {
   "type": "object",
   "className": "Array",
   "description": "Array",
   "objectId": "5084384295708308525.1.9"
 }

The actual object is missing the subtype, which might be because something went wrong. This is for a js object, so it isn't controlled by our debug proxy. If it isn't an error then we should update the test. That could be tested by checking some contents of the array.

cc @ilonatommy

Author: radical
Assignees: -
Labels:

arch-wasm, blocking-clean-ci, area-Debugger-mono, Known Build Error

Milestone: -

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Dec 13, 2023
@radical radical removed the untriaged New issue has not been triaged by the area owner label Dec 13, 2023
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Dec 13, 2023
radical added a commit that referenced this issue Dec 13, 2023
….6099.71 (#95832)

* Automated bump of chrome version

* [wasm] Disable DebuggerTests.CallFunctionOnTests.CheckVSCodeTestFunction1

Issue: #95950

---------

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: Ankit Jain <radical@gmail.com>
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Dec 13, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jan 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
arch-wasm WebAssembly architecture area-Debugger-mono blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' Known Build Error Use this to report build issues in the .NET Helix tab
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants