Skip to content
This repository has been archived by the owner on Nov 18, 2023. It is now read-only.

End-to-end-test may use the wrong PyPi version #41

Closed
jmsfltchr opened this issue Feb 4, 2019 · 1 comment · Fixed by #69
Closed

End-to-end-test may use the wrong PyPi version #41

jmsfltchr opened this issue Feb 4, 2019 · 1 comment · Fixed by #69
Assignees
@jmsfltchr
Labels
status: solved type: build
Milestone
0.2

Comments

@jmsfltchr
Copy link
Contributor

If there are 2 workflows running at the same time, since date is used as the VERSION number for test PyPi, and the highest number is used as the latest, then the wrong version may be used by the next job in one of those workflows. That job is end-to-end-test.
@jmsfltchr jmsfltchr added this to the v0.2 milestone Feb 4, 2019
@jmsfltchr jmsfltchr self-assigned this Feb 4, 2019
@jmsfltchr
Copy link
Contributor Author

Fixed by #69

@jmsfltchr jmsfltchr mentioned this issue Sep 24, 2019
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jmsfltchr jmsfltchr

Labels
status: solved type: build
Projects
None yet
Milestone
0.2
Development

Successfully merging a pull request may close this issue.

Test deployment jmsfltchr/kglib
2 participants
@jmsfltchr @grabl