<div dir="ltr">A quick note, be sure you have the last packages gobject-introspection and pygobject3<div>from dsd repository [1] or the patches applied to your own packages.</div><div><br></div><div>Gonzalo</div><div><br></div>
<div>[1] <a href="http://dev.laptop.org/~dsd/public_rpms/f18/">http://dev.laptop.org/~dsd/public_rpms/f18/</a></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 10, 2014 at 12:22 PM, Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<br>
<div>El 09/03/14 12:46, Daniel Narvaez
escribió:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><div class="">On 9 March 2014 17:53, Sebastian Silva <span dir="ltr"><<a href="mailto:sebastian@fuentelibre.org" target="_blank">sebastian@fuentelibre.org</a>></span>
wrote:<br>
</div><div class=""><div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
For us to base our work on 0.101+ (new) Sugar, we have
to make sure we have solved the performance issues
plaguing (new) Sugar and/or OLPC/OS 13.x.<br>
</div>
</blockquote>
<div><br>
</div>
<div>Which OLPC version are you comparing with? In the rest
of the answer I'll call that X.x :)<br>
</div>
<div> </div>
</div>
</div>
</div></div>
</blockquote>
Well we deployed an image based on 11.3 i.e. Fedora 14. However the
focus of my research is Sugar itself. I figure base OS issues are a
different beast and worth isolating for this first approach, that's
why I figured I wanted the same setup with different Sugar versions.<div class=""><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> <br>
For this I need your advice.<br>
<br>
<b>How do I setup an identical environment for (classic)
0.94 Sugar and (new) 0.101+ Sugar? Can I use
sugar-build for this, or something else...?</b><b><br>
</b></div>
</blockquote>
<div><br>
</div>
On which hardware and on which distribution?<br>
</div>
</div>
</div>
</blockquote></div>
For Christmas I got an Acer Chromebook c720, cost $US200, got 2GB
ram and 16GBSSD. Pretty fast Haswell based processor, coming from an
Atom netbook. Quite happy with the upgrade, btw.<div class=""><br>
<br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br>
Anyway it's probably not going to be trivial. So let me
suggest an easier first step. You could test 0.94 activities
on the top of OLPC 13.x. If they perform the same as OLPC
X.x then we know the issue is the gtk3 toolkit (no change
was made to the gtk2 toolkit). If they are bad as stock 13.x
activities, then we will know it's something in the system.
If it's something in the middle we will have to come up with
a more complicated strategy. But I think the data we get
from this initial testing will be useful to figure out that
strategy.<br>
</div>
</div>
</div>
</blockquote>
<br></div>
I will make the time to flash 13.2 on an XO1 and do this informal
test. However I has hoping to use my dev environment because I
really want a test that can be automated/done quickly, and gives
numbers, not just impressions.<div class=""><br>
<blockquote type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
</div>
<div class="gmail_quote">
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><b> </b><b>How do I
profile the session (CPU usage, memory consumption,
timing)? <br>
</b></div>
</blockquote>
<div><br>
</div>
<div>For memory I would try this<br>
<br>
<a href="https://github.com/pixelb/ps_mem" target="_blank">https://github.com/pixelb/ps_mem</a><br>
<br>
</div>
<div>For CPU top should be fine, but it depends what exactly
you want to test. For timing I usually just print out
time.time intervals from the code :)<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><b> Do we have some
automated GUI testing? Can I make some?</b></div>
</blockquote>
<div><br>
</div>
<div>See sugar-build/build/tests/shell.py, you could use
something like that to measure startup time I suppose.
Anyway you can use the same kind of code to click around
in activities UI etc.<br>
</div>
</div>
</div>
</div>
</blockquote></div>
Is this what runs when you do ./osbuild check ?<br>
<br>
I tried but it's failing for me and I'm not finding the error. Below
is the output. shell.log and datastore.log in home/dotsugar/logs/
don't show any traceback either.<br>
<br>
<tt>[icarito@aiki sugar-build]$ ./osbuild check<br>
<br>
= Check =<br>
<br>
* Running smoke test<br>
<br>
Command failed: sugar-runner<br>
<br>
<br>
Initializing built-in extension Generic Event Extension<br>
Initializing built-in extension SHAPE<br>
Initializing built-in extension MIT-SHM<br>
Initializing built-in extension XInputExtension<br>
Initializing built-in extension XTEST<br>
Initializing built-in extension BIG-REQUESTS<br>
Initializing built-in extension SYNC<br>
Initializing built-in extension XKEYBOARD<br>
Initializing built-in extension XC-MISC<br>
Initializing built-in extension SECURITY<br>
Initializing built-in extension XINERAMA<br>
Initializing built-in extension XFIXES<br>
Initializing built-in extension RENDER<br>
Initializing built-in extension RANDR<br>
Initializing built-in extension COMPOSITE<br>
Initializing built-in extension DAMAGE<br>
Initializing built-in extension MIT-SCREEN-SAVER<br>
Initializing built-in extension DOUBLE-BUFFER<br>
Initializing built-in extension RECORD<br>
Initializing built-in extension DPMS<br>
Initializing built-in extension X-Resource<br>
Initializing built-in extension XVideo<br>
Initializing built-in extension XVideo-MotionCompensation<br>
Initializing built-in extension GLX<br>
screen 0 shmid 110952503<br>
[dix] Could not init font path element /usr/share/fonts/Type1/,
removing from list!<br>
xinit: XFree86_VT property unexpectedly has 0 items instead of 1<br>
Xlib: extension "RANDR" missing on display ":99".<br>
The XKEYBOARD keymap compiler (xkbcomp) reports:<br>
> Warning: Compat map for group 2 redefined<br>
> Using new definition<br>
> Warning: Compat map for group 3 redefined<br>
> Using new definition<br>
> Warning: Compat map for group 4 redefined<br>
> Using new definition<br>
Errors from xkbcomp are not fatal to the X server<br>
xinit: connection to X server lost<br>
<br>
<br>
! Failed to run command check<br>
[icarito@aiki sugar-build]$ </tt><br>
<br>
</div>
<br>_______________________________________________<br>
Sugar-devel mailing list<br>
<a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
<a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Gonzalo Odiard<br><br><div>SugarLabs - Learning Software for children<br></div></div>
</div>