You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run the same test using mariaex 0.8.1 and ecto 2.1.2 everything works fine. The same thing happens with many tests. The line in my code causing the problem is a simple Repo.insert! function.
My temporary solution is to set ecto to 2.1.2 (using: {:ecto, "2.1.2"}) in my mix.exs file rather than using {:ecto, "~> 2.1"}
The text was updated successfully, but these errors were encountered:
I was in an umbrella project and the creation of a new application within the project caused the issue. Even though the new application had no reference with the application which contained the Ecto code in the initial post.
The solution is to force a recompilation of all the code before running the tests again. This can be achieved by explicitly changing the ecto version in the mix.exs file run:
$ mix.deps.update ecto
followed by:
$ mix test
Then change the ecto version back again and run the two commands above again.
This is strange and I have no idea as to what may be causing it.
This should probably be closed which I will do next week if you have not already done so. Sorry for the inconvenience.
paulgithub
changed the title
0.8.1 incompatibility with ecto 2.1.3
0.8.1 incompatibility with ecto 2.1.3 (Solved NOT an issue)
Feb 3, 2017
When running a test using mariaex 0.8.1 and ecto 2.1.3 I get the following error:
If I run the same test using mariaex 0.8.1 and ecto 2.1.2 everything works fine. The same thing happens with many tests. The line in my code causing the problem is a simple Repo.insert! function.
My temporary solution is to set ecto to 2.1.2 (using: {:ecto, "2.1.2"}) in my mix.exs file rather than using {:ecto, "~> 2.1"}
The text was updated successfully, but these errors were encountered: