You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue was imported from the GSFC issue tracking system
Imported from: [GSFCCFS-1784] CF test incorrect initialization of "dummy_channel" pipe ID Originally submitted by: Hickey, Joseph P. (GSFC-582.0)[VANTAGE SYSTEMS INC] on Tue Nov 16 17:22:51 2021
Original Description:
These three tests utilize a "dummy_channel" structure:
These are calling Any_uint8() and assigning that value to to the pipe member of the structure. However on Caelum the Pipe IDs are actually 32 bits like other IDs (not 8) and when using strict ID types, this assignment will (correctly) fail with a compiler error as being invalid.
The test needs to be explicit that it is intentionally using an integer as a made-up PipeID and needs to use the conversion macro do to so.
The text was updated successfully, but these errors were encountered:
Correct the pipe ID assignment in UT to use the resourceID type.
This also uses a fixed/consistent value here, rather than a random
value. There is no real need to use a random value.
jphickey
added a commit
to jphickey/CF
that referenced
this issue
Dec 1, 2021
Correct the pipe ID assignment in UT to use the resourceID type.
This also uses a fixed/consistent value here, rather than a random
value. There is no real need to use a random value.
This issue was imported from the GSFC issue tracking system
Imported from: [GSFCCFS-1784] CF test incorrect initialization of "dummy_channel" pipe ID
Originally submitted by: Hickey, Joseph P. (GSFC-582.0)[VANTAGE SYSTEMS INC] on Tue Nov 16 17:22:51 2021
Original Description:
These three tests utilize a "dummy_channel" structure:
These are calling
Any_uint8()
and assigning that value to to thepipe
member of the structure. However on Caelum the Pipe IDs are actually 32 bits like other IDs (not 8) and when using strict ID types, this assignment will (correctly) fail with a compiler error as being invalid.The test needs to be explicit that it is intentionally using an integer as a made-up PipeID and needs to use the conversion macro do to so.
The text was updated successfully, but these errors were encountered: