Skip to content

Handle incomplete / none JSON elements

Sign in for the full log view
GitHub Actions / Test Results (Test Files) succeeded Nov 9, 2023 in 0s

13 parse errors, 11 errors, 210 fail, 73 skipped, 1 517 pass in 2h 12m 37s

   145 files       13 errors  735 suites   2h 12m 37s ⏱️
1 811 tests 1 517 ✔️   73 💤 210 ❌ 11 🔥
4 117 runs  3 428 ✔️ 214 💤 454 ❌ 21 🔥

Results for commit eb03c06.

Annotations

Check failure on line 0 in test-files/nunit/nunit3/jenkins/NUnit-issue47367.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

attributes construct error, line 5, column 109 (NUnit-issue47367.xml, line 5)
Raw output 
test-files/nunit/nunit3/jenkins/NUnit-issue47367.xml

Check failure on line 0 in test-files/json/empty.json

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

File is empty.
Raw output 
test-files/json/empty.json

Check failure on line 0 in test-files/xml/non-xml.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Unsupported file format: test-files/xml/non-xml.xml
Raw output 
test-files/xml/non-xml.xml

Check failure on line 0 in test-files/junit-xml/pytest/corrupt-xml.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Premature end of data in tag skipped line 9, line 11, column 22 (corrupt-xml.xml, line 11)
Raw output 
test-files/junit-xml/pytest/corrupt-xml.xml

Check failure on line 0 in test-files/json/non-json.json

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Unsupported file format: test-files/json/non-json.json
Raw output 
test-files/json/non-json.json

Check failure on line 0 in test-files/json/malformed-json.json

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Unsupported file format: test-files/json/malformed-json.json
Raw output 
test-files/json/malformed-json.json

Check failure on line 0 in test-files/nunit/nunit3/jenkins/NUnit-issue17521.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Char 0x0 out of allowed range, line 33, column 16 (NUnit-issue17521.xml, line 33)
Raw output 
test-files/nunit/nunit3/jenkins/NUnit-issue17521.xml

Check failure on line 0 in test-files/xml/empty.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

File is empty.
Raw output 
test-files/xml/empty.xml

Check failure on line 0 in test-files/junit-xml/non-junit.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Unsupported file format: test-files/junit-xml/non-junit.xml
Raw output 
test-files/junit-xml/non-junit.xml

Check failure on line 0 in test-files/junit-xml/pytest/corrupt-xml.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Premature end of data in tag skipped line 9, line 11, column 22 (corrupt-xml.xml, line 11)
Raw output 
test-files/junit-xml/pytest/corrupt-xml.xml

Check failure on line 0 in test-files/junit-xml/non-junit.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Invalid format.
Raw output 
test-files/junit-xml/non-junit.xml

Check failure on line 0 in test-files/nunit/nunit3/jenkins/NUnit-issue47367.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

attributes construct error, line 5, column 109 (NUnit-issue47367.xml, line 5)
Raw output 
test-files/nunit/nunit3/jenkins/NUnit-issue47367.xml

Check failure on line 0 in test-files/nunit/nunit3/jenkins/NUnit-issue17521.xml

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

Error processing result file 

Char 0x0 out of allowed range, line 33, column 16 (NUnit-issue17521.xml, line 33)
Raw output 
test-files/nunit/nunit3/jenkins/NUnit-issue17521.xml

Check warning on line 0 in Pickles.TestHarness.MSTest.AdditionFeature

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: FailToAddTwoNumbers (Pickles.TestHarness.MSTest.AdditionFeature) 

test-files/trx/mstest/pickles.trx [took 0s]
Raw output 
            Test method Pickles.TestHarness.MSTest.AdditionFeature.FailToAddTwoNumbers threw exception:
            Should.Core.Exceptions.NotEqualException: Assert.NotEqual() Failure
          
            at Pickles.TestHarness.MSTest.Steps.ThenTheResultShouldBePass(Int32 result) in C:\dev\pickles-results-harness\Pickles.TestHarness\Pickles.TestHarness.MSTest\Steps.cs:line 28
            at lambda_method(Closure , IContextManager , Int32 )<...>
            at TechTalk.SpecFlow.Bindings.MethodBinding.InvokeAction(IContextManager contextManager, Object[] arguments, ITestTracer testTracer, TimeSpan& duration)
            at TechTalk.SpecFlow.Bindings.StepDefinitionBinding.Invoke(IContextManager contextManager, ITestTracer testTracer, Object[] arguments, TimeSpan& duration)
            at TechTalk.SpecFlow.Infrastructure.TestExecutionEngine.ExecuteStepMatch(BindingMatch match, Object[] arguments)
            at TechTalk.SpecFlow.Infrastructure.TestExecutionEngine.ExecuteStep(StepArgs stepArgs)
            at TechTalk.SpecFlow.Infrastructure.TestExecutionEngine.OnAfterLastStep()
            at TechTalk.SpecFlow.TestRunner.CollectScenarioErrors()
            at Pickles.TestHarness.MSTest.AdditionFeature.ScenarioCleanup() in C:\dev\pickles-results-harness\Pickles.TestHarness\Pickles.TestHarness.MSTest\Addition.feature.cs:line 0
            at Pickles.TestHarness.MSTest.AdditionFeature.FailToAddTwoNumbers() in c:\dev\pickles-results-harness\Pickles.TestHarness\Pickles.TestHarness.MSTest\Addition.feature:line 18

Check warning on line 819 in test/test_spark.py

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

2 out of 6 runs failed: test_rsh_events (test.test_spark.SparkTests) 

test-files/junit-xml/pytest/junit.fail.xml [took 7s]
Raw output 
self = <test_spark.SparkTests testMethod=test_rsh_events>

                def test_rsh_events(self):
                > self.do_test_rsh_events(3)

                test_spark.py:821:
                _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
                test_spark.py:836: in do_test_rsh_events
                self.do_test_rsh(command, 143, events=events)
                test_spark.py:852: in do_test_rsh
                self.assertEqual(expected_result, res)
                E AssertionError: 143 != 0

Check warning on line 0 in [genericTestClass]

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

2 out of 6 runs failed: ShouldBeString ([genericTestClass]) 

test-files/xunit/mstest/fixie.xml [took 1s]
Raw output 
Expected: System.String
Actual:   System.Int32   at [genericTestClassForStackTrace].ShouldBeString[T](T genericArgument) in [fileLocation]:line #

Check warning on line 0 in [testClass]

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: Fail ([testClass]) 

test-files/xunit/mstest/fixie.xml [took 1s]
Raw output 
'Fail' failed!   at [testClassForStackTrace].Fail() in [fileLocation]:line #

Check warning on line 0 in [testClass]

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: FailByAssertion ([testClass]) 

test-files/xunit/mstest/fixie.xml [took 1s]
Raw output 
Expected: 2
Actual:   1   at [testClassForStackTrace].FailByAssertion() in [fileLocation]:line #

Check warning on line 0 in Prueba_Sistema.SIARAlgorithmTest

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: EST_INTER_TEMPTest (Prueba_Sistema.SIARAlgorithmTest) 

test-files/trx/yami_YAMILEX 2015-10-24 04_18_59.trx [took 19s]
Raw output 
El método de prueba Prueba_Sistema.SIARAlgorithmTest.EST_INTER_TEMPTest produjo la excepción: 
System.ArgumentOutOfRangeException: El índice estaba fuera del intervalo. Debe ser un valor no negativo e inferior al tamaño de la colección.
Nombre del parámetro: index    en System.ThrowHelper.ThrowArgumentOutOfRangeException()
   en System.Collections.Generic.List`1.set_Item(Int32 index, T value)
   en TMC.Components.TemperatureControl.SIARAlgorithm.EST_INTER_TEMP(Double TAMP, Int32 TEXTERN) en E:\TMC\TMC\Components\TemperatureControl\SIARAlgorithms.cs:línea 363
   en Prueba_Sistema.SIARAlgorithmTest.EST_INTER_TEMPTest() en E:\TMC\Prueba_Sistema\SIARAlgorithmTest.cs:línea 199

Check warning on line 0 in Prueba_Sistema.SIARAlgorithmTest

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: EST_LAMB_TEMPTest (Prueba_Sistema.SIARAlgorithmTest) 

test-files/trx/yami_YAMILEX 2015-10-24 04_18_59.trx [took 2s]
Raw output 
El método de prueba Prueba_Sistema.SIARAlgorithmTest.EST_LAMB_TEMPTest produjo la excepción: 
System.ArgumentOutOfRangeException: El índice estaba fuera del intervalo. Debe ser un valor no negativo e inferior al tamaño de la colección.
Nombre del parámetro: index    en System.ThrowHelper.ThrowArgumentOutOfRangeException()
   en System.Collections.Generic.List`1.get_Item(Int32 index)
   en TMC.Components.TemperatureControl.SIARAlgorithm.EST_LAMB_TEMP(Double TINTPP, Double TAMP, Int32 TEXTERN, Int32 CRPBuscar) en E:\TMC\TMC\Components\TemperatureControl\SIARAlgorithms.cs:línea 474
   en Prueba_Sistema.SIARAlgorithmTest.EST_LAMB_TEMPTest() en E:\TMC\Prueba_Sistema\SIARAlgorithmTest.cs:línea 217

Check failure on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs with error: bazel/failing_absl_test 

test-files/junit-xml/bazel/suite-logs.xml [took 0s]
Raw output 
exited with error code 1

Check warning on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: Unknown test 

test-files/xunit/mstest/jenkinsci/testcase6.xml [took 36s]
Raw output 
OK: TestProcess.Execution.ExitCode == 0
FAIL: Output differs from reference.
  Left:  data\ref
  Right: results\out

Check warning on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: factorial_of_value_from_fixture 

test-files/junit-xml/tst/disabled.xml [took 0s]
Raw output 
/home/ivan/prj/tst/tests/failed/main.cpp:72: error: check_eq(3628800, 3628801)

Check warning on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs failed: positive_arguments_must_produce_expected_result 

test-files/junit-xml/tst/disabled.xml [took 0s]
Raw output 
/home/ivan/prj/tst/tests/failed/main.cpp:45: error: check_ne(6, 6)hello world!

Check failure on line 0 in /

See this annotation in the file changed.

@github-actions github-actions / Test Results (Test Files)

All 2 runs with error: test_which_throws_unknown_exception 

test-files/junit-xml/tst/disabled.xml [took 0s]
Raw output 
uncaught (anonymous namespace)::some_unknown_exception
View more details on GitHub Actions