Re: [linuxtools-dev] Hudson integration with Gerrit

[sami wagiaalla]

Hi Anna,


Can I take a look at the verification job config?
The trigger didn't work for awhile:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=384827



We got most of our settings from here: 
http://wiki.eclipse.org/Gerrit#Verifying_Changes_on_Hudson_using_Gerrit_Trigger_Plugin 
and http://wiki.hudson-ci.org/display/HUDSON/Gerrit+Trigger


We have not had any problems with the trigger. The main problem was 
getting Hudson to build the right commit on the right branch for which 
we used the following "execute shell" build step before running maven:


#!/bin/sh -x
git fetch 
git://git.eclipse.org/gitroot/linuxtools/org.eclipse.linuxtools 
$GERRIT_REFSPEC

git checkout FETCH_HEAD
CODE=$?
if [ ${CODE} -ne 0 ]; then
  git reset --hard
  exit ${CODE}
fi

You should be able to view the configuration if you login: 
https://hudson.eclipse.org/sandbox/job/linuxtools/


Hope this helps.
  Sami

___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev

[linuxtools-dev] CTF timestamps in big endian

[Gerlando Falauto]

Hi everyone,

I am trying to use the stock LTTng plugin that came with the Eclipse IDE 
for C/C++ Developers, Juno (version number looks like 
1.0.0.201206130106) in order to view Kernel CTF traces generated by 
LTTng 2.0 on two different embedded targets (ARM and PowerPC).


While on ARM (little endian) everything seems to work fine, on PowerPC 
(big endian) I get absolutely meaningless timestamps, ranging to years 
2050, 2145, and so on...
I get huge gaps (as I see only the time of day part, it looks like 
hours, but it might be as well be years!) between consecutive events.


Groups of adjacent events do sometimes get displayed with reasonably 
close timestamps though (I guess for those events which got dumped with 
a compact representation of the timestamp and/or header).


The output of babeltrace for the same trace looks OK.

Any other fields (pids, tids, task names, etc..) which would be affected 
by a global endianness problem still look OK, so it's definitely 
something related to timestamps.


Any ideas? Shall I send the affected trace?

Thank you,
Gerlando
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/linuxtools-dev