Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Default scheduler human-friendly warning ordering #87149
While working on pod affinity, I got a typical warning from the
Now the problem here is I messed up my affinity labelling. But by putting the memory error first, the error message can (and did, in the case of my colleagues) mislead people into trying to diagnose the memory issue.
In languages like C and C++ you are taught (or learn the hard way) to investigate the first error first, in case subsequent errors are just artifacts caused by the compiler state after discovering the first error.
In my mind, the default scheduler needs the concept of priority order in the warning message - this could be modelled in two ways: