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
{{ message }}
This repository was archived by the owner on Dec 13, 2021. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 13, 2021. It is now read-only.
ok github.com/osrg/namazu/nmz/cli 2.768s coverage: 0.3% of statements
ok github.com/osrg/namazu/nmz/cli/container/run 2.432s coverage: 0.0% of statements
ok github.com/osrg/namazu/nmz/cli/inspectors 2.568s coverage: 12.6% of statements
ok github.com/osrg/namazu/nmz/cli/tools 1.024s coverage: 2.5% of statements
ok github.com/osrg/namazu/nmz/container 2.534s coverage: 0.0% of statements
ok github.com/osrg/namazu/nmz/container/ns 1.025s coverage: 0.0% of statements
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated
ok github.com/osrg/namazu/nmz/cli 2.220s coverage: 0.3% of statements
ok github.com/osrg/namazu/nmz/cli/container/run 2.226s coverage: 0.0% of statements
ok github.com/osrg/namazu/nmz/cli/inspectors 2.230s coverage: 12.6% of statements
ok github.com/osrg/namazu/nmz/cli/tools 1.017s coverage: 2.5% of statements
ok github.com/osrg/namazu/nmz/container 2.223s coverage: 0.0% of statements
ok github.com/osrg/namazu/nmz/container/ns 1.015s coverage: 0.0% of statements
ok github.com/osrg/namazu/nmz/endpoint 2.404s coverage: 72.1% of statements <--- this
...
The result suggests that the cause of the issue is just related to the initialization of the test process.
So the issue is not likely to happen in the usual case.
Activity
AkihiroSuda commentedon Jun 6, 2016
locally reproducible.
TestEndpointWithPacketEvent_256_4seems hanging.4919228
a.txt
AkihiroSuda commentedon Jun 9, 2016
for f in $(seq 1 5000);do ./endpoint.test -test.run TestEndpointWithPacketEvent_1_1 -test.v ; donefor f in $(seq 1 5000);do ./endpoint.test -test.run TestEndpointWithPacketEvent_256_4 -test.v ; done./endpoint.test -test.run TestEndpointWithPacketEvent_1_1 -test.v -test.count 5000./endpoint.test -test.run TestEndpointWithPacketEvent_256_4 -test.v -test.count 5000The result suggests that the cause of the issue is just related to the initialization of the test process.
So the issue is not likely to happen in the usual case.
minimized log:
[-]Flaky test?: nmz/endpoint[/-][+]Flaky test: nmz/endpoint[/+]