-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PETSc error in tests in v0.3.0 on a clean install due the environment not being instantiated. #204
Comments
I initially encountered the same on my local machine, but did not notice it anymore after the last push before 0.3.0 |
I deleted all my dev files so that it pulled in the latest released version, and now I get a package related error with MPI. I can't quite figure out why this suddenly started happening now.
|
This doesn't happen in the CI because For first time users of the package, however, the tests are likely to fail with this issue. |
will it help if we instantiate the package at the beginning of the tests? Line 8 in e6f8a88 |
I think it would be valuable to have that. To test it, you have to make sure you remove all development copies and instantiated environments. Otherwise it is pretty easy to never see it unless you install PETSc.jl on a new machine. |
I was able to reproduce the issue on a local machine and addressed this in PR #205, but it would be good if you an try this as well as it is possible I spoiled the machine while testing |
I didn't see this error in CI, but getting this when running tests locally on v0.3.0. The tests were running fine before I made the release.
The text was updated successfully, but these errors were encountered: