Golang tests are not reported

[epot]

I am trying to move away from our custom junit tests reporting in favor of orchestrion, but I didn't manage to make it work.
I am pretty sure I am doing something wrong, but here is a snippet of my gh workflow:

    - name: Install dep
      run: |
        go install github.com/DataDog/orchestrion@v1.9.0
      shell: bash

    - name: Configure Datadog Test Optimization
      uses: datadog/test-visibility-github-action@ef8406bf5f987037fcbe3bf8ecf023f5dd1f9e36 # v2.8.0
      with:
        languages: go
        api_key: ${{ secrets.DD_API_KEY }}
        site: datadoghq.com # Change if your site is not US1

    - name: Test
      run: |
         # this uses a golang script that ends up calling `go test` at some point

I don't see anything in Datadog. When is the test upload supposed to happen exactly? In the cleanup of "Configure Datadog Test Optimization"? Can I turn on verbose logs to figure it out?

[tonyredondo]

Hey @epot , you don't need to install orchestrion first, everything should get resolved by the action, I recommend you to comment this step. Can you add DD_TRACE_DEBUG: true as environment variable in the Test step? Also, it would be awesome if you can share some logs to debug the issue.

[epot]

All good, it was because I was messing with GO_FLAGS. Small question though: I see this in the test logs:

2026/04/28 09:02:08 Datadog Tracer v2.7.3 WARN: civisibility: failed to fetch head commit data for 58333c014642f92435ccf903d7fa4c99f979333e: civisibility.fetchCommitData: error: exit status 128
fatal: could not read Username for 'https://github.com/': No such device or address

What can I do to get rid of it? What feature am I missing?

[epot]

Oh and I am sorry if I am not using the right channel, so feel free to redirect me, but another question: we were adding manually tags in the junit xml to add context for each individual test. Is there a way to do that with orchestrion?
And the last issue that we have is that orchestrion does not seem to forward/attach logs to the test, which we really want (and had with junit reports).

[tonyredondo]

Hi, I’ll look into that warning. It’s the first time I’ve seen this message.

Regarding adding tags with Orchestrion, there is currently no way to enrich tests with custom tags.

For logs, there is an experimental environment variable, DD_CIVISIBILITY_LOGS_ENABLED, that enables log collection when set to true or 1. Please note that enabling this may affect billing, since it generates usage in the Logs product. That’s why it is disabled by default.

[epot]

ok @tonyredondo do you know if adding tags is going to be prioritized? We run the same test with different environment variables that tweak the underlying behavior, so we really need to be able to do something to make the distinction in the UI.
I'll test out the logs flag, thanks!

[epot]

Out of curiosity, do you know if the tagging thing is going to be addressed? I would love to migrate but we can't without it.

[epot]

@tonyredondo I think we are good with tags, I am using DD_TAGS as mentioned here.
However I tried playing with DD_CIVISIBILITY_LOGS_ENABLED and I don't see any logs. Anything I could enable to troubleshoot?

[tonyredondo]

Good, I'm glad you solved the issue by using custom configurations.
for the logs feature, can you do a test run with DD_TRACE_DEBUG=1 environment variable and share with me the debug logs output, I want to check that we were able to collect the logs in the first place. If everything is ok in the runner side then we might need to create an index in the logs product to make sure we are retaining those logs.

[epot]

I shared some output with you on DD community slack.