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

test panic in logs #492

Merged
merged 1 commit into from Jan 27, 2021
Merged

test panic in logs #492

merged 1 commit into from Jan 27, 2021

Conversation

giggsoff
Copy link
Collaborator

Adds flag to fire kernel panic and wait for logs with it inside vnc_test.

Signed-off-by: Petr Fedchenkov giggsoff@gmail.com

return fmt.Errorf("SSH success. You can access it via SSH on %s:%d", externalIP, *sshPort)
}
}

//checkPanicInLog try to find panic in app log
Copy link
Contributor

Choose a reason for hiding this comment

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

Can we do a general function Check (message) in log and call it with string param (message) and move it to pkg?

Signed-off-by: Petr Fedchenkov <giggsoff@gmail.com>
@rvs
Copy link
Contributor

rvs commented Jan 27, 2021

This looks great, but I'm confused as to why does this have to do with VNC? We need these panic logs on the serial console, not VNC. What's going on @giggsoff ?

@giggsoff
Copy link
Collaborator Author

We wait for panic messages inside logs of application, not in VNC. VNC test is just the place where we have VM and we can access it via ssh, VNC and read logs/infos.

@mydatascience mydatascience merged commit 7873abb into lf-edge:master Jan 27, 2021
@giggsoff giggsoff deleted the vm-crash-test branch January 28, 2021 17:48
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