Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/567 metrics to identify stuck jobs #582

Closed

Conversation

Waschndolos
Copy link

Fixes #567

Changes proposed

New metrics to get "executor.isLikelyStuck();" and "job.isLogUpdated()"

Checklist

  • Includes tests covering the new functionality?
  • Ready for review
  • Follows CONTRIBUTING rules

@Waschndolos Waschndolos linked an issue Oct 25, 2023 that may be closed by this pull request
}

@Test
public void testLogIsUpdatedReturnsOne() {

Check notice

Code scanning / Pmd (reported by Codacy)

JUnit tests should include assert() or fail() Note test

JUnit tests should include assert() or fail()
}

@Test
public void testLogIsNotUpdatedReturnsZero() {

Check notice

Code scanning / Pmd (reported by Codacy)

JUnit tests should include assert() or fail() Note test

JUnit tests should include assert() or fail()


@Test
public void testBasicAttributes() {

Check notice

Code scanning / Pmd (reported by Codacy)

JUnit tests should include assert() or fail() Note test

JUnit tests should include assert() or fail()

public class NodeCollectorFactory extends BaseCollectorFactory {

public NodeCollectorFactory(){super();}

Check warning

Code scanning / Pmd (reported by Codacy)

Avoid unnecessary constructors - the compiler will generate these for you Warning

Avoid unnecessary constructors - the compiler will generate these for you
@Waschndolos Waschndolos deleted the feature/567-metrics-to-identify-stuck-jobs branch November 26, 2023 07:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant