test: fix ci image/avatar test error

[warmthsea]

dev: test

Edit Before: dev test*70 ✅

Edit After: Same Edit Before ✅

github ci: test

Edit before: probabilistic occurrence (Is the node version affected?) ❗

#16860 (comment)

Edit After:

✅

[pull-request-triage]

👋 @warmthsea, thank you for contributing element-plus.

• You can comment with /label Components:[component_name] to add a label for which component you are working on.
• You may join our for staying tuned.

[github-actions]

[github-actions]

Hello @warmthsea, thank you for contributing to element-plus, please see our guideline to see how to make contribution

[github-actions]

🧪 Playground Preview: https://element-plus.run/?pr=16863
Please comment the example via this playground if needed.

[warmthsea]

@btea
Please ask a question, how can I execute ci unit-test again without changing the code?

[warmthsea]

new test error avatar

[btea]

@btea Please ask a question, how can I execute ci unit-test again without changing the code?

Generally, it will only be run when the code is updated, or the project team members can help click re-run.
Regarding the test case you modified, it sometimes fails, but it should be related to the environment, so there is no need to modify it, just rerun it.

[warmthsea]

I only changed the test errors that I encountered with a high probability. (CI)

[btea]

I ran several tests and everything seemed to be normal. We can merge this PR first and see if there will be no errors in the future.

[warmthsea]

I ran several tests and everything seemed to be normal. We can merge this PR first and see if there will be no errors in the future.

I added 25 duplicate CIs for testing, and 1 or 2 errors occurred each time.

[btea]

I looked at some of the error conditions, and it seems that they are not a problem with the use case, but an internal problem with jsdom. This random situation can be ignored.

[warmthsea]

I looked at some of the error conditions, and it seems that they are not a problem with the use case, but an internal problem with jsdom. This random situation can be ignored.

OK.