Skip to content

feat(metrics): add near-duplicate block detection #65

feat(metrics): add near-duplicate block detection

feat(metrics): add near-duplicate block detection #65

Triggered via pull request March 18, 2026 21:24
Status Failure
Total duration 10m 57s
Artifacts

test.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 1 warning
test: test/codeqa/block_impact_analyzer_test.exs#L65
test analyze/3 preserves existing 'codebase' key in pipeline result (CodeQA.BlockImpactAnalyzerTest)
test: test/codeqa/block_impact_analyzer_test.exs#L22
test analyze/3 adds 'nodes' key to each file entry in the pipeline result (CodeQA.BlockImpactAnalyzerTest)
test: test/codeqa/block_impact_analyzer_test.exs#L74
test analyze/3 nodes_top option limits refactoring_potentials per node (CodeQA.BlockImpactAnalyzerTest)
test: test/codeqa/health_report/grader_test.exs#L252
test grade_cosine_categories/3 worst_offenders uses worst_files lookup (CodeQA.HealthReport.GraderTest)
test: test/codeqa/health_report/grader_test.exs#L180
test grade_cosine_categories/3 each entry has required top-level keys (CodeQA.HealthReport.GraderTest)
test: test/codeqa/health_report/grader_test.exs#L198
test grade_cosine_categories/3 scores are integers in [0, 100] (CodeQA.HealthReport.GraderTest)
test: test/codeqa/health_report/grader_test.exs#L219
test grade_cosine_categories/3 name is humanized from key (CodeQA.HealthReport.GraderTest)
test: test/codeqa/health_report/grader_test.exs#L267
test grade_cosine_categories/3 worst_offenders defaults to [] when key absent (CodeQA.HealthReport.GraderTest)
test: test/codeqa/health_report/grader_test.exs#L193
test grade_cosine_categories/3 type is :cosine for every entry (CodeQA.HealthReport.GraderTest)
test: test/codeqa/analysis/file_metrics_server_test.exs#L57
test get_for_content/3 different content returns different metrics (CodeQA.Analysis.FileMetricsServerTest)
test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, erlef/setup-beam@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/