On 2023-07-10 06:10, Ross Burton wrote:
On 7 Jul 2023, at 23:43, Alexander Kanavin <[email protected]> wrote:
On Fri, 7 Jul 2023 at 21:46, Trevor Gamblin <[email protected]> wrote:
FYI I didn't see the junit output option anywhere. Are you referring to
an extra module?
If you run 'python3 -m test --help' you should see it:
--junit-xml FILENAME writes JUnit-style XML results to the specified file
I like this. JUnit XML is fairly common and a well-written conversion tool can
be used by multiple recipes.
I offer https://gitlab.com/rossburton/python-unittest-automake-output as a
holding location once it’s been proven to work.
It looks like there are some issues with the test code itself. Running
"python3 -m test -W -j 4 --junit-xml TESTRESULTS" to try it out, I see
things like this at the top of the output file:
|<testsuites tests="39396" errors="0" failures="0"><testsuite
start="2023-07-10 16:02:38.119463" tests="8" errors="0"
failures="0"><testcase
name="test.test_opcodes.OpcodeTest.test_compare_function_objects"
|status="run" result="completed" time="0.000520" /><testcase
name="test.test_opcodes.OpcodeTest.test_default_anno
| File "/usr/lib/python3.11/unittest/case.py", line 57, in testPartExecutor
| yield
| File "/usr/lib/python3.11/unittest/case.py", line 623, in run
| self._callTestMethod(testMethod)
| File "/usr/lib/python3.11/unittest/case.py", line 579, in _callTestMethod
| if method() is not None:
| ^^^^^^^^
| File "/usr/lib/python3.11/test/test_descr.py", line 1790, in test_bad_new
| self.assertRaises(TypeError, C)
| File "/usr/lib/python3.11/unittest/case.py", line 766, in assertRaises
| return context.handle('assertRaises', args, kwargs)
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| File "/usr/lib/python3.11/unittest/case.py", line 236, in handle
| with self:
| File "/usr/lib/python3.11/unittest/case.py", line 259, in __exit__
| self._raiseFailure("{} not raised by {}".format(exc_name,
| File "/usr/lib/python3.11/unittest/case.py", line 199, in _raiseFailure
| raise self.test_case.failureException(msg)
|AssertionError: TypeError not raised by C
|</output></testcase><testcase
name="test.test_descr.ClassPropertiesAndMethods.test_basic_inheritance"
status="run" result="completed" time="0.008526" /><testcase
|name="test.test_descr.ClassPropertiesAndMethods.test_binary_operator_override"
status="run" result="completed" time="0.000292" /><testcase
name="test.test_d
| File "/usr/lib/python3.11/unittest/case.py", line 57, in testPartExecutor
| yield
| File "/usr/lib/python3.11/unittest/case.py", line 623, in run
| self._callTestMethod(testMethod)
| File "/usr/lib/python3.11/unittest/case.py", line 579, in _callTestMethod
| if method() is not None:
| ^^^^^^^^
| File "/usr/lib/python3.11/test/test_descr.py", line 1841, in
test_restored_object_new
| b = B(3)
| ^^^^
|TypeError: object.__new__() takes exactly one argument (the type to
instantiate)
There are numerous others as well. I compiled 3.11.4 on my F38 host and
saw the same errors, which seems to suggest there's a problem with that
part of the source. I wonder if we should continue using sed for now,
but add the missing dependencies for test_cppext and the parallelized
testing option. Thoughts?
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184092):
https://lists.openembedded.org/g/openembedded-core/message/184092
Mute This Topic: https://lists.openembedded.org/mt/100005852/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
