Tests that read ../../../mesh-catalog or ../../../mesh-host gave a verdict that depended on what sat beside the checkout: a stale or dirty sibling failed them on a desktop, and a missing one skipped them unseen. They now read the clone the build seat puts in MESH_CHECK_BESIDE, failing when it is absent there, and elsewhere a copy captured at a named commit. The skip had hidden that the builder test read a module retired by ADR 0190. The systemd reading test no longer counts the machine's own environment.d.
44 lines
750 B
Plaintext
44 lines
750 B
Plaintext
{
|
|
"module": "avahi",
|
|
"version": "1",
|
|
"capabilities": [
|
|
"package-manager",
|
|
"service-manager"
|
|
],
|
|
"tools": [
|
|
"avahi_status",
|
|
"avahi_browse",
|
|
"avahi_resolve",
|
|
"avahi_services"
|
|
],
|
|
"resources": [
|
|
{
|
|
"id": "package",
|
|
"type": "package",
|
|
"package": "avahi"
|
|
},
|
|
{
|
|
"id": "daemon",
|
|
"type": "service",
|
|
"unit": "avahi-daemon.service",
|
|
"state": "running",
|
|
"boot": "enabled"
|
|
}
|
|
],
|
|
"build": {
|
|
"artifacts": [
|
|
{
|
|
"name": "tools",
|
|
"kind": "bundle",
|
|
"language": "go",
|
|
"system": "arch",
|
|
"from": "cmd/avahi-tools",
|
|
"binary": "avahi-tools",
|
|
"loads": [
|
|
"avahi-tools"
|
|
]
|
|
}
|
|
]
|
|
}
|
|
}
|