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

CI test failled (Temporary failure in name resolution) #108

Open
Sispheor opened this issue Oct 4, 2022 · 2 comments
Open

CI test failled (Temporary failure in name resolution) #108

Sispheor opened this issue Oct 4, 2022 · 2 comments

Comments

@Sispheor
Copy link

Sispheor commented Oct 4, 2022

Error:

requests.exceptions.ConnectionError: HTTPConnectionPool(host='placeholder_hostname', port=80): Max retries exceeded with url: /api/v2/users/?page_size=25&username__iexact=workflow_normal (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f5dc5fe9250>: Failed to establish a new connection: [Errno -3] Temporary failure in name resolution'))

The 'placeholder_hostname' seems to be a string.
Need to be added to /etc/hosts?
Need to be transformed with a sed command before executing?

What was the idea? :)
How can we help.

@costastf
Copy link
Collaborator

costastf commented Oct 4, 2022

The idea is that under tests/fixtures/ there is a docker-compose.yml that sets up a full stack with a local directory mounted for the postgres backend and all the tests run towards that exposed service. So that service needs to be up before you execute the tests which is done by sourcing the setup_aliases.(sh|ps1 depending on your platform) and running _test. The problem is that the that stack no longer works and I do not have docker any more due to licensing. So we need to come up with a way to have that stack fully functional so the tests can run as indended and probably update the instances to something more recent. Any help there is appreciated. I will als try to find some time to look into this.

@costastf
Copy link
Collaborator

costastf commented Oct 4, 2022

I have looked into setting up the latest suggested stack, still not fully done. I will post updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants