kubernetes: [Failing Test] Conformance - OpenStack (ci-cloud-provider-openstack-acceptance-test-e2e-conformance)
Which jobs are failing:
Conformance - OpenStack (ci-cloud-provider-openstack-acceptance-test-e2e-conformance)
Which test(s) are failing:
[sig-scheduling] SchedulerPreemption [Serial] validates basic preemption works [Conformance]
Since when has it been failing:
06-03-20 07:08 PDT
Testgrid link:
https://testgrid.k8s.io/sig-release-master-informing#Conformance - OpenStack
Reason for failure:
Jun 3 15:32:47.275: FAIL: We need at least two pods to be created butall nodes are already heavily utilized, so preemption tests cannot be run
Anything else we need to know:
Looks like this is a new test that was just promoted here: https://github.com/kubernetes/kubernetes/pull/80545
/cc @spiffxp
/cc @kubernetes/ci-signal /priority critical-urgent /milestone v1.19 /sig testing /assign @hkamel
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 27 (25 by maintainers)
s/liggitt/bentheelder/ for test aggregation discussions
they’re available in prow.k8s.io’s viewer if the bucket is public, and testgrid config controls what log viewer is used on click through (it’s templated IIRC)
On Wed, Jul 22, 2020 at 1:31 PM Taylor Dolezal notifications@github.com wrote:
@BenTheElder Openstack team is discussing in Slack 😃 Their job config is outside of Kubernetes org, but I’ll make sure to xref any PR’s here.
Looks like this is running again! (albeit with a failure on
DumpClusterLogs)… will investigateGiven that this is not release blocking and we have limited insight into the testing environment, I am going to bump this to v1.20
/milestone v1.20
can you elaborate on what you mean by log aggregation?
third party CI can upload any files they want, but the intention is primarily that testgrid can display structured JUnit xml results. testgrid / prow also have some JSON files with timestamps and pass/fail essentially.
On Wed, Jul 22, 2020 at 1:11 PM Jordan Liggitt notifications@github.com wrote:
This is really hard for us to track as the CI system it runs in is entirely opaque to us. Any thoughts on what to do about this? @liggitt @onlydole