- 30 Aug, 2016 5 commits
-
-
Different threads could call run(), satisfy() and fail() method. Each of the methods reads/writes multiple fields during the method call. These method calls need to be synchronized to gurantee to see the latest value. Change-Id: Ic252b56e0902170d7e0fdb83f96f0fb2e55ec56b
Sho SHIMIZU authored -
The field assignment doesn't change over the life time Change-Id: I022dbe7ce8a1cbae8837fd97bff8610a4cada610
Sho SHIMIZU authored
- 29 Aug, 2016 1 commit
-
-
This reverts commit 2451a099. Change-Id: Iab7afd7c61cc1e25292e093660170101da779cf8
Jonathan Hart authored
-
- 26 Aug, 2016 4 commits
- 24 Aug, 2016 3 commits
-
-
Updated unit tests, and added a test for the app context in the URL. Change-Id: I110b62ff8366a503c3309df0f26a7dd213ae0c5f (cherry picked from commit fa875bb1)
Simon Hunt authored -
…nos is behind an app prefix Change-Id: I271da533f39091efdd01d8104c1e6740effead52
David K. Bainbridge authored
-
- 23 Aug, 2016 1 commit
- 18 Aug, 2016 1 commit
- 22 Aug, 2016 6 commits
-
-
Multiple threads could access the field, lastSink, then they should read the latest value of lastSink Change-Id: I279ed6fa3db357008603cde5cb2c57671e66b33c
Sho SHIMIZU authored -
The field, dispatchFuture, is accessed in activate() method and the thread where Watchdog is running. Then, different threads could access the field and couldn't read the latest value. Change-Id: Iceb390bcf3c5711c1dbb59198667138c8a90b036
Sho SHIMIZU authored -
The field, dispatchLoop, is accessed in activate() method and the thread where Watchdog is running. Then, different threads could access the field and could miss the latest value. Change-Id: Id218522f5b318fb3d05833ba57d908a1bf6d2949
Sho SHIMIZU authored -
The field, lastStart, is read/written from different thread pools. As a result, the field could be accessed from different threads. Change-Id: Ia50c5bd3405bf2af98abb9d14f7e35d840f62483
Sho SHIMIZU authored
-
- 20 Aug, 2016 1 commit
- 19 Aug, 2016 1 commit
- 16 Aug, 2016 3 commits
-
-
Change-Id: Ie537c9fc7b6751ca071b3c7bf1e465bafe7913d3 (cherry picked from commit df97013b)
Yuta HIGUCHI authored -
Change-Id: I3bb8eeb2abf140d44cf4dc7186cf1bf316c23f70 (cherry picked from commit c3d69f52)
Yuta HIGUCHI authored
- 11 Aug, 2016 1 commit
- 10 Aug, 2016 2 commits
-
-
This is an external dependency because it relies on DNS resolving localhost. Change-Id: I1f8aa481b2173a166334c8a7bffb60647c666e12
Jonathan Hart authored
- 09 Aug, 2016 3 commits
-
-
Change-Id: I28e35520b5bd5737117d8c2b84f9effa3c46bfaf (cherry picked from commit fb630488)
Avantika-Huawei authored
-
- 08 Aug, 2016 2 commits
- 05 Aug, 2016 1 commit
- 04 Aug, 2016 1 commit
- 03 Aug, 2016 1 commit
- 02 Aug, 2016 1 commit
- 01 Aug, 2016 2 commits
-
-
- Was excluding EdgePort when trying to remove EdgePort... Change-Id: I79da723da5b045e322ec9b9cdb5457a17f1aceb4
Yuta HIGUCHI authored -
- Edge point update should be triggered based on TopologyEvent. {Device, Link}Event can be triggered before TopologyEvent, which will result in use of the outdated Topology to determine if the port is an edge port leading to incorrect edge port set. (ONOS-4896) - Ports on Edge Link should not be considered part of infrastructure, should be candidate for Edge point. Change-Id: I7d69cc242ba7849996c1105ccd1956975db63480 (cherry picked from commit b440ef46)
Yuta HIGUCHI authored
-