Open ArthurSens opened 3 months ago
Yup, CI is NOT running this generative script.
We only check if metrics given by the runtime is what we expect in those generated _test files and then complain with instruction to potentially rerun that script. This helps us to figure out what metrics changed across Go version. That's the main goal of those files.
You might be right some CI check that would rerun this script and point mismatch on TOP of our existing test would let us know if someone shoveled some custom manual code to those files.
Do you mind adding clear acceptance criteria to description?
This might need proper refactor e.g. have one generated set in internals and separate logic to filter those for test purposes (it's just regex)
Ideally I would also have only one script that generates both package files 🤔
Hello guys, I would like to start contributing to the project and this issue was recommend to me. Can i start working on this?
Sure thing! Is the discussion here enough for you to start working, or do you feel like you need extra guidance?
While working on https://github.com/prometheus/client_golang/pull/1559, we noticed that the generated files for the go collector can be manually changed and CI won't block the merge.
Let's investigate this and adjust :)