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.

Sign up for GitHub

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

Jump to bottom

CI failures symptoms #672

Open
martijnbastiaan opened this issue Nov 13, 2024 · 2 comments
Open

CI failures symptoms #672

martijnbastiaan opened this issue Nov 13, 2024 · 2 comments
Labels
bug Something isn't working CI GHA or CI related

Comments

@martijnbastiaan
Copy link
Contributor

List of (USB related?) failures we've seen. Feel free to edit!
@martijnbastiaan martijnbastiaan added bug Something isn't working CI GHA or CI related labels Nov 13, 2024
@rslawson
Copy link
Collaborator

rslawson commented Nov 13, 2024 •
edited
Loading

So far in #653 I have seen all of these in the Vex RISC-V TCP test:

  1. Caught exception in receive client data
  2. Timeout in connecting to clients
  3. Caught exception in connecting to clients

@lmbollen
Copy link
Contributor

We've also seen a timeout in the picocom handshake.
At the moment the expectLine functionality consumes all input and we can't see what has been received over uart. I think #669 should adjust expectLine to return the consumed output.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working CI GHA or CI related
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martijnbastiaan @lmbollen @rslawson