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

Disable travis [take 526] #23887

Closed
copumpkin opened this issue Mar 14, 2017 · 10 comments · Fixed by #23905
Closed

Disable travis [take 526] #23887

copumpkin opened this issue Mar 14, 2017 · 10 comments · Fixed by #23905

Comments

@copumpkin
Copy link
Member

I know we've raised this before, but it's getting ridiculous. Every email I get from it is "still broken", and everything in the commit log for the past few days has been a red X. It's providing negative value right now, and I think we should just turn it off until someone has time to put against fixing it or replacing it with a more tailored solution.

@edolstra @shlevy @domenkozar @grahamc

@grahamc
Copy link
Member

grahamc commented Mar 14, 2017

I fully agree.

@domenkozar
Copy link
Member

It happens on stdenv rebuild. Our documentation depends on pandoc, which takes ages to build and travis-ci can't handle it.

@dezgeg
Copy link
Contributor

dezgeg commented Mar 14, 2017

I think this time it's that nixpkgs tarball job (or specifically eval-release.nix) takes more memory than is available in Travis.

@copumpkin
Copy link
Member Author

copumpkin commented Mar 14, 2017

The specifics seem less important than the gist of what I'm saying. I largely just ignore the emails because I don't trust the system to do anything useful for me. Does anyone get any value out of it, and enough value to justify the amount of noise it causes for everyone else?

@shlevy
Copy link
Member

shlevy commented Mar 14, 2017

+1million.

@shlevy
Copy link
Member

shlevy commented Jun 3, 2017

Shockingly I'm still getting bullshit emails. Now that hydra can build PRs I think we really need to just kill this.

@FRidh
Copy link
Member

FRidh commented Jun 3, 2017

Let's just reduce it to checking evaluation only.

@shlevy
Copy link
Member

shlevy commented Jun 3, 2017

Even that breaks spuriously at times. Can you honestly say you've ever gotten value out of these travis checks?

@shlevy
Copy link
Member

shlevy commented Jun 3, 2017

Fixed by d0b4c5f

@shlevy shlevy closed this as completed Jun 3, 2017
@7c6f434c
Copy link
Member

7c6f434c commented Jun 3, 2017

I cna say that I have got some value out of Travis build logs when reviewing some PRs, but still the situation is ridiculous.

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

Successfully merging a pull request may close this issue.

7 participants