Enable creation of missing directories in GPR file

[zertovitch]

Plus, build using all cores.

[mgrojo]

The conformance tests are failing with this commit, but it worked with the parent commit. Do you think these flags could affect them in any way? I guess not, then we depend on something outside the repository, which has changed. I will rerun the action on the parent commit to verify it.

https://github.com/reznikmm/protobuf/actions/runs/23223928246/job/70895706356#step:8:2478

ERROR, test=Required.Proto3.ProtobufInput.BadTag_FieldNumberTooHigh: Should have failed to parse, but didn't., request=goo.gle/debugonly   protobuf_payload: "\210\200\200\200\200\200\017\322\t" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto3.TestAllTypesProto3" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\010\322\t"
ERROR, test=Required.Proto3.ProtobufInput.BadTag_OverlongVarint: Should have failed to parse, but didn't., request=goo.gle/debugonly   protobuf_payload: "\210\200\200\200\200\200\200\200\000\322\t" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto3.TestAllTypesProto3" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\010\322\t"
ERROR, test=Required.Proto3.ProtobufInput.BadTag_VarintMoreThanTenBytes: Should have failed to parse, but didn't., request=goo.gle/debugonly   protobuf_payload: "\210\200\200\200\200\200\200\200\200\200\200\200\000\322\t" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto3.TestAllTypesProto3" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\010\322\t"
ERROR, test=Required.Proto2.ProtobufInput.BadTag_FieldNumberTooHigh: Should have failed to parse, but didn't., request=goo.gle/debugonly   protobuf_payload: "\210\200\200\200\200\200\017\322\t" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\010\322\t"
ERROR, test=Required.Proto2.ProtobufInput.BadTag_OverlongVarint: Should have failed to parse, but didn't., request=goo.gle/debugonly   protobuf_payload: "\210\200\200\200\200\200\200\200\000\322\t" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\010\322\t"
ERROR, test=Required.Proto2.ProtobufInput.BadTag_VarintMoreThanTenBytes: Should have failed to parse, but didn't., request=goo.gle/debugonly   protobuf_payload: "\210\200\200\200\200\200\200\200\200\200\200\200\000\322\t" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\010\322\t"
WARNING, test=Recommended.Proto2.ProtobufInput.ValidMessageSetEncoding.SubmessageEncoding.ProtobufOutput: Output was not equivalent to reference message: deleted: message_set_correct.(protobuf_test_messages.proto2.TestAllTypesProto2.MessageSetCorrectExtension2.message_set_extension): { i: 99 }
, request=goo.gle/debugonly   protobuf_payload: "\242\037\007\202\231\343\017\002Hc" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=goo.gle/debugonly   protobuf_payload: "\242\037\000"
WARNING, test=Recommended.Proto2.ProtobufInput.ValidMessageSetEncoding.SubmessageEncoding.NotUnknown.ProtobufOutput: Failed to parse input or produce output., request=goo.gle/debugonly   protobuf_payload: "\242\037\023\252\321\371\326\003\002\010*\013\020\225\232\357:\032\002\020c\014" requested_output_format: PROTOBUF message_type: "protobuf_test_messages.proto2.TestAllTypesProto2" test_category: BINARY_TEST, response=goo.gle/debugonly   parse_error: "Parse_Error:raised CONSTRAINT_ERROR : Group encoding is unimplemented\nLoad address: 0x5645a4df6000\nCall stack traceback locations:\n0x7f8d7bd09fb1 0x5645a4eb1dba 0x5645a4e71b98 0x5645a4e78144 0x5645a4e844e3 0x5645a4e71d3d 0x5645a4e1d4b6 0x5645a4e1f5d2 0x5645a4e218f3 0x7f8d7ac2a1c8 0x7f8d7ac2a289 0x5645a4e1c613 0xfffffffffffffffe\n"

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 from the root of your workspace:
  bazel run //google/protobuf/conformance:update_failure_list -- ada_failing_tests.txt --add /failing_tests.txt

  Required.Proto2.ProtobufInput.BadTag_FieldNumberTooHigh # Should have failed to parse, but didn't.
  Required.Proto2.ProtobufInput.BadTag_OverlongVarint # Should have failed to parse, but didn't.
  Required.Proto2.ProtobufInput.BadTag_VarintMoreThanTenBytes # Should have failed to parse, but didn't.
  Required.Proto3.ProtobufInput.BadTag_FieldNumberTooHigh # Should have failed to parse, but didn't.
  Required.Proto3.ProtobufInput.BadTag_OverlongVarint # Should have failed to parse, but didn't.
  Required.Proto3.ProtobufInput.BadTag_VarintMoreThanTenBytes # Should have failed to parse, but didn't.

Failed to open file: /failing_tests.txt
CONFORMANCE SUITE FAILED: 1395 successes, 1394 skipped, 11 expected failures, 6 unexpected failures.

make: *** [Makefile:40: check] Error 1
ERROR: Command ["make", "check"] exited with code 2
Error: Process completed with exit code 1.

[mgrojo]

OK, I cannot rerun the successful actions in this repository, but not needed, it's clear that it's failing because we are using a moving conformance test (the latest from the repo https://github.com/protocolbuffers/protobuf as can be seen in:

protobuf/.github/workflows/main.yml

Lines 17 to 20 in 20fe933

	- uses: actions/checkout@v2
	with:
	repository: protocolbuffers/protobuf
	path: google

So the changes look good to me.

[mgrojo]

This is simple enough to be merged without further approvals. Thanks, @zertovitch.