You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Same issue as #324 (which is closed as they found a workaround).
Expecto is generating junit files with invalid xml, such as 
, for example:
<?xml version="1.0" encoding="utf-8"?>
<testsuites>
<testsuite name="Nemo.Processors.RP65816.Tests, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null">
<testcase name="addressing/absolute address x, long/always fails" time="0.065">
<failure message="
.
[32mexpected[36m: [32m2[36m
[31m actual[36m: [31m1[36m
 at Nemo.Processors.RP65816.Tests.ModeTests.modes@137-6.Invoke(Unit unitVar) in /home/adam/Repos/nemo/Nemo.Processors.RP65816.Tests/src/ModeTests.fs:line 137
 at Expecto.Impl.execTestAsync@935-1.Invoke(Unit unitVar) in C:\Users\Anthony Lloyd\src\expecto\Expecto\Expecto.fs:line 939
 at Microsoft.FSharp.Control.AsyncPrimitives.CallThenInvoke[T,TResult](AsyncActivation`1 ctxt, TResult result1, FSharpFunc`2 part2)
 at <StartupCode$FSharp-Core>.$Async.StartChild@1641-5.Invoke(AsyncActivation`1 ctxt)
 at Microsoft.FSharp.Control.Trampoline.Execute(FSharpFunc`2 firstAction)" />
</testcase>
</testsuites>
As a result, none of the xml file readers I've tried is able to parse it, including CircleCI which I want to use it to give me analytics.
The workaround is to use --colours 0 but that removes colours from console output, which isn't what we want either. We should never be putting this invalid XML into the XML files.
The text was updated successfully, but these errors were encountered:
Same issue as #324 (which is closed as they found a workaround).
Expecto is generating junit files with invalid xml, such as


, for example:As a result, none of the xml file readers I've tried is able to parse it, including CircleCI which I want to use it to give me analytics.
The workaround is to use
--colours 0
but that removes colours from console output, which isn't what we want either. We should never be putting this invalid XML into the XML files.The text was updated successfully, but these errors were encountered: