MantisBT - CDash
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0007648CDashpublic2008-09-10 16:022008-09-10 16:57
ReporterFrançois Bertel 
Assigned ToJulien Jomier 
PrioritynormalSeverityminorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.0.2 
Target VersionFixed in Version1.2 
Summary0007648: commit ordering issue in Nightly Changes page of VTK Cdash (1.0.3)
DescriptionOn this page:
http://www.cdash.org/CDash/viewChanges.php?project=VTK&date=20080910 [^]

you can see:

          vtkWin32OpenGLRenderWindow.cxx Revision: 1.155 by fbertel
        BUG:Fixed bug 7638.

          vtkWin32OpenGLRenderWindow.cxx Revision: 1.157 by fbertel
        BUG:Try to fix morva with PV in client-server mode.

          vtkWin32OpenGLRenderWindow.cxx Revision: 1.156 by fbertel
        COMP:Oops.

Commits are not displayed in proper order: 1.155,1.157,1.156 instead of 1.155,1.156,1.157

but some other parts are correct:

   vtkCosmicTreeLayoutStrategy.cxx Revision: 1.2 by utkarsh
        COMP: fixed build issues

          vtkCosmicTreeLayoutStrategy.cxx Revision: 1.3 by bnwylie
        COMP: Fixing variable scoping issues.

          vtkCosmicTreeLayoutStrategy.cxx Revision: 1.4 by bnwylie
        BUG: Parent array was being accessed one off the end. :( Thompson should look at this when he gets a chance. BUG: Fixing Printself test.

Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-09-10 16:02François BertelNew Issue
2008-09-10 16:13Julien JomierStatusnew => assigned
2008-09-10 16:13Julien JomierAssigned To => Julien Jomier
2008-09-10 16:31Julien JomierNote Added: 0013399
2008-09-10 16:57Julien JomierStatusassigned => closed
2008-09-10 16:57Julien JomierNote Added: 0013402
2008-09-10 16:57Julien JomierResolutionopen => fixed
2008-09-10 16:57Julien JomierFixed in Version => 1.2

Notes
(0013399)
Julien Jomier   
2008-09-10 16:31   
For some reasons the checkin date in the database are all 00:00:00 that's why it's failing. I'm looking at it now.
(0013402)
Julien Jomier   
2008-09-10 16:57   
The date was converted into a timestamp which was wrong since the date is store in the database. This has been fixed in 1.2 and should solve the problem since now the date should be correct in the database. If you see some strange behavior feel free to reopen.
Thanks for the report!