Skip to content
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.

fix: Add output of failed events to logs #249

Merged
merged 3 commits into from
May 17, 2022

Conversation

christian-kreuzberger-dtx
Copy link
Contributor

@christian-kreuzberger-dtx christian-kreuzberger-dtx commented May 16, 2022

Disclaimer: Thanks to the code provided by @Raffy23 in PR #229

Fixes #234 by providing an appropriate error message

image

Unfortunately, we cannot easily fix #235, as it would require us to delete jobs (which we shouldn't do at the moment). I would dedicate the fix of #235 to the refactoring ticket of #244

@github-actions
Copy link
Contributor

github-actions bot commented May 16, 2022

Unit Test Results

    1 files    13 suites   2s ⏱️
115 tests 108 ✔️ 7 💤 0

Results for commit 4623907.

♻️ This comment has been updated with latest results.

@Raffy23
Copy link
Member

Raffy23 commented May 16, 2022

Shouldn't we also implement a basic unit test for GetFailedEventsForJob?

Signed-off-by: Christian Kreuzberger <[email protected]>
Signed-off-by: Christian Kreuzberger <[email protected]>
Signed-off-by: Christian Kreuzberger <[email protected]>
@christian-kreuzberger-dtx
Copy link
Contributor Author

Added two unit tests and rebased main branch

@github-actions
Copy link
Contributor

The following Docker Images have been built:

  • keptncontrib/job-executor-service:0.2.1-dev-PR-249,keptncontrib/job-executor-service:0.2.1-dev-PR-249.202205171052
  • keptncontrib/job-executor-service-initcontainer:0.2.1-dev-PR-249,keptncontrib/job-executor-service-initcontainer:0.2.1-dev-PR-249.202205171052

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Job that cannot start pod -> orphaned Specifying non-existing Service Account leads to job not starting
2 participants