Skip to content

[Bug]: Integration test "must check that an existing highlight is ignored on hovering" permafails on Windows #20136

@timvandermeij

Description

@timvandermeij

Attach (recommended) or Link to PDF file

N/A

Web browser and its version

Firefox 141.0

Operating system and its version

Arch Linux

PDF.js version

5.4.54 (and current master)

Is the bug present in the latest PDF.js version?

Yes

Is a browser extension

No

Steps to reproduce the problem

  1. Run npx gulp integrationtest on Windows.
  2. Notice that the "must check that an existing highlight is ignored on hovering" consistently fails:
Failures:
1) Highlight Editor Select text with the pointer hovering an existing highlight must check that an existing highlight is ignored on hovering
  Message:
�[31m    ProtocolError: script.callFunction timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.�[0m
  Stack:
        at <instance_members_initializer> (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:98:14)
        at new Callback (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:102:16)
        at CallbackRegistry.create (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:21:26)
        at BidiConnection.send (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/Connection.js:51:32)
        at Session.send (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/core/Session.js:134:42)
        at Session.<anonymous> (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:101:27)
        at WindowRealm.callFunction (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/core/Realm.js:92:51)
        at WindowRealm.<anonymous> (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:101:27)
        at #evaluate (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/Realm.js:134:42)
        at BidiFrameRealm.evaluateHandle (file:///C:/pdfjs/botio-files-pdfjs/private/8f63419cc49c9df/node_modules/puppeteer-core/lib/esm/puppeteer/bidi/Realm.js:101:36)

What is the expected behavior?

The test should consistently pass.

What went wrong?

The test consistently fails.

Link to a viewer

No response

Additional context

This particular test was already failing intermittently before #20126, but fails consistently afterwards due to more deterministic behavior. This should, however, make it easier to debug.

Note that we already had issues with this test on Windows as well before in #18775, which was addressed in #18860 at the time. It does pass on Linux.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions