fixed ctb dbit clock changing period in tests as it was setting run clock instead
All checks were successful
Build on RHEL9 / build (push) Successful in 3m36s
Build on RHEL8 / build (push) Successful in 5m10s

This commit is contained in:
2025-08-04 14:11:51 +02:00
parent 956103bbd4
commit 071b142b10

View File

@@ -1000,7 +1000,7 @@ TEST_CASE("dbitclk", "[.cmdcall]") {
auto det_type = det.getDetectorType().squash(); auto det_type = det.getDetectorType().squash();
if (det_type == defs::CHIPTESTBOARD) { if (det_type == defs::CHIPTESTBOARD) {
auto prev_val = det.getRUNClock(); auto prev_val = det.getDBITClock();
{ {
std::ostringstream oss; std::ostringstream oss;
caller.call("dbitclk", {"20"}, -1, PUT, oss); caller.call("dbitclk", {"20"}, -1, PUT, oss);
@@ -1017,7 +1017,7 @@ TEST_CASE("dbitclk", "[.cmdcall]") {
REQUIRE(oss.str() == "dbitclk 10\n"); REQUIRE(oss.str() == "dbitclk 10\n");
} }
for (int i = 0; i != det.size(); ++i) { for (int i = 0; i != det.size(); ++i) {
det.setRUNClock(prev_val[i], {i}); det.setDBITClock(prev_val[i], {i});
} }
} else { } else {
// clock index might work // clock index might work