Bug 409984 - -export-fixes does not export anything for a relative file path
Summary: -export-fixes does not export anything for a relative file path
Status: REPORTED
Alias: None
Product: clazy
Classification: Developer tools
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-19 09:28 UTC by Nikolai Kosjar
Modified: 2019-07-19 09:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nikolai Kosjar 2019-07-19 09:28:08 UTC
% /d2/clazy/install/bin/clazy-standalone -export-fixes=clazy.yaml -checks=qgetenv main.cpp 
/home/nik/work/testprojects/tidyAnalyzerInclusions/source/main.cpp:8:5: warning: qgetenv().isEmpty() allocates. Use qEnvironmentVariableIsEmpty() instead
      [-Wclazy-qgetenv]
    qgetenv("Foo").isEmpty();
    ^~~~~~~      ~~~~~~~~~~~
    qEnvironmentVariableIsEmpty )
1 warning generated.
% ls -l clazy.yaml
ls: cannot access 'clazy.yaml': No such file or directory
zsh: exit 2     ls --color=auto --group-directories-first -l clazy.yaml


Providing an absolute path like /tmp/clazy.yaml works fine.
Comment 1 Nikolai Kosjar 2019-07-19 09:30:00 UTC
I'm on current master, bd40d70a1855df9c7de54a94c2f78b13c411113c