You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@plbossart Sure, i will discuss this with CI team in gitlab.
In my understanding CI didn't depends on any debug log, but only error logs. This is more likely to provide more verbose logs for developers. Having said that, your initial version is good to go.
sof-dyndbg.conf will be downloaded to /etc/modprobe.d/ in every deploy of daily/pr build.
I don't think any new test case is required for this. closing this issue.
Activity
fredoh9 commentedon Jun 24, 2020
@xiulipan This is matter of updating sof-dyndbg.conf for all test devices. What test case is required for this.
Updating /etc/modprobe.d/sof-dyndbg.conf will be done when deploying a build to DUT.
In addition, probably we need to udpate env-check.sh to warn if sof-dyndbg.conf is not available in the system.
plbossart commentedon Jun 24, 2020
@fredoh9 we should check which logs CI depends on, the file I provided initially was more for developer debug and may contain too many traces.
fredoh9 commentedon Jun 24, 2020
@plbossart Sure, i will discuss this with CI team in gitlab.
In my understanding CI didn't depends on any debug log, but only error logs. This is more likely to provide more verbose logs for developers. Having said that, your initial version is good to go.
fredoh9 commentedon Jun 29, 2020
sof-dyndbg.conf will be downloaded to /etc/modprobe.d/ in every deploy of daily/pr build.
I don't think any new test case is required for this. closing this issue.