always will run independent of conditional testing logic?

it is more like conditional test logic will always emit the "always" tag.

before this change, it will always emit the "lint" tag, and I worry that people will just start to use "lint" to mean "always", even when the test job is not "lint"

always will run independent of conditional testing logic?

it is more like conditional test logic will always emit the "always" tag.

before this change, it will always emit the "lint" tag, and I worry that people will just start to use "lint" to mean "always", even when the test job is not "lint"

actually, this is the change that adds the "always" tag in conditional testing:
#51662

for this change, the new version ofrayci will not auto run steps that do not have "tags" (the old version treated those steps as having the "always" tag). this will make it that the default behavior for a new test job is to not run on any premerge, and people need to add a proper tag to enable proper conditional testing. test jobs with no tag will still run in postmerge, so if they are broken/easy to break by changes, we can easily tell and add proper tags as follow ups.

if test/jobs with no tags happen really frequently, I can also add a test that tests that all buildkite test jobs has a tag as follow up.. we will see.

this upgrade will hopefully save some test costs, by largely speaking only running tests that matter the most.