Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Packed Bool EOF Conformance Test Failure in Latest Protobuf Suite #12

Open
cretz opened this issue Dec 27, 2018 · 2 comments
Open

Packed Bool EOF Conformance Test Failure in Latest Protobuf Suite #12

cretz opened this issue Dec 27, 2018 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@cretz
Copy link
Owner

cretz commented Dec 27, 2018

Running conformance tests results in the following:

CONFORMANCE TEST BEGIN ====================================

ERROR, test=Required.Proto3.ProtobufInput.PrematureEofInPackedField.BOOL: Should have failed to parse, but didn't. request=protobuf_payload: "\332\002\001" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto3.TestAllTypesProto3" test_category: BINARY_TEST, response=protobuf_payload: "\330\002\001"
ERROR, test=Required.Proto2.ProtobufInput.PrematureEofInPackedField.BOOL: Should have failed to parse, but didn't. request=protobuf_payload: "\332\002\001" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=protobuf_payload: "\330\002\001"

These tests failed.  If they can't be fixed right now, you can add them to the failure list so the overall suite can succeed.  Add them to the failure list by running:
./update_failure_list.py  --add failing_tests.txt

Required.Proto2.ProtobufInput.PrematureEofInPackedField.BOOL
Required.Proto3.ProtobufInput.PrematureEofInPackedField.BOOL

CONFORMANCE SUITE FAILED: 386 successes, 443 skipped, 0 expected failures, 2 unexpected failures.


CONFORMANCE TEST BEGIN ====================================

ERROR, test=Required.Proto3.ProtobufInput.PrematureEofInPackedField.BOOL: Should have failed to parse, but didn't. request=protobuf_payload: "\332\002\001" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto3.TestAllTypesProto3" test_category: BINARY_TEST, response=protobuf_payload: "\330\002\001"
ERROR, test=Required.Proto2.ProtobufInput.PrematureEofInPackedField.BOOL: Should have failed to parse, but didn't. request=protobuf_payload: "\332\002\001" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=protobuf_payload: "\330\002\001"

These tests failed.  If they can't be fixed right now, you can add them to the failure list so the overall suite can succeed.  Add them to the failure list by running:
./update_failure_list.py /home/cretz/work/gojvm/pb-and-k/conformance/conformance-js/failing_tests.txt --add failing_tests.txt

Required.Proto2.ProtobufInput.PrematureEofInPackedField.BOOL
Required.Proto3.ProtobufInput.PrematureEofInPackedField.BOOL

CONFORMANCE SUITE FAILED: 378 successes, 443 skipped, 8 expected failures, 2 unexpected failures.

Which means it fails in Java and JS for both proto2 and proto3.

@cretz cretz added the bug Something isn't working label Dec 27, 2018
@cretz cretz added this to the v0.4.0 milestone Dec 27, 2018
@phcoder
Copy link

phcoder commented Jan 27, 2019

I looked at it and it seems to me to be a problem in the test rather than in the code

@phcoder
Copy link

phcoder commented Jan 29, 2019

#16

garyp added a commit to streem/pbandk that referenced this issue Jan 6, 2020
garyp added a commit to streem/pbandk that referenced this issue Jan 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants