Skip to content

feat: Enable trust remote code in CI. - #498

Open
dushyantbehl wants to merge 2 commits into
torch-spyre:mainfrom
dushyantbehl:fix-trust-remote-code
Open

feat: Enable trust remote code in CI.#498
dushyantbehl wants to merge 2 commits into
torch-spyre:mainfrom
dushyantbehl:fix-trust-remote-code

Conversation

@dushyantbehl

Copy link
Copy Markdown
Contributor

Fixes #482

Builds on top of #478 and requires #478 to be merged before this PR.

@dushyantbehl

Copy link
Copy Markdown
Contributor Author

FYI @BenjSz @arielge

Comment thread tests/model_registry.py Outdated
@BenjSz

BenjSz commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Don't forget to remove the model from the excluded.yaml list when we merge.

@BenjSz

BenjSz commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

st_backend file should also contain the handing of trust_remote_code

@BenjSz

BenjSz commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

tests/spyre/test_e2e_question_answering_compare_spyre.py
tests/spyre/test_e2e_masked_lm_compare_spyre.py
tests/spyre/test_e2e_token_classification_compare_spyre.py
tests/cpu/test_question_answering_cpu_accuracy.py
tests/cpu/test_masked_lm_cpu_accuracy.py
tests/cpu/test_token_classification_cpu_accuracy.py
tests/cpu/_seq_classification_helpers.py
tests/spyre/test_load_spyre.py
tests/_vision_helpers.py
tests/spyre/test_vlm_e2e_spyre.py
tests/spyre/test_e2e_smoke_vision_spyre.py
tests/cpu/test_vlm_e2e_cpu.py
tests/spyre/_seq_classification_helpers.py
tests/spyre/test_multicard_spyre.py
test_dspark_draft_spyre.py

You do not handle the trust_remote_code in these scripts when you call from_pretrained()

@dushyantbehl

Copy link
Copy Markdown
Contributor Author

Thanks @BenjSz let me update code and check the other files.

Comment thread tests/cpu/test_adapter_cpu_accuracy.py
Comment thread tests/model_registry.py Outdated
Comment thread tests/cpu/test_embed_cpu_accuracy.py Outdated
@dushyantbehl

Copy link
Copy Markdown
Contributor Author

@BenjSz please see the updated code and my comment on clarifying the design choice for maintaining a separate REMOTE_CODE_PATHS and let me know your thoughts.

Signed-off-by: Dushyant Behl <myselfdushyantbehl@gmail.com>
Signed-off-by: Dushyant Behl <myselfdushyantbehl@gmail.com>

@BenjSz BenjSz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

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.

Add trust_remote_code support in model_registry.py and wire it through CI tests

2 participants