-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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] Malformed testResults.xml
causing CI test runs to fail
#61749
Comments
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsTests pass:
but then the log parsing fails:
Lines 1100,1101 from <test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest181" type="XPathTests.FunctionalTests.Expressions.NodeSetsTests" method="NodeSetsTest181" time="0.000645" result="Pass" /> <test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest183" type="XPathTests.FunctionalTests.E
<test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest185" type="XPathTests.FunctionalTests.Expressions.NodeSetsTests" method="NodeSetsTest185" time="0.00062" result="Pass" /> The top line there (1100) has an incomplete element: cc @pavelsavara
|
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
@radical |
See how emscripten implaments putChar on stdout. |
I mean into the |
Or it could be buffering of WasmBrowserTestRunner |
Possibly related ? xunit/xunit#2090 |
We noticed that
See base
|
That's the case for all platforms. So there is no point in calling it. |
Tagging subscribers to this area: @directhex Issue DetailsTests pass:
but then the log parsing fails:
Lines 1100,1101 from <test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest181" type="XPathTests.FunctionalTests.Expressions.NodeSetsTests" method="NodeSetsTest181" time="0.000645" result="Pass" /> <test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest183" type="XPathTests.FunctionalTests.E
<test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest185" type="XPathTests.FunctionalTests.Expressions.NodeSetsTests" method="NodeSetsTest185" time="0.00062" result="Pass" /> The top line there (1100) has an incomplete element: cc @pavelsavara
|
Another one, but failing because:
.. that debug message is showing up in the xml. And another with:
.. again with the debug message showing up in the second line. |
Both messages thru WS and thru chrome devtools protocol are written into same |
Seen on #59479, build, log
Tests pass:
but then the log parsing fails:
Lines 1100,1101 from
testResults.xml
:The top line there (1100) has an incomplete element:
<test name="XPathTests.FunctionalTests.Expressions.NodeSetsTests.NodeSetsTest183" type="XPathTests.FunctionalTests.E
at the end.cc @pavelsavara
The text was updated successfully, but these errors were encountered: