The build.gluster.org machine had the PDT timezone set. So the timestamps should be UTC-7 or UTC-8 depending on daylight savings. It's currently UTC-7.
Would having the archive timestamps also in UTC help?
~kaushal
On Mon, May 19, 2014 at 10:32 AM, Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx> wrote:
----- Original Message -----
> From: "Vijay Bellur" <vbellur@xxxxxxxxxx>
> To: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx>
> Cc: "gluster-infra" <gluster-infra@xxxxxxxxxxx>, gluster-devel@xxxxxxxxxxx
Its working now. But how do we convert the timestamp to logs' timestamp. I want to know the time difference.> Sent: Monday, 19 May, 2014 10:03:41 AM
> Subject: Re: Changes to Regression script
>
> On 05/19/2014 09:41 AM, Pranith Kumar Karampuri wrote:
> >
> >
> > ----- Original Message -----
> >> From: "Vijay Bellur" <vbellur@xxxxxxxxxx>
> >> To: "Pranith Kumar Karampuri" <pkarampu@xxxxxxxxxx>
> >> Cc: "gluster-infra" <gluster-infra@xxxxxxxxxxx>, gluster-devel@xxxxxxxxxxx
> >> Sent: Saturday, 17 May, 2014 2:52:03 PM
> >> Subject: Re: Changes to Regression script
> >>
> >> On 05/17/2014 02:10 PM, Pranith Kumar Karampuri wrote:
> >>>
> >>>
> >>> ----- Original Message -----
> >>>> From: "Vijay Bellur" <vbellur@xxxxxxxxxx>
> >>>> To: "gluster-infra" <gluster-infra@xxxxxxxxxxx>
> >>>> Cc: gluster-devel@xxxxxxxxxxx
> >>>> Sent: Tuesday, May 13, 2014 4:13:02 PM
> >>>> Subject: Changes to Regression script
> >>>>
> >>>> Hi All,
> >>>>
> >>>> Me and Kaushal have effected the following changes on regression.sh in
> >>>> build.gluster.org:
> >>>>
> >>>> 1. If a regression run results in a core and all tests pass, that
> >>>> particular run will be flagged as a failure. Previously a core that
> >>>> would cause test failures only would get marked as a failure.
> >>>>
> >>>> 2. Cores from a particular test run are now archived and are available
> >>>> at /d/archived_builds/. This will also prevent manual intervention for
> >>>> managing cores.
> >>>>
> >>>> 3. Logs from failed regression runs are now archived and are available
> >>>> at /d/logs/glusterfs-<timestamp>.tgz
> >>>>
> >>>> Do let us know if you have any comments on these changes.
> >>>
> >>> This is already proving to be useful :-). I was able to debug one of the
> >>> spurious failures for crypt.t. But the only problem is I was not able
> >>> copy
> >>> out the logs. Had to take avati's help to get the log files. Will it be
> >>> possible to give access to these files so that anyone can download them?
> >>>
> >>
> >> Good to know!
> >>
> >> You can access the .tgz files from:
> >>
> >> http://build.gluster.org:443/logs/
> >
> > I was able to access these yesterday. But now it gives 404.
Pranith.
> >
>
> Fixed.
>
> -Vijay
>
>
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-devel
