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

Investigate No modules found of kind dummy CI #5286

Closed
bradleystachurski opened this issue May 14, 2024 · 1 comment
Closed

Investigate No modules found of kind dummy CI #5286

bradleystachurski opened this issue May 14, 2024 · 1 comment
Labels
CI Continuous integration

Comments

@bradleystachurski
Copy link
Member

          review club: dpc relayed that the problem was resolved by removing the diff that caused it. We should followup with an investigation to see what we were getting the `No modules found of kind dummy` error for the mint tests.

Originally posted by @bradleystachurski in #5264 (comment)

@dpc
Copy link
Contributor

dpc commented May 24, 2024

"what we were getting"?

I'm kind of confused, but assuming this means "why"...

The test is very artificial and hacked together from different pieces. Client and federation have only one module.

The refactoring made is so federation is still down (all peers have API not started), while the test starts already executing.

In the test the Client is new, but it doesn't do a normal initialization, and gets config passed to it. So the first thing that actually runs in the initial API version discovery. That API version discovery fails, because connections to all peers fail. So it does what it seems reasonable - returns that it's unable to find version to use for all modules.

A big WARN logs are printed "Unable to discover blabhablah", "Disabling module dummy", etc. so it was immediately clear (to me) what is going on, but it does need to be immediately clear to everyone.

The test moves on, tries to get client dummy module to print some fake money, and panics because the module is not there.

The root cause is the APIs are down. Normally this would lead to client failing to get a config, but the test is hacked to skip this part. So version discovery fails loudly but doesn't really panic.

@dpc dpc closed this as completed May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous integration
Projects
None yet
Development

No branches or pull requests

2 participants