`pyfive` spams test suite STDOUT
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 38/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- python
- Ambito
- testing-qa
Direzione di ricerca
Inizia eseguendo test_dsg.py autonomamente e tramite run_tests.py, concentrandoti su test_DSG_contiguous e sull’output di pyfive mostrato nell’issue. Confronta il comportamento della verbosità in entrambi i percorsi e consulta la documentazione di pyfive collegata. Il lavoro è completato quando l’intera suite di test non produce più l’output inaspettatamente voluminoso, senza modificare il risultato dei test.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
When run as part of the full test suite, test_DSG_contiguous displays a lot of high-verbosity output from pyfive that spams the test suite, though when run standalone (python test_dsg.py) it doesn't. Partial output (curtailed from full STDOUT which shows thousands of lines) is as follows:
$ python run_tests.py
...
...
test_DSG_contiguous (test_dsg.DSGTest.test_DSG_contiguous) ... [pyfive] Obtained 3(3+0) attributes from offset 88 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Accessing object '/station' with link target 331 (lazy access: False)
[pyfive] Obtained 4(4+0) attributes from offset 132 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Accessing object '/obs' with link target 685 (lazy access: False)
[pyfive] Obtained 4(4+0) attributes from offset 132 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Accessing object '/row_size' with link target 1155 (lazy access: False)
[pyfive] Obtained 5(5+0) attributes from offset 126 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Accessing object '/bounds' with link target 8192 (lazy access: False)
[pyfive] Obtained 4(4+0) attributes from offset 132 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Accessing object '/time_bounds' with link target 8661 (lazy access: False)
[pyfive] Obtained 3(3+0) attributes from offset 262 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Building chunk index (pyfive version=1.1.1)
[pyfive] Chunk index built: btree range=(9707, 9707); elapsed=0ms
[pyfive] Accessing object '/time' with link target 12323 (lazy access: False)
[pyfive] Obtained 7(7+0) attributes from offset 287 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Building chunk index (pyfive version=1.1.1)
[pyfive] Chunk index built: btree range=(13203, 13203); elapsed=0ms
[pyfive] Accessing object '/lat' with link target 15299 (lazy access: False)
[pyfive] Obtained 6(6+0) attributes from offset 132 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Accessing object '/lon_bounds' with link target 16014 (lazy access: False)
[pyfive] Obtained 3(3+0) attributes from offset 148 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Accessing object '/lon' with link target 16607 (lazy access: False)
[pyfive] Obtained 7(7+0) attributes from offset 134 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Accessing object '/alt' with link target 18491 (lazy access: False)
[pyfive] Obtained 8(8+0) attributes from offset 134 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Accessing object '/station_name' with link target 19116 (lazy access: False)
[pyfive] Obtained 5(5+0) attributes from offset 135 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Building chunk index (pyfive version=1.1.1)
[pyfive] Chunk index built: btree range=(19592, 19592); elapsed=0ms
[pyfive] Accessing object '/station_info' with link target 21688 (lazy access: False)
[pyfive] Obtained 4(4+0) attributes from offset 126 (fh_id=140712493448032 type=BufferedReader) in 0.0001s
[pyfive] Accessing object '/humidity' with link target 22117 (lazy access: False)
[pyfive] Obtained 6(6+0) attributes from offset 194 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Building chunk index (pyfive version=1.1.1)
[pyfive] Chunk index built: btree range=(22851, 22851); elapsed=0ms
[pyfive] Accessing object '/temp' with link target 24947 (lazy access: False)
[pyfive] Obtained 7(7+0) attributes from offset 194 (fh_id=140712493448032 type=BufferedReader) in 0.0002s
[pyfive] Building chunk index (pyfive version=1.1.1)
[pyfive] Chunk index built: btree range=(25733, 25733); elapsed=0ms
[pyfive] Accessing object '/station' with link target 331 (lazy access: False)
[pyfive] Accessing object '/station' with link target 331 (lazy access: False)
[pyfive] Accessing object '/station' with link target 331 (lazy access: False)
[pyfive] Accessing object '/obs' with link target 685 (lazy access: False)
[pyfive] Accessing object '/obs' with link target 685 (lazy access: False)
[pyfive] Accessing object '/obs' with link target 685 (lazy access: False)
[pyfive] Accessing object '/bounds' with link target 8192 (lazy access: False)
[pyfive] Accessing object '/bounds' with link target 8192 (lazy access: False)
[pyfive] Accessing object '/bounds' with link target 8192 (lazy access: False)
Reading netCDF file: /home/slb93/git-repos/cf-python/cf/test/tmp55h9odyr_test_dsg.nc
...
[pyfive] Building chunk index (pyfive version=1.1.1)
[pyfive] Chunk index built: btree range=(25733, 25733); elapsed=0ms
[pyfive] Accessing object '/station' with link target 331 (lazy access: False)
[pyfive] Accessing object '/station' with link target 331 (lazy access: False)
[pyfive] Accessing object '/station_info' with link target 21688 (lazy access: False)
Referenced netCDF variables:alt
lat
lon
lon_bounds
station_info
station_name
time
time_bounds
row_size
Unreferenced netCDF variables:
humidity
temp
Unaggregatable 'specific_humidity' has been output: <CF AuxiliaryCoordinate: cf_role=timeseries_id(4) > has no identity or no data
Unaggregatable 'air_temperature' has been output: <CF AuxiliaryCoordinate: cf_role=timeseries_id(4) > has no identity or no data
Read 2 fields from 1 dataset
ok
So seems like some verbosity setting/changing interaction might be at play and this might not hit users and only the test suite, but we should investigate this is case it could emerge in some user-facing way, anyhow (with low priority).
(A quick/skim read of the pyfive docs isn't indicating anything that might toggle verbosity as an obvious cause of this.)
- Lingua principale
- Python
- Stelle
- 151
- Fork
- 23
- Merge medio
- 21h 29m
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di NCAS-CMS/cf-python
-
code tidy
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Attempt at unsupported conservative 3D mesh regriddingForse già presa @sadielbartholomew l’ha presa 23 giorni fa. Apertabug?
-
Release: migrate from deprecated build commandForse già presa @sadielbartholomew l’ha presa 25 giorni fa. Apertarelease
-
Remove support for Python 3.10 (EOL)Forse già presa @sadielbartholomew l’ha presa 25 giorni fa. Apertaenhancement
-
bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
Tutte le issue di NCAS-CMS/cf-python
Issue simili
-
P4: low tooling
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
jeffknupp/association#318 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
petercorke/robotics-toolbox-python#709 ·
I maintainer di solito rispondono entro 2 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
MakerYuichi/Aegis-pro#114 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
mpfaffenberger/code_puppy#985 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno