Fix for PVA links to set UTAG/userTag when link is set with TIME=-2

Added test case for PVA link with 'time:true' and checked if cached timestamp and userTag/UTAG are propagated

Convert snap_tag to uint32_t to avoid sign extension. Modified test case
to cover this scenario.
This commit is contained in:
Joao Paulo Martins authored and Michael Davidsaver committed 2026-06-03 16:26:48 -07:00
1 parent bf90ac6bec
commit 26961de931
5 files changed
+78 -6

No files matched your search

+3 -3
View File
@@ -56,7 +56,7 @@ void forceUTAG(const char *rec)
{
dbCommon *prec = testdbRecordPtr(rec);
dbScanLock(prec);
#ifdef DBR_UTAG
#if DBR_UTAG
prec->utag = 42;
#endif
dbScanUnlock(prec);
@@ -64,7 +64,7 @@ void forceUTAG(const char *rec)
void checkUTAG(Value& v, int32_t expect=42)
{
#ifdef DBR_UTAG
#if DBR_UTAG
auto utag = v["timeStamp.userTag"];
if(!utag.isMarked() || utag.as<int32_t>()!=expect)
testFail("userTag not set");
@@ -278,7 +278,7 @@ void testGetScalar()
forceUTAG("test:nsec"); // forced value should be ignored
val = ctxt.get("test:nsec").exec()->wait(5.0);
#ifdef DBR_UTAG
#if DBR_UTAG
testFldEq(val, "timeStamp.userTag", 142);
val["timeStamp.userTag"].unmark();
#else