-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix parsing adjacent hyphens in a literal #616
Conversation
I am ready to merge this if the checks pass. Do you need any help on how to run the checks locally? |
I saw that you pushed a fix the same second I wrote the comment, good :-) |
@kraigher I do not have the current master or black locally to check. I looked at the checks to see where it failed. If it is more work than that, I will have to wait until tonight. EDIT: Yeah, looks like black is stil complaining. I'll get everything in order by tomorrow. |
You should be able to run black using just: > python -m pip install tox
> python -m tox -e py37-fmt Where you can replace py37 which whatever version you have. |
I can't download anything where I am. If you want this in today, feel free to make any changes. |
@ktbarrett, if this is just an issue with running black once, I'll pick it later. Otherwise, I'll push the format fix and leave it open. |
I pushed black fixes, but CI jobs seem to be stalled regardless. These are the last three attempts: |
@eine Thanks. I'm home now. How do I recreate the environment the regressions run in? I'm assuming there is some assumed set of tools the regression work with. Just running tox locally leads to all the acceptance tests failing. And is there anyway to increase the verbosity of the tests while they are running? What I have now is not enough to go forward. |
The environment just requires a simulator (GHDL is used in the CI workflow) and docker run --rm -tv $(pwd):/src -w /src ghdl/vunit:llvm bash -c "pip3 install tox; tox -e py38-acceptance-ghdl"
Tests are in subdir pytest -v tests/acceptance/test_artificial.py::TestVunitArtificial::test_artificial_verilog However, it seems to be failing when testing external run scripts. These are, indeed, the examples. Hence, you can first try to execute each example individually. |
The old pattern was correct, but really slow, so I optimized. I'm running raw times master vs this PR to see the effect on performance. |
All tests pass and there seems to be no time penalty any more. However, no specific test is added. That'd be interesting to prevent future regressions. Anyway, @ktbarrett, I'm ok with merging if you confirm that the examples you were trying in #529 do work now. |
@eine I have confirmed that these fix my issues locally. I can add a unit test to the regression as well. |
Thanks. Please, go ahead on this same PR. |
Addresses #529 by improving the comment removal regular expression. But this time it actually works!
Will rebase into a single commit tonight.