0Successfully parsed console log-> found 1 issue (skipped 0 duplicates)Parsing console log (workspace: '/var/jenkins/workspace/ArborX_nightly')Post processing issues on 'CPU_Node_06' with source code encoding 'UTF-8'Creating SCM blamer to obtain author and commit information for affected files-> No blamer installed yet. You need to install the 'git-forensics' plugin to enable blaming for Git.Resolving file names for all issues in workspace '/var/jenkins/workspace/ArborX_nightly'-> none of the issues requires resolving of pathsResolving module names from module definitions (build.xml, pom.xml, or Manifest.mf files)-> resolved module names for 1 issuesResolving package names (or namespaces) by parsing the affected files-> resolved package names of 1 affected filesApplying 2 filters on the set of 1 issues (0 issues have been removed, 1 issues will be published)Creating fingerprints for all affected code blocks to track issues over different builds-> created fingerprints for 0 issues (skipped 1 issues)Copying affected files to Jenkins' build folder '/var/jenkins_home/jobs/ArborX_nightly/builds/992/files-with-issues'-> 0 copied, 0 not in workspace, 1 not-found, 0 with I/O errorSkipping cleaning of source code files in old buildsRepository miner is not configured, skipping repository miningReference build recorder is not configuredNo valid reference build foundAll reported issues will be considered outstandingEvaluating quality gates-> Some quality gates have been missed: overall result is UNSTABLE-> Details for each quality gate: - [Total (any severity)]: ≪Unstable≫ - (Actual value: 1, Quality gate: 1.00)Health report is disabled - skippingCreated analysis result for 1 issues (found 0 new issues, fixed 0 issues)Attaching ResultAction with ID 'cmake' to build 'ArborX_nightly #992'.0-1Started by timer0008257457242803621.66556992f804f078c9aefedfa9eed6127a5e6e9fb169f53bf804f078c9aefedfa9eed6127a5e6e9fb169f53brefs/remotes/origin/masterf804f078c9aefedfa9eed6127a5e6e9fb169f53bf804f078c9aefedfa9eed6127a5e6e9fb169f53brefs/remotes/origin/masterf804f078c9aefedfa9eed6127a5e6e9fb169f53bf804f078c9aefedfa9eed6127a5e6e9fb169f53brefs/remotes/origin/masterhttps://github.com/arborx/ArborX00116testReportfalse#99225745722599033ArborX_nightly #992992false99260901FAILURE1792125170756https://cloud1.cees.ornl.gov/jenkins-ci/job/ArborX_nightly/992/- src/spatial/ArborX_LinearBVH.hppsrc/spatial/detail/ArborX_CrsGraphWrapperImpl.hpp4d8ac6687b56a32f5b7a0fae6dedceffb7f5734f1791993980000https://cloud1.cees.ornl.gov/jenkins-ci/user/aprokopAndrey Prokopenkoandrey.prok@gmail.comAvoid computations in BVH for emptry tree
Besides improving performance, this also fixes floating point exception.
We use tree's bounding box to project predicates onto space filling
curve. For the empty tree, the box is invalid, so the projection does
not make sense. Moreover, the projection may result in floating point
exception in translateAndScale
auto const a = ref.minCorner()[d]; // 3.40282347e+38
auto const b = ref.maxCorner()[d]; // -3.40282347e+38
// in[d] - a = -3.40282347e+38
// b - a = -inf -> FE_OVERFLOW
// out[0] = -3.40282347e+38 / -inf = 0
out[d] = (a != b ? (in[d] - a) / (b - a) : 0);
2026-10-14 12:06:20 -04004d8ac6687b56a32f5b7a0fae6dedceffb7f5734fAvoid computations in BVH for emptry treeeditsrc/spatial/ArborX_LinearBVH.hppeditsrc/spatial/detail/ArborX_CrsGraphWrapperImpl.hpp
- test/utf_main.cpp896606194cec9f895f405fce16269a579374244e1791993980000https://cloud1.cees.ornl.gov/jenkins-ci/user/aprokopAndrey Prokopenkoandrey.prok@gmail.comAdd more exception checks in the tests
2026-10-14 12:06:20 -0400896606194cec9f895f405fce16269a579374244eAdd more exception checks in the testsedittest/utf_main.cpp
githttps://cloud1.cees.ornl.gov/jenkins-ci/user/aprokopAndrey Prokopenkohttps://cloud1.cees.ornl.gov/jenkins-ci/user/masterleinadDaniel Arndthttps://cloud1.cees.ornl.gov/jenkins-ci/user/noreplynoreplyfalse993https://cloud1.cees.ornl.gov/jenkins-ci/job/ArborX_nightly/993/991https://cloud1.cees.ornl.gov/jenkins-ci/job/ArborX_nightly/991/WARNINGTotal (any severity)UNSTABLE1.01-11