Skip to content

Conversation

@maflcko
Copy link
Member

@maflcko maflcko commented Apr 26, 2016

Should be safe to revert now, I assume?

Edit: Initially this timed out, but it seems this does no longer timeout as of today...

Good to merge?

@maflcko maflcko force-pushed the Mf1604-travisQtCache branch from faaa62a to fade891 Compare April 27, 2016 09:35
@maflcko maflcko force-pushed the Mf1604-travisQtCache branch from c2da600 to fade891 Compare April 27, 2016 11:00
@laanwj
Copy link
Member

laanwj commented Apr 27, 2016

@theuni Is this ok to do now?

@theuni
Copy link
Member

theuni commented Apr 27, 2016

Not yet. It's building quickly now because it's been incrementally cached. The issue will be fresh builds with no cache (#7165 as an example, which will essentially be a complete rebuild).

I think we should work on speeding up tests first. I played around with parallelizing the rpc tests yesterday with reasonable success.

Additionally, travis-ci/travis-build#706 will buy us a few extra minutes, as we'll be able to switched to the stripped down image that should startup quicker.

@MarcoFalke to see where we stand, you could try merging #7165 in here and seeing how long it takes.

@laanwj
Copy link
Member

laanwj commented Apr 28, 2016

Maybe we can build against the platform qt in the meantime?
The qt tests aren't very worthwhile, but building against qt was a good way to make sure a full compilation still works.

@maflcko
Copy link
Member Author

maflcko commented May 9, 2016

Concept NACK per above discussion but I am leaving this open as an issue to indicate something needs to be done here.

@maflcko maflcko closed this May 23, 2016
@maflcko maflcko deleted the Mf1604-travisQtCache branch May 23, 2016 16:23
@laanwj laanwj mentioned this pull request May 30, 2016
1 task
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants