LPC LOC Test suite flakiness

[uncleDecart]

This is a tracker to collect all failed LPC LOC test Suite runs in GitHub Actions.

How to contribute?

If you see any failure in GitHub actions runs, please add it to this table.

How to find eden version?

Open workflow file of the run and see which eden tag is invoked, like here it is 0.9.3.

How to find EVE version?

In setup-job of workflow which failed find eve image parameter which in inputs. For example, here it is evebuild/pr:3698. In case if it contains evebuild/pr put PR in it.

Link to run	Eden version	EVE version	test
1	0.9.5	PR	profile
2	master	11.7.0	profile

How to run suite locally

Clean previous build and add default config with debug level of printing

make clean && make build-tests
./eden config add default
./eden config set default --key eve.log-level --value debug

(optional) set EVE tag to a version you're testing

./eden config set default --key eve.tag --value 11.3.0

Setup and run a test

./eden setup
./dist/bin/eden+ports.sh 2223:2223
./eden start
./eden eve onboard
./eden test ./tests/workflow -s lpc-loc.tests.txt -v debug

[uncleDecart]

@eriknordmark I'm copying your comment so there will be no duplicate issue

A recent run https://github.com/lf-edge/eve/actions/runs/7806282543/job/21310964084?pr=3742 shows the LOC test suite failing to deploy an app instance due to insufficient memory.
Can we easily increase the memory for the virtual device?

[uncleDecart]

Stabilised. Will open new one if something occurs again