-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Unskip some tests, delete others #1742
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
Conversation
… test. This fixes this test as well (I have no idea how it could possibly work in pyscript classic)
I love this PR and I badly want this in but we had this discussion with Fabio before and there was no super clear outcome ... the |
I assumed that pyweb had its own tests, but I admit I didn't check. |
@@ -81,12 +81,12 @@ def test_script_type_py_src_attribute(self): | |||
) | |||
assert self.console.log.lines[-1] == "hello from foo" | |||
|
|||
@pytest.mark.skip("FIXME: test failure is unrelated") | |||
@pytest.mark.skip("FIXME: wait_for_pyscript is broken") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume wait_for_pyscript
is broken for the same execution-order reasons? Or is it more generally broken? Again, really just curious for later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume wait_for_pyscript is broken for the same execution-order reasons? Or is it more generally broken?
yes, it's the same problem.
The problem is that the current version of wait_for_pyscript()
waits for PyScript Ready
which is printed before the tags are executed, not after.
Basically right now all the tests are at risk of being flaky, but most of them are just fast enough that they work in practice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thanks for updating the skip notes on these - sounds like some fruitful things to investigate.
This is another PR which aims to clean up a bit the testsuite and integration tests.
Highlights:
@skipped
tests just worked -- I unskipped themMoreover, I killed/removed the ones which no longer make sense in the context of pyscript next; in particular, I removed all the ones which tested
Element
(which is now gone) and the one which testedpy-config
features which are no longer needed (e.g., multiple interpreters).The testsuite passes locally.
I plan to open an umbrella issue where to keep track of the remaining skipped/xfailed tests, so be handled after the release of RC1