aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/OpenSim/Region/Framework/Scenes/Serialization
diff options
context:
space:
mode:
authorJustin Clark-Casey (justincc)2013-02-12 21:34:12 +0000
committerJustin Clark-Casey (justincc)2013-02-12 21:34:12 +0000
commita82bd5678ec14ea45f7ddcf54e4dd0af43b64c8c (patch)
treef54b50be843f78eb225c6b517913db89c2058d57 /OpenSim/Region/Framework/Scenes/Serialization
parentRe-enable subtest for single quoted token in TestJsonSetValueJson() (diff)
downloadopensim-SC-a82bd5678ec14ea45f7ddcf54e4dd0af43b64c8c.zip
opensim-SC-a82bd5678ec14ea45f7ddcf54e4dd0af43b64c8c.tar.gz
opensim-SC-a82bd5678ec14ea45f7ddcf54e4dd0af43b64c8c.tar.bz2
opensim-SC-a82bd5678ec14ea45f7ddcf54e4dd0af43b64c8c.tar.xz
Use an integer when specifying the XWorkItem wait rather than a TimeSpan to avoid a Windows casting issue in SmartThreadPool for large TimeSpans.
TimeSpan.Milliseconds is an int64. However, STP casts this to an int (32-bit). If TimeSpan.MaxValue is given then the casting results in an invalid value for the SDK WaitHandle.WaitAll() call. This was causing the co-op script termination regression tests to fail on Windows but not Mono 2.10.8 (which is perhaps not strict in the negative values that it accepts). Solution here is to use the int millisecondsTimeout STP call rather than the TimeSpan one. This also allows us to more clearly specify Timeout.Infinite rather than TimeSpan.MaxValue Thanks to Teravus for this spot.
Diffstat (limited to 'OpenSim/Region/Framework/Scenes/Serialization')
0 files changed, 0 insertions, 0 deletions