Skip to content

Firmware-CI testing#245

Open
AtomicFS wants to merge 3 commits into
mainfrom
feat/add-fwci-testing
Open

Firmware-CI testing#245
AtomicFS wants to merge 3 commits into
mainfrom
feat/add-fwci-testing

Conversation

@AtomicFS
Copy link
Copy Markdown

@AtomicFS AtomicFS commented Dec 2, 2025 •
edited
Loading

I have cleaned up the commits, files and everything, and moved the more advanced stuff into another branch.

Anyway, this should be the bare minimum as requested, using the dummy modules.

At the moment the FWCI tests are failing because I suspect the dutctl does not yet contain the fix #296 (I think, not sure, @llogen did not tell me exactly which PR fixes the "missing stdout" problem).

@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch 11 times, most recently from bdf39e2 to b7360d7 Compare December 3, 2025 16:43
@jenstopp jenstopp changed the title Feat/add fwci testing Firmware-CI testing Dec 5, 2025
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch 5 times, most recently from 8efa240 to 10a2a17 Compare December 5, 2025 11:53
@AtomicFS AtomicFS changed the title Firmware-CI testing Firmware-CI testing (WIP) Mar 24, 2026
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch from 6fcc8f3 to 9fb90d0 Compare March 24, 2026 15:07
@AtomicFS AtomicFS requested a review from jenstopp March 24, 2026 15:16
@AtomicFS AtomicFS changed the title Firmware-CI testing (WIP) Firmware-CI testing Mar 24, 2026
@AtomicFS AtomicFS mentioned this pull request Mar 24, 2026
Draft
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch from 9fb90d0 to 7758e57 Compare March 24, 2026 15:45
@jenstopp
Copy link
Copy Markdown
Member

jenstopp commented Mar 25, 2026

At the moment the FWCI tests are failing because I suspect the dutctl does not yet contain the fix #296 (I think, not sure, @llogen did not tell me exactly which PR fixes the "missing stdout" problem).

I'm looking into #306. Does this describe the problem you are facing with the client app @AtomicFS ?

jenstopp
jenstopp requested changes Mar 25, 2026
View reviewed changes
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .firmwareci/dutagent.service
Comment thread .firmwareci Outdated
Comment thread .gitignore
Comment thread .gitmodules Outdated
Comment thread .goreleaser.yaml
@AtomicFS
Copy link
Copy Markdown
Author

AtomicFS commented Mar 25, 2026

At the moment the FWCI tests are failing because I suspect the dutctl does not yet contain the fix #296 (I think, not sure, @llogen did not tell me exactly which PR fixes the "missing stdout" problem).

I'm looking into #306. Does this describe the problem you are facing with the client app @AtomicFS ?

Possibly, not sure. The agent is ran from systemd service.

@jenstopp
Copy link
Copy Markdown
Member

jenstopp commented Mar 25, 2026

At the moment the FWCI tests are failing because I suspect the dutctl does not yet contain the fix #296 (I think, not sure, @llogen did not tell me exactly which PR fixes the "missing stdout" problem).

I'm looking into #306. Does this describe the problem you are facing with the client app @AtomicFS ?

Fixed with #307

@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch from 7758e57 to 04ddf2f Compare March 25, 2026 12:49
@AtomicFS
Copy link
Copy Markdown
Author

AtomicFS commented Mar 25, 2026

The FWCI is kinda funky and still tries to run the test-dutctl - Test power GPIO script test, even though it should not.

Seems like the #307 did fix the problem 🎊

@AtomicFS AtomicFS requested a review from jenstopp March 25, 2026 13:01
jenstopp
jenstopp reviewed Mar 25, 2026
View reviewed changes
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .firmwareci/dutagent.service
Comment thread .github/workflows/fwci-test.yml Outdated
Comment thread .goreleaser.yaml Outdated
Comment thread Taskfile.yml Outdated
Comment thread .firmwareci/duts/dut-rpi-fti-tester/dut.yaml Outdated
Comment thread .firmwareci/duts/dut-rpi-dutctl-tester/dut.yaml.j2
Comment thread .firmwareci/.jinja2_templates/defaults.yaml
Comment thread .firmwareci/workflows/workflow-rpi-dutctl-tester/workflow.yaml Outdated
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch from 04ddf2f to 46ff535 Compare March 26, 2026 11:01
@AtomicFS
feat: add systemd service
930dadc 
Signed-off-by: AtomicFS <vojtech.vesely@9elements.com>
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch from 46ff535 to f128eeb Compare April 16, 2026 14:03
@AtomicFS
build: add goreleaser config
9f38dca 
- goreleaser is great because we can use it to very easily build linux
  distribution packages, like a package for debian, fedora and so on
- we do not have to use goreleaser to handle the releases themselves

Signed-off-by: AtomicFS <vojtech.vesely@9elements.com>
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch from f128eeb to 35486c6 Compare April 16, 2026 14:18
@AtomicFS
ci: add fwci test
4190fc9 
- add fwci configuration files
- add CI/CD job for triggering the FWCI testing suite

Signed-off-by: AtomicFS <vojtech.vesely@9elements.com>
@AtomicFS AtomicFS force-pushed the feat/add-fwci-testing branch 2 times, most recently from 86a2278 to 4190fc9 Compare April 16, 2026 14:58
@AtomicFS AtomicFS requested a review from jenstopp April 16, 2026 14:58
@AtomicFS
Copy link
Copy Markdown
Author

AtomicFS commented Apr 16, 2026 •
edited
Loading

There are right now 2 tests failing:

  • Test Device 2 - is failing only sometimes, because the FWCI has still issues with test consistency across branches
  • Test Device 3 - failing maybe because the example config file is broken???

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jenstopp jenstopp Awaiting requested review from jenstopp

Requested changes must be addressed to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@AtomicFS @jenstopp