jangala-dev / jangala-dev/devicecode-lua

Cap SDK tests fail

Open
#326 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Lua
Stars
1
Forks
0
Avg merge
6d 8h
Merged PRs (30d)
6

Description

Failure summary:
- unit.hal.sdk_cap_spec :: cap_sdk_curated_listener_accepts_available_status_payload [0.001s]
./unit/hal/sdk_cap_spec.lua:60: attempt to call method 'wait_for_cap' (a nil value)
- unit.hal.sdk_cap_spec :: cap_sdk_curated_listener_accepts_available_true_payload [0.002s]
./unit/hal/sdk_cap_spec.lua:88: attempt to call method 'wait_for_cap' (a nil value)
- unit.hal.sdk_cap_spec :: cap_sdk_curated_listener_ignores_removed_status_payload [0.001s]
./unit/hal/sdk_cap_spec.lua:116: attempt to call method 'wait_for_cap' (a nil value)
- unit.hal.sdk_cap_spec :: cap_sdk_raw_host_listener_and_ref_follow_raw_host_topics [0.003s]
./unit/hal/sdk_cap_spec.lua:146: attempt to call method 'wait_for_cap' (a nil value)
- unit.hal.sdk_cap_spec :: cap_sdk_raw_member_listener_and_ref_follow_raw_member_topics [0.003s]
./unit/hal/sdk_cap_spec.lua:220: attempt to call method 'wait_for_cap' (a nil value)
- unit.update.test_active_policy :: test_artifact_missing_stage_resume_moves_mcu_job_to_reconcile [0.000s]
./unit/update/test_active_policy.lua:7: expected awaiting_return, got staging
- unit.update.test_active_policy :: test_artifact_missing_stage_resume_without_identity_still_fails [0.000s]
./unit/update/test_active_policy.lua:7: expected failed, got staging
make: *** [Makefile:93: test] Error 1

Contributor guide

No contributing guide indexed for this repository

Research direction

Run make test and start with unit/hal/sdk_cap_spec.lua and unit/update/test_active_policy.lua, focusing on the listed failures: the missing wait_for_cap method and the unexpected staging states. Trace those test expectations to the relevant implementation, then rerun the affected tests and make test; done means all listed failures pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua
Domain
embedded-iot, testing
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.