Bug 12596 - python3-native do_compile failure on master-next
Summary: python3-native do_compile failure on master-next
Status: RESOLVED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 2.5
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 2.5 M4
Assignee: Alexander Kanavin
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2018-03-12 13:49 UTC by California Sullivan
Modified: 2018-03-20 03:30 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
python-native do_compile (116.07 KB, text/plain)
2018-03-12 13:49 UTC, California Sullivan 		no flags Details
another do_compile failure (101.80 KB, text/plain)
2018-03-13 12:56 UTC, California Sullivan 		no flags Details
anther logs showing a compile error (109.57 KB, text/plain)
2018-03-14 13:11 UTC, Juro Bystricky 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description California Sullivan 2018-03-12 13:49:47 UTC 
Created attachment 4232 [details]
python-native do_compile

https://autobuilder.yocto.io/builders/nightly-non-gpl3/builds/834/

https://autobuilder.yocto.io/builders/nightly-non-gpl3/builds/834/steps/BuildImages/logs/stdio

It looks like Python-ast.(c|h) gets generated, and everything relying on it fails. Likely a race condition?
Comment 1 California Sullivan 2018-03-13 12:56:23 UTC 
Created attachment 4234 [details]
another do_compile failure

Another similar do_compile failure: https://autobuilder.yocto.io/builders/nightly-world-lsb/builds/839/steps/BuildImages/logs/stdio
Comment 2 Juro Bystricky 2018-03-14 13:11:33 UTC 
Created attachment 4235 [details]
anther logs showing a compile error
Comment 3 Juro Bystricky 2018-03-14 13:11:51 UTC 
There is some kind of a race, some files don't seem to be generated deterministically.
I don't think this is master-next specific. I ran into this with "master" several times on a (machine with rather heavy load)
I attached my log, possibly same as the ones already attached.
Comment 4 Alexander Kanavin 2018-03-15 09:54:24 UTC 
Issue reported here:

https://bugs.python.org/issue33080

Patch is coming shortly.
Comment 5 Alexander Kanavin 2018-03-15 10:02:46 UTC 
Patch on the list: http://lists.openembedded.org/pipermail/openembedded-core/2018-March/148813.html