Open smoshiur1237 opened 4 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten This is still an issue.
We are having an issue where prow Jenkins operator is not supporting Jenkins parallel pipelines. Since migrating from ghprb, we have noticed instances where tests triggered from prow reported as passed on GitHub, while some of the parallel stages had failed/aborted on Jenkins.
The issue reproduced in the following test PR where it has parallel Jenkins job was running: Test PR . Here we can see
metal3-centos-e2e-feature-test-main — Jenkins job succeeded.
status for parallel run even though only one test was passing and two other tests were aborted/failed. Jenkins Reproduction 1 , Jenkins Reproduction 2Also, adding the link to the parallel test pipeline code which was working properly before the prow migration from ghprb.
We expect to have correct prow response in case of any failure in the parallel test pipeline. In the above test cases prow response status should have
Failure
status instead ofSuccess
.