Skip to content

Test ends with exit code 139 #268

@milo

Description

@milo

Nette Tester 1.6.1 is failing with exit code 139. The 1.6.0 is OK. Discovered here.

I tried to reproduce it. Successfully, but only once. I clonned the nextras/dbal repo, composer update and run vendor/bin/tester tests/cases/integration/DbalExtensionTest.phpt. It failed on first run, but never on next. Googling for 139 exit... in UNIX usually means SIGSEGV 11 (139 - 128 = 11).

Imho, this is the PHP bug. I'll digging deeper later.

Ref nextras/dbal#18

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