Skip to content
This repository has been archived by the owner on May 29, 2019. It is now read-only.

Travis-CI build failed because it automatically routed the builds to Ubuntu Trusty #6649

Closed
angelina999990 opened this issue Oct 9, 2017 · 3 comments
Closed

Travis-CI build failed because it automatically routed the builds to Ubuntu Trusty #6649

angelina999990 opened this issue Oct 9, 2017 · 3 comments

Comments

@angelina999990
Copy link

angelina999990 commented Oct 9, 2017 •
edited
Loading

Travis-ci build failed because it automatically routed the builds to Ubuntu Trusty, which is the Ubuntu distribution used by default now. However, the builds is supposed to work in Ubuntu Precise which has reached the end of life.

check following
https://blog.travis-ci.com/2017-07-11-trusty-as-default-linux-is-coming

related Issue
#6624
@icfantv
Copy link
Contributor

icfantv commented Oct 14, 2017

Looking into this. Thanks.

@icfantv
Copy link
Contributor

icfantv commented Oct 14, 2017

That's not why the build failed. I'm pretty sure it's this: jasmine/jasmine#1327

@icfantv
Copy link
Contributor

icfantv commented Oct 14, 2017

Ok, I've played around with this for an hour and I'm calling it. I don't have time to debug this. If you want to, please feel free. I've tried both precise and trusty as well as the timeout/retry settings in the issue above and pinning jasmine-core at 2.5.2, none of which works. Maybe there's a magic combination that gets it passing, and maybe there's not. This project is EOL'd and there was a 9 month span between the last successful build and the first failed one.

@icfantv icfantv closed this as completed Oct 14, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@icfantv @angelina999990