#5787
50%
main: 49%

Ran 21 Jan 2026 02:08PM UTC

Jobs 1

Files 157

Run time 1min

Badge

Embed ▾

Committed 21 Jan 2026 01:59PM UTC coverage: 49.508% (+0.05%) from 49.454%

Build # #5787

Build Type

Pull #4016

travis-ci

Committed by

howardgao

Commit Message

Use random storageclass names in datavolume_test.go (#4015)

Currently the datavolume_test.go uses the same name to create
storage classes in multiple tests. Sometimes it is seen test
failures due to storage class not being cleaned up
(perhaps the test cluster in bad shape).

The tests shouldn't be affected by such situations. Using
a unique (random) name for each storageclass for each test
would improve the stability of the tests because each test
wouldn't be affected by a dangling storageclass
from the last test.

Signed-off-by: Howard Gao <howard.gao@gmail.com>

Pull Request Pull Request #4016: Use random storageclass names in datavolume_test.go (#4015)

Run Details

14650 of 29591 relevant lines covered (49.51%)

0.55 hits per line

Uncovered Existing Lines

Lines	Coverage	∆	File
2	62.42	-0.26%	pkg/importer/vddk-datasource_amd64.go

Jobs

ID	Job ID	Ran	Files	Coverage
1	#5787.1	21 Jan 2026 02:08PM UTC	157	49.51

kubevirt / containerized-data-importer / #5787
50%
main: 49%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build #5787

kubevirt / containerized-data-importer / #5787 50% main: 49%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Uncovered Existing Lines

Jobs

Source Files on build #5787

kubevirt / containerized-data-importer / #5787
50%
main: 49%

README BADGES
x