test: cleanup relevant devices after each test

[reubenmiller]

Proposed changes

Update robotframework-devicelibrary to 1.25.0. The new version cleans up relevant devices after each test rather than at the end of a suite.

This is in an effort to reduce the amount of resources (i.e. running containers) during the system tests.

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
• Documentation Update (if none of the other choices apply)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA (in all commits with git commit -s. You can activate automatic signing by running just prepare-dev once)
• I ran just format as mentioned in CODING_GUIDELINES
• I used just check as mentioned in CODING_GUIDELINES
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

Further comments

[github-actions]

Robot Results

✅ Passed	❌ Failed	⏭️ Skipped	Total	Pass %	⏱️ Duration
812	31	3	843	96.32	2h46m18.397985s

Failed Tests

Name	Message	⏱️ Duration	Suite
Check PID number in lock file after restarting the services	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	2.042 s	Lock File
Switch off lock file creation	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	2.218 s	Lock File
Heartbeat is sent	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	18.674 s	Heartbeat
Heartbeat is sent based on the custom health topic status	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	49.733 s	Heartbeat
Default plugin configuration	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	10.107 s	Configuration Operation
Default plugin configuration	rm /etc/tedge/plugins/tedge-lo... returned an unexpected exit code stdout: stderr: rm: cannot remove '/etc/tedge/plugins/tedge-log-plugin.toml': No such file or directory [RETRY] FAIL on 3. retry.	33.413 s	Log Operation
Reporting sudo misconfiguration	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	23.098 s	Log Operation Plugins
Mapper recovers and processes output of ongoing software update request	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	3.870 s	Recover And Publish Software Update Message
Recovery from corrupt entity store file	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	2.244 s	Recover And Publish Software Update Message
Processes many devices	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	16.013 s	Processes Many Devices
Register tedge-agent when tedge-mapper-c8y is not running #2389	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	18.333 s	Registration Lifecycle
Test if all c8y services are up	Several failures occurred: 1) Keyword with same name defined multiple times. 2) Keyword with same name defined multiple times. 3) Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	20.097 s	Service Monitoring
Test if all c8y services are down	Several failures occurred: 1) Keyword with same name defined multiple times. 2) Keyword with same name defined multiple times. 3) Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	25.097 s	Service Monitoring
Check health status of tedge-mapper-c8y service on broker stop start	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	16.227 s	Service Monitoring
tedge-agent should terminate on SIGINT while downloading file	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	21.771 s	Software
Operation gets updated regardless of the order of the creation time	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	19.976 s	Software
Create and publish the tedge agent supported operations on mapper restart	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	21.044 s	Mapper-Publishing-Agent-Supported-Ops
Check retained alarms	Several failures occurred: 1) Keyword with same name defined multiple times. 2) Keyword with same name defined multiple times. 3) Keyword with same name defined multiple times. 4) Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	15.859 s	Raise Alarms
thin-edge components support a custom config-dir location via flags	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.331 s	Config Dir
thin-edge components support a custom config-dir location via an environment variable	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.368 s	Config Dir
Ignore env variable by using an empty value	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.343 s	Config Dir
Check existence of init directories	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.365 s	Tedge Init
Tedge init and check creation of folders	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.348 s	Tedge Init
Check ownership of the folders	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.346 s	Tedge Init
Change user/group and check the change	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.350 s	Tedge Init
Tedge init and check if default values are restored	Parent suite setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	0.436 s	Tedge Init
Support starting and stopping services	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	14.692 s	Service-Control
Publish event whilst mapper is down	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	22.044 s	Offline Publishing
Check remote mqtt broker #1773	Setup failed: Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	21.945 s	Remote Mqtt Broker
On start process all the pending operations	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	19.174 s	Main Tedge Agent
Resume On Restart A Pending Operation Which Workflow Is Deprecated	Keyword with same name defined multiple times. [RETRY] FAIL on 3. retry.	31.637 s	Dynamic Workflow Reloading

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.