| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
and we don't use it
|
| |
|
|
|
|
| |
the time with an in-memory data plugin
|
|
|
|
|
|
|
| |
IAR. This still doesn't work proprerly since some required textures/contained item assets might be missing.
From pure code inspection, it looks like the uuid gatherer may get most asset uuids because the scene object serializer naively pulls non-root parts from all contained scene objects into one mega-object. However, root part uuids may well still be missing, and there may be other odd artifacts from this bug.
It appears that storing the size of the coalescence and the offsets is redundant, since one can work out this information from the position data already in the scene object groups.
|
| |
|
|
|
|
| |
For test code, take a part name prefix when creating objects, so that these can be more easily identified in the logs
|
|
|
|
| |
Also adds SceneSetupHelpers methods to easily create sogs with different part UUIDs
|
| |
|
|
|
|
| |
construction into SceneSetupHelpers.CreateSceneObject()
|
| |
|
|
|
|
| |
preserving service instances between tests. This wasn't being used anyway and just leads to hard to diagnose test failures.
|
|
|
|
| |
static dictionaries on NullUserAccountData instance instead to stop user accounts being carried over between tests
|
|
|
|
| |
Calling async code in automated tests is never a good idea - things become very fragile very quickly
|
|
|
|
| |
this is done differently elsewhere
|
|
|
|
| |
Stop tests setting up a capabilities module by default
|
|
|
|
|
|
|
| |
for the last stage of AddRootAgent() instead of SP.MakeRootAgent()
Going this extra step doesn't appear to cause any test failures.
This is arguably better for test purposes, though at some stage another method may arise which does just call AddRootAgent().
|
|
|
|
|
|
|
| |
yet complete.
While implementing this, a bug was fixed in scene setup helpers where module RegionLoaded() was called immediately after AddRegion() instead of waiting for all AddRegions() to complete.
Also, XmlRpcGroupsModule non-message functionality will now work without a message transfer module (as indicated in the comments but with a contradictory implementation)
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
| |
* Removed StorageManager
* CONFIG CHANGE: There are no more database settings in OpenSim.ini. Check the config-include configuration files for region store and estate store database settings
|
|
|
|
|
| |
Added a MockRegionDataPlugin to do in-memory persistence for tests since adding this to OpenSim.Data.Null.NullDataStore doesn't seem appropriate
NullDataStore can do nothing because OpenSim only ever retrieve region objects from the database on startup. Adding an in-memory store here would be unecessary overhead.
|
|
|
|
|
|
| |
goes to the correct directory
Also removes some mono compiler warnings
|
| |
|
|
|
|
| |
easily configured for test purposes
|
|
|
|
|
|
| |
OpenSim.Data.Null.UserAuthenticationData plugin
additional tweaks to get this working properly
|
|
|
|
| |
didn't get the authentication server to work and my brain is about to fizzle out my ears
|
|
|
|
| |
improve test to retrieve object by known uuid rather than dynamically assigned local id
|
|
|
|
|
|
| |
reference
* Added a MockConsole that doesn't require a handle to System.Console
|
|
|
|
|
|
|
|
|
| |
config-include settings to a separate file for standalone
Update information in StandaloneCommon.ini.example to reflect this
Remove ISharedRegionModule interfaces from all SimianGrid connector classes temporarily since this stopped standalone from working (due to absence of AssetURI settings, etc.).
Solution here may be to create separate region module connectors as done by local/grid/hypergrid so that loading can be controlled via include files
Or otherwise work out how to stop these modules from being loaded for all OpenSim invocations
|
|
|
|
|
|
| |
Adds MockUserAccountService and connects it up
Stops services being carried over between tests since this leads to hard to find bugs
Improves information and error reporting when loading plugins
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
can now determine if a connection is from login, teleport or crossing.
Needed for a meaningful banlines implementation
|
|
|
|
| |
remove duplicate mock inventory service
|
|
|
|
| |
does the real LandChannel), percolating to SceneSetupHelpers.
|
|
|
|
| |
- adding LandDataSerializer to OAR mechanics
|
|
|
|
| |
and that needs to be reflected in all other services setups. But the teleport test still doesn't work. Commenting it for now.
|
|
|
|
|
|
| |
find it in the cache.
Commented out the Standalone teleport test because it's failing, and the scene setup is very confusing. I suspect it may be wrong -- the connectors-as-ISharedRegionModules are being instantiated several times when there are several scenes.
|
| |
|
|
|
|
|
| |
IConfigSource causing grief to region modules expecting it to be
non-empty (which a number of them do).
|
|
|
|
|
|
| |
randomly occurs.
* LongVersion nIni may be causing the test thread death. Pausing OpenSimulator during startup causes a nIni error that makes debugging startup operations difficult for users. It might be because when it's in pause mode, something else reads from the nini config passed? If it is, it might not be fixable.. however, if it's concurrency that causes nini death it would make sense to give each section of the tests a new IConfigSource so that they don't read from the same configsource at the same time.
|
|
|
|
| |
panda)
|
|
|
|
|
|
|
|
| |
inventory and asset, service modules. The boolean startServices was replaced with realServices string. If the string contains the word asset, it will start a real asset module, if it contains inventory, it starts a real inventory. Otherwise, it use mock (NullPlugin-like) objects, for tests that don't really need functionality.
* SetupScene is now actually sharing the asset and inventory modules if the tester wishes to have multiple regions connected. To link regions, just start SetupScene with the same CommunicationManager for all scenes. SceneSetupHelper will hold a static reference to the modules and won't initialize them again, just run the scenes through the modules AddRegion, RegionLoaded and PostInitialize.
* With the recent changes, both asset and inventory (and in the future, user) services should always be asked from the scene, not instantiated alone. The tests should reflect this new behavior and always start a scene.
|
|
|
|
| |
SceneSetupHelpers.SetupScene()
|