Details
-
Task
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Fixed
-
None
Description
The results from running build/unittest/json_lib/json_normalize-t could be more clear.
For example:
ok 73 - normalize err?
|
ok 74 - expected '{"foo":"value"}' from '{
|
"foo": "value"
|
}
|
' but was '{"foo":"value"}'
|
There are two problems:
1) the TAP context strings are worded such that they only make sense in the failure case, not the (far more likely) success case
2) the input, expected, and actual results are not aligned to make it visiable at a glance if they match or not.
Attachments
Activity
Key |
|
|
Affects Version/s | N/A [ 27305 ] | |
Environment | Developer running unit tests locally | |
Project | MariaDB Foundation Development [ 11901 ] | MariaDB Server [ 10000 ] |
Assignee | Daniel Black [ danblack ] |
Fix Version/s | 11.8.1 [ 29961 ] |
issue.field.resolutiondate | 2024-12-17 23:13:16.0 | 2024-12-17 23:13:15.792 |
Component/s | Tests [ 10800 ] | |
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
I'm sorry. I don't know how I goofed this, but it seems when I tried to create an issue, it created as a Column-Store issue:
https://jira.mariadb.org/browse/MCOL-5872
I also don't see how I can change it. Can someone please help me move this to be an MDEV ?