Summary: | sys-apps/portage tests stall on arm64 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Roy Bamford <neddyseagoon> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | arm64, chewi, leio, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | ARM64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Log of stalled build of sys-apps:portage-2.3.16 |
Description
Roy Bamford
2017-11-28 13:45:01 UTC
Created attachment 506920 [details]
Log of stalled build of sys-apps:portage-2.3.16
I haven't updated my odroid-c2 in a while (stock odroid kernel), but I just synced, "emerge -vaD portage" (2.3.13). Then started FEATURES=test emerge -va --jobs=1 portage It is running, 2.7 and 3.4 tests are completed, working on 3.5, 3.6 will be next... I am getting a lot of: * Unable to trace static ELF: /sbin/ldconfig: /sbin/ldconfig -p on many of the tests, but the tests are tagged [OK] I'll do a full system update after and retest (In reply to Brian Dolbec from comment #2) > I haven't updated my odroid-c2 in a while (stock odroid kernel), but I just > synced, "emerge -vaD portage" (2.3.13). > > Then started FEATURES=test emerge -va --jobs=1 portage > > It is running, 2.7 and 3.4 tests are completed, working on 3.5, 3.6 will be > next... > > I am getting a lot of: > > * Unable to trace static ELF: /sbin/ldconfig: /sbin/ldconfig -p > > on many of the tests, but the tests are tagged [OK] > > I'll do a full system update after and retest I've copy/pasted FEATURES=test emerge -va --jobs=1 portage and FEATURES=test emerge -va --jobs=1 =portage-2.3.13 So we are using the same commands. No change in output. The tests that do run, pass. I don't see any * Unable to trace static ELF: /sbin/ldconfig: /sbin/ldconfig -p Please use pstree or `ps axf` to identify the pid of the hung process, and check if it's using cpu time. Also, output of `strace -p <pid>` would be interesting. (In reply to Zac Medico from comment #4) > Please use pstree or `ps axf` to identify the pid of the hung process, and > check if it's using cpu time. Also, output of `strace -p <pid>` would be > interesting. 2274 ? Ss 0:00 /usr/sbin/sshd 2345 ? Ss 0:00 \_ sshd: root@pts/0 2347 pts/0 Ss 0:00 | \_ -bash 2351 pts/0 S+ 0:00 | \_ screen 2352 ? Ss 0:00 | \_ SCREEN 2353 pts/1 Ss 0:00 | \_ -/bin/bash 2357 pts/1 SN+ 0:43 | \_ /usr/bin/python3.4 -b /usr/lib/python-exec/python3.4/emerge -1 portage -av 3115 pts/1 SN+ 0:00 | \_ [sys-apps/portage-2.3.16] sandbox /var/tmp/portage/._portage_reinstall_.oi9l1vub/bin/ebuild.sh test 3116 pts/1 SN+ 0:00 | \_ /bin/bash /var/tmp/portage/._portage_reinstall_.oi9l1vub/bin/ebuild.sh test 3133 pts/1 SN+ 0:00 | \_ /bin/bash /var/tmp/portage/._portage_reinstall_.oi9l1vub/bin/ebuild.sh test 3174 pts/1 SN+ 0:00 | \_ tee -a /var/tmp/portage/sys-apps/portage-2.3.16/temp/build-python2_7.log 3205 pts/1 SN+ 0:00 | \_ /usr/bin/python2.7 setup.py test 3208 pts/1 RN+ 3:22 | \_ /usr/bin/python2.7 -bWd /var/tmp/portage/sys-apps/portage-2.3.16/work/portage-2.3.16-python2_7/lib/portage/tests/runTests.py The hung process is /usr/bin/python2.7 -bWd /var/tmp/portage/sys-apps/portage-2.3.16/work/portage-2.3.16-python2_7/lib/portage/tests/runTests.py Its using 100% of one core. Pi3_64 ~ # strace -p 3208 strace: Process 3208 attached That's all it says. It seems like array_fromfile is not working correctly. Maybe we should simply remove this test, since array_fromfile has never really been reliable and portage doesn't use it anymore. I've tested on arm64 where testArrayFromfileEof fails. Its reported to work on arm (32 bit) I've tested on amd64 too, just to compare results, that works. This all started out to add ~arm64 KEYWORDS to dev-python/pyblake2-1.1.0 and sys-apps/portage-2.3.16. They both work on arm64, so you may want to add the keywords anyway. Seems fixed now? (In reply to Zac Medico from comment #6) > It seems like array_fromfile is not working correctly. Maybe we should > simply remove this test, since array_fromfile has never really been reliable > and portage doesn't use it anymore. I'll be happy to remove the test if it's still an issue. Also, it's possible that the hang only affected python2.7, and we don't support that anymore anyway. |