Skip to content

No way to get exception stacktrace caused by parallel-only bug because --debug disables parallel #3731

@enumag

Description

@enumag

Bug report

Maybe it's already known / fixed? I was unable to find a similar issue though...

With the latest release my CI is failing but not every time, only sometimes (locally everything is fine though) with PHPStan throwing bunch of errors like this:

<unknown location> Internal error: Internal error: Class '[random phpstan class]' not found in file [random project file]
Run PHPStan with --debug option and post the stack trace to:
https://github.com/phpstan/phpstan/issues/new

There are many errors, the phpstan class is nearly always different and the project file path is always different.

I tried to add --debug to get a stacktrace but as it is a bit random so far the error didn't trigger while I had --debug in place.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions