This job view page is being replaced by Spyglass soon. Check out the new job view.
PRbhcleek: update the testing example in README.md
ResultFAILURE
Tests 1 failed / 4 succeeded
Started2019-12-11 23:27
Elapsed4m20s
Revisiondac9718783c61661822974975e0601f7de4b9edb
Refs 385

Test Failures


NPD Metric-only Suite NPD should export Prometheus metrics. When ext4 filesystem error happens NPD should update problem_counter{reason:Ext4Error} and problem_gauge{type:ReadonlyFilesystem} 52s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=NPD\sMetric\-only\sSuite\sNPD\sshould\sexport\sPrometheus\smetrics\.\sWhen\sext4\sfilesystem\serror\shappens\sNPD\sshould\supdate\sproblem\_counter\{reason\:Ext4Error\}\sand\sproblem\_gauge\{type\:ReadonlyFilesystem\}$'
/home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:113
Got value for metric problem_counter with label map[reason:Ext4Error]: 3, expect at most 2.
Expected
    <float64>: 3
to be <=
    <float64>: 2
/home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:190
				
				Click to see stdout/stderrfrom junit-01.xml

Filter through log files


Show 4 Passed Tests

Error lines from build-log.txt

... skipping 116 lines ...
====================================
Random Seed: 1576106944
Will run 5 specs

Running in parallel across 3 nodes

NPD should export Prometheus metrics. When ext4 filesystem error happens 
  NPD should update problem_counter{reason:Ext4Error} and problem_gauge{type:ReadonlyFilesystem}
  /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:113

Using image cos-73-11647-348-0 from image family cos-73-lts at project cos-cloud


• Failure [52.528 seconds]
NPD should export Prometheus metrics.
/home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:36
  When ext4 filesystem error happens
  /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:104
    NPD should update problem_counter{reason:Ext4Error} and problem_gauge{type:ReadonlyFilesystem} [It]
    /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:113

    Got value for metric problem_counter with label map[reason:Ext4Error]: 3, expect at most 2.
    Expected
... skipping 30 lines ...
/home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:36
  On a clean node
  /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:69
    NPD should not report any problem
    /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:82
------------------------------
NPD should export Prometheus metrics. When ext4 filesystem error happens 
  NPD should remain healthy
  /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:123

• [SLOW TEST:59.096 seconds]
NPD should export Prometheus metrics.
/home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:36
  When ext4 filesystem error happens
  /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:104
    NPD should remain healthy
    /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:123
------------------------------
NPD should export Prometheus metrics. When OOM kills and docker hung happen 
  NPD should update problem_counter and problem_gauge
... skipping 8 lines ...
    /home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:139
------------------------------


Summarizing 1 Failure:

[Fail] NPD should export Prometheus metrics. When ext4 filesystem error happens [It] NPD should update problem_counter{reason:Ext4Error} and problem_gauge{type:ReadonlyFilesystem} 
/home/prow/go/src/k8s.io/node-problem-detector/test/e2e/metriconly/metrics_test.go:190

Ran 5 of 5 Specs in 155.306 seconds
FAIL! -- 4 Passed | 1 Failed | 0 Pending | 0 Skipped


Ginkgo ran 1 suite in 3m4.922986239s
Test Suite Failed
make: *** [Makefile:128: e2e-test] Error 1
+ EXIT_VALUE=2
+ set +o xtrace