teor

fix(ci): Limit checkpoint and lwd full sync concurrency

1

## Motivation After PR #5393, we'll have 3 long jobs that only run on the `main` branch. We only want to run one of each of these jobs at a...

change(state): Add block channel metrics, in preparation for block fork metrics

3

## Motivation These metrics are part of #5297, but we also needed them to diagnose bugs in PR #5257. This is a low-risk change that is not a release blocker....

## Motivation Currently, the send transactions test is very slow, because it: - copies the entire Zebra finalized state directory - syncs to the tip - gets transactions from the...

Consider using `nextest` to run tests faster and reduce Google Cloud costs

2

## Motivation `cargo nextest` runs more Rust tests in parallel, making tests faster, and making better use of CI machine CPUs. We might want to use it to reduce Google...

## Motivation I'm seeing errors like this in CI: > - The resource 'projects/zealous-zebra/zones/us-central1-a/instances/update-to-tip-5360-merge-818a593' was not found https://github.com/ZcashFoundation/zebra/actions/runs/3203311358/jobs/5239744583#step:6:101 ### Command Reference https://cloud.google.com/sdk/gcloud/reference/topic/filters ### Designs I'm not sure what is causing...

Only run the `lightwalletd` full sync on the `main` branch

4

## Motivation In PR #5164, we made `lightwalletd` sync all the way to the tip in its full sync test. This increases that test's time from 1 hour to 4...

Fix parameter download hangs with Rust 1.64

15

## Scheduling This is only a release blocker if it is a miscompile or denial of service. If we find out it is something else, we can fix it after...

Make file locations appear in zebrad Docker error messages

2

## Motivation When Zebra's Rust test harness fails in CI, I can't see the file and line in the panic backtrace: ``` 12: zebra_test::command::TestChild::expect_stdout_line_matches::h471f18611d79fb45 at : 13: acceptance::lightwalletd_integration_test::h1e497ff748a26c03 at :...

Occasional local_listener_fixed_port_localhost_addr_v4 failure

2

## Motivation The `peer_set::initialize::tests::vectors::local_listener_fixed_port_localhost_addr_v4` test failed once on the `main` branch with: > proptest: If this test was run on a CI system, you may wish to add the following...

Write up how we want to do audit tags, audit branches, and feature branches

1

## Motivation We want to document the process we decided for audits and new features. We also want to write down the goals we're trying to satisfy. The draft notes...