~bigbes/tarantool

tarantool-protobuf

ref: 39233ed5be83b65ef40ec2a275e85a01ab7fa284 tarantool-protobuf/test/conformance/known_failures_text.txt -rw-r--r-- 1.5 KiB
39233ed5 — Eugene Blikh text: wire pb.text into conformance runner TEXT_FORMAT output 3 months ago
                                                                                
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
# conformance_test_runner --text_format_failure_list
#
# Text-format OUTPUT is now wired through cmd/conformance/core.lua to
# pb.text.encode (protobuf/JSON input → text output). Input parsing is
# still deferred — pb.text only encodes — so any test whose payload is
# text_payload still returns `skipped`.
#
# Remaining expected failures all stem from unknown-field handling:
#
#   * Group/Repeated *_Drop: our decoder rejects payloads carrying
#     wire types 3/4 (proto2 groups) and length-mismatched repeated
#     unknown bytes, so we never reach the encoder. Expected output is
#     an empty text body, which we'd produce trivially if the decoder
#     accepted the input. Fixing requires skip_field to tolerate groups.
#
#   * *_Print: with `print_unknown_fields: true` the harness expects the
#     text output to include the original unknown fields. We capture
#     unknown bytes during decode but pb.text doesn't render them, so
#     output comes back empty. Fixing requires the text encoder to walk
#     the captured unknown set.
Recommended.Proto3.ProtobufInput.GroupUnknownFields_Drop.TextFormatOutput
Recommended.Proto3.ProtobufInput.GroupUnknownFields_Print.TextFormatOutput
Recommended.Proto3.ProtobufInput.MessageUnknownFields_Print.TextFormatOutput
Recommended.Proto3.ProtobufInput.RepeatedUnknownFields_Drop.TextFormatOutput
Recommended.Proto3.ProtobufInput.RepeatedUnknownFields_Print.TextFormatOutput
Recommended.Proto3.ProtobufInput.ScalarUnknownFields_Print.TextFormatOutput