I like the date - they indicate the "human factor" like "there is a regression 2 days already and nobody cares". And a revision is a "technical help" for someone who evaluates the regression.
So I would show both first-failure-data and last-success-revision on CI page (if it is possible). Thanks Vladimir Beliaev 2007/10/18, Alexey Varlamov <[EMAIL PROTECTED]>: > > Hi Vladimir, > > This makes sense. The only concern from my side is that the table may > look too cluttered. > Actually we may completely switch to revisions instead of dates - what > do you think? > > -- > Alexey > > 2007/10/17, Vladimir Beliaev <[EMAIL PROTECTED]>: > > Alexey, > > > > currently the Code Integrity Status page contains the date when the > > regression happen, like: > > > > "JDKTools tests" "12:01 since 2007-09-26" > > > > This information is proposed to be kept, also let's add a latest > revision > > which PASSED for this suite, i.e. let's have something like: > > > > "JDKTools tests" "12:01 since 2007-09-26, last passed > > r556677" > > > > Let's have it done for all suites for Code Integrity testing. Such an > > improvement would simplyfy the search of "bad patch" introducing > regression > > and improve "no regression" tracking process. > > > > [1]: http://people.apache.org/~varlax/harmony-integrity/ > > Thanks > > -- > > Vladimir Beliaev > > Intel Middleware Products Division >
