Skip to content

Conversation

@aslonnie
Copy link
Collaborator

@aslonnie aslonnie commented Oct 8, 2025

cherypick #57273

The image_embedding_from_jsonl_fixed_size_chaos release test runs a large image embedding workload with a preemption every minute. Since this test features long-running tasks and frequent preemptions, it's expected to time out (it's not a regression). So, this PR changes the frequency to manual.

… frequency

cherypick #57273

Signed-off-by: Lonnie Liu <lonnie@anyscale.com>
@aslonnie aslonnie merged commit bf7133e into releases/2.50.0 Oct 8, 2025
3 of 5 checks passed
@aslonnie aslonnie deleted the lonnie-2500-cp2 branch October 8, 2025 05:56
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

Thank you for this contribution. The change to disable the image_embedding_from_jsonl_fixed_size_chaos test by setting its frequency to manual is well-justified, given that it's expected to time out. I have one suggestion to improve the maintainability of the YAML configuration by reducing redundancy. Please see my detailed comment.


- name: image_embedding_from_jsonl_{{case}}
frequency: weekly
frequency: "{{frequency}}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To reduce redundancy and improve maintainability, consider using a default value for frequency. If the templating engine supports Jinja2-style filters, you can use the default filter here.

This would make weekly the default frequency, allowing you to remove the explicit frequency: weekly declarations on lines 582 and 587 for the fixed_size and autoscaling cases. The configuration becomes cleaner as you only need to specify the frequency when it deviates from the default.

  frequency: "{{ frequency | default('weekly') }}"

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.

2 participants