ci(gevent): improve ddtrace-run test assertion message

[brettlangdon]

This job can fail with exit code -11, but no additional context is provided, likely because there isn't anything on stderr ?

This updates the job to output stderr and stdout when the resulting process signal is not 0.

I was unable to reproduce the issue locally, so this is an attempt to collect more data when it fails on CI.

Example failure:

>       assert p.returncode == 0, stderr.decode()
E       AssertionError: 
E       assert -11 == 0
E        +  where -11 = <subprocess.Popen object at 0x7f3144d97eb0>.returncode

Checklist

• PR author has checked that all the criteria below are met
• The PR description includes an overview of the change
• The PR description articulates the motivation for the change
• The change includes tests OR the PR description describes a testing strategy
• The PR description notes risks associated with the change, if any
• Newly-added code is easy to change
• The change follows the library release note guidelines
• The change includes or references documentation updates if necessary
• Backport labels are set (if applicable)

Reviewer Checklist

• Reviewer has checked that all the criteria below are met
• Title is accurate
• All changes are related to the pull request's stated goal
• Avoids breaking API changes
• Testing strategy adequately addresses listed risks
• Newly-added code is easy to change
• Release note makes sense to a user of the library
• If necessary, author has acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[github-actions]

CODEOWNERS have been resolved as:

tests/contrib/gevent/test_tracer.py                                     @DataDog/apm-core-python @DataDog/apm-idm-python
tests/contrib/suitespec.yml                                             @DataDog/apm-core-python @DataDog/apm-idm-python

[pr-commenter]

Benchmarks

Benchmark execution time: 2024-12-17 16:01:44

Comparing candidate commit 5aa0c37 in PR branch brettlangdon/improve.assertion with baseline commit a4f0e38 in branch main.

Found 0 performance improvements and 0 performance regressions! Performance is the same for 394 metrics, 2 unstable metrics.

[sanchda]

11 is a segfault--do we have crashtracking?

[brettlangdon]

11 is a segfault--do we have crashtracking?

Let me check again, it should be enabled by default with ddtrace-run, I was surprised to not find it.

[brettlangdon]

I also updated this job to have it not use the test agent.