Lombok support sometimes breaks and makes ~500 tests fail if the lombok test profile is enabled (as of me submitting this issue, this is currently the case). However, it breaks regularly and there's not too much we can do about that but wait until a new patch fixing lombok gets released.
In the mean time, while it's broken, it'd be helpful to have accurate reporting of whether the other tests pass without lombok enabled. It seems in the past that we've manually disabled the lombok profile on each CI job (two on Jenkins, one on GitHub CI), but I think we could do it better and in a way that doesn't require regularly reconfiguring CI. I think the easiest way to do this would be to split out the lombok test suite into a different test bundle, similar to what's been done for the syntax server tests, then create a different job that executes the lombok tests.
Lombok support sometimes breaks and makes ~500 tests fail if the lombok test profile is enabled (as of me submitting this issue, this is currently the case). However, it breaks regularly and there's not too much we can do about that but wait until a new patch fixing lombok gets released.
In the mean time, while it's broken, it'd be helpful to have accurate reporting of whether the other tests pass without lombok enabled. It seems in the past that we've manually disabled the lombok profile on each CI job (two on Jenkins, one on GitHub CI), but I think we could do it better and in a way that doesn't require regularly reconfiguring CI. I think the easiest way to do this would be to split out the lombok test suite into a different test bundle, similar to what's been done for the syntax server tests, then create a different job that executes the lombok tests.