test-infra: status updates for run_after_success jobs seem to be bugged

Observed in the wild here: https://github.com/kubernetes/kubernetes/pull/51064#issuecomment-330968747

The kubeadm job failed but was still marked as "Parent Job Status Changed: Job triggered."

/cc @luxas @kargakis

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 17 (17 by maintainers)

Most upvoted comments

The kubeadm job was never meant to trigger for the linked PR (see run_if_changed below; fixed by https://github.com/kubernetes/test-infra/pull/4586) https://github.com/kubernetes/test-infra/blob/b4a4bd5a8c4f15c9cd4d40a371edf8242663e140/prow/config.yaml#L93-L98 Also, it was never meant to report (skip_report: true). Maybe https://github.com/kubernetes/test-infra/pull/4563 was deployed in the meantime?

+1
0xmichalis on Sep 20, 2017
Read more comments on GitHub
← test-infra: [SQ-blocking] DumpClusterLogs failing in federation presubmit
test-infra: Test cluster `default` reports `unauthorized` error →