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

Github workflows for at_onboarding_cli #150

Merged
merged 38 commits into from
Mar 25, 2022
Merged

Conversation

srieteja
Copy link
Contributor

- What I did
adding git workflows to test at_onboarding_cli

- How I did it

- How to verify it

- Description for the changelog

@srieteja srieteja marked this pull request as draft March 23, 2022 19:51
@srieteja srieteja marked this pull request as ready for review March 24, 2022 14:47
@srieteja srieteja requested a review from cpswan March 24, 2022 19:21
@srieteja srieteja changed the title At onboarding cli Github workflows for at_onboarding_cli Mar 24, 2022
@srieteja
Copy link
Contributor Author

srieteja commented Mar 24, 2022

@cpswan both the 'check_docker_readiness' and 'check_test_env' seem to be failing. They are retrying a couple of times and then timing out after 5mins.

This is the response from ping:

Run ping -c 10 vip.ve.atsign.zone -p 64
ping -c 10 vip.ve.atsign.zone -p 64
shell: /usr/bin/bash -e {0}
env:
PUB_CACHE: /home/runner/.pub-cache
DART_HOME: /opt/hostedtoolcache/dart-sdk
PATTERN: 0x64
PING vip.ve.atsign.zone (10.64.64.64) 56(84) bytes of data.

--- vip.ve.atsign.zone ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9203ms

@cpswan
Copy link
Member

cpswan commented Mar 25, 2022

@srieteja I'm looking at this now.

One of the tests used by at_client_sdk depends on running a script against the virtual environment to load data. So I'd expect that to fail.

Do you have things working locally?

Copy link
Member

@cpswan cpswan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the echo echo is causing a bad entry to /etc/hosts, which then prevents vip.ve.atsign.zone name resolution from working as it should.

.github/workflows/at_libraries.yaml Outdated Show resolved Hide resolved
.github/workflows/at_libraries.yaml Outdated Show resolved Hide resolved
.github/workflows/at_libraries.yaml Show resolved Hide resolved
.github/workflows/at_libraries.yaml Outdated Show resolved Hide resolved
@cpswan
Copy link
Member

cpswan commented Mar 25, 2022

The logs confirm that vip.ve.atsign.zone is being resolved by DNS to 10.64.64.64 rather than hosts to 127.0.0.1:

Run ping -c 10 vip.ve.atsign.zone -p 64
  ping -c 10 vip.ve.atsign.zone -p 64
  shell: /usr/bin/bash -e {0}
  env:
    PUB_CACHE: /home/runner/.pub-cache
    DART_HOME: /opt/hostedtoolcache/dart-sdk
PATTERN: 0x64
PING vip.ve.atsign.zone (10.64.64.64) 56(84) bytes of data.

--- vip.ve.atsign.zone ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9[2](https://github.com/atsign-foundation/at_libraries/runs/5682044466?check_suite_focus=true#step:15:2)[10](https://github.com/atsign-foundation/at_libraries/runs/5682044466?check_suite_focus=true#step:15:10)ms

@srieteja srieteja requested a review from cpswan March 25, 2022 12:48
@murali-shris murali-shris merged commit f208c80 into trunk Mar 25, 2022
@srieteja srieteja deleted the at_onboarding_cli branch October 20, 2022 06:34
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

Successfully merging this pull request may close these issues.

None yet

3 participants