Intermitted error in test_datasaver_scalars
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- testing-qa
Research direction
Start with the test_datasaver_scalars test shown in the issue and review errorlog.txt for the intermittent failure details. Reproduce the failure under the test's Hypothesis settings, then identify the relevant DataSaver behavior and verify that the test completes reliably with the expected points_written value.
Written by the indexing model from the issue text.
Description
@settings(max_examples=5, deadline=None,
suppress_health_check=(HealthCheck.function_scoped_fixture,))
@given(breakpoint=hst.integers(min_value=1, max_value=19),
write_period=hst.floats(min_value=0.1, max_value=1.5),
set_values=hst.lists(elements=hst.floats(), min_size=20, max_size=20),
get_values=hst.lists(elements=hst.floats(), min_size=20, max_size=20))
@pytest.mark.usefixtures('set_default_station_to_none')
def test_datasaver_scalars(experiment, DAC, DMM, set_values, get_values,
breakpoint, write_period):
no_of_runs = len(experiment)
station = qc.Station(DAC, DMM)
meas = Measurement(station=station)
meas.write_period = write_period
assert meas.write_period == write_period
meas.register_parameter(DAC.ch1)
meas.register_parameter(DMM.v1, setpoints=(DAC.ch1,))
with meas.run() as datasaver:
for set_v, get_v in zip(set_values[:breakpoint],
get_values[:breakpoint]):
datasaver.add_result((DAC.ch1, set_v), (DMM.v1, get_v))
assert datasaver._dataset.number_of_results == 0
sleep(write_period * 1.1)
datasaver.add_result((DAC.ch1, set_values[breakpoint]),
(DMM.v1, get_values[breakpoint]))
> assert datasaver.points_written == breakpoint + 1
E assert 0 == (1 + 1)
E + where 0 = <qcodes.dataset.measurements.DataSaver object at 0x000002006588C8B0>.points_written
See details in the log below.
- Dominant language
- Python
- Stars
- 459
- Forks
- 361
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 79
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from microsoft/Qcodes
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/Qcodes#8168 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
microsoft/Qcodes#1087 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
All instruments share a single logging.Logger, so per-instrument log configuration leaks between instrumentsPossibly taken @ymampaey claimed this 13 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Export to xarray dataset fails when two data variables do not share same setpointsMay be free again @jenshnielsen claimed this 102 days ago, and no pull request is open. Open
microsoft/Qcodes#8232 · 1 reaction · 2 assignees ·
Maintainers usually reply within 1 day
All issues in microsoft/Qcodes
Similar issues
-
json_params_matcher fails on falsy top-level JSON primitives (0, False, "")Possibly taken @mayureshsonawane17 claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bojieli/ai-agent-book#1169 ·
Maintainers usually reply within 1 day
-
priority:low ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/extensions#738 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
micronaut-projects/micronaut-core#13677 ·
Maintainers usually reply within 1 day