Skip to content

remove hacks to avoid failure due to deprecations #216

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

Merged
merged 1 commit into from
Jun 5, 2015

Conversation

dbu
Copy link
Contributor

@dbu dbu commented Jun 5, 2015

No description provided.

@ddeboer
Copy link
Member

ddeboer commented Jun 5, 2015

Hm, Scrutinizer now fails because of my #215. The problem is that there’s no way to influence the order of builds on Travis (as far as I’m aware), so when the code coverage build ends up last, we’re way over Scrutinizer’s timeout. I suggest we just raise that timeout to 10 mins. or so.

@dbu dbu force-pushed the remove-deprecation-hacks branch from 2517c23 to 03869a9 Compare June 5, 2015 14:27
@dbu
Copy link
Contributor Author

dbu commented Jun 5, 2015

can you change scrutinizer timeout in the configuration panel?

@ddeboer
Copy link
Member

ddeboer commented Jun 5, 2015

You can try to set it in this PR:

external_code_coverage:
  timeout: 600    # Timeout in seconds.

ddeboer added a commit that referenced this pull request Jun 5, 2015
remove hacks to avoid failure due to deprecations
@ddeboer ddeboer merged commit 7c59031 into master Jun 5, 2015
@lsmith77 lsmith77 removed the wip/poc label Jun 5, 2015
@ddeboer
Copy link
Member

ddeboer commented Jun 5, 2015

Thanks! Nice to get rid of the hacks. I’ll tweak code coverage in a separate PR.

@ddeboer ddeboer deleted the remove-deprecation-hacks branch June 5, 2015 14:52
ddeboer added a commit to FriendsOfSymfony/FOSHttpCache that referenced this pull request Jun 10, 2015
ddeboer added a commit that referenced this pull request Jun 10, 2015
ddeboer added a commit that referenced this pull request Jun 10, 2015
@stof
Copy link
Member

stof commented Jun 10, 2015

Actually, I think jobs are started in the order they are listed in the travis config

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.

4 participants