Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Code coverage report creation fails for big schema #48

Copy link
Copy link
Open
@tkleiber

Description

@tkleiber
Issue body actions

We have here an enterprise application with more than 1000 packages, functions and procedures with over 1 million LoC in one of the schemas.

We have created one fresh test now, and have to convert our v2 tests later.

Actually we start with utPLSQL v3 and want measure code coverage too.
I have tried this CLI in Jenkins, but after 10 minutes the build is broken. I have seen that 180 MB of html file of the report is written till then.

If I run CLI without coverage the build is successful in 4s.

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

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.