Skip to content

(experimental, do_not_merge) Move delay to dispatch loop v2#12879

Closed
spraza wants to merge 5 commits into
apple:release-7.3from
spraza:move-delay-to-dispatch-loop-v2
Closed

(experimental, do_not_merge) Move delay to dispatch loop v2#12879
spraza wants to merge 5 commits into
apple:release-7.3from
spraza:move-delay-to-dispatch-loop-v2

Conversation

@spraza
Copy link
Copy Markdown
Collaborator

@spraza spraza commented Mar 27, 2026

20260327-012409-praza-d5ee1f25e932001c             compressed=True data_size=35184776 duration=13676211 ended=500000 fail=40 fail_fast=50 max_runs=500000 pass=499960 priority=100 remaining=0 runtime=10:07:28 sanity=False started=500000 stopped=20260327-113137 submitted=20260327-012409 timeout=5400 username=praza

Failure categories:

  1. invalid_tuple_data_type (2250) - from_7.3.50 restart tests, 35 occurrences
  2. invalid_tuple_index (2251) - to_7.3.0/CycleTestRestart-2, 2 occurrences
  3. RocksDB MANIFEST corruption, SIGABRT - UpgradeAndBackupRestore-2, ClientTransactionProfilingCorrectness-2
  4. timed_out (1004) - fast/PrivateEndpoints, 1 occurrence

(1) and (2) were fixed in #12324 and possibly #12283. These PRs were merged after 7.3.69, causing 7.3.69 baseline to be noisy. This covers 37/40 failures.

(3) is a known issue, due to a rocksdb bug. See #12690. This fix is not present in 7.3.69. This covers 2/40 failures.

(4) is something I'm investigating. The test itself has to do with request authorization, etc., unrelated to DD. But I am not 100% that the error is related. Will debug. This is the last 1/40 of the failures.

Update on (4): does not related to this change.

So overall, don't think any of the 40 failures here are related to this change.


Follow-up to this is: #12880, with these changes:

  • change to 0.1 delay
  • cherry-pick some commits that were merged after 7.3.69, so that noise is reduced in simulation results

Code-Reviewer Section

The general pull request guidelines can be found here.

Please check each of the following things and check all boxes before accepting a PR.

  • The PR has a description, explaining both the problem and the solution.
  • The description mentions which forms of testing were done and the testing seems reasonable.
  • Every function/class/actor that was touched is reasonably well documented.

For Release-Branches

If this PR is made against a release-branch, please also check the following:

  • This change/bugfix is a cherry-pick from the next younger branch (younger release-branch or main if this is the youngest branch)
  • There is a good reason why this PR needs to go into a release branch and this reason is documented (either in the description above or in a linked GitHub issue)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-arm on Linux CentOS 7

  • Commit ID: aef3a59
  • Duration 0:04:18
  • Result: ❌ FAILED
  • Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-cluster-tests on Linux RHEL 9

  • Commit ID: aef3a59
  • Duration 0:08:06
  • Result: ❌ FAILED
  • Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)
  • Cluster Test Logs zip file of the test logs (available for 30 days)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang on Linux RHEL 9

  • Commit ID: aef3a59
  • Duration 0:08:32
  • Result: ❌ FAILED
  • Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr on Linux RHEL 9

  • Commit ID: aef3a59
  • Duration 0:08:36
  • Result: ❌ FAILED
  • Error: Error while executing command: ninja -v -C build_output -j ${NPROC} all packages strip_targets. Reason: exit status 1
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-macos-m1 on macOS Ventura 13.x

  • Commit ID: aef3a59
  • Duration 0:38:41
  • Result: ✅ SUCCEEDED
  • Error: N/A
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-macos on macOS Ventura 13.x

  • Commit ID: aef3a59
  • Duration 0:39:31
  • Result: ❌ FAILED
  • Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /usr/local/bin/bash --login -c ./build_pr_macos.sh. Reason: exit status 1
  • Build Log terminal output (available for 30 days)
  • Build Workspace zip file of the working directory (available for 30 days)

Copy link
Copy Markdown
Collaborator

@gxglass gxglass left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine trying this out

Copy link
Copy Markdown
Collaborator

@gxglass gxglass left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(...)

@spraza spraza closed this Apr 6, 2026
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.

4 participants