[CI][Bugfix] Fix bad tolerance for test_batch_base64_embedding

[mgoin]

Previously the test was doing equality on float values, which is always a bad idea. See an example of flaky test https://buildkite.com/vllm/fastcheck/builds/19776/steps?jid=0196126c-0cdf-4b29-9363-d925adaf681a#0196126c-0cdf-4b29-9363-d925adaf681a/6-13621

This PR changes it to use allclose

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.

💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels.

Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can either: Add ready label to the PR or enable auto-merge.

🚀

[ywang96]

Thank you for the fix 🙏 !

[DarkLight1337]

Seems that the default tolerance isn't quite enough. Does this issue appear when we use V0?

[hmellor]

LGTM

[mgoin]

Does this issue appear when we use V0?

I think embedding doesn't work on V1 yet, so this should be V0

[maxdebayser]

I faced the same problem in my PR #16188

I used the check_embeddings_close function from models.embedding.utils. That function uses cosine similarity, but I think allclose should be fine as well.