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

Run functional tests for both historic and non-historic versions #1693

Closed
dimalit opened this issue Oct 16, 2023 · 1 comment · Fixed by #1788, #1799 or #1801
Closed

Run functional tests for both historic and non-historic versions #1693

dimalit opened this issue Oct 16, 2023 · 1 comment · Fixed by #1788, #1799 or #1801
Assignees
Milestone

Comments

@dimalit
Copy link
Contributor

dimalit commented Oct 16, 2023

Currently, after "Build and publish skaled container" we run "functional tests" for this container. So happened, that we run these tests for -historic container only. Need to run them both for historic and non-historic containers.

@DmytroNazarenko DmytroNazarenko added this to the SKALE 2.3 milestone Oct 16, 2023
@PolinaKiporenko PolinaKiporenko moved this from To Do to Ready For Pickup in SKALE Engineering 🚀 Oct 27, 2023
@DmytroNazarenko DmytroNazarenko moved this from Ready For Pickup to To Do in SKALE Engineering 🚀 Dec 11, 2023
@dimalit dimalit moved this from To Do to In Progress in SKALE Engineering 🚀 Jan 17, 2024
@dimalit dimalit linked a pull request Jan 19, 2024 that will close this issue
@DmytroNazarenko DmytroNazarenko moved this from In Progress to Code Review in SKALE Engineering 🚀 Jan 19, 2024
@github-project-automation github-project-automation bot moved this from Code Review to Ready For Release Candidate in SKALE Engineering 🚀 Jan 19, 2024
@DmytroNazarenko
Copy link
Collaborator

skaled: 3.18.0-beta.0

@DmytroNazarenko DmytroNazarenko moved this from Ready For Release Candidate to Done in SKALE Engineering 🚀 Jan 23, 2024
@dimalit dimalit linked a pull request Jan 23, 2024 that will close this issue
@DmytroNazarenko DmytroNazarenko linked a pull request Jan 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment