-
Notifications
You must be signed in to change notification settings - Fork 20
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
Turn on basic testing #23
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I _wanted_ to turn on the automated tests that we have, but it fails because pytest is not installed. @couryrr-afs can you please fix the automated tests so we can include them as well. <details> <summary>Existing automated e2e tests fail</summary> ``` $ bash demo-automated-testing.sh [+] Building 0.0s (0/0) docker:desktop-linux [+] Running 2/0 ✔ Container everest-ac-demo-mqtt-server-1 Created 0.0s ✔ Container everest-ac-demo-manager-1 Created 0.0s Attaching to everest-ac-demo-manager-1, everest-ac-demo-mqtt-server-1 everest-ac-demo-mqtt-server-1 | 1710048535: mosquitto version 2.0.10 starting everest-ac-demo-mqtt-server-1 | 1710048535: Config loaded from /mosquitto/config/mosquitto.conf. everest-ac-demo-mqtt-server-1 | 1710048535: Opening ipv4 listen socket on port 1883. everest-ac-demo-mqtt-server-1 | 1710048535: Opening websockets listen socket on port 9001. everest-ac-demo-mqtt-server-1 | 1710048535: mosquitto version 2.0.10 running everest-ac-demo-manager-1 | ./run-test.sh: line 3: pytest: not found everest-ac-demo-manager-1 exited with code 127 ``` </details> Signed-off-by: Shankari <[email protected]>
shankari
force-pushed
the
turn_on_basic_testing
branch
from
March 10, 2024 05:34
44576f5
to
7d44a4f
Compare
Signed-off-by: Shankari <[email protected]>
When we have true automated tests, we will not need this, but the scripts all currently run without -d and expect UI interaction, so we will timeout. Note that this means that the action will always be canceled, but not much we can do to avoid that now. Signed-off-by: Shankari <[email protected]>
When we have true automated tests, we will not need this, but the scripts all currently run without -d and expect UI interaction, so we will timeout. Note that this means that the action will always be canceled, but not much we can do to avoid that now. Signed-off-by: Shankari <[email protected]>
…erest-demo into turn_on_basic_testing
Signed-off-by: Shankari <[email protected]>
To be as close to the laptop environment as possible
Since 10 minutes is too short for OSX ``` c9a245e33d92 Extracting [=================> ] 357.1MB/1.048GB c9a245e33d92 Extracting [=================> ] 357.6MB/1.048GB c9a245e33d92 Extracting [=================> ] 358.2MB/1.048GB c9a245e33d92 Extracting [=================> ] 358.7MB/1.048GB c9a245e33d92 Extracting [=================> ] 359.3MB/1.048GB Error: The action 'Download and launch' has timed out after 10 minutes. ```
Download takes 20 mins Build should take another 10 mins
Signed-off-by: Shankari <[email protected]>
Signed-off-by: Shankari <[email protected]>
Although the error is likely because we are trying to mount a directory outside $HOME and /tmp/colima
Marking this PR as a draft to avoid confusion. I am not really committed to working on it, and there should not be any expectations around when/if it will ever be ready for prime time. |
Closing it completely to avoid even more confusion |
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jun 20, 2024
Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo -----
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jun 23, 2024
Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo ----- Signed-off-by: Mahadik, Mukul Chandrakant <[email protected]>
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jul 3, 2024
Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo ----- Signed-off-by: Mahadik, Mukul Chandrakant <[email protected]>
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jul 3, 2024
------ Created e2etest.yaml Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo -----
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jul 3, 2024
Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo ----- Signed-off-by: Mahadik, Mukul Chandrakant <[email protected]>
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jul 3, 2024
------ Created e2etest.yaml Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo ----- Signed-off-by: Mahadik, Mukul Chandrakant <[email protected]>
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jul 16, 2024
Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo ----- Signed-off-by: Mahadik, Mukul Chandrakant <[email protected]>
MukuFlash03
pushed a commit
to MukuFlash03/everest-demo
that referenced
this pull request
Jul 16, 2024
------ Created e2etest.yaml Used the existing file template from this PR: EVerest#23 -------- Currently testing only with ubuntu-latest OS. The demo scripts used are: - demo-automated-testing.sh I have commented out the existing /demo-iso15118-2-ac-plus-ocpp201.sh since as per the Readme.md it requires arguments to be passed and I am unsure which set of arguments need to be passed for the purpose of the workflow. https://github.com/EVerest/everest-demo#step-1-run-the-demo ----- Signed-off-by: Mahadik, Mukul Chandrakant <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I wanted to turn on the automated tests that we have, but it fails because pytest is not installed. @couryrr-afs can you please fix the automated tests so we can include them as well.
Existing automated e2e tests fail