[Failing Test]: Python Container Builds Fail with SIGSEGV: segmentation violation

[jrmccluskey]

What happened?

Python container builds that are invoked through processArtifactsInSetupOnlyMode() fail because of the newly introduced logRuntimeDependencies() function. It appears that the function always tries to invoke the logger directly instead of using a buffered logger, accessing a nil value. This should be fixed by accepting a buffered logger type instead, which accounts for this issue.

goroutine 1 [running]:
github.com/apache/beam/sdks/v2/go/container/tools.(*Logger).Log(0x0, {0xa4c3a8, 0xe36cc0}, 0x2, {0xc000038640, 0x1d})
	/runner/_work/beam/beam/sdks/go/container/tools/logging.go:59 +0x66
github.com/apache/beam/sdks/v2/go/container/tools.(*Logger).Printf(0x0?, {0xa4c3a8, 0xe36cc0}, {0x99939e?, 0xc9f8ade50?}, {0x0?, 0x7fffffffffffffff?, 0xa4c3a8?})
	/runner/_work/beam/beam/sdks/go/container/tools/logging.go:106 +0x5a
main.logRuntimeDependencies({0xa4c3a8, 0xe36cc0}, 0x0)
	/runner/_work/beam/beam/sdks/python/container/boot.go:463 +0x5b
main.installSetupPackages({0xa4c3a8, 0xe36cc0}, 0x0, {0xc000042e30, 0x1, 0x1}, {0x7fff05c69db0, 0x1a}, {0xc00018fd80, 0x1, ...})
	/runner/_work/beam/beam/sdks/python/container/boot.go:412 +0x50b
main.processArtifactsInSetupOnlyMode()
	/runner/_work/beam/beam/sdks/python/container/boot.go:455 +0x51f
main.main()
	/runner/_work/beam/beam/sdks/python/container/boot.go:82 +0x76

Issue Failure

Failure: Test is continually failing

Issue Priority

Priority: 0 (outage / failing precommit test impacting development)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner