I was just suggesting that if there were a number of small bugs already discovered that maybe one JIRA would be enough to cover them. I'm certainly not suggesting that we have a JIRA that is continually updated. Perhaps there should just be a separate JIRA for each issue found.
-- Michael Mior mm...@apache.org Le mer. 19 sept. 2018 à 10:51, Vladimir Sitnikov < sitnikov.vladi...@gmail.com> a écrit : > Michael>Looks good to me! Should we maybe create a JIRA that we can point > to for > Michael>those interested in fixing some bugs? > > Frankly speaking I have no idea how that should work. > The identified expressions are new every time, so do you mean we should > have "ever-opened JIRA issue that suggests running RexProgramFuzzyTest"? > > How about the following? > > 1) RexProgramFuzzyTest runs with predefined seed and iteration count for > regression purposes. It prints nothing when the test is fine. > > 2) Then RexProgramFuzzyTest runs with a random seed till the first failure > (with a time budget of 5 seconds). It prints the error message to the > console. > It might inspire those who stare at build logs. Of course the stacktrace > should either be hidden or truncated to 3-4 lines to avoid log clutter. > > Vladimir >
