Archivist can't resolve memory_monitor from universe?

[Shai Barack]

Hi folks,

This change attempts to migrate memory_monitor to CFv2:

https://fuchsia-review.googlesource.com/c/fuchsia/+/533901

I'm running into some failures:

https://ci.chromium.org/ui/p/fuchsia/builders/try/core.x64-release/b8844573855284275056/overview

I'm seeing this:

[component_manager] ERROR: Failed to route protocol `fuchsia.sys.internal.ComponentEventProvider` with target component `/bootstrap:0/archivist:0`: failed to resolve "fuchsia-pkg://fuchsia.com/memory_monitor#meta/memory_monitor.cm": failed to route resolver capability: Routing error: Failed to resolve `/core:0/universe-resolver:0`: failed to resolve "fuchsia-pkg://fuchsia.com/universe-resolver#meta/universe-resolver.cm": package not found: remote resolver responded with PackageNotFound

Huh? Is this because memory_monitor is in universe but Archivist is in bootstrap where only base resolver is present? Any ideas what's going on?

Appreciate a hand because I'm stumped. Thanks!

[Adam Lesinski]

I had this problem before and it is due to the "eager" startup mode: https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=70883

There is some sort of cycle happening, but this was (or I thought it was) due to universe resolver depending on pkg-resolver, which was in appmgr. With pkg-resolver, I thought the dependency on appmgr would be gone....

--
All posts must follow the Fuchsia Code of Conduct https://fuchsia.dev/fuchsia-src/CODE_OF_CONDUCT or may be removed.
---
You received this message because you are subscribed to the Google Groups "component-framework-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to component-framewo...@fuchsia.dev.
To view this discussion on the web visit https://groups.google.com/a/fuchsia.dev/d/msgid/component-framework-dev/CAK0PkCGUePJ-YGbM8XMbfzydH2Z9ggYMEpaY2H3Zd3PyCDgZsA%40mail.gmail.com.

[Shai Barack]

Confirmed Adam's theory.

Filed: https://bugs.fuchsia.dev/p/fuchsia/issues/detail?id=78801