Fix EVerest Testing Environment #30
Comments
|
Using the |
|
@couryrr-afs Shankari recommended reaching out to you for assistance. Do you know what might be happening? |
jhoshiko
changed the title
|
Looks like others have had issues with the |
|
@jhoshiko that looks to be a missing python dependency. I am attempting to rebuild the docker image calling |
|
Update on the status of the issue. There was a missing step for installing pytest which solves the initial problem outline here. There is a branch on the US-JOET fork that provides the needed updates couryrr/updating-dockerfile-for-testing. However, as we attempt to run the test there appears to have been a breaking change in a new release of everest. Currently, attempting to track down the breaking change. |
|
@couryrr-afs the UI-based tests are running (or will be running after I make push some changes). You might want to try replicating them in the automated tests. |
|
Just wanted to give a quick status update. To get by the pytest issue described here it was simply adding the package along with pytest-asyncio via pip. After making this change there were issues with the packages that were being pulled in via the build-kit image and what we had been building. I moved the version up for the everest tag which appears to have solved all of the pytest issue from what I can tell. Unfortunately, when testing the full process with the bash script I am running into a new issue below. I am working to track down the cause of this. |
|
@couryrr-afs have you tried any of the existing demos as a template? I am able to run most of the existing demos and certainly the scenarios being tested in these tests through the UI. The only tests that are failing are ISO 15118-2 + OCPP 201.
It would be helpful to understand what these changes were and how they are different from the script currently in the Dockerfile. I have (today morning) updated the demo images to the RC1 tag. I would suggest sticking to that tag for easier reproducibility and coordination within the community |
|
Currently we are able to install pytest so the initial reported issue was a fairly simple fix. However, we cannot successfully get the test to run at this point in the docker container. I was able to replicate the setup in the devcontainer here: https://github.com/EVerest/everest-utils/tree/main/docker/everest-playground. Inside this devcontainer we are able to successfully run the test on the 2024.3.0-rc2 tag. When moving this back over to the docker container for the test we receive a failure as outline above. There is a zulip thread here around getting more details from the manager https://lfenergy.zulipchat.com/#narrow/stream/417679-EVerest.3A-Testing-.26-CI/topic/Verbose.20Manager.20Error.20Output/near/430684671. At the moment this has been unsuccessful. At this point we are considering this blocked by this issue: EVerest/everest-framework#180 |
|
Per a comment on the issue EVerest/everest-framework#180 I have attempted to rebuild and run the container in a proper linux environment. Currently, the build process is using a high amount of resource that my system cannot sustain. I am attempting to find an alternative to verify the solution. |
|
The demo was successfully ran in docker on a PopOS host per the details here: EVerest/everest-framework#180 (comment) It appear we were communicating in multiple github issues. I will keep this one up-to-date going forward. |
|
Moving conversation for the demo work here. This is in response to EVerest/everest-framework#180 (comment)
For the issue opened here tests could not be ran because pytest was not installed. This issue was resolved with the updated The manager however was booting but then dying with a cryptic error:
A successful build of the image and running container using Docker CE was completed on:
To Reproduce
Run
|
|
Here's what I am seeing: Clone https://github.com/US-JOET/everest-demo Resulting logs: |
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When trying to run the automated testing demo, the tests fail to run because pytest is not installed:
However, after installing pytest (specifically
pytest-asyncio), the tests still fail because theeverest.testingmodule is missing:I can see that
everestpyandedm_toolare both installed, and I can import everest.The text was updated successfully, but these errors were encountered: