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

Tests fail #392

Closed
elouanKeryell-Even opened this issue Jan 25, 2019 · 2 comments · Fixed by #726
Closed

Tests fail #392

elouanKeryell-Even opened this issue Jan 25, 2019 · 2 comments · Fixed by #726
Assignees
Labels
release Relative to ARLAS release process type:bug Something isn't working

Comments

@elouanKeryell-Even
Copy link
Contributor

elouanKeryell-Even commented Jan 25, 2019

./release.sh breaks on tests execution (i.e. when not using --no-tests), with following error message:

===> start arlas-server stack
Creating network "arlas_default" with the default driver
Pulling elasticsearch (docker.elastic.co/elasticsearch/elasticsearch:6)...
manifest for docker.elastic.co/elasticsearch/elasticsearch:6 not found

Detailed description

  • release.sh iterates over ELASTIC_RANGE to provide --es=<...> values for calls to ./scripts/tests-integration.sh. See here.
  • ELASTIC_RANGE is in fact not an array, but a string, whose value is forced to 6, see here.
  • This results in tests being called as follow:
./scripts/tests-integration.sh --es=6

How to reproduce

time ./release.sh --simulate --api-major-version=0 --elastic-range=6  --arlas-release=0 --arlas-dev=0  --api-minor-version=0 --api-patch-version=0 | tee release_test_logs.txt

Fix

In this line, replace ELASTIC_RANGE with ELASTIC_VERSIONS.

@elouanKeryell-Even elouanKeryell-Even added type:bug Something isn't working release Relative to ARLAS release process labels Jan 25, 2019
@elouanKeryell-Even
Copy link
Contributor Author

ping @MohamedHamouGisaia

@elouanKeryell-Even
Copy link
Contributor Author

I think I might have fixed it in branch fix/release_tests (commit
c7b8a19), but I cannot perform a full execution of release.sh to validate, because of issue #412.

@mbarbet mbarbet added this to To do in ARLAS Explore via automation Dec 2, 2019
ARLAS Explore automation moved this from To do Backend to Done Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release Relative to ARLAS release process type:bug Something isn't working
Projects
ARLAS Explore
  
Done
Development

Successfully merging a pull request may close this issue.

1 participant