mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
47 lines
941 B
Go
47 lines
941 B
Go
package suite
|
|
|
|
import "time"
|
|
|
|
// SuiteInformation stats stores stats for the whole suite execution.
|
|
type SuiteInformation struct {
|
|
Start, End time.Time
|
|
TestStats map[string]*TestInformation
|
|
}
|
|
|
|
// TestInformation stores information about the execution of each test.
|
|
type TestInformation struct {
|
|
TestName string
|
|
Start, End time.Time
|
|
Passed bool
|
|
}
|
|
|
|
func newSuiteInformation() *SuiteInformation {
|
|
testStats := make(map[string]*TestInformation)
|
|
|
|
return &SuiteInformation{
|
|
TestStats: testStats,
|
|
}
|
|
}
|
|
|
|
func (s SuiteInformation) start(testName string) {
|
|
s.TestStats[testName] = &TestInformation{
|
|
TestName: testName,
|
|
Start: time.Now(),
|
|
}
|
|
}
|
|
|
|
func (s SuiteInformation) end(testName string, passed bool) {
|
|
s.TestStats[testName].End = time.Now()
|
|
s.TestStats[testName].Passed = passed
|
|
}
|
|
|
|
func (s SuiteInformation) Passed() bool {
|
|
for _, stats := range s.TestStats {
|
|
if !stats.Passed {
|
|
return false
|
|
}
|
|
}
|
|
|
|
return true
|
|
}
|