github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
56,154 Commits
32 Branches
881 Tags
633 MiB
Commit Graph

11 Commits (a5f722e181420cec5ef5533a111487034a713d7b)

Author SHA1 Message Date
Jeff Grafton aee5f457db update BUILD files 2017-10-15 18:18:13 -07:00
Jeff Grafton a7f49c906d Use buildozer to delete licenses() rules except under third_party/ 2017-08-11 09:32:39 -07:00
Jeff Grafton 33276f06be Use buildozer to remove deprecated automanaged tags 2017-08-11 09:31:50 -07:00
Jeff Grafton 3579017b86 Run hack/update-bazel.sh to generate BUILD files 2017-08-02 18:33:25 -07:00
David McMahon ef0c9f0c5b Remove "All rights reserved" from all the headers. 2016-06-29 17:47:36 -07:00
Madhusudan.C.S 47efee7ce4 Add more tests. 2016-05-14 23:19:18 -07:00
Madhusudan.C.S 317a7d2e52 Write the first test: Isn't it strange that the elaborate setup that is required alone is somewhat longer than the actual code to do the staleness check\!? 2016-05-14 20:29:38 -07:00
Madhusudan.C.S 55589e070b Virtualize the constructs a bit to make the code testable. 2016-05-14 05:03:15 -07:00
Madhusudan.C.S 704ef5bb6e Replace log with glog. 
Show log messages to users is unnecessary. It is only for
debugging purposes.
 2016-05-13 23:09:44 -07:00
Madhusudan.C.S dd154350e8 Address review comments. 2016-05-13 23:09:44 -07:00
Madhusudan.C.S dcaf005ffe Improve the speed of do-nothing build. 
As thockin found out here https://github.com/kubernetes/kubernetes/issues/24518,
vast majority of the do-nothing build time is spent in rebuilding the test
binaries. There is no staleness check support for test binaries.

This commit implements the staleness checks for test binaries and uses them
while building packages.

Tests are TBD. I am still trying to figure out how to test this.
 2016-05-13 23:09:44 -07:00