Skip to content

fix(ci): skip base_service Valgrind leak and xfail OpenSSL SNI tests#3772

Open
Leiyks wants to merge 9 commits intomasterfrom
leiyks/fix-ci-valgrind-and-openssl-xfail
Open

fix(ci): skip base_service Valgrind leak and xfail OpenSSL SNI tests#3772
Leiyks wants to merge 9 commits intomasterfrom
leiyks/fix-ci-valgrind-and-openssl-xfail

Conversation

@Leiyks
Copy link
Copy Markdown
Contributor

@Leiyks Leiyks commented Apr 3, 2026

Summary

  • tests/ext/base_service.phpt: add --SKIPIF-- to skip under Valgrind (USE_TRACKED_ALLOC=1). The test has a memory leak on PHP 7.0 that causes test_extension_ci: [7.0] to fail via the leaked-test check in the Makefile.
  • dockerfiles/ci/xfail_tests/*.list (7.0, 7.2–8.5): add sni_server.phpt, sni_server_key_cert.phpt, and bug74796.phpt. These are loopback TLS tests that do not check SKIP_ONLINE_TESTS and fail due to CI pod networking producing flakiness. PHP 7.1 already had sni_server.phpt xfailed; this extends coverage to all other versions.

Test plan

  • test_extension_ci: [7.0] Valgrind pass no longer reports leaked test
  • PHP Language Tests (all versions) no longer fail on OpenSSL SNI tests

Leiyks added 3 commits April 3, 2026 13:04
…ci [7.0]

The test has a memory leak under Valgrind on PHP 7.0 that causes
the Makefile's leaked-test check to fail. Skip it during the
Valgrind pass (USE_TRACKED_ALLOC=1) to unblock CI.
sni_server.phpt, sni_server_key_cert.phpt, and bug74796.phpt are
loopback TLS tests that do not check SKIP_ONLINE_TESTS and fail when
CI pod networking does not support SNI loopback connections. PHP 7.1
already had sni_server.phpt xfailed; add all three for 7.0 and 7.2+.
@datadog-official
Copy link
Copy Markdown

datadog-official bot commented Apr 3, 2026

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
Patch Coverage: 100.00%
Overall Coverage: 60.69% (+0.01%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 732de87 | Docs | Datadog PR Page | Was this helpful? React with 👍/👎 or give us feedback!

@Leiyks Leiyks marked this pull request as ready for review April 3, 2026 11:20
@Leiyks Leiyks requested a review from a team as a code owner April 3, 2026 11:20
bwoebi and others added 4 commits April 3, 2026 13:30
Signed-off-by: Bob Weinand <bob.weinand@datadoghq.com>
…ice leak

Set DD_SPAWN_WORKER_STABLE_TRAMPOLINE=1 in the test_extension_ci Valgrind
pass so the sidecar spawn_worker writes the trampoline to a stable per-
process path instead of a random temp file that gets self-deleted before
Valgrind can read it.

Updates libdatadog to DataDog/libdatadog#1844.
@Leiyks Leiyks requested review from a team as code owners April 3, 2026 15:26
Leiyks added 2 commits April 3, 2026 17:31
…chema

- runtime_stack moved to message.experimental.runtime_stack
- new error block with native crash stack (Datadog Crashtracker 1.0 format)
- data_schema_version bumped to 1.6
- signal message changed to "Process terminated with SI_USER (SIGSEGV)"
@pr-commenter
Copy link
Copy Markdown

pr-commenter bot commented Apr 3, 2026

Benchmarks [ tracer ]

Benchmark execution time: 2026-04-03 20:39:46

Comparing candidate commit 732de87 in PR branch leiyks/fix-ci-valgrind-and-openssl-xfail with baseline commit 5bc467b in branch master.

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

scenario:MessagePackSerializationBench/benchMessagePackSerialization

  • 🟩 execution_time [-5.080µs; -3.480µs] or [-4.728%; -3.239%]

scenario:MessagePackSerializationBench/benchMessagePackSerialization-opcache

  • 🟩 execution_time [-5.973µs; -4.787µs] or [-5.409%; -4.334%]

scenario:PDOBench/benchPDOOverhead

  • 🟥 execution_time [+5.997µs; +8.448µs] or [+2.495%; +3.515%]

scenario:PDOBench/benchPDOOverheadWithDBM

  • 🟥 execution_time [+6.171µs; +8.907µs] or [+2.564%; +3.701%]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants