-
Notifications
You must be signed in to change notification settings - Fork 511
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
[Xharness] Fix all xml parsing issues and ensure that the xml can be consumed by VSTS. #7768
Conversation
We ping the tcp listener to know that we have a tcp connection, that is written in the xml logs, which means that parsing will not work. Ignore the ping, parse xml, and make sure that the xml that will be consume by vsts is valid.
Build failure Test results66 tests failed, 21 tests passed.Failed tests
|
Co-Authored-By: Rolf Bjarne Kvinge <rolf@xamarin.com>
Build failure |
New commits in xamarin/maccore: * xamarin/maccore@80ebc03 [VSTS] Add a status to pending after we ping VSTS for device tests. (#2135) Diff: https://github.com/xamarin/maccore/compare/acfea010d8381fd009ce3a1eaa685d5c8286321d..80ebc03ea89eb4a911bbd73ea45b308b610ab213
Build failure Test results66 tests failed, 21 tests passed.Failed tests
|
build |
build |
build |
Build failure Test results66 tests failed, 21 tests passed.Failed tests
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException ✅ Build succeeded ✅ API Diff (from stable) |
Build failure |
Build failure Test results66 tests failed, 21 tests passed.Failed tests
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded ✅ API Diff (from stable) Test results141 tests failed, 38 tests passed.Failed tests
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pong
logic closer to the error.
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Packaging' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException |
Build failure |
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded ✅ API Diff (from stable) Test results142 tests failed, 37 tests passed.Failed tests
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException ✅ Build succeeded ✅ API Diff (from stable) |
Build failure ✅ Build succeeded |
Build failure Test results27 tests failed, 136 tests passed.Failed tests
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded ✅ API Diff (from stable) Test results73 tests failed, 106 tests passed.Failed tests
|
Build failure Test results27 tests failed, 136 tests passed.Failed tests
|
* Do not clean the xml, seems not to be needed and gives issues with threading. * Set the size of the client buffer in the tcp listener.
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException ✅ Build succeeded ✅ API Diff (from stable) |
Build failure ✅ Build succeeded |
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Upload to Azure' 🔥 : org.jenkinsci.plugins.workflow.steps.FlowInterruptedException |
Build failure |
Build failure Test results1 tests failed, 162 tests passed.Failed tests
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded ✅ API Diff (from stable) Test results1 tests failed, 178 tests passed.Failed tests
|
exception and stop uploading results: ``` Failed to parse result files: System.NotSupportedException: Invalid file format. at Microsoft.TeamFoundation.TestClient.PublishTestResults.NUnitResultParser.ParseTestResultFile(TestRunContext runContext, String filePath) at Microsoft.TeamFoundation.TestClient.PublishTestResults.NUnitResultParser.<>c__DisplayClass1_0.<ParseTestResultFiles>b__0(String file) at System.Linq.Enumerable.SelectListIterator`2.MoveNext() at System.Linq.Enumerable.WhereEnumerableIterator`1.ToList() at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at Microsoft.TeamFoundation.TestClient.PublishTestResults.NUnitResultParser.ParseTestResultFiles(TestRunContext runContext, IList`1 resultFilePaths) at Microsoft.VisualStudio.Services.Agent.Worker.TestResults.Parser.ParseFiles(IExecutionContext executionContext, TestRunContext testRunContext, List`1 testResultsFiles, ITestResultParser testResultParser) ```
Build failure Test results1 tests failed, 162 tests passed.Failed tests
|
❌ Build was (probably) aborted 🔥 Jenkins job (on internal Jenkins) failed in stage(s) 'Test run, Test run' 🔥 ✅ Build succeeded ✅ API Diff (from stable) Test results1 tests failed, 178 tests passed.Failed tests
|
…consumed by VSTS. (xamarin#7768) We ping the tcp listener to know that we have a tcp connection, that is written in the xml logs, which means that parsing will not work. Ignore the ping, parse xml, and make sure that the xml that will be consume by vsts is valid. This PR also fixes xamarin/maccore#827 which does not longer happen.
…consumed by VSTS. (xamarin#7768) We ping the tcp listener to know that we have a tcp connection, that is written in the xml logs, which means that parsing will not work. Ignore the ping, parse xml, and make sure that the xml that will be consume by vsts is valid. This PR also fixes xamarin/maccore#827 which does not longer happen.
…consumed by VSTS. (xamarin#7768) We ping the tcp listener to know that we have a tcp connection, that is written in the xml logs, which means that parsing will not work. Ignore the ping, parse xml, and make sure that the xml that will be consume by vsts is valid. This PR also fixes xamarin/maccore#827 which does not longer happen.
…consumed by VSTS. (xamarin#7768) We ping the tcp listener to know that we have a tcp connection, that is written in the xml logs, which means that parsing will not work. Ignore the ping, parse xml, and make sure that the xml that will be consume by vsts is valid. This PR also fixes xamarin/maccore#827 which does not longer happen.
We ping the tcp listener to know that we have a tcp connection, that is
written in the xml logs, which means that parsing will not work. Ignore
the ping, parse xml, and make sure that the xml that will be consume by
vsts is valid.
Sample of the ping in CI: http://xamarin-storage/jenkins/xamarin-macios/master/a2a48c4e003b5394a9a354d1dfcd99a064103390/3422594/device-tests/jenkins-results/tests/mscorlib%20Part%201/1621/test-ios-20200128_182116.log