28Feb17r23162 - detailed test results for COMPLEX

To reconnect the TextTest GUI to these results, run:

texttest -a complex -d /home/delphi/sumo/tests -reconnect /home/delphi/texttesttmp/gcc4_64.05Mar012900.32468 -g

To start TextTest for these tests, run:

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

default: 102 tests: 89 succeeded 10 known bugs 3 FAILED

Detailed information for the tests that FAILED:

TEST FAILED on sim-build : netconvert osm_roundtrip ( Last six runs Mar2017 Feb2017 )

---------- Differences in errors ----------
21c21
< @@ -1648,7 +1648,7 @@
---
> @@ -1647,7 +1647,7 @@
30c30
< @@ -1657,9 +1657,9 @@
---
> @@ -1656,9 +1656,9 @@
42c42
< @@ -1684,7 +1684,7 @@
---
> @@ -1683,7 +1683,7 @@
51c51
< @@ -1699,12 +1699,12 @@
---
> @@ -1698,12 +1698,12 @@

TEST FAILED on sim-build : traffic_lights loop_flow ( Last six runs Mar2017 Feb2017 )

---------- Differences in errors ----------
0a1,512
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '2i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '3i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '4i_tl0_l0' since argument 'tl' was given.
> Warning: Ignoring argument 'frequency' for E2Detector '1i_tl0_l0' since argument 'tl' was given.
<truncated after showing first 30 lines>

TEST FAILED on sim-build : tutorial san_pablo_dam ( Last six runs Mar2017 Feb2017 )

---------- Differences in errors ----------
1c1
< Warning: Value of tau=0.92 in car following model 'carFollowing-Krauss' lower than simulation step size may cause collisions
---
> Warning: Value of tau=0.923223304703 in car following model 'carFollowing-Krauss' lower than simulation step size may cause collisions
40c40
< Warning: Value of tau=0.92 in car following model 'carFollowing-Krauss' lower than simulation step size may cause collisions
---
> Warning: Value of tau=0.923223304703 in car following model 'carFollowing-Krauss' lower than simulation step size may cause collisions
391c391
< Warning: Value of tau=1.00 in car following model 'carFollowing-Krauss' lower than simulation step size may cause collisions
---
> Warning: Value of tau=0.99844020776 in car following model 'carFollowing-Krauss' lower than simulation step size may cause collisions
---------- Differences in net ----------
19c19
<     <junction id="obs1" type="unregulated" x="0.00" y="0.00" incLanes="" intLanes="" shape="0.00,-0.05 0.00,-3.25"/>
---
>     <junction id="obs1" type="dead_end" x="0.00" y="0.00" incLanes="" intLanes="" shape="0.00,-0.05 0.00,-3.25"/>
23c23
<     <junction id="obs8" type="unregulated" x="6039.00" y="0.00" incLanes="7to8_0" intLanes="" shape="6039.00,-3.25 6039.00,-0.05"/>
---
>     <junction id="obs8" type="dead_end" x="6039.00" y="0.00" incLanes="7to8_0" intLanes="" shape="6039.00,-3.25 6039.00,-0.05"/>
---------- Differences in output ----------
30c30,31
<   Unregulated junctions       : 2
---
>   Unregulated junctions       : 0
>   Dead-end junctions          : 2

Detailed information for the tests that had known bugs:

TEST had known bugs (bug 1691 (new)) on sim-build : netconvert dlr-navteq_roundtrip ( Last six runs Mar2017 Feb2017 )

******************************************************
Ticket #1691 (new defect: )
edge shapes at junctions get lost on matsim reimport
http://sumo.dlr.de/trac.wsgi/ticket/1691
Reported By: behrisch Owned by: 
Priority: major Milestone: 1.0.0
Component: net building (NETGEN, NETCONVERT) Version: 
Description:
matsim always include the node into the edge shape and thus a reimport does not give the same result. The same issue exists for dlr-navteq #1687
******************************************************
(This bug was triggered by text found in file 'net' matching '.*')
---------- Differences in net ----------
4c4
< <net version="0.13" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd">
---
> <net version="0.27" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd">
6c6
<     <location netOffset="-399345.66,-5809365.64" convBoundary="-1.31,0.00,1737.68,767.39" origBoundary="13.519602,52.425528,13.545248,52.434465" projParameter="+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"/>
---
>     <location netOffset="-399345.66,-5809362.43" convBoundary="0.00,0.00,1737.68,770.60" origBoundary="1351960.240000,5242549.880000,1354524.800000,5243232.070000" projParameter="+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"/>
9c9
<         <lane id=":175648134_0_0" index="0" allow="bicycle" speed="5.56" length="4.82" shape="15.90,169.70 14.56,169.04 14.04,168.28 14.35,167.40 15.46,166.42"/>
---
>         <lane id=":175648134_0_0" index="0" allow="bicycle" speed="5.56" length="4.82" shape="15.89,172.91 14.56,172.25 14.04,171.49 14.34,170.61 15.46,169.63"/>
12,13c12,13
<         <lane id=":261599791_0_0" index="0" speed="27.78" length="0.10" shape="34.60,181.48 34.67,181.47"/>
<         <lane id=":261599791_0_1" index="1" speed="27.78" length="0.10" shape="34.18,178.21 34.20,178.20"/>
---
>         <lane id=":261599791_0_0" index="0" speed="27.78" length="0.28" shape="34.72,184.67 34.46,184.71"/>
>         <lane id=":261599791_0_1" index="1" speed="27.78" length="0.28" shape="34.30,181.40 34.00,181.44"/>
16c16
<         <lane id=":261599791_2_0" index="0" speed="27.78" length="2.41" shape="34.18,178.21 32.85,177.55 32.33,176.78"/>
---
>         <lane id=":261599791_2_0" index="0" speed="27.78" length="2.41" shape="34.30,181.40 32.97,180.73 32.46,179.97"/>
19c19
<         <lane id=":261599791_6_0" index="0" speed="27.78" length="2.41" shape="32.33,176.78 32.64,175.91 33.76,174.93"/>
---
>         <lane id=":261599791_6_0" index="0" speed="27.78" length="2.41" shape="32.46,179.97 32.76,179.10 33.89,178.12"/>
22,23c22,23
<         <lane id=":261599791_3_0" index="0" speed="27.78" length="0.10" shape="33.34,171.66 33.34,171.66"/>
<         <lane id=":261599791_3_1" index="1" speed="27.78" length="0.10" shape="33.75,174.93 33.76,174.93"/>
---
<truncated after showing first 30 lines>

TEST had known bugs (bug 1691 (new)) on sim-build : netconvert matsim_roundtrip ( Last six runs Mar2017 Feb2017 )

******************************************************
Ticket #1691 (new defect: )
edge shapes at junctions get lost on matsim reimport
http://sumo.dlr.de/trac.wsgi/ticket/1691
Reported By: behrisch Owned by: 
Priority: major Milestone: 1.0.0
Component: net building (NETGEN, NETCONVERT) Version: 
Description:
matsim always include the node into the edge shape and thus a reimport does not give the same result. The same issue exists for dlr-navteq #1687
******************************************************
(This bug was triggered by text found in file 'net' matching '.*')
---------- Differences in net ----------
4c4
< <net version="0.13" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd">
---
> <net version="0.27" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/net_file.xsd">
6c6
<     <location netOffset="-399345.66,-5809365.64" convBoundary="-1.31,0.00,1737.68,767.39" origBoundary="13.519602,52.425528,13.545248,52.434465" projParameter="+proj=utm +zone=33 +ellps=WGS84 +datum=WGS84 +units=m +no_defs"/>
---
>     <location netOffset="0.00,-19.68" convBoundary="0.00,0.00,1737.68,747.71" origBoundary="0.00,19.68,1737.68,767.39" projParameter="!"/>
9c9
<         <lane id=":175648134_0_0" index="0" allow="bicycle" speed="5.56" length="4.82" shape="15.90,169.70 14.56,169.04 14.04,168.28 14.35,167.40 15.46,166.42"/>
---
>         <lane id=":175648134_0_0" index="0" speed="5.56" length="4.82" shape="15.90,150.02 14.56,149.36 14.04,148.60 14.35,147.72 15.46,146.74"/>
12,13c12,13
<         <lane id=":261599791_0_0" index="0" speed="27.78" length="0.10" shape="34.60,181.48 34.67,181.47"/>
<         <lane id=":261599791_0_1" index="1" speed="27.78" length="0.10" shape="34.18,178.21 34.20,178.20"/>
---
>         <lane id=":261599791_0_0" index="0" speed="27.78" length="0.22" shape="34.72,161.78 34.53,161.81"/>
>         <lane id=":261599791_0_1" index="1" speed="27.78" length="0.22" shape="34.32,158.51 34.06,158.54"/>
16c16
<         <lane id=":261599791_2_0" index="0" speed="27.78" length="2.41" shape="34.18,178.21 32.85,177.55 32.33,176.78"/>
---
>         <lane id=":261599791_2_0" index="0" speed="27.78" length="2.41" shape="34.32,158.51 32.98,157.84 32.47,157.08"/>
19c19
<         <lane id=":261599791_6_0" index="0" speed="27.78" length="2.41" shape="32.33,176.78 32.64,175.91 33.76,174.93"/>
---
>         <lane id=":261599791_6_0" index="0" speed="27.78" length="2.41" shape="32.47,157.08 32.78,156.21 33.91,155.24"/>
22,23c22,23
<         <lane id=":261599791_3_0" index="0" speed="27.78" length="0.10" shape="33.34,171.66 33.34,171.66"/>
<         <lane id=":261599791_3_1" index="1" speed="27.78" length="0.10" shape="33.75,174.93 33.76,174.93"/>
---
<truncated after showing first 30 lines>

TEST had known bugs (see #1229) on sim-build : state plain ( Last six runs Mar2017 Feb2017 )

to many tls events
(This bug was triggered by text found in file 'tls_state' matching '<tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>')
---------- Differences in tls_state ----------
4c4,54
< <tls-states>
---
> <tls-states xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://sumo.dlr.de/xsd/tlsstate_file.xsd">
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
>     <tlsState time="50.00" id="0/0" programID="0" phase="2" state="GrGg"/>
<truncated after showing first 30 lines>

TEST had known bugs (see #254) on sim-build : sumo output one_vehicle ( Last six runs Mar2017 Feb2017 )

different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
10c10
< success 0.1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (71.3, 71.4) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
12c12
< success 1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (72.0, 73.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
14c14
< success 10 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
18c18
< success 0.1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (71.3, 71.4) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
20c20
< success 1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (72.0, 73.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
22c22
< success 10 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
24c24
< success 100 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (100.0, 200.0) [('e1', -1.0), ('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
34c34
< success 0.1 ['--step-length', '1', '--end', '100'] ['3/1to2/1_0']
<truncated after showing first 30 lines>

TEST had known bugs (see #254) on sim-build : sumo output teleport ( Last six runs Mar2017 Feb2017 )

different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
2c2
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
---
> success 0.1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
4c4
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
---
> success 0.1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
6c6
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
---
> success 1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
8c8
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
---
> success 1 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
10c10
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
---
> success 10 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
12c12
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
---
> success 10 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
14c14
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
---
> success 100 ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0']
16c16
< success ['--step-length', '.1', '--end', '51'] ['2/1to1/1_0', '1/1to0/1_0']
<truncated after showing first 30 lines>

TEST had known bugs (see #254) on sim-build : sumo output teleport_multihop ( Last six runs Mar2017 Feb2017 )

different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
34c34
< success 0.1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (230.0, 230.1) [('e2', 9.99), ('e3', 10.0), ('edge', 9.99), ('lane', 9.99)]
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.1, 148.2) [('e2', 9.99), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
36c36
< success 0.1 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (148.1, 148.2) [('e2', 9.99), ('e3', 10.0), ('edge', 9.99), ('lane', 9.99)]
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.1, 148.2) [('e2', 9.99), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
38c38
< success 1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (230.0, 231.0) [('e2', 9.99), ('e3', 10.0), ('edge', 9.99), ('lane', 9.99)]
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.0, 149.0) [('e2', 9.96), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
40c40
< success 1 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (148.0, 149.0) [('e2', 9.91), ('e3', 10.0), ('edge', 9.91), ('lane', 9.91)]
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (148.0, 149.0) [('e2', 9.96), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
42c42
< success 10 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (230.0, 240.0) [('e2', 9.42), ('e3', 9.9), ('edge', 9.42), ('lane', 9.42)]
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (140.0, 150.0) [('e2', 9.98), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
44c44
< success 10 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (140.0, 150.0) [('e2', 9.96), ('e3', 9.99), ('edge', 9.96), ('lane', 9.96)]
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (140.0, 150.0) [('e2', 9.98), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
46c46
< success 100 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (200.0, 300.0) [('e1', 10.0), ('e2', 9.22), ('e3', 5.71), ('edge', 9.22), ('lane', 9.22)]
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 2/1to1/1_0 (100.0, 200.0) [('e1', 10.0), ('e2', 7.95), ('e3', 10.0), ('edge', 10.0), ('lane', 10.0)]
48c48
< success 100 ['--step-length', '.1', '--end', '1000'] 1/1to0/1_0 (100.0, 200.0) [('e1', 9.53), ('e2', 5.82), ('e3', 6.93), ('edge', 5.82), ('lane', 5.82)]
<truncated after showing first 30 lines>

TEST had known bugs (see #254) on sim-build : sumo output two_same_vehicles ( Last six runs Mar2017 Feb2017 )

different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
10c10
< success 0.1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (75.4, 75.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
12c12
< success 1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (76.0, 77.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
14c14
< success 10 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
18c18
< success 0.1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (75.4, 75.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
20c20
< success 1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (76.0, 77.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
22c22
< success 10 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
24c24
< success 100 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (100.0, 200.0) [('e1', -1.0), ('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
34c34
< success 0.1 ['--step-length', '1', '--end', '100'] ['3/1to2/1_0']
<truncated after showing first 30 lines>

TEST had known bugs (see #254) on sim-build : sumo output two_vehicles_diff_length ( Last six runs Mar2017 Feb2017 )

different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
10c10
< success 0.1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (76.4, 76.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
12c12
< success 1 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (77.0, 78.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
14c14
< success 10 ['--step-length', '.1', '--end', '100'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
18c18
< success 0.1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (76.4, 76.5) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
20c20
< success 1 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (77.0, 78.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
22c22
< success 10 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (80.0, 90.0) [('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
24c24
< success 100 ['--step-length', '.1', '--end', '1000'] ['3/1to2/1_0']
---
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (100.0, 200.0) [('e1', -1.0), ('e2', 10.0), ('e3', -1.0), ('edge', -1.0), ('lane', -1.0)]
34c34
< success 0.1 ['--step-length', '1', '--end', '100'] ['3/1to2/1_0']
<truncated after showing first 30 lines>

TEST had known bugs (see #254) on sim-build : sumo output two_vehicles_diff_speed ( Last six runs Mar2017 Feb2017 )

different outputs from detectors which should detect the same
(This bug was triggered by text found in file 'output' matching 'failed')
---------- Differences in output ----------
0a1,48
> Loading configuration... done.
> failed 0.1 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (38.4, 38.5) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (38.0, 39.0) [('e2', 9.64), ('e3', 9.5), ('edge', 9.64), ('lane', 9.64)]
> Loading configuration... done.
> failed 10 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (30.0, 40.0) [('e2', 9.86), ('e3', 9.5), ('edge', 9.86), ('lane', 9.86)]
> Loading configuration... done.
> failed 100 ['--step-length', '.1', '--end', '51'] 3/1to2/1_0 (0.0, 51.0) [('e2', 9.62), ('e3', 9.5), ('edge', 9.62), ('lane', 9.62)]
> Loading configuration... done.
> failed 0.1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (38.4, 38.5) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (38.0, 39.0) [('e2', 9.64), ('e3', 9.5), ('edge', 9.64), ('lane', 9.64)]
> Loading configuration... done.
> failed 10 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (30.0, 40.0) [('e2', 9.86), ('e3', 9.5), ('edge', 9.86), ('lane', 9.86)]
> Loading configuration... done.
> failed 100 ['--step-length', '.1', '--end', '100'] 3/1to2/1_0 (0.0, 100.0) [('e1', 9.5), ('e2', 9.53), ('e3', 9.5), ('edge', 9.47), ('lane', 9.47)]
> Loading configuration... done.
> failed 0.1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (38.4, 38.5) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (38.0, 39.0) [('e2', 9.64), ('e3', 9.5), ('edge', 9.64), ('lane', 9.64)]
> Loading configuration... done.
> failed 10 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (30.0, 40.0) [('e2', 9.86), ('e3', 9.5), ('edge', 9.86), ('lane', 9.86)]
> Loading configuration... done.
> failed 100 ['--step-length', '.1', '--end', '1000'] 3/1to2/1_0 (0.0, 100.0) [('e1', 9.5), ('e2', 9.53), ('e3', 9.5), ('edge', 9.47), ('lane', 9.47)]
> Loading configuration... done.
> failed 0.1 ['--step-length', '1', '--end', '51'] 3/1to2/1_0 (39.0, 40.0) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
> failed 1 ['--step-length', '1', '--end', '51'] 3/1to2/1_0 (39.0, 40.0) [('e2', 9.6), ('e3', 9.5), ('edge', 9.6), ('lane', 9.6)]
> Loading configuration... done.
<truncated after showing first 30 lines>

TEST had known bugs (bug 2465 (assigned)) on sim-build : traci pythonApi distance_after_reroute ( Last six runs Mar2017 Feb2017 )

******************************************************
Ticket #2465 (assigned defect: )
traci distance request is incorrect after rerouting
http://sumo.dlr.de/trac.wsgi/ticket/2465
Reported By: behrisch Owned by: hilb_ro
Priority: major Milestone: 1.0.0
Component: TraCI Version: 
Description:
retrieving the already driven distance (0xa4 0x84) gives incorrect values (starting from the rerouting edge instead of the beginning)
******************************************************
(This bug was triggered by text found in file 'output' matching '162')
---------- Differences in output ----------
7c7
< 1165.0
---
> 162.04