CI: three Oracle-only tests in test_cypher_compiled.py never run, as -k oracle doesn't select them
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
Research direction
Read the Oracle job configuration in .github/workflows and the three listed tests in tests/integration/test_cypher_compiled.py, along with their sync copies. Run the provided ORACLE_TESTS=true uv run pytest --collect-only -q -k oracle tests/integration/test_cypher_compiled.py command to confirm they are omitted. Done when all three Oracle-only tests match the job’s selection and are collected.
Written by the indexing model from the issue text.
Description
CI runs the Oracle tests with pytest -k oracle (.github/workflows, the Oracle job), which picks the tests whose name or parameters say oracle. Three tests in tests/integration/test_cypher_compiled.py (and their sync copies) are skipped unless Oracle is configured, take no oracle parameter, and don't say oracle in their names, so no CI job runs them: the main job skips them, and the Oracle job deselects them.
test_nodes_of_two_labels_a_transaction_has_made_and_not_yet_committed_are_found_by_both(line ~320)test_a_text_past_32_kb_set_on_two_nodes_beside_a_whole_float_or_not_leaves_the_session_open(line ~343, the #131 regression test)test_a_text_past_32_kb_in_a_map_parameter_read_and_set_on_two_nodes_leaves_the_session_open(line ~367, the #145 regression test)
Checked with ORACLE_TESTS=true uv run pytest --collect-only -q -k oracle tests/integration/test_cypher_compiled.py: none of the three is collected.
Fix: name each ..._on_oracle (as the #144 test is named), or mark the Oracle-only tests so -k oracle matches them.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 149
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 liberation-data/drivine-python
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
liberation-data/drivine-python#363 ·
Maintainers usually reply within 1 day
-
Docs: drivine4j doesn't read the flat DATABASE_* variables, as 02-connecting.md and design.md sayOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine-python#361 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
liberation-data/drivine-python#250 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
liberation-data/drivine-python#209 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 40/100
liberation-data/drivine-python#366 ·
Maintainers usually reply within 1 day
All issues in liberation-data/drivine-python
Similar issues
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
conda-forge/vc-feedstock#132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
limitlessprojects/Go-Hybrid#3342 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
UKGovernmentBEIS/inspect_ai#6268 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
LSSTDESC/rail_sompz#42 ·
-
All tests fail with 'EXITED with status 3' on pytest 9.2.0 (TestReport._id is not marshallable)Open
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
pytest-dev/pytest-forked#113 ·