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

Fix an error that occurred in e2e-nightly #519

Open
Mdaiki0730 opened this issue Dec 2, 2022 · 0 comments
Open

Fix an error that occurred in e2e-nightly #519

Mdaiki0730 opened this issue Dec 2, 2022 · 0 comments
Labels
C: bug Classification: Something isn't working Stale For github bot

Comments

@Mdaiki0730
Copy link
Member

Ostracon version (use ostracon version or git rev-parse --verify HEAD if installed from source):
latest

ABCI app (name for built-in, URL for self-written if it's publicly available):

Environment:

  • OS (e.g. from /etc/os-release):
  • Install tools:
  • Others:

What happened:
It looks like we haven't passed the e2e-nightly workflow for the past year and a half.

After investigating the cause, it seems that docker build fails with the following error.

...
Step 15/35 : ARG LIBSODIUM_OS=${SRCDIR}/${VRF_ROOT}/sodium/linux_amd64
 ---> Running in 0f96aec6faed
Removing intermediate container 0f96aec6faed
 ---> 7e71f8113496
Step 16/35 : COPY ${LIBSODIUM_ROOT} ${LIBSODIUM_ROOT}
 ---> a65d705ea42e
Step 17/35 : RUN cd ${LIBSODIUM_ROOT} &&     ./autogen.sh &&     ./configure --disable-shared --prefix="${LIBSODIUM_OS}" &&     make &&     make install
 ---> Running in 5806b3c1511a
/bin/sh: 1: ./autogen.sh: not found

I fixed this in feat/fix-e2e-nightly, but the error still occurs.

...
Step 21/35 : ENV LIBSODIUM 1
 ---> Running in fc8b5f28763b
Removing intermediate container fc8b5f28763b
 ---> 7e74b7a2b844
Step 22/35 : COPY go.mod go.sum ${SRCDIR}
When using COPY with more than one source file, the destination must be a directory and end with a /

Even if you fix this, more errors may occur.

I think that it is necessary to consider once whether the above should be corrected.
Because it's a test that won't be noticed even if it fails for a long time.

What you expected to happen:

Have you tried the latest version: yes/no
yes

How to reproduce it (as minimally and precisely as possible):

Logs (paste a small part showing an error (< 10 lines) or link a pastebin, gist, etc. containing more of the log file):
https://github.com/line/ostracon/actions/runs/3598975246/jobs/6062202782
https://github.com/line/ostracon/actions/runs/3599098047/jobs/6062433166

Config (you can paste only the changes you've made):

node command runtime flags:

Please provide the output from the http://<ip>:<port>/dump_consensus_state RPC endpoint for consensus bugs

Anything else we need to know:

@Mdaiki0730 Mdaiki0730 added the C: bug Classification: Something isn't working label Dec 2, 2022
@github-actions github-actions bot added the Stale For github bot label Dec 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: bug Classification: Something isn't working Stale For github bot
Projects
None yet
Development

No branches or pull requests

1 participant