I'm running a (Kotlin) build that the build discovery receives an OOM on. I'm seeing it then detect that but (it appears) simultaneously start two more build discovery pipelines:
{"level":"info","ts":"2024-03-19T08:09:58Z","logger":"dependencybuild","caller":"dependencybuild/dependencybuild.go:206","msg":"running build discovery with 0 additional memory","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:09:58Z","logger":"dependencybuild","caller":"util/util.go:74","msg":"GetImageName controller image quay.io/ncross/hacbs-jvm-controller:dev","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:09:58Z","logger":"dependencybuild","caller":"jbsconfig/jbsconfig.go:647","msg":"Parsing sharedRegistry list []v1alpha1.ImageRegistry(nil)\n","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:14:12Z","logger":"dependencybuild","caller":"dependencybuild/dependencybuild.go:297","msg":"build discovery failed due to memory issues","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8-build-discovery-0","kind":"PipelineRun"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"dependencybuild/dependencybuild.go:206","msg":"running build discovery with 2048 additional memory","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"util/util.go:74","msg":"GetImageName controller image quay.io/ncross/hacbs-jvm-controller:dev","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"jbsconfig/jbsconfig.go:647","msg":"Parsing sharedRegistry list []v1alpha1.ImageRegistry(nil)\n","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"dependencybuild/dependencybuild.go:297","msg":"build discovery failed due to memory issues","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8-build-discovery-0","kind":"PipelineRun"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"dependencybuild/dependencybuild.go:206","msg":"running build discovery with 4096 additional memory","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"util/util.go:74","msg":"GetImageName controller image quay.io/ncross/hacbs-jvm-controller:dev","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
{"level":"info","ts":"2024-03-19T08:14:13Z","logger":"dependencybuild","caller":"jbsconfig/jbsconfig.go:647","msg":"Parsing sharedRegistry list []v1alpha1.ImageRegistry(nil)\n","namespace":"test-jvm-namespace","resource":"9b460fd90f9af5ea4ef79dc9d7b300a8","kind":"DependencyBuild","db-scm-url":"https://github.com/JetBrains/kotlin.git","db-scm-tag":"v1.7.22"}
This might be similar to #8 in that the same underlying change may need to be rexamined.
I'm running a (Kotlin) build that the build discovery receives an OOM on. I'm seeing it then detect that but (it appears) simultaneously start two more build discovery pipelines:
This might be similar to #8 in that the same underlying change may need to be rexamined.