Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upPut travis verification limits in documentation #1070
Comments
hamiltont
added
the
travis-related
label
Oct 19, 2014
hamiltont
referenced this issue
Oct 20, 2014
Closed
Cabal occasionally fails on Travis-CI due to low memory #1117
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
hamiltont
Oct 25, 2014
Contributor
Tests requesting lots of RAM may not be able to allocate it consistently. Jobs are only guaranteed a small amount of RAM, and if the the worker is heavily loaded with jobs they may only get the min guarantee. If the worker is not heavily loaded they may get all the requested RAM. Only known fix at the moment is to check if os.environ["TRAVIS"] is set and start your system differently
Tests using multiprocessing.cpu_count will get inaccurate numbers on travis, where cpuset is used. Multiprocessing returns all CPUs on the machine, not CPUs your program is allowed to use.
Tests requesting lots of DB connections may not be able to get them all properly
Pool connect error: PostgreSQL FATAL 53300 remaining connection slots are reserved for non-replication superuser connection
|
Tests requesting lots of RAM may not be able to allocate it consistently. Jobs are only guaranteed a small amount of RAM, and if the the worker is heavily loaded with jobs they may only get the min guarantee. If the worker is not heavily loaded they may get all the requested RAM. Only known fix at the moment is to check if Tests using Tests requesting lots of DB connections may not be able to get them all properly
|
hamiltont
added
the
benchmark toolset
label
Mar 12, 2015
LadyMozzarella
added
New Feature: Documentation
and removed
benchmark toolset
labels
Mar 31, 2015
hamiltont
referenced this issue
Apr 3, 2015
Closed
Put travis verification limits in documentation #21
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Moved to TechEmpower/TFB-Documentation#21 |
hamiltont commentedAug 28, 2014
As I've been setting up the vagrant stuff, I've noticed that multiple tests that pass in travis fail in a clean virtual machine running on EC2. This mostly seems ot be due to travis coming with a ton of pre-installed software, whereas the VM truly is clean. So we should encourage people to use the vagrant setup scripts and run inside a local virtual machine for full confidence in their code