Aaron Lehmann 8691a77e44 Fix build cache false positives when build context tar contains unnormalized paths ... If a build context tar has path names of the form 'x/./y', they will be stored in this unnormalized form internally by tarsum. When the builder walks the untarred directory tree and queries hashes for each relative path, it will query paths of the form 'x/y', and they will not be found. To correct this, have tarsum normalize path names by calling Clean. Add a test to detect this caching false positive. Fixes #21715 Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com>		2016-04-14 17:57:45 -07:00
..
testdata	Remove PortSpecs from Config	2015-05-29 22:38:09 +02:00
builder_context.go	Lint on pkg/* packages	2015-07-27 21:26:21 +02:00
builder_context_test.go	Add test coverage for pkg/tarsum	2015-06-02 09:08:01 +02:00
fileinfosums.go	Fix typos found across repository	2015-12-13 18:04:12 +02:00
fileinfosums_test.go	Add test coverage for pkg/tarsum	2015-06-02 09:08:01 +02:00
tarsum.go	Fix build cache false positives when build context tar contains unnormalized paths	2016-04-14 17:57:45 -07:00
tarsum_spec.md	fix common misspell	2016-02-11 15:49:36 -08:00
tarsum_test.go	fix variables that werent being called	2016-03-17 13:19:55 -07:00
versioning.go	Fix uses of "int" where "int64" should be used instead	2015-07-31 16:31:40 -07:00
versioning_test.go	Add test coverage for pkg/tarsum	2015-06-02 09:08:01 +02:00
writercloser.go	TarSum: versioning	2014-09-10 15:41:52 -04:00