The "Complexity by Change Frequency" is always empty

[aik099]

For my repo (see https://scrutinizer-ci.com/g/aik099/qa-tools/statistics/) all graphs are working, but the "Complexity by Change Frequency" is always showing that it doesn't have enough data.

I'm suspecting, that I might have turned off some of the analyzers in my config that generate that graph. Or maybe a specific commit rate threshold needs to be met before this graph starts to work.

[stof]

Try enabling the PhpAnalyzer

[aik099]

Now the config I'm using looks like this:

filter:
    excluded_paths:
        - 'vendor/*'
    paths:
        - 'library/*'
        - 'tests/*'

before_commands:
    - git clone https://github.com/aik099/CodingStandard.git ../CodingStandard/

tools:
    php_cpd: true
    php_analyzer: true

    php_pdepend:
        excluded_dirs: [vendor]

    php_code_sniffer:
        enabled: true
        config:
            tab_width: 0
            standard: custom
            ruleset: ../CodingStandard/CodingStandard

    external_code_coverage:
        timeout: 600

However looking at config used for inspection I can't see php_analyzer word anywhere (I've rerun the inspection after config change): https://scrutinizer-ci.com/g/aik099/qa-tools/inspections/16cf9fa8-10ce-4e94-b1bb-adeaedd39443/config

Also log doesn't show that "php_ananyzer" is being executed: https://scrutinizer-ci.com/g/aik099/qa-tools/inspections/16cf9fa8-10ce-4e94-b1bb-adeaedd39443/log

[stof]

See the logs of the "Installing source on workers" step. It looks like PhpAnalyzer still need to be enabled explicitly by @schmittjoh for open-source repos (or maybe only for older repos as I think new repos have it now)

[aik099]

So, when PHP Analyzer was added it wasn't enabled by default for all repos? I haven't received any e-mail about such tool being added and if I wish to use it, then manual steps needs to be taken.

[stof]

@aik099 see https://scrutinizer-ci.com/blog/new-major-version-of-php-analyzer-available

[aik099]

So without composer.lock the PHP Analyzer won't work I presume (based on blog post).

[stof]

no, this has been changed in the meantime (see Mink repos for instance). It will only be a bit slower because it needs to do the composer resolution in such case while it can skip it when it has the lock file, as it already knows the locked dependencies

[tonglil]

Bump.

We have been using a paid private repo for quite some time now and the graph remains empty (for the past 6 months since we started).

The message is "Not enough data available, yet.".

We have a fairly sizable codebase and all analysis tools are enabled (takes about 7-10 per inspection in the "PHP Analyzer: Running Analysis" stage).

Can @schmittjoh provide any clarity for that?

[schmittjoh]

We currently only display this graph if there is a class/method with at least 10 changes. You can check this when viewing the list of classes and sorting it by changes. There should not be any class or method with 10 or more.

This is because the graph is not very useful if there are not enough changes (= outliers).

[tonglil]

Thanks for explaining how it works!

Most of the classes are showing 0 changes, even though git shows they have been frequently updated.

Is this something wrong with the tracker or does it reset due to some condition?