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
I have a CI job as below (mainly auto-generated by maturin v1.0.1: maturin generate-ci github --pytest).
When I created a Pull-Request, with code changes but not updating the package version,
I was surprised that the tests failed.
It appears this was because it was using a cached build of that package version,
and indeed when I updated the version the job began to pass.
Is this expected?
For PRs CI, obviously, I would expect that I would not have to always update the version to have it pass.
I have a CI job as below (mainly auto-generated by maturin v1.0.1:
maturin generate-ci github --pytest
).When I created a Pull-Request, with code changes but not updating the package version,
I was surprised that the tests failed.
It appears this was because it was using a cached build of that package version,
and indeed when I updated the version the job began to pass.
Is this expected?
For PRs CI, obviously, I would expect that I would not have to always update the version to have it pass.
The text was updated successfully, but these errors were encountered: