Hi all,

This is provide an update of where I'm at with the overnight tests:

I have a PR up at https://github.com/cs-shadow/buildstream/pull/142

This basically provides a docker-compose approach for tackling all tests, not 
just the overnight ones. I found this allowed for separation of configuration 
into hopefully logical sections (docker run commands in the docker-compose, 
build time container configuration in the dockerfile, top level parameters in 
the github workflow). 

This allows then flexible use of matrices to define the jobs.

Work that I think still needs to be done:

- Translation of gitlab cache -> github cache

- Setting up self-hosted runners. I think we will need this for the overnight 
tests to run successfully as I think on gitlab these take several hours to run 
on 8 vCPU machines to build the entirety of freedesktop-sdk. The github 
provided ones are 2vCPU with a time limit of 6 hours.

- Moving the overnight tests into its own workflow with a different trigger. 
This may require moving the pattern of invoking the docker-compose file into 
its own custom action so it can be reused by different workflows. Afaict you 
can't have multiple jobs within a single workflow operate off different 
triggers like you can with gitlab, although happy to be wrong in that assertion!

Reviews and comments welcome!

Many thanks

Chris


Reply via email to