Skip to content

Monitor and Update Progress of BackupWorkers#12844

Merged
akankshamahajan15 merged 5 commits intoapple:mainfrom
akankshamahajan15:bk_monitoring
Apr 10, 2026
Merged

Monitor and Update Progress of BackupWorkers#12844
akankshamahajan15 merged 5 commits intoapple:mainfrom
akankshamahajan15:bk_monitoring

Conversation

@akankshamahajan15
Copy link
Copy Markdown
Contributor

@akankshamahajan15 akankshamahajan15 commented Mar 24, 2026

This PR implements:

  1. monitorBackupRangePartitionedProgress which reads the progress of all backup workers and set up backupkeys accordingly.
  2. New file BackupRangePartitionedProgress that has minimal functions needed as of now (because it doesn't need log router stuff and key name and their respective decoding functions will be different).
  3. Complete 'BackupWorkerRangePartitioned' which calls multiple actors like pullAsync, uploadData, shouldExitEarly etc
  4. Add decoding of backupProgressKeys and it's value

Flow:

  1. Each backup worker uses a key in the key range \xff\x02/backupRangePartitionedProgress/
    which is \xff\x02/backupRangePartitionedProgress/

    UID_abc123 is backup worker id
    ┌────────────────────────────── ──┐
    │ FDB System Keyspace (backupRangePartitionedProgressKeys range) |
    │─────────────────────────────────┤
    │ │
    │ Key: \xff\x02/backupRangePartitionedProgress/<UID_abc123> │
    │ Value: {epoch: 5, pop version: 1000000, tag: Tag(-2,0), totalTags: 3} │
    │ ↑ Worker 0 progress │
    │ │
    │ Key: \xff\x02/backupRangePartitionedProgress/<UID_def456> │
    │ Value: {epoch: 5, pop version: 999500, tag: Tag(-2,1), totalTags: 3} │
    │ ↑ Worker 1 progress │
    │ │
    │ Key: \xff\x02/backupRangePartitionedProgress/<UID_ghi789> │
    │ Value: {epoch: 5, pop version: 1001000, tag: Tag(-2,2), totalTags: 3} │
    │ ↑ Worker 2 progress │
    │ │
    └────────────────────────────────┘

  2. Each worker periodically calls saveProgress() to write to the database. Each worker writes it progress (Value) (same for all backups it is handling).

  3. Only Worker 0 calls BackupWorker.monitorBackupRangePartitionedProgress() which further calls BackupRangePartitionedProgress.getBackupRangePartitionedProgress.

  4. BackupProgress.getBackupRangePartitionedProgress:
    a. It reads all the keys and values in tr.getRange(backupRangePartitionedProgressKeys) which is \xff\x02/backupRangePartitionedProgress/ and gets
    a flat list of key value pairs. For ex:

UID_a is backup worker id.

results = [
    		{key: "/progress/UID_a", value: {epoch: 5, version: 1.8M, tag: (-2,0), totalTags: 3}},
    		{key: "/progress/UID_b", value: {epoch: 5, version: 1.7M, tag: (-2,1), totalTags: 3}},
    		{key: "/progress/UID_c", value: {epoch: 5, version: 1.9M, tag: (-2,2), totalTags: 3}},
    		{key: "/progress/UID_d", value: {epoch: 6, version: 2.1M, tag: (-2,0), totalTags: 3}},
    		{key: "/progress/UID_e", value: {epoch: 6, version: 2.0M, tag: (-2,1), totalTags: 3}},
    		{key: "/progress/UID_f", value: {epoch: 6, version: 2.2M, tag: (-2,2), totalTags: 3}}
	    ]


b.  It Iterates over all keys and values, and constructs the progress map for each epoch. For ex:
progress = {
			5: {  // Group all Epoch 5 workers together
				Tag(-2,0): 1.8M,
				Tag(-2,1): 1.7M, 
				Tag(-2,2): 1.9M
			},
			6: {  // Group all Epoch 6 workers together
				Tag(-2,0): 2.1M,
				Tag(-2,1): 2.0M,
				Tag(-2,2): 2.2M
			}
	    }
	bStatus->addBackupStatus(status);
  1. Now BackupWorker calls progress->getEpochStatus(recuitedEpoch) to get the progress of all workers in the recruited epoch.
    For ex:
tagVersions = {
			Tag(-2,0): 1.8M,
			Tag(-2,1): 1.7M, 
			Tag(-2,2): 1.9M
		}
  1. It iterates over all tagVersions and find minimum version backup up among all workers and set the backup keys. according.

@akankshamahajan15 akankshamahajan15 changed the title Monitor and Update Progress [In Progress] Monitor and Update Progress Mar 24, 2026
@foundationdb-ci
Copy link
Copy Markdown
Contributor

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

  • Commit ID: 9e393d1
  • Duration 0:03:25
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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-clang-ide on Linux RHEL 9

  • Commit ID: 9e393d1
  • Duration 0:04:19
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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-clang on Linux RHEL 9

  • Commit ID: 9e393d1
  • Duration 0:04:19
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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: 9e393d1
  • Duration 0:04:27
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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: 9e393d1
  • Duration 0:04:47
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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-macos on macOS Ventura 13.x

  • Commit ID: 9e393d1
  • Duration 0:22:09
  • 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)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

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

  • Commit ID: 9e393d1
  • Duration 0:26:24
  • Result: ❌ FAILED
  • Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /opt/homebrew/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)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

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

  • Commit ID: 26d44d4
  • Duration 0:03:42
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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-clang on Linux RHEL 9

  • Commit ID: 26d44d4
  • Duration 0:04:28
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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: 26d44d4
  • Duration 0:04:33
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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 on Linux RHEL 9

  • Commit ID: 26d44d4
  • Duration 0:04:32
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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-clang-ide on Linux RHEL 9

  • Commit ID: 26d44d4
  • Duration 0:04:30
  • Result: ❌ FAILED
  • Error: Error while executing command: if [[ $(git diff --shortstat 2> /dev/null | tail -n1) == "" ]]; then echo "CODE FORMAT CLEAN"; else echo "CODE FORMAT NOT CLEAN"; echo; echo "THE FOLLOWING FILES NEED TO BE FORMATTED"; echo; git ls-files -m; echo; if [[ $FDB_VERSION =~ 7\.\3. ]]; then echo skip; else exit 1; fi; fi. 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 on macOS Ventura 13.x

  • Commit ID: 26d44d4
  • Duration 0:21:44
  • 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)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

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

  • Commit ID: 26d44d4
  • Duration 0:25:20
  • Result: ❌ FAILED
  • Error: Error while executing command: ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -i ${HOME}/.ssh_key ec2-user@${MAC_EC2_HOST} /opt/homebrew/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)

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux RHEL 9

  • Commit ID: 09f6b13
  • Duration 0:30:20
  • 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-clang-arm on Linux CentOS 7

  • Commit ID: 09f6b13
  • Duration 0:43:27
  • 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 on Linux RHEL 9

  • Commit ID: 09f6b13
  • Duration 1:06:36
  • 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-clang on Linux RHEL 9

  • Commit ID: 09f6b13
  • Duration 1:10:56
  • 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-cluster-tests on Linux RHEL 9

  • Commit ID: 09f6b13
  • Duration 2:13:28
  • 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)
  • Cluster Test Logs zip file of the test logs (available for 30 days)

}
}

Future<Void> backupWorkerRangePartitioned(BackupInterface interf,
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Moved this function to end and added more actors to add like monitorBackupRangePartitionedProgress,
pullAsync, uploadData etc

@akankshamahajan15 akankshamahajan15 changed the title [In Progress] Monitor and Update Progress Monitor and Update Progress of BackupWorkers Mar 26, 2026
@akankshamahajan15 akankshamahajan15 marked this pull request as ready for review March 26, 2026 21:58
@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux RHEL 9

  • Commit ID: cf76e9f
  • Duration 0:24:20
  • 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-clang-arm on Linux CentOS 7

  • Commit ID: cf76e9f
  • Duration 0:43: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-clang on Linux RHEL 9

  • Commit ID: cf76e9f
  • Duration 0:55:00
  • 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 on Linux RHEL 9

  • Commit ID: cf76e9f
  • Duration 0:56:01
  • 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-cluster-tests on Linux RHEL 9

  • Commit ID: cf76e9f
  • Duration 2:01:05
  • 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)
  • Cluster Test Logs zip file of the test logs (available for 30 days)

Copy link
Copy Markdown
Contributor

@saintstack saintstack left a comment

Choose a reason for hiding this comment

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

The writeup on this PR is very nice. Its not in code though or in a doc. Should it be?

What are these <UID_abc123> ? These are the UID and range a backup worker is reponsible for? The start key? Is the UID not enough?

If a backup worker fails to write status, thats ok? The 'progress' is just stale?

Copy link
Copy Markdown
Contributor

@saintstack saintstack left a comment

Choose a reason for hiding this comment

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

Looks good. What is the testing story? Is that in subsequent PRs?

co_return;
}

Future<Void> monitorBackupRangePartitionedProgress(BackupRangePartitionedData* self) {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Ok this runs forever... no cancel?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes. According to current BackupWorker, this function runs continuously.
When backup worker is removed, it throws an error worker_removed()

and in the catch, all actors are cancelled including monitor actor.

const LogEpoch backupEpoch; // the epoch workers should pull mutations
// TODO akanksha: Update oldestBackupEpoch wherever needed.
LogEpoch oldestBackupEpoch = 0; // oldest epoch that still has data on tLogs for backup to pull
// Minimumum known committed version in StorageServers.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: sp

// update progress so far if previous epochs are done.
if (self->recruitedEpoch == self->oldestBackupEpoch) {
Version v = std::numeric_limits<Version>::max();
// Find the version we can gurantee is fully backed up for all backup workers.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: spelling

done = exitEarly ? Void() : uploadData(&self);

while (true) {
auto res = co_await race(dbInfoChange, done, error);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Nice ('race')

Comment thread fdbserver/core/BackupRangePartitionedProgress.cpp Outdated
@akankshamahajan15
Copy link
Copy Markdown
Contributor Author

Looks good. What is the testing story? Is that in subsequent PRs?

Yes, Testing will be done once backup worker completes. Right now it's not integrated. So I'm kind of testing in a hacky way by doing mock servers. But it will be done in later PRs

@akankshamahajan15
Copy link
Copy Markdown
Contributor Author

akankshamahajan15 commented Apr 1, 2026

What are these <UID_abc123> ? These are the UID and range a backup worker is reponsible for? The start key? Is the UID not enough?

UID_abc123 is actually backup_worker id.
Progress shows which worker has backed up upto what version.
Let me change the description of UID.

If a backup worker fails to write status, thats ok? The 'progress' is just stale?
That's a good question. Let me dig deep.

@akankshamahajan15
Copy link
Copy Markdown
Contributor Author

If a backup worker fails to write status, thats ok? The 'progress' is just stale?
If backup worker fails to write status below flow is executed ->

uploadData()
↓ calls
saveMutationsToFile()
↓ calls
if (popVersion > savedVersion) {
co_await saveProgress(self, popVersion); ← Exception thrown here
// ↓
// Exception propagates UP, not DOWN
//
self->savedVersion = ... ← NEVER EXECUTED
self->pop(); ← NEVER EXECUTED
}
↓ Exception continues UP

and goes to backupWorker.
BackupWorker than handles the error based on what kind of error is it.

Comment thread fdbserver/core/BackupRangePartitionedProgress.cpp Outdated
BackupWorkerDoneRequest(self.myId, self.backupEpoch)));
break;
} else if (res.index() != 2) {
UNREACHABLE();
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Does this just assert if any of the actor fails?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes it prints an assertion failure message to stderr and creates a TraceEvent with severity SevError

@foundationdb-ci
Copy link
Copy Markdown
Contributor

Result of foundationdb-pr-clang-ide on Linux RHEL 9

  • Commit ID: 8a179c5
  • Duration 0:23:17
  • 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-m1 on macOS Ventura 13.x

  • Commit ID: 8a179c5
  • Duration 0:35:22
  • 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-clang-arm on Linux CentOS 7

  • Commit ID: 8a179c5
  • Duration 0:44:56
  • 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: 8a179c5
  • Duration 0:47:42
  • 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-clang on Linux RHEL 9

  • Commit ID: 8a179c5
  • Duration 0:53:16
  • 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 on Linux RHEL 9

  • Commit ID: 8a179c5
  • Duration 0:59:49
  • 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-cluster-tests on Linux RHEL 9

  • Commit ID: 8a179c5
  • Duration 2:10:35
  • 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)
  • Cluster Test Logs zip file of the test logs (available for 30 days)

@akankshamahajan15 akankshamahajan15 merged commit 77622b9 into apple:main Apr 10, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants