[VTN-52] VTN Coordinator test may fail if too many threads are present. Created: 05/Dec/14  Updated: 03/May/18  Resolved: 05/Dec/14

Status: Resolved
Project: vtn
Component/s: Core
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Shigeru Yasuda Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: All


External issue ID: 2479

 Description   

I observed that VTN Jenkins job failed due to failure of VTN Coordinator UT.

https://jenkins.opendaylight.org/vtn/job/vtn-verify/628/

[ RUN ] atomic.sub_old_uint8_race
test_atomic.cc:631: Failure
Expected: (0U) != (c), actual: 0 vs 0
[ FAILED ] atomic.sub_old_uint8_race (270 ms)

This test creates 4 threads, and let them invoke atomic operation.
Although the test expects all test threads invoked atomic operation at least once,
it may not invoke if the thread scheduler on the build host did not dispatch
test threads. This test needs to ensure that all test threads has been dispatched
at least once.



 Comments   
Comment by Shigeru Yasuda [ 05/Dec/14 ]

https://git.opendaylight.org/gerrit/13405 (master)

Comment by Shigeru Yasuda [ 05/Dec/14 ]

https://git.opendaylight.org/gerrit/13409 (stable/helium)

Generated at Wed Feb 07 20:47:53 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.