action #56813
closed
START_AFTER_TEST dependency error should use `@$MACHINE` syntax
Added by livdywan over 4 years ago.
Updated over 4 years ago.
Category:
Regressions/Crashes
Description
Reading this message, and considering I was investigating failures to do with replacing test suites with @staging or _staging in the name with parametrized ones, I was mildly confused:
START_AFTER_TEST=RAID0:64bit-staging not found - check for dependency typos and dependency cycles
I feel like this should be RAID0@64bit-staging using an @ rather than a : to separate the name of the test from the machine. This is how it's displayed elsewhere.
- Category set to Regressions/Crashes
- Target version set to Ready
- Difficulty set to easy
- Priority changed from Normal to High
- Difficulty changed from easy to medium
As we also use this for input, we need to write a migration and we really should do this rather soon before it spreads. So raising Difficulty and Priority
- Related to action #59082: Dependency graph shows just test name (misses machine) added
- Assignee set to mkittler
- Target version changed from Ready to Current Sprint
@coolo Because you added the relation to the dependency graph: The dependency graph doesn't show the machine within the tool tip which shows START_AFTER_TEST and the other variables. That is because the graph relies on the job dependencies database table which doesn't contain the original specification anymore. However, it would be possible to show the variables as specified from the job settings table.
I don't follow - can you provide examples?
- Status changed from New to In Progress
the relation of the ticket is mainly to make sure we use @ everywhere
The PR has been merged. But do we actually need a migration? The backwards compatible parsing should just work.
I would like to see at least a migration of our job groups to settle on @ - that doesn't need to be in git
- Status changed from In Progress to Feedback
- Status changed from Feedback to Resolved
- Target version changed from Current Sprint to Done
I've checked OSD and it is deployed and migrated.
Also available in: Atom
PDF