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

TST Mark flaky X-LoRA test as xfail #2114

Conversation

BenjaminBossan
Copy link
Member

Currently, CI is failing constantly because one of the X-LoRA tests has become flaky lately, most likely caused by the transformers 4.45.0 release. Therefore, this test is now marked to non-strictly xfail.

One example of the time of writing:

https://github.com/huggingface/peft/actions/runs/11104075939/job/30847479626?pr=2113

I cannot reproduce this error locally, neither on CPU nor GPU. It is thus unclear how to fix this test.

Currently, CI is failing constantly because one of the X-LoRA tests has
become flaky lately, most likely caused by the transformers 4.45.0
release. Therefore, this test is now marked to non-strictly xfail.

I cannot reproduce this error locally, neither on CPU nor GPU. It is
thus unclear how to fix this test.
@HuggingFaceDocBuilderDev

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

Copy link
Member

@EricLBuehler EricLBuehler left a comment

Choose a reason for hiding this comment

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

Looks good!

@BenjaminBossan BenjaminBossan merged commit 534d361 into huggingface:main Oct 2, 2024
14 checks passed
@BenjaminBossan BenjaminBossan deleted the tst-mark-flaky-xlora-test-as-xfail branch October 2, 2024 16:31
BenjaminBossan added a commit to BenjaminBossan/peft that referenced this pull request Oct 22, 2024
Currently, CI is failing constantly because one of the X-LoRA tests has
become flaky lately, most likely caused by the transformers 4.45.0
release. Therefore, this test is now marked to non-strictly xfail.

I cannot reproduce this error locally, neither on CPU nor GPU. It is
thus unclear how to fix this test.
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.

3 participants