On the PMRS Jenkins, build-pulse nightly runs have been consistently failing due to timeouts while querying run information. This also occurs on the experimental async-db branch which refactored much of the API query logic to be async stream based, meaning it's likely unrelated to the number of queries done in parallel. Sometimes the request goes through, so I've been thinking that the timeout may be too aggressive given we're querying a significant amount of information in one request. More work is needed to determine the root cause, however.
+ ./target/release/build-pulse -o report.html
[2026-01-12T16:07:12Z INFO build_pulse] build-pulse 0.1.0
[2026-01-12T16:07:12Z INFO build_pulse] Compiling issue patterns...
[2026-01-12T16:07:12Z INFO build_pulse] Opening database...
[2026-01-12T16:07:12Z INFO build_pulse] Updating tags...
[2026-01-12T16:07:12Z INFO build_pulse] Pulling associated jobs for mpich-main-nightly from https://jenkins-pmrs.cels.anl.gov/...
[2026-01-12T16:07:12Z INFO build_pulse] Pulling build info for each job...
[2026-01-12T16:07:12Z INFO build_pulse] ----------------------------------------
Error: error sending request for url (https://jenkins-pmrs.cels.anl.gov/view/mpich-main-nightly/api/json?tree=jobs%5Bname%2Curl%2Cbuilds%5Bnumber%2Curl%2CdisplayName%2Ctimestamp%2Cresult%2Cruns%5Burl%2Cnumber%5D%5D%5D)
Caused by:
operation timed out
On the PMRS Jenkins,
build-pulsenightly runs have been consistently failing due to timeouts while querying run information. This also occurs on the experimentalasync-dbbranch which refactored much of the API query logic to be async stream based, meaning it's likely unrelated to the number of queries done in parallel. Sometimes the request goes through, so I've been thinking that the timeout may be too aggressive given we're querying a significant amount of information in one request. More work is needed to determine the root cause, however.