Phillip Wittrock
b7bbefd9b1
Always to a live lookup of version info instead of caching.
2015-08-20 16:48:45 -07:00
Victor Marmol
651ee5648f
Use watch instead of sh.
...
Use of sh was making the test flaky and harder to read.
2015-07-01 14:54:35 -07:00
Victor Marmol
ee119e26f1
Add a test for differing network stats.
2015-06-25 12:00:11 -07:00
Victor Marmol
fc635c1cde
Watch for deletion event before the container runs.
...
This eliminates a race.
2015-04-22 09:21:53 -07:00
Rohit Jnagal
dfcc05a953
Fix networking stats by switching Tx and Rx stats.
...
A better fix is to directly use stats collected by libcontainer.
2015-04-13 17:01:06 +00:00
Katie Knister
fc63243801
Added todo for oom integration test
2015-04-10 14:10:25 -07:00
Katie Knister
ee4bdc2698
Improvements to events integration test
2015-04-10 13:33:22 -07:00
Katie Knister
766e7556f6
Preliminary integration tests for getting events
2015-04-08 10:20:03 -07:00
Rohit Jnagal
872546ba3a
Bulk move current info api to info/v1. Making room for info/v2.
2015-03-04 00:47:28 +00:00
Rohit Jnagal
667a8e0fd1
Rename load to load average.
...
Load is now LoadAverage. Also added comments about smoothing interval.
2015-01-28 00:37:45 +00:00
Victor Marmol
593d546946
Expect user + cpu to be within 500ms of total.
...
This should be a sane default.
2015-01-27 13:51:32 -08:00
Victor Marmol
5d579b43c9
Remove assertion that is only true in AUFS systems.
2015-01-22 15:00:45 -08:00
Vishnu Kannan
aedf42ba8c
Adding 'HasDiskIo' to Container Spec to indicate if diskio stats are available for a given container.
2015-01-20 05:06:57 +00:00
Rohit Jnagal
9a4e6304b8
Add missing copyright notices.
...
We'll add a travis rule when this is in.
2015-01-09 00:06:04 +00:00
Victor Marmol
024c3770a3
Refactoring Docker integration test.
...
Uses assert and require. Moves common components to a common file for
reuse.
2014-12-17 15:52:55 -08:00
Victor Marmol
f6a90d7bac
Adding integration test framework along with 3 tests.
...
These tests are similar to Go unit tests except that they're targetting
tesing of a running cAdvisor client. They do this by interacting with
the testing framework that is able to talk to the running cAdvisor. This
cAdvisor could be local or remote.
2014-11-19 13:02:24 -08:00
