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
Our current CI grew to be too wide due to all pair combinations of ($TARGET, $VARIETY). Currently it's 33 pairs. It makes it hard to fit into a screen, it's not very easy to comprehend, given that we end up with a table of 33 cols * 220 rows = 7260 cells.
I propose to add a checkbox (enabled by default) to summarize these by ($TARGET). In case if results from different $VARIETY instances inside a $TARGET for a given test are different, we can highlight that as a severe error with a text like "mixed".
The text was updated successfully, but these errors were encountered:
See kaitai-io/kaitai_struct#823
Until now, the order in which variants are shown has
been somewhat "random". Not completely random, it was
just printed in the order in which the "ci.json" files
arrived. But the result was that for instance
the "javascript" variants were in a different order
every time: sometimes it was "node10, node12, node4, node8",
after reload some other one... This is not convenient to
work with, because you need to pay attention to the variant
labels, whose order is not consistent between reloads.
Our current CI grew to be too wide due to all pair combinations of ($TARGET, $VARIETY). Currently it's 33 pairs. It makes it hard to fit into a screen, it's not very easy to comprehend, given that we end up with a table of 33 cols * 220 rows = 7260 cells.
I propose to add a checkbox (enabled by default) to summarize these by ($TARGET). In case if results from different $VARIETY instances inside a $TARGET for a given test are different, we can highlight that as a severe error with a text like "mixed".
The text was updated successfully, but these errors were encountered: