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

EMBA return value #372

Closed
BenediktMKuehne opened this issue Oct 28, 2022 · 4 comments · Fixed by #373
Closed

EMBA return value #372

BenediktMKuehne opened this issue Oct 28, 2022 · 4 comments · Fixed by #373
Labels
bug Something isn't working

Comments

@BenediktMKuehne
Copy link
Member

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. EMBArk installation (default mode/docker-mode)
  2. Start EMBArk: sudo ./run-server.sh
  3. Run any firmware
  4. Error:
    Report-dashboard empty

Expected behavior
Return 0 on success?

Screenshots
vmware_GCupRqt8Hm

Desktop (please complete the following information):

  • OS: Ubuntu 22XX

Additional context
0 expected-> Exception trown since it is not 0
2 options:

  1. Fix EMBA return code
  2. Ignore code in EMBArk
@BenediktMKuehne BenediktMKuehne added the bug Something isn't working label Oct 28, 2022
@BenediktMKuehne
Copy link
Member Author

BenediktMKuehne commented Oct 28, 2022

image

additionaly weird json print in emba_run.log

  1. cat emab_run.log (execute log from within boundedexec)
  2. weird output-> break -> print after return?
    Suspecting weird json character inside log

@BenediktMKuehne
Copy link
Member Author

image

@BenediktMKuehne BenediktMKuehne transferred this issue from e-m-b-a/embark Oct 28, 2022
@BenediktMKuehne
Copy link
Member Author

EMBA-Version: 1.1.2
FW: DIR-300A1_FW105b09.bin
default-scan

@m-1-k-3
Copy link
Member

m-1-k-3 commented Oct 28, 2022

wtf
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants