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

Fix vm download URL as for issue #319 #320

Merged
merged 5 commits into from Oct 6, 2017

Conversation

Projects
None yet
4 participants
@guillep
Collaborator

guillep commented Oct 6, 2017

Pharo stable and 6.1 should use vm61.

Pharo 6.0, and moose should keep vm60.

@fniephaus

This comment has been minimized.

Show comment
Hide comment
@fniephaus

fniephaus Oct 6, 2017

Member

Do you know if Moose-6.1 is based on Pharo-6.1 and also needs a 6.1 vm?

Member

fniephaus commented Oct 6, 2017

Do you know if Moose-6.1 is based on Pharo-6.1 and also needs a 6.1 vm?

@fniephaus fniephaus self-requested a review Oct 6, 2017

@guillep

This comment has been minimized.

Show comment
Hide comment
@guillep

guillep Oct 6, 2017

Collaborator

No idea, I don't maintain Moose, that's why I did not dare to change it :)

Collaborator

guillep commented Oct 6, 2017

No idea, I don't maintain Moose, that's why I did not dare to change it :)

@fniephaus fniephaus self-assigned this Oct 6, 2017

@fniephaus

This comment has been minimized.

Show comment
Hide comment
@fniephaus

fniephaus Oct 6, 2017

Member

Do you know if Moose-6.1 is based on Pharo-6.1 and also needs a 6.1 vm?

@SergeStinckwich can you answer that question?

Member

fniephaus commented Oct 6, 2017

Do you know if Moose-6.1 is based on Pharo-6.1 and also needs a 6.1 vm?

@SergeStinckwich can you answer that question?

@SergeStinckwich

This comment has been minimized.

Show comment
Hide comment
@SergeStinckwich

SergeStinckwich Oct 6, 2017

Contributor

Apparently Moose6.1 is based on Pharo 6.1 (update 60510).

Contributor

SergeStinckwich commented Oct 6, 2017

Apparently Moose6.1 is based on Pharo 6.1 (update 60510).

@fniephaus

This comment has been minimized.

Show comment
Hide comment
@fniephaus

fniephaus Oct 6, 2017

Member

FYI: the Pharo download servers are very slow at the moment (it took almost 5min to download image and vm in this build).

Member

fniephaus commented Oct 6, 2017

FYI: the Pharo download servers are very slow at the moment (it took almost 5min to download image and vm in this build).

@guillep

This comment has been minimized.

Show comment
Hide comment
@guillep

guillep Oct 6, 2017

Collaborator

About the slowness of servers, this is a known issue. @demarey is going to talk with the people from the hosting service to find a solution early next week.

Collaborator

guillep commented Oct 6, 2017

About the slowness of servers, this is a known issue. @demarey is going to talk with the people from the hosting service to find a solution early next week.

@fniephaus fniephaus merged commit eca514d into hpi-swa:master Oct 6, 2017

3 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 79.221%
Details
@fniephaus

This comment has been minimized.

Show comment
Hide comment
@fniephaus

fniephaus Oct 6, 2017

Member

@guillep ok cool, just wanted to make sure you are aware of this as it can cause CI builds to fail.

Member

fniephaus commented Oct 6, 2017

@guillep ok cool, just wanted to make sure you are aware of this as it can cause CI builds to fail.

@marianopeck

This comment has been minimized.

Show comment
Hide comment
@marianopeck

marianopeck Oct 6, 2017

Contributor

Hi @fniephaus
After you have merged this PR (which I see you did) do you know how long it takes to have SmalltalkCI runner (the production runner for Travis) to take effect of this fix?

Contributor

marianopeck commented Oct 6, 2017

Hi @fniephaus
After you have merged this PR (which I see you did) do you know how long it takes to have SmalltalkCI runner (the production runner for Travis) to take effect of this fix?

@fniephaus

This comment has been minimized.

Show comment
Hide comment
@fniephaus

fniephaus Oct 6, 2017

Member

@marianopeck Travis CI pulls smalltalkCI's master branch, so as soon as this was merged it should take effect. Restart your old builds or it should be fixed with your next push.

Member

fniephaus commented Oct 6, 2017

@marianopeck Travis CI pulls smalltalkCI's master branch, so as soon as this was merged it should take effect. Restart your old builds or it should be fixed with your next push.

@marianopeck

This comment has been minimized.

Show comment
Hide comment
@marianopeck

marianopeck Oct 7, 2017

Contributor

thanks @fniephaus
Yeah, I can confirm it is fixed now! Cool and thanks

Contributor

marianopeck commented Oct 7, 2017

thanks @fniephaus
Yeah, I can confirm it is fixed now! Cool and thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment