limit memory for travis builds

[stephengroat]

I'm trying to check quite a few external links (around 1700) on travis. I'm getting error 137, which i think is out of memory.

other than limiting concurrency with hydra, are there any other ways to limit memory usage?

[stephengroat]

just bumping to see if i can get any advice, have no idea what's going on.

[gjtorikian]

Out of curiosity, how did you settle on 12 for Hydra's max concurrency?

The best advice I can give is to set it to an absurdly low number, like, 5, and see how high you can go before it crashes. ☹️

[stephengroat]

I just went with my favorite number (the truth doesn't sound very scientific of me)

I started trying to reconfigure, got it to finish with 1, started stepping it up and added typhoeus: { ssl_verifypeer: false, ssl_verifyhost: 0 } and now get a segfault https://travis-ci.org/stephengroat/twofactorauth/jobs/232602544

[gjtorikian]

Haha, amazing. I can't do anything about the sefaults I'm afraid, that's either a Travis problem (something on the box?) or a Typhoeus problem (something in the C library that's busted?).

[stephengroat]

opened something with typhoeus to see if someone can figure something out. someone also reported a memory leak in typhoeus when using hydra, might be related

typhoeus/typhoeus/issues/567

[stephengroat]

i'm closing this with the other typhoeus issues that have been found