[
https://issues.apache.org/jira/browse/YETUS-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530884#comment-17530884
]
Allen Wittenauer commented on YETUS-1175:
-----------------------------------------
OK, tracking this down has been interesting.
1. project has a relative path BUF_BASEDIR defined in the personality
2. as part of parse_args, BUF_BASEDIR is yetus_abs'd... except that doesn't
does actually work since the launch location is not the same as BASEDIR
3. As a result, BUF_BASEDIR is now empty since yetus_abs is trusted implicitly
(woops)
4. Then yetus_relative_dir gets kicked off which cements it being empty
5. when the awk eventually runs to supplement the BUF_BASEDIR into the log, it
gets resolved down to awk '{print "/"$0}' which is obviously incorrect
So there is a lot going wrong here.
> buf output not showing up in results-full
> -----------------------------------------
>
> Key: YETUS-1175
> URL: https://issues.apache.org/jira/browse/YETUS-1175
> Project: Yetus
> Issue Type: Bug
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Fix For: 0.14.0
>
>
> buflint (and probably bufcompat)'s output is not showing up in
> results-full.txt. Additionally, there is an extra / in buflint's specific
> output.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
