Simulated PXIe-4322 overcurrent is not consistent
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 592
- Forks
- 199
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 10
Description
Bug Report
These tests (tests/component/task/test_out_stream_write_properties.py) use a simulated PXIe-4322 ("aoTester") to validate basic functionality of runtime-checked attributes.
test___ao_current_task___get_bool_property___returns_default_valuetest___ao_current_task___get_string_list_property___returns_default_value
We assume it will always return false (and therefore an empty set of channels), but that doesn't appear to be the case. I looked at the driver code and this goes all the way to the primitive even on simulated devices. It checks if an interrupt occurred or if a register is set. On a simulated device, that register value is random memory and seems like it can indicate a flipped bit.
Repro or Code Sample
Run the component tests and get (un)lucky.
Expected Behavior
This shouldn't be intermittent.
Current Behavior
It is intermittent, but thankfully quite rare.
Possible Solution
We either need to find a new device that we know is consistent or mayb disable these tests.
Context
This run failed on only a single OS for those tests, but consistently. This was for #831 . I am going to queue another one.
Your Environment
- Operating system and version: [e.g. Windows 11 24H2, Ubuntu Linux 24.04]
- NI-DAQmx version: [e.g. 2024 Q4]
nidaqmx-pythonversion: [e.g. 1.0.1]- Python version [e.g. 3.9]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with tests/component/task/test_out_stream_write_properties.py and the two named runtime-checked attribute tests. Run the component tests using the simulated PXIe-4322 ("aoTester") to reproduce the intermittent result, then trace the simulated overcurrent behavior described in the driver code. Done means those tests produce consistent results across runs and operating systems.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100