Skip to content
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

[notebook2] libsass depends on a c++ compiler #5489

Merged
merged 1 commit into from
Feb 28, 2019

Conversation

danking
Copy link
Contributor

@danking danking commented Feb 28, 2019

notebook2 deploys are currently broken, which breaks all deploys

Copy link
Collaborator

@chrisvittal chrisvittal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately, the only way to check if this actually works right now is for deploy to succeed. 😞

@akotlar
Copy link
Contributor

akotlar commented Feb 28, 2019

Pushed a similar fix a few minutes ago, good timing.

@akotlar
Copy link
Contributor

akotlar commented Feb 28, 2019

Unfortunately, the only way to check if this actually works right now is for deploy to succeed. 😞

Can't you check by building the docker image?

@danking
Copy link
Contributor Author

danking commented Feb 28, 2019

@akotlar is right, I tested this locally.

@akotlar
Copy link
Contributor

akotlar commented Feb 28, 2019

@danking btw, we can drop the pip <19 req: pypa/pip#6197

@danking
Copy link
Contributor Author

danking commented Feb 28, 2019

#5482 :P

@akotlar
Copy link
Contributor

akotlar commented Feb 28, 2019

#5482 :P

Haha man we're on the same wavelength today: akotlar@c0c3751
(g++ is a neater solution, I was going to test that next)

@chrisvittal
Copy link
Collaborator

Well yes. What I mean is in an automated fashion. We haven't deployed any builds in around a day because of this error, the deploy job keeps restarting and it was very difficult for me to interrogate what was going on.

@akotlar
Copy link
Contributor

akotlar commented Feb 28, 2019

Well yes. What I mean is in an automated fashion. We haven't deployed any builds in around a day because of this error, the deploy job keeps restarting and it was very difficult for me to interrogate what was going on.

yeah, sorry, that's on me. I didn't notice because the pod's log didn't change between the first PR, which didn't have libsass, and the next, which did; assumed CI hadn't deployed it because it was backed up.

@danking danking merged commit be4b854 into hail-is:master Feb 28, 2019
tpoterba pushed a commit to tpoterba/hail that referenced this pull request Nov 7, 2019
@danking danking deleted the fix-notebook2-deploy branch December 18, 2019 19:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants