Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependencies #8179

Merged
merged 3 commits into from Apr 30, 2024
Merged

Update dependencies #8179

merged 3 commits into from Apr 30, 2024

Conversation

qutebrowser-bot
Copy link
Contributor

Changed files

  • tests

Version updates

File Requirement old new
tests blinker 1.7.0 1.8.1
tests hypothesis 6.100.1 6.100.2
tests pytest 8.1.2 8.2.0
tests pytest-xdist 3.5.0 3.6.1

I'm a bot, bleep, bloop. 馃

qutebrowser-bot and others added 2 commits April 29, 2024 04:20
With pytest 8.2, pytest.importorskip(...) now only considers ModuleNotFoundError
rather than all ImportErrors, and warns otherwise:
pytest-dev/pytest#12220

While we could override this via

    pytest.importorskip(..., exc_type=machinery.Unavailable)

this is a simpler solution, and it also makes more sense semantically:

We only raise Unavailable when an import is being done that would otherwise
result in a ModuleNotFoundError anyways (e.g. trying to import QtWebKit on Qt
6).
@The-Compiler
Copy link
Member

The arguably only relevant upgrade here is pytest 8.2, and that actually broke our tests due to a change reviewed by yours truly 馃槅

Fixed here: 3d96fc2

Similarly to 24d01ad, failing Qt 5.15 tests
showed some evidence of us being stuck in command mode in the next test file
(hints.feature). On the first test there ("Scenario: Using :hint-follow outside
of hint mode (issue 1105)"):

    17:38:51.073 ERROR    message    message:error:63 hint-follow: This command
    is only allowed in hint mode, not command.

but:

    end2end.fixtures.testprocess.WaitForTimeout: Timed out after 15000ms waiting
    for {'category': 'message', 'loglevel': 40, 'message': 'hint-follow: This
    command is only allowed in hint mode, not normal.'}.

I agree with what has been said: This should never happen, because we restart
the qutebrowser process between test files. I did some of the mentioned "more
examination" but also don't have an explanation.

To avoid more flaky tests, let's roll with another bandaid solution.
@The-Compiler The-Compiler merged commit 5152296 into main Apr 30, 2024
33 checks passed
@The-Compiler The-Compiler deleted the update-dependencies branch April 30, 2024 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants