Fixes #892

Describe the changes you have made in this PR -

Two changes were made in app/services/tracer_client/aws_batch_jobs.py:

1. Timezone fix: datetime.fromtimestamp() now uses tz=UTC explicitly. Without this, AWS Batch timestamp conversion depended on the local timezone, causing tests to fail in CI (which runs with TZ=UTC).

2. 14 unit tests in tests/services/tracer_client/test_aws_batch_jobs.py:

   • TestNoTraceId (2 tests): behavior when no trace_id is passed, both in typed and raw dict modes.
   • TestStatusFilter (3 tests): default values (SUCCEEDED, FAILED, RUNNING), custom filters, and endpoint verification.
   • TestTypedReturnMode (9 tests): job parsing, extracted fields (vcpu, memory, gpu, exit_code, failure_reason), failed/succeeded counts, failure reason extraction from first failed job, timestamp conversion, and empty data or unsuccessful response cases.
   • TestRawReturnMode (1 test): return_dict=True returns the raw response without parsing.

Tests use _FakeBatchJobsClient and _FakeBatchJobsClientWithCapture which stub _get(), with no real HTTP calls.

Demo/Screenshot for feature changes and bug fixes -

# Local (CEST)
uv run python -m pytest tests/services/tracer_client/test_aws_batch_jobs.py -v
# 14 passed

# CI simulation (UTC)
env TZ=UTC uv run python -m pytest tests/services/tracer_client/test_aws_batch_jobs.py -v
# 14 passed

Code Understanding and AI Usage

Did you use AI assistance (ChatGPT, Claude, Copilot, etc.) to write any part of this code?

• Yes, I used AI assistance (continue below)

If you used AI assistance:

• I have reviewed every single line of the AI-generated code
• I can explain the purpose and logic of each function/component I added
• I have tested edge cases and understand how the code handles them
• I have modified the AI output to follow this project's coding standards and conventions

Explain your implementation approach:

• What problem does your code solve? Adds unit test coverage for AWSBatchJobsMixin.get_batch_jobs() which had none, and fixes a timezone bug in timestamp conversion that would cause tests to fail in CI.

• What alternative approaches did you consider? I could have used pytest-mock or unittest.mock, but following the existing pattern in test_tracer_pipelines.py, a fake subclass that stubs _get() is simpler and more idiomatic.

• Why did you choose this specific implementation? The fake subclass pattern is already established in the codebase (see test_tracer_pipelines.py). It keeps tests readable and avoids complex mock setup.

• What are the key functions/components and what do they do?

  • _FakeBatchJobsClient — returns a configurable response from _get(), used for testing return value parsing.
  • _FakeBatchJobsClientWithCapture — captures the endpoint and params passed to _get(), used for verifying API calls.
  • TestNoTraceId — verifies early return behavior when no trace_id is provided (both typed and raw modes).
  • TestStatusFilter — verifies default and custom status filters are passed correctly to the API params.
  • TestTypedReturnMode — verifies AWSBatchJobResult parsing: job fields, failure reason extraction, timestamp conversion, counts.
  • TestRawReturnMode — verifies return_dict=True returns the raw API response unchanged.
  • Timezone fix in aws_batch_jobs.py — uses tz=UTC in datetime.fromtimestamp() so the conversion is deterministic regardless of the local timezone.

Checklist before requesting a review

• I have added proper PR title and linked to the issue
• I have performed a self-review of my code
• I can explain the purpose of every function, class, and logic block I added
• I understand why my changes work and have tested them thoroughly
• I have considered potential edge cases and how my code handles them
• If it is a core feature, I have added thorough tests
• My code follows the project's style guidelines and conventions

Note: Please check Allow edits from maintainers if you would like us to assist in the PR.