issues lacking CI

[plebhash]

context

there's been a lot of discussion around the need for a sustainable strategy to enforce SRI is not only compliant to specs, but also that every bugfix is accompanied by some CI that enforces that this bug doesn't manifest again

Discussion #944 started as a proposal for a new policy where every bugfix is accompanied with a Message Generator test integrated into the CI workflows

We started noticing some bottlenecks on this approach, namely:

• lack of deterministic behavior on some MG tests
• high complexity and steep learning curve for writing MG tests
• missing features on MG preventing full coverage (e.g.: New feature for the Message Generator #1059)

@jbesraa is working on a proposal for a new integration testing framework via #1066, which could potentially present an alternative strategy for CI

the best approach for CI remains to be discussed on the SRI community

during the SRI community dev call of 30/07/24, it was agreed to de-prioritize some issues to unlock the next milestone

these issues were originally conceived as adding MG tests to CI, but with the current ongoing discussions, it was agreed it's best to set them aside for a while

however, it remains critical that those issues are not forgotten, and once there's consensus on the best long-term approach for CI, they should be revisited

so this issue is actually a compilation of all issues that need to be addressed in the future in CI

issue list

bug	patch	CI tracker
#840	#868	#955
#901	#904	#923
#844	#1055	-
#1004	#1001	-