maemo.org - Talk - [Announcement] Python2.7 for Maemo5

Page 4 of 10

« First

< Prev

Next >

Last »

Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)

- Development (https://talk.maemo.org/forumdisplay.php?f=13)

- - [Announcement] Python2.7 for Maemo5 (https://talk.maemo.org/showthread.php?t=86900)

AapoRantalainen

2013-08-15 16:02

Re: [Announcement] Python2.7 for Maemo5

Quote:

Originally Posted by freemangordon (Post 1367398)

Do you mind to put that in the repos? Increasing the version ofc, as it is the same as the latest in extras-devel :)

I have tried to put this fixed version to the extras-devel, but it silently rejects it. Can you fetch some logs for me?

I should use bigger version number for fixed version (and not same than non-fixed version).

freemangordon

2013-08-15 17:12

Re: [Announcement] Python2.7 for Maemo5

Quote:

Originally Posted by AapoRantalainen (Post 1367446)

Hmm, those logs are available to everyone: https://garage.maemo.org/builder/fremantle/

However, could you reupload python2.7_2.7.3~rc2-2.1-maemo5 (I guess this is the fixed version) to the builder again, I have the feeling your attempt coincide with some maintaining or reboot. Try first without increasing the version.

EDIT:
If it fails again, I'll look at it more closely

EDIT2:
And I'll appreciate if I receive reports for anything suspicious related to the autobuilder/package interface ;)

EDIT3:
don;t reupload to builder, there are some problems, will inform you when the builder is fixed

AapoRantalainen

2013-08-16 07:28

Re: [Announcement] Python2.7 for Maemo5

Now I can see builder logs (you did something?)

armel build ok: 04-Aug-2013 21:17
i386 failed: 15-Aug-2013 18:07

(Reading from logs) During tests on arm qemu seg faults and then skips tests and success with packages.
On i386 it runs tests and fails with "Name or service not known" during test_docxmlrpc (SimpleXMLRPCServer.py+SocketServer.py) which looks something that builder might block for reason.

And actually it is not tests, but run_profile_task on

Code:

profile-opt:

        @echo "Building with support for profile generation:"

        $(MAKE) clean

        $(MAKE) build_all_generate_profile

        @echo "Running benchmark to generate profile data:"

        $(MAKE) profile-removal

        $(MAKE) run_profile_task

        @echo "Rebuilding with profile guided optimizations:"

        $(MAKE) clean

        $(MAKE) build_all_use_profile

And debian/rules is explicitly asking profiled build (so it can easily disabled).

freemangordon

2013-08-16 08:56

Re: [Announcement] Python2.7 for Maemo5

Quote:

Originally Posted by AapoRantalainen (Post 1367594)

Code:

profile-opt:

        @echo "Building with support for profile generation:"

        $(MAKE) clean

        $(MAKE) build_all_generate_profile

        @echo "Running benchmark to generate profile data:"

        $(MAKE) profile-removal

        $(MAKE) run_profile_task

        @echo "Rebuilding with profile guided optimizations:"

        $(MAKE) clean

        $(MAKE) build_all_use_profile

And debian/rules is explicitly asking profiled build (so it can easily disabled).

Yep, I did, there was a make -j4 ... stuck since 4th of August. We suspect OOM, now there is more memory added to builder VM. I killed that stuck make, so it continued, albeit failed.

Could you upload python2.7 again, to see if it will work this time.

freemangordon

2013-08-16 10:31

Re: [Announcement] Python2.7 for Maemo5

@aapo - Definitely it is not autobuilder to blame, for some reason a python process got stuck. I killed it by hand, so the build will succeed, but I think you should check the build rules and disable whatever is not really needed. Like profiled build, tests, etc.

EDIT:

Code:

Exception in thread Thread-268:

Traceback (most recent call last):

  File "/home/builder1/maemo-fremantle-i386-extras-devel/work/python2.7-2.7.3~rc2-2.1/Lib/threading.py", line 551, in __bootstrap_inner

    self.run()

  File "/home/builder1/maemo-fremantle-i386-extras-devel/work/python2.7-2.7.3~rc2-2.1/Lib/logging/config.py", line 883, in run

    ready=self.ready)

  File "/home/builder1/maemo-fremantle-i386-extras-devel/work/python2.7-2.7.3~rc2-2.1/Lib/logging/config.py", line 851, in __init__

    ThreadingTCPServer.__init__(self, (host, port), handler)

  File "/home/builder1/maemo-fremantle-i386-extras-devel/work/python2.7-2.7.3~rc2-2.1/Lib/SocketServer.py", line 408, in __init__

    self.server_bind()

  File "/home/builder1/maemo-fremantle-i386-extras-devel/work/python2.7-2.7.3~rc2-2.1/Lib/SocketServer.py", line 419, in server_bind

    self.socket.bind(self.server_address)

  File "/home/builder1/maemo-fremantle-i386-extras-devel/work/python2.7-2.7.3~rc2-2.1/Lib/socket.py", line 224, in meth

    return getattr(self._sock,name)(*args)

gaierror: [Errno -2] Name or service not known



make[2]: *** [run_profile_task] Terminated

Terminated is because of me killing the stuck python

AapoRantalainen

2013-08-16 11:05

Re: [Announcement] Python2.7 for Maemo5

Built success. Waiting package coming to the repository for testing.

Quote:

Originally Posted by freemangordon (Post 1367624)

@aapo - Definitely it is not autobuilder to blame, for some reason a python process got stuck.

How about this, happens on builder for ARM, but not my local SB.

Code:

test_exceptions

qemu: uncaught target signal 11 (Segmentation fault) - core dumped

make[2]: [run_profile_task] Error 126 (ignored)

Quote:

Originally Posted by freemangordon (Post 1367624)

you should check the build rules and disable whatever is not really needed. Like profiled build, tests, etc.

I have tried to do that, but this time that profiled build was slipped out of my radar.

freemangordon

2013-08-16 11:14

Re: [Announcement] Python2.7 for Maemo5

Quote:

Originally Posted by AapoRantalainen (Post 1367634)

Built success. Waiting package coming to the repository for testing.

How about this, happens on builder for ARM, but not my local SB.

Code:

test_exceptions

qemu: uncaught target signal 11 (Segmentation fault) - core dumped

make[2]: [run_profile_task] Error 126 (ignored)

I have tried to do that, but this time that profiled build was slipped out of my radar.

qemu, only devils know how it works, not the God even :).

I guess your SB setup differs from autobuilder.

Code:

ii  scratchbox-core:i386                               1.0.18                       Scratchbox base system

ii  scratchbox-devkit-apt-https:i386                   1.0.11                       APT HTTPS devkit for Scratchbox

ii  scratchbox-devkit-debian-squeeze:i386              1.0.4                        Debian Squeeze devkit for Scratchbox

ii  scratchbox-devkit-doctools:i386                    1.0.14                       Doctools for Scratchbox

ii  scratchbox-devkit-git:i386                         1.0.2                        Git for Scratchbox

ii  scratchbox-devkit-perl:i386                        1.0.5                        Perl modules for Scratchbox

ii  scratchbox-devkit-qemu:i386                        0.12.50-0sb3                 Qemu scratchbox devkit

ii  scratchbox-libs:i386                               1.0.18                       Scratchbox libraries

ii  scratchbox-toolchain-cs2005q3.2-glibc2.5-arm:i386  1.0.7.2                      cs2005q3.2-glibc2.5-arm compiler for Scratchbox

ii  scratchbox-toolchain-cs2005q3.2-glibc2.5-i386:i386 1.0.7                        cs2005q3.2-glibc2.5-i386 compiler for Scratchbox

ii  scratchbox-toolchain-cs2007q3-glibc2.5-arm7:i386   1.0.16-2                     cs2007q3-glibc2.5-arm7 compiler for Scratchbox

ii  scratchbox-toolchain-cs2007q3-glibc2.5-i486:i386   1.0.16-1                     cs2007q3-glibc2.5-i486 compiler for Scratchbox

ii  scratchbox-toolchain-host-gcc:i386                 1.0.18                       Scratchbox host-gcc toolchain

and fremantle scratchbox in autobuilder is using debian-squeeze, not debian-etch

AapoRantalainen

2013-08-16 19:06

Re: [Announcement] Python2.7 for Maemo5

Builder got -maemo5 built (arm+i386) , but there were also stucked -maemo6, so it didn't push it to the repository.

I bumped version number and reuploaded, but seems i386 version is again exhausted, armel deps are already in results: https://garage.maemo.org/builder/fre...c2-2.1-maemo6/

freemangordon

2013-08-18 19:45

Re: [Announcement] Python2.7 for Maemo5

Quote:

Originally Posted by AapoRantalainen (Post 1367740)

For some reason it hangs on "./python ../Lib/test/regrtest.py -x test_bsddb3 test_compiler test_cprofile test_dbm_dumb test_dbm_ndbm...", I guess next time you should disable regression tests in the build scripts.

There seems to be another problem with python2.7, similar to the KP problem - newest version does not appear in the package interface as the latest version. I'll look at that problem as soon as I have some spare time.

AapoRantalainen

2013-08-19 06:26

Re: [Announcement] Python2.7 for Maemo5

Quote:

Originally Posted by freemangordon (Post 1368079)

I guess next time you should disable regression tests in the build scripts

I think I now got how to disable it correctly (for next time).

Quote:

Originally Posted by freemangordon (Post 1368079)

There seems to be another problem with python2.7, similar to the KP problem - newest version does not appear in the package interface as the latest version. I'll look at that problem as soon as I have some spare time.

Yes, this is weird. But now working package is in extras-devel. And package page is: http://maemo.org/packages/package_in...c2-2.1-maemo6/
Is there risk that builder will remove it as a old version? Should I save it to the testing?

All times are GMT. The time now is 16:42.

Page 4 of 10

Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8