On 2021-11-02 1:12 a.m., Pgowda wrote:
Hi Alexandre,
There are still issues with that series and I replied the following a
https://lists.openembedded.org/g/openembedded-core/message/156655
I had a detailed investigation on the cryptic errors which was
mentioned in the build.
Those are the tests that are supposed to FAIL in the rust testsuite.
Ah, that's good to know.
The current patch provides the framework to run the rust testsuite
from rust sources.
It does not modify the test case or results and hence is unable to
deal with failures
from rust source.
Hence, we see the final message as "command failed" at the end of testsuite run
due to some test case failures from rust source.
Can you please let me know how to deal with this?
In Yocto, we want the return status to indicate only that we were
able to _try_ to run all the tests. If some tests fail that's acceptable.
We need to know what the result was and we'll monitor it to ensure that
the number of failed tests does not increase.
Is there a way we can provide these failures as expected or ignore them?
I think this problem is rust specific so you'd have to deal with it in
your patch. Maybe someone can point out another case that is similar to
this one but I don't know of one offhand.
../Randy
Thanks,
Pgowda
--
# Randy MacLeod
# Wind River Linux
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#158842):
https://lists.openembedded.org/g/openembedded-core/message/158842
Mute This Topic: https://lists.openembedded.org/mt/86459542/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
