-
Notifications
You must be signed in to change notification settings - Fork 66
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
Build number collisions #353
Comments
Right, will be working on that with higher priority. |
What account is OpenRA under? |
Also it didn't fix itself. I had to manually increment the build number. OpenRA/OpenRA#8839 (comment) |
I've had to do the same. We've gotten multiple builds now for 1.0.7651, 1.0.7647, and 1.0.7624 just within the last day. And 1.0.7678. |
What time of the day is it usually happening? |
The state sadly also butchers build times. Not sure if this is helpful:
|
It happened recently (currently time is 10:58pm EST) again on https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.7696 with build times of: |
We are working on the solution. Restart the build - there were two stuck jobs. |
Seems to happen at least daily now: 7 Aug, 2015 6:00:39 but the times seem to differ. |
What was the build number? |
I think this has been mitigated successfully for a few days, thanks. Will reopen if it happens again. |
This is still happening. See all of the 1.0.7841 repeats at https://ci.appveyor.com/project/StefanKarpinski/julia/history |
Will check what happened. I've reset the queue - start a new build. |
This hasn't happened in a while. Will call it fixed unless I see it again. |
This is happening increasingly frequently at https://ci.appveyor.com/project/StefanKarpinski/julia/history, and it's getting to be disruptive. Something needs to be made more atomic when the build number increments upon starting a new build.
The text was updated successfully, but these errors were encountered: