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

[Bug] dataprep test run fail on Xeon #931

Open
2 of 6 tasks
ZePan110 opened this issue Nov 21, 2024 · 6 comments
Open
2 of 6 tasks

[Bug] dataprep test run fail on Xeon #931

ZePan110 opened this issue Nov 21, 2024 · 6 comments

Comments

@ZePan110
Copy link
Collaborator

ZePan110 commented Nov 21, 2024

Priority

P1-Stopper

OS type

Ubuntu

Hardware type

Xeon-SPR

Installation method

  • Pull docker images from hub.docker.com
  • Build docker images from source

Deploy method

  • Docker compose
  • Docker
  • Kubernetes
  • Helm

Running nodes

Single Node

Description

dataprep/test_dataprep_multimodal_redis_langchain.sh and dataprep/test_dataprep_multimedia.sh test fail.
log link:
dataprep/test_dataprep_multimodal_redis_langchain.sh: https://github.com/opea-project/GenAIComps/actions/runs/11929971908/job/33250378694
dataprep/test_dataprep_multimedia.sh: https://github.com/opea-project/GenAIComps/actions/runs/11929971908/job/33250379480
In addition, test_dataprep_multimedia.sh has port conflicts (9099). The DOCKER_NAME name in validate_microservices() is inconsistent before and after.
After modifying 9099 to 5045 and correcting DOCKER-NAME, the local test log error is consistent with test_dataprep_multimodal_redis_langchain.sh.
image

@ZePan110 ZePan110 changed the title [Feature] dataprep test run fail [Bug] dataprep test run fail Nov 21, 2024
@ZePan110 ZePan110 changed the title [Bug] dataprep test run fail [Bug] dataprep test run fail on Xeon Nov 21, 2024
@ZePan110
Copy link
Collaborator Author

@tileintel @MSCetin37 could you please take a look at this issue?

@MSCetin37
Copy link
Contributor

MSCetin37 commented Nov 21, 2024

Since we don't track the versions of the libraries in the requirements file and moviepy 2.0.0 was released on November 19, 2024, this created the issue. I will fix this issue. However, if we don't specify versions in the requirements file, it will create version conflict problems similar to this one in OPEA

@tileintel
Copy link
Contributor

tileintel commented Nov 21, 2024

I have checked the previous release. It is moviepy==1.0.3. Would you like to fix the source code to adapt the latest released moviepy library? Or would you like to update the docker file to install the correct version moviepy==1.0.3? Please let me know.
@ZePan110 @MSCetin37

@MSCetin37
Copy link
Contributor

@tileintel, we are working on it.

@ZePan110
Copy link
Collaborator Author

@tileintel @MSCetin37 Thank you for your reply. I added some comments in the PR

@ZePan110
Copy link
Collaborator Author

This issue is fixed by #942
CD test pass, log link: https://github.com/opea-project/GenAIComps/actions/runs/12002252809
So close this issue.

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

No branches or pull requests

3 participants