Skip to content
Continuous Benchmark (PR)

[BE] No warning if user sets the log_prob_key explicitly and only one variable is sampled from the ProbTDMod #2723

Sign in to view logs

[BE] No warning if user sets the log_prob_key explicitly and only one variable is sampled from the ProbTDMod

[BE] No warning if user sets the log_prob_key explicitly and only one variable is sampled from the ProbTDMod #2723

Triggered via pull request February 5, 2025 11:44
@vmoensvmoens
synchronize #1209
gh/vmoens/47/head
Status Cancelled
Total duration 2m 58s
Artifacts –

benchmarks_pr.yml

on: pull_request
CPU Pytest benchmark
2m 32s
CPU Pytest benchmark
GPU Pytest benchmark
0s
GPU Pytest benchmark
Fit to window
Zoom out
Zoom in

Annotations

3 errors
GPU Pytest benchmark
Canceling since a higher priority waiting request for 'Continuous Benchmark (PR)-ci-refs/pull/1209/merge' exists
CPU Pytest benchmark
Canceling since a higher priority waiting request for 'Continuous Benchmark (PR)-ci-refs/pull/1209/merge' exists
CPU Pytest benchmark
The operation was canceled.