Bug #25025: Unclear error message when running rudderc technique test without providing a library path - Rudder - Issue Tracker

Actions

Copy link

Bug #25025

open

Unclear error message when running rudderc technique test without providing a library path

Added by Félix DALLIDET 6 months ago. Updated 24 days ago.

Status:

New

Priority:

N/A

Assignee:

Category:

rudderc

Target version:

8.1.11

Pull Request:

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

To do

Fix check:

To do

Regression:

Description

It default to '/var/rudder/ncf', but if the path does not point to a method library, it fails with a quite complicated error:

root@server:/var/rudder/configuration-repository/techniques/ncf_techniques/abcdd/1.0# /opt/rudder/bin/rudderc test -l /var/rudder/ncf
        Read 183 methods
   Compiling ABCDd v1.0 [Linux]
       Wrote target/technique.cf
   Compiling ABCDd v1.0 [Windows]
       Wrote target/technique.ps1
  Generating ABCDd v1.0 [Metadata]
       Wrote target/metadata.xml
     Running 1 test(s)
     Testing tests/case1.yml
     Running technique test with parameters from 'tests/case1.yml'
ERROR Failed to run cf-agent:
stdout:     info: Setting workdir to '/tmp/.tmpb7PRC5'
   error: Can't stat file '/var/rudder/ncf//bin/sh: 0: cannot open /var/rudder/ncf/10_ncf_internals/list-compatible-inputs: No such file' for parsing. (stat: No such file or directory)
   error: Policy failed validation with command '"/tmp/.tmpb7PRC5/bin/cf-promises" -c "./target/technique.cf"'
   error: Error reading CFEngine policy. Exiting...

stderr:

A non developer user has no way to understand what is missing here