<@UB89GSWCF> I'm seeing different PRs fail on the ...
# atmos-dev
e
@Andriy Knysh (Cloud Posse) I'm seeing different PRs fail on the same test:
Copy code
=== RUN   TestDescribeComponentWithOverridesSection
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x104d2fb78]

goroutine 350 [running]:
github.com/cloudposse/atmos/pkg/merge.Merge(0x1081e4950?, {0x14001f53a60?, 0x1062ed7b2?, 0xaa?})
	/Users/runner/work/atmos/atmos/pkg/merge/merge.go:85 +0xa8
github.com/cloudposse/atmos/internal/exec.ProcessYAMLConfigFile(0x14001e1f988, {0x14001ecd020, 0x56}, {0x140013e63cf, 0x6a}, 0x14001dea000, 0x0, 0x0, 0x0, 0x0, ...)
	/Users/runner/work/atmos/atmos/internal/exec/stack_processor_utils.go:323 +0x10b4
github.com/cloudposse/atmos/internal/exec.ProcessYAMLConfigFiles.func1(0x2, {0x140013e63cf, 0x6a})
	/Users/runner/work/atmos/atmos/internal/exec/stack_processor_utils.go:76 +0x2fc
created by github.com/cloudposse/atmos/internal/exec.ProcessYAMLConfigFiles in goroutine 322
	/Users/runner/work/atmos/atmos/internal/exec/stack_processor_utils.go:61 +0xf8
FAIL	github.com/cloudposse/atmos/internal/exec	22.577s
a
looks there were some issues with the GitHub runners, the jobs were "randomly" failing. today everything is OK, both PRs are approved and merged