Skip to contentSkip to conversation

Broken "bitbake -S printdiff" in current OE

DISCUSSION Mike Looijmans 2 participants 3 messages Aug 23, 2016

lore
Share & tools
lore
#0 lore raw

Was attempting to figure out why something wasn't being grabbed from the sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields tons of lines like this:

WARNING: /home/mike/.../bitbake/lib/bb/runqueue.py:1347: ResourceWarning:
unclosed file <_io.BufferedReader name='/home/mike/.../build/tmp-glibc/stamps/cortexa9hf-neon-oe-linux-gnueabi/tiff/4.0.6-r0.do_populate_sysroot.sigdata.868460a5d532ef809db9bfa7ce2a89e4'> out2 = bb.siggen.compare_sigfiles(hashfiles[hash1], hashfiles[hash2],
recursecb)

Left it running for about fifteen minutes, but nothing useful came out.


Kind regards,

Mike Looijmans
System Expert

TOPIC Products


Materiaalweg 4


5681 RJ Best
T:
+31 (0) 499 33 69 69
Postbus 440
E:
[email protected]
5680 AK Best
W:
www.topicproducts.com
The Netherlands

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!

#1 lore raw
Quoted 4 lines · Mike Looijmans

Was attempting to figure out why something wasn't being grabbed from the sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields tons of lines like this:

Quoted 8 lines

WARNING: /home/mike/.../bitbake/lib/bb/runqueue.py:1347: ResourceWarning:
unclosed file <_io.BufferedReader name='/home/mike/.../build/tmp-glibc/stamps/cortexa9hf-neon-oe-linux-gnueabi/tiff/4.0.6-r0.do_populate_sysroot.sigdata.868460a5d532ef809db9bfa7ce2a89e4'> out2 = bb.siggen.compare_sigfiles(hashfiles[hash1], hashfiles[hash2],
recursecb)

Left it running for about fifteen minutes, but nothing useful came out.

Sent a patch to squelch the ResourceWarning messages, but that doesn't fix the problem that the whole thing just hangs and could only be killed by blunt force.


Kind regards,

Mike Looijmans
System Expert

TOPIC Products


Materiaalweg 4


5681 RJ Best
T:
+31 (0) 499 33 69 69
Postbus 440
E:
[email protected]
5680 AK Best
W:
www.topicproducts.com
The Netherlands

Please consider the environment before printing this e-mail

Topic zoekt gedreven (embedded) software specialisten!

#2 lore raw
In reply to Mike Looijmans
Quoted 13 lines · Mike Looijmans

Was attempting to figure out why something wasn't being grabbed from the sstate-cache, but running "bitbake -S printdiff qt4-embedded" only yields tons
of lines like this:

WARNING: /home/mike/.../bitbake/lib/bb/runqueue.py:1347: ResourceWarning:
unclosed file <_io.BufferedReader name='/home/mike/.../build/tmp-glibc/stamps/cortexa9hf- neon-oe-linux-gnueabi/tiff/4.0.6-r0.do_populate_sysroot.sigdata. 868460a5d532ef809db9bfa7ce2a89e4'>
out2 = bb.siggen.compare_sigfiles(hashfiles[hash1], hashfiles[hash2],
recursecb)

Quoted 2 lines

Left it running for about fifteen minutes, but nothing useful came out.

Not a fix for the original issue, but for what it's worth, I just added more comprehensive documentation on how to view task signatures here:

http://www.yoctoproject.org/docs/2.2/ref-manual/ref-manual.html#usingpoky-viewing-task-variable-dependencies

Running bitbake-diffsigs instead of 'bitbake -S diffsigs' would be an alternative.

I also had trouble getting 'bitbake -S diffsigs' and 'bitbake -S none' to work as advertised. They write a file locked-sigs.inc too, which seems to be undocumented. I relegated the bitbake -S documentation to the end of the new section and kept it as it was before.

Cheers,
Ulf