Boost test junit output violates schema
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start with the JUnit results formatter and inspect how XML attributes such as time are serialized. Reproduce the schema or Bazel parsing failure, then verify that generated time values conform to the JUnit schema's xs:decimal format without scientific notation.
Written by the indexing model from the issue text.
Description
When using the junit results formatter, the XML attributes like time use default float ostream formatting which uses scientific notation at times. However the junit schema says time is xs:decimal and scientific notation is not valid xs:decimal.
I suggest that boost uses fixed formatting instead.
Among other things this means boost test results fail to be parsed by bazel.
- Dominant language
- C++
- Stars
- 217
- Forks
- 149
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/test
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
-
Conversion Warning with GCC15 when using operator<< within custom failure message and -WConversionOpen
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Similar issues
-
Server-side raycast misses objects with `rotate = true` selection boxes (degrees passed as radians)OpenUnconfirmed bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
luanti-org/luanti#17624 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
moneymanagerex/moneymanagerex#8564 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
tesseract-robotics/tesseract_nanobind#190 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
telegramdesktop/tdesktop#31409 ·
Maintainers usually reply within 10 days