On Tue, 2020-01-14 at 13:19 +0100, Alexander Kanavin wrote: > On Tue, 14 Jan 2020 at 11:23, Richard Purdie < > richard.pur...@linuxfoundation.org> wrote: > > For extra data I reran this on a builder where it failed. This time > > it > > worked out ok. I can think of two different things we could try: > > > > a) Add some debug to the code so that when a unknown user error > > occurs, > > it triggers a mention of the filename with the issue > > > > b) Potentially try turning off any parallel install code for > > python. > > I'm starting to wonder if that is racing somehow over file > > ownership. > > Making it single thread may make the issue appear (or it may > > disappear). > > I tried setting PARALLEL_MAKEINST to "", and it didn't make any > difference (python is using standard autotools). I guess we'll have > to catch the build directory when it happens again somehow.
The autobuilder failed with this again, I went in and the first bit of debugging I added was to say which file its failing on. Answer was: WARNING: python3-3.8.1-r0 do_package: ./package/usr/libx32/python3.8/__pycache__/_bootlocale.cpython-38.opt-2.pyc so for some reason the ownership of the pyc file (or files) is suspect. I did a quick inspection of the pseudo database and its only this one file. That leads me to suspect its a race in how its being generated/owned... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembeddedemail@example.com http://lists.openembedded.org/mailman/listinfo/openembedded-core