CI failed on Windows
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 25/100
- Tipo di issue
- Bug
- Chiarezza
- Da chiarire
- Stato di attività
- Ferma
- Stack tecnologico
- python
- Ambito
- testing-qa
Direzione di ricerca
Inizia dai test che falliscono in pyperf/tests/test_perf_cli.py e pyperf/tests/test_timeit.py, quindi riproduci i fallimenti della CI Windows. Segui gli errori dei sottoprocessi RSS e timeit riportati nelle stack trace. Il lavoro è completato quando i tre test passano su Windows senza modificare il comportamento previsto.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
======================================================================
FAIL: test_command_track_memory (test_perf_cli.TestPerfCLI)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\a\pyperf\pyperf\pyperf\tests\test_perf_cli.py", line 619, in test_command_track_memory
self.run_command(*args)
File "D:\a\pyperf\pyperf\pyperf\tests\test_perf_cli.py", line 35, in run_command
self.assertEqual(proc.stderr, '')
AssertionError: 'Traceback (most recent call last):\n Fil[2698 chars] 1\n' != ''
- Traceback (most recent call last):
- File "c:\hostedtoolcache\windows\python\3.9.2\x64\lib\runpy.py", line 197, in _run_module_as_main
- return _run_code(code, main_globals, None,
- File "c:\hostedtoolcache\windows\python\3.9.2\x64\lib\runpy.py", line 87, in _run_code
- exec(code, run_globals)
- File "D:\a\pyperf\pyperf\pyperf\__main__.py", line 763, in <module>
- main()
- File "D:\a\pyperf\pyperf\pyperf\__main__.py", line 759, in main
- func()
- File "D:\a\pyperf\pyperf\pyperf\__main__.py", line 728, in cmd_bench_command
- runner.bench_command(name, command)
- File "D:\a\pyperf\pyperf\pyperf\_runner.py", line 622, in bench_command
- return self._main(task)
- File "D:\a\pyperf\pyperf\pyperf\_runner.py", line 427, in _main
- bench = self._worker(task)
- File "D:\a\pyperf\pyperf\pyperf\_runner.py", line 401, in _worker
- run = task.create_run()
- File "D:\a\pyperf\pyperf\pyperf\_worker.py", line 284, in create_run
- self.compute()
- File "D:\a\pyperf\pyperf\pyperf\_command.py", line 53, in compute
- raise RuntimeError("failed to get the process RSS")
- RuntimeError: failed to get the process RSS
- Traceback (most recent call last):
- File "c:\hostedtoolcache\windows\python\3.9.2\x64\lib\runpy.py", line 197, in _run_module_as_main
- return _run_code(code, main_globals, None,
- File "c:\hostedtoolcache\windows\python\3.9.2\x64\lib\runpy.py", line 87, in _run_code
- exec(code, run_globals)
- File "D:\a\pyperf\pyperf\pyperf\__main__.py", line 763, in <module>
- main()
- File "D:\a\pyperf\pyperf\pyperf\__main__.py", line 759, in main
- func()
- File "D:\a\pyperf\pyperf\pyperf\__main__.py", line 728, in cmd_bench_command
- runner.bench_command(name, command)
- File "D:\a\pyperf\pyperf\pyperf\_runner.py", line 622, in bench_command
- return self._main(task)
- File "D:\a\pyperf\pyperf\pyperf\_runner.py", line 432, in _main
- bench = self._manager()
- File "D:\a\pyperf\pyperf\pyperf\_runner.py", line 560, in _manager
- bench = Manager(self).create_bench()
- File "D:\a\pyperf\pyperf\pyperf\_manager.py", line 229, in create_bench
- worker_bench, run = self.create_worker_bench()
- File "D:\a\pyperf\pyperf\pyperf\_manager.py", line 128, in create_worker_bench
- suite = self.create_suite()
- File "D:\a\pyperf\pyperf\pyperf\_manager.py", line 122, in create_suite
- suite = self.spawn_worker(0, 0)
- File "D:\a\pyperf\pyperf\pyperf\_manager.py", line 104, in spawn_worker
- raise RuntimeError("%s failed with exit code %s"
- RuntimeError: D:\a\pyperf\pyperf\.tox\py\Scripts\python.EXE failed with exit code 1
======================================================================
FAIL: test_python_option (test_timeit.TestTimeit)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\a\pyperf\pyperf\pyperf\tests\test_timeit.py", line 248, in test_python_option
self.assertEqual(cmd.returncode, 0, repr(cmd.stdout + cmd.stderr))
AssertionError: 1 != 0 : 'Error when running timeit benchmark:\n\nStatement:\n\'time.sleep(1e-6)\'\n\nSetup:\n\'import time\'\n\nNo pyvenv.cfg file\nTraceback (most recent call last):\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_timeit.py", line 230, in bench_timeit\n runner.bench_time_func(name, timer.time_func, **kwargs)\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_runner.py", line 462, in bench_time_func\n return self._main(task)\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_runner.py", line 432, in _main\n bench = self._manager()\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_runner.py", line 560, in _manager\n bench = Manager(self).create_bench()\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_manager.py", line 229, in create_bench\n worker_bench, run = self.create_worker_bench()\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_manager.py", line 128, in create_worker_bench\n suite = self.create_suite()\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_manager.py", line 122, in create_suite\n suite = self.spawn_worker(0, 0)\n File "D:\\a\\pyperf\\pyperf\\pyperf\\_manager.py", line 104, in spawn_worker\n raise RuntimeError("%s failed with exit code %s"\nRuntimeError: C:\\Users\\runneradmin\\AppData\\Local\\Temp\\tmpsstomtue failed with exit code 106\n'
======================================================================
FAIL: test_worker_verbose (test_timeit.TestTimeit)
----------------------------------------------------------------------
Traceback (most recent call last):
File "D:\a\pyperf\pyperf\pyperf\tests\test_timeit.py", line 107, in test_worker_verbose
self.assertIsNotNone(match, repr(cmd.stdout))
AssertionError: unexpectedly None : "Warmup 1: 337 us (loops: 1, raw: 337 us)\n\nValue 1: 1.86 ms\nValue 2: 853 us\n\nMetadata:\n- boot_time: 2021-03-16 06:40:42.876194\n- cpu_count: 2\n- date: 2021-03-16 06:46:56.876194\n- duration: 16.0 ms\n- hostname: fv-az68-167\n- loops: 1\n- mem_peak_pagefile_usage: 9988.0 kB\n- name: timeit\n- perf_version: 2.1.1\n- platform: Windows-10-10.0.17763-SP0\n- python_compiler: MSC v.1928 64 bit (AMD64)\n- python_executable: D:\\a\\pyperf\\pyperf\\.tox\\py\\Scripts\\python.EXE\n- python_hash_seed: 337\n- python_implementation: cpython\n- python_version: 3.9.2 (64-bit) revision 1a79785\n- timeit_setup: 'import time'\n- timeit_stmt: 'time.sleep(1e-3)'\n- timer: QueryPerformanceCounter(), resolution: 100 ns\n- unit: second\n- uptime: 6 min 14.0 sec\n\nMean +- std dev: 1.36 ms +- 0.71 ms\n"
----------------------------------------------------------------------
Ran 165 tests in 18.766s
FAILED (failures=3)
ERROR: InvocationError for command 'D:\a\pyperf\pyperf\.tox\py\Scripts\python.EXE' -bb -Wd -m unittest discover -s pyperf/tests/ -v (exited with code 1)
___________________________________ summary ___________________________________
ERROR: py: commands failed
- Lingua principale
- Python
- Stelle
- 967
- Fork
- 112
- Merge medio
- 5g 8h
- PR unite (30g)
- 9
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
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 psf/pyperf
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
-
Improve Type System for `pyperf`Forse già presa @DebanKsahu l’ha presa 69 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 45/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 32/100
I maintainer di solito rispondono entro 1 giorno
-
Extend hook's teardown metadata with warmup/calibration flagsForse già presa @maurycy l’ha presa 170 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
psf/pyperf#239 · 12 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 20/100
I maintainer di solito rispondono entro 1 giorno
Issue simili
-
plot_graph crashes when a mesh node has no m2m edgeForse già presa @tygvi l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
mllam/neural-lam#883 · 1 commento ·
I maintainer di solito rispondono entro 2 giorni
-
enhancement possible-duplicate
Difficoltà 1/5 1-3 ore Idoneità per principianti 78/100
AOSSIE-Org/PictoPy#1715 · 2 commenti ·
I maintainer di solito rispondono entro 6 giorni
-
SQLite connector omits generated columns from the catalog, and drops relationships sourced on themAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
NVIDIA/auto-ontology#511 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ethereum/execution-specs#3996 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
cpp-best-practices/project_validator#267 ·
I maintainer di solito rispondono entro 1 giorno