Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Make some fixes to logging in PVF subsystem #6180

Merged
merged 3 commits into from
Oct 26, 2022
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Log exit status code for workers
  • Loading branch information
mrcnski committed Oct 23, 2022
commit 39879c5219a60734a4ddd97339dc1734ec550fcc
2 changes: 1 addition & 1 deletion node/core/pvf/src/execute/queue.rs
Original file line number Diff line number Diff line change
Expand Up @@ -244,7 +244,7 @@ fn handle_job_finish(
};

queue.metrics.execute_finished();
gum::debug!(
gum::trace!(
target: LOG_TARGET,
validation_code_hash = ?artifact_id.code_hash,
worker_rip = idle_worker.is_none(),
Expand Down
2 changes: 1 addition & 1 deletion node/core/pvf/src/executor_intf.rs
Original file line number Diff line number Diff line change
Expand Up @@ -129,7 +129,7 @@ impl Executor {
// 2. It cannot and does not limit the stack space consumed by Rust code.
//
// Meaning that if the wasm code leaves no stack space for Rust code, then the Rust code
// and that will abort the process as well.
// will abort and that will abort the process as well.
//
// Typically on Linux the main thread gets the stack size specified by the `ulimit` and
// typically it's configured to 8 MiB. Rust's spawned threads are 2 MiB. OTOH, the
Expand Down
18 changes: 15 additions & 3 deletions node/core/pvf/src/worker_common.rs
Original file line number Diff line number Diff line change
Expand Up @@ -200,7 +200,7 @@ pub enum SpawnErr {
/// This is a representation of a potentially running worker. Drop it and the process will be killed.
///
/// A worker's handle is also a future that resolves when it's detected that the worker's process
/// has been terminated. Since the worker is running in another process it is obviously not necessarily
/// has been terminated. Since the worker is running in another process it is obviously not necessary
/// to poll this future to make the worker run, it's only for termination detection.
///
/// This future relies on the fact that a child process's stdout `fd` is closed upon it's termination.
Expand All @@ -209,6 +209,7 @@ pub struct WorkerHandle {
child: async_process::Child,
#[pin]
stdout: async_process::ChildStdout,
program: PathBuf,
drop_box: Box<[u8]>,
}

Expand All @@ -233,6 +234,7 @@ impl WorkerHandle {
Ok(WorkerHandle {
child,
stdout,
program: program.as_ref().to_path_buf(),
// We don't expect the bytes to be ever read. But in case we do, we should not use a buffer
// of a small size, because otherwise if the child process does return any data we will end up
// issuing a syscall for each byte. We also prefer not to do allocate that on the stack, since
Expand Down Expand Up @@ -267,9 +269,19 @@ impl futures::Future for WorkerHandle {
cx.waker().wake_by_ref();
Poll::Pending
},
Err(_) => {
Err(err) => {
// The implementation is guaranteed to not to return `WouldBlock` and Interrupted. This
// leaves us with a legit errors which we suppose were due to termination.
// leaves us with legit errors which we suppose were due to termination.

// Log the status code.
gum::debug!(
target: LOG_TARGET,
worker_pid = %me.child.id(),
status_code = ?me.child.try_status(),
"pvf worker ({}): {:?}",
me.program.display(),
err,
);
Poll::Ready(())
},
}
Expand Down