-
Notifications
You must be signed in to change notification settings - Fork 367
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
Fix export test esti job #7635
Fix export test esti job #7635
Conversation
de1ce22
to
d770136
Compare
d770136
to
2e15b4c
Compare
depends_on: | ||
- "lakefs" | ||
- "postgres" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not blocking on this, sharing my thoughts though:
This solves the problem, and because we run it in later steps it works to overcome the dependencies, but we regarding the docker-compose file it's wrong to remove these dependencies.
Did we try using project names?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand the concern, however:
- I feel like we should not invest more time on this since this provides a good enough solution
- Lets address this when this actually becomes painful
run_cmd_and_validate() { | ||
echo $1 | ||
echo "Running: $2" | ||
newVariable=$(eval $2) | ||
if [[ $? != "0" ]] | ||
then | ||
echo "FAILED!" && exit 1 | ||
fi | ||
echo "Output:" | ||
echo $newVariable | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like 😎
Closes #7628
The main issue was the dependencies in the container configuration that resulted in another lakeFS instance being brought up and which caused some weird collision.
In addition, added prints and status code checks