You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When one or more tests is a unanimous failure, a commit should be colored 'red' for failed. Mixed yellow color should be reserved for cases where there are no unanimous failures.
The text was updated successfully, but these errors were encountered:
I made the choice to prioritize mixed results since they are more anomalous than across-the-board failures. Perhaps in the era of some computers running fpe or optional tests, this muddies the waters since we'll have many more mixed results.
Adding indicators at the branch and commit level views for fpe and optional tests is midway down my to-do list, so that may help clarify the noise, but do we really want to make the mixed tests less prominent in favor of full-on failures (though both are countable from the badges on the right)?
At present, because of the aggregation with the optional and FPE tests, the full failures are "worse" (i.e., more likely to demand my attention) than the mixed tests. But I see your point that might not always be the case. Fine to punt on this issue for now until the filtering/indication of other test types get polished.
When one or more tests is a unanimous failure, a commit should be colored 'red' for failed. Mixed yellow color should be reserved for cases where there are no unanimous failures.
The text was updated successfully, but these errors were encountered: