Can_call_up_then_down_on_migrations fails

[danielmarbach]

System.InvalidOperationExceptionBulk operation cancelled because the index is stale and allowStale is false at Raven.Database.Impl.DatabaseBulkOperations.PerformBulkOperation(String index, IndexQuery indexQuery, Boolean allowStale, Func`3 batchOperation) in c:\Builds\RavenDB-Stable\Raven.Database\Impl\DatabaseBulkOperations.cs: line 77 at Raven.Database.Impl.DatabaseBulkOperations.DeleteByIndex(String indexName, IndexQuery queryToDelete, Boolean allowStale) in c:\Builds\RavenDB-Stable\Raven.Database\Impl\DatabaseBulkOperations.cs: line 31 at Raven.Client.Embedded.EmbeddedDatabaseCommands.DeleteByIndex(String indexName, IndexQuery queryToDelete, Boolean allowStale) in c:\Builds\RavenDB-Stable\Raven.Client.Embedded\EmbeddedDatabaseCommands.cs: line 852 at Raven.Client.Embedded.EmbeddedDatabaseCommands.DeleteByIndex(String indexName, IndexQuery queryToDelete) in c:\Builds\RavenDB-Stable\Raven.Client.Embedded\EmbeddedDatabaseCommands.cs: line 841 at RavenMigrations.Tests.First_Migration.Down() in RunnerTests.cs: line 257 at RavenMigrations.Runner.Run(IDocumentStore documentStore, MigrationOptions options) in Runner.cs: line 38 at RavenMigrations.Tests.RunnerTests.Can_call_up_then_down_on_migrations() in RunnerTests.cs: line 120

[khalidabuhakmeh]

This is a limitation of RavenDB, I'm not sure what I can do here. You could write your migrations to be mindful of stale indexes.

[danielmarbach]

I was talking about your intergration tests

Am 15.07.2014 um 18:12 schrieb Khalid Abuhakmeh notifications@github.com:

This is a limitation of RavenDB, I'm not sure what I can do here. You could write your migrations to be mindful of stale indexes.

— Reply to this email directly or view it on GitHub.

[dportzline83]

This issue has been addressed.