Skip to content
Python Integration

Fix NaN upper-bound check in strict metrics NotIn #5563

Sign in to view logs

Fix NaN upper-bound check in strict metrics NotIn

Fix NaN upper-bound check in strict metrics NotIn #5563

Triggered via pull request September 7, 2026 20:11
@ptimizeroracleptimizeroracle
opened #3921
ptimizeroracle:fix/strict-not-in-nan-upper-bound
Status Cancelled
Total duration 5m 54s
Artifacts 3

python-integration.yml

on: pull_request
integration-test
5m 44s
integration-test
integration-test-s3
1m 7s
integration-test-s3
integration-test-adls
1m 22s
integration-test-adls
integration-test-gcs
1m 6s
integration-test-gcs
integration-coverage-report
0s
integration-coverage-report
python-integration-required
4s
python-integration-required
Fit to window
Zoom out
Zoom in

Annotations

4 errors
integration-test
Canceling since a higher priority waiting request for Python Integration-refs/pull/3921/merge exists
integration-test
The operation was canceled.
python-integration-required
Process completed with exit code 1.
Python Integration
Canceling since a higher priority waiting request for Python Integration-refs/pull/3921/merge exists

Artifacts

Produced during runtime
Name Size Digest
coverage-adls
8.49 KB
sha256:00981c88a31e4d1433acfc300fbc50813c2115caadae4a4402647c97290c6e52
coverage-gcs
8.49 KB
sha256:76d6ac0b4f535d452b28c463a20bc9ca3b9877636cfbac2ef6481fd7f889a3b7
coverage-s3
8.48 KB
sha256:144b6590473e170db2c22c8e863122e5dbd1d6209945d6b410d54aae6ae2ec50