22May2023 - detailed test results for COMPLEX.libsumo

To reconnect the TextTest GUI to these results, run:

texttest -a complex -d /home/delphi/extraGcc/sumo/tests -reconnect /home/delphi/extraGcc/texttesttmp/extra_gcc4_64.31May091822.3075114 -g

To start TextTest for these tests, run:

texttest -a complex -d /home/delphi/extraGcc/sumo/tests

libsumo: 485 tests: 482 succeeded 2 FAILED 1 known bugs

Detailed information for the tests that FAILED:

TEST FAILED on ts-sim-build-ba : traci contextSubscriptions matrix_test ( Last six runs May2023 )

---------- Differences in output ----------
14c14
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
28c28
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
30c30
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
32c32
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
46c46
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
48c48
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
50c50
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
---
> restarting sumo due to FatalTraCIError 'Connection closed by SUMO.'
52c52
< restarting sumo due to FatalTraCIError 'connection closed by SUMO'
<truncated after showing first 30 lines>

TEST FAILED on ts-sim-build-ba : traci_java concurrent ( Last six runs May2023 )

---------- Differences in errors ----------
1a2
> double free or corruption (out)
---------- Differences in output ----------
77,86c77,91
< Thread started
< Thread started
< Thread started
< Thread started
< Thread started
< Thread started
< Thread started
< Thread started
< Thread started
< Thread started
---
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007f7afb1d247e, pid=3212254, tid=3212483
> #
> # JRE version: OpenJDK Runtime Environment (11.0.18+10) (build 11.0.18+10-post-Ubuntu-0ubuntu122.04)
> # Java VM: OpenJDK 64-Bit Server VM (11.0.18+10-post-Ubuntu-0ubuntu122.04, mixed mode, sharing, tiered, compressed oops, g1 gc, linux-amd64)
> # Problematic frame:
> # C  [libc.so.6+0xa547e]Thread started  free+0x1e
> #
> # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to <TEXTTEST_SANDBOX>/core.3212254)
> #
> 
> # An error report file with more information is saved as:
> # <TEXTTEST_SANDBOX>/hs_err_pid3212254.log

Detailed information for the tests that had known bugs:

TEST had known bugs (see #3263) on ts-sim-build-ba : traci vehicle moveToXY keepRoute2 ( Last six runs May2023 )

mapping failure
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
0a1
> internal corner (inside, segment2) failed: x=198, x2=198.0,   y=1.9, y2=1.9,   lane=middle_0, lane2=middle_0, pos=102, pos2=98.0   posLat=2.0 posLat2=1.9