• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 512 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS: javascript fails when using GIT project

Robert Wolfe
Mastermind 7860 points
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

Hello,

I'm using JavaScript for running various CCS commands, in V7.3  But I'm having timeouts when trying to perform them on a GIT source revision-backed project.  A specific example is when trying to script the cleanProject() command.  It does the clean project, but the script command does not return correctly, and times out:

js:> cleanProject("> project_name")

Wait condition time out. (C:\ti\ccsv7\eclipse\configuration\org.eclipse.osgi\401\0\.cp\resources\javascript\project.js#33)

Referencing this thread, putting the ">" before a project name in GIT resolved a similar problem (and did for me with an earlier project). 

https://e2e.ti.com/support/wireless-connectivity/zigbee-and-thread/f/158/t/766890?tisearch=e2e-sitesearch&keymatch=git%2525252520build

But this time around, the command never returns without a time out.

Prior to putting my project in GIT, this command, and others, did not time out.

Also, that timeout period seems to be long, regardless what I try to set as the timeout period.  Can you tell me what is wrong with this attempt to shorten the timeout period?  No matter what value I used, the script timeout is still the same (long).

js:> script = ScriptingEnvironment.instance()

js:> script.setScriptTimeout( 3000 )

(timeout is much longer than the 3 seconds indicated).

Please advise,

Robert

  • 0
    TI__Guru**** 450031 points

    Hi Robert,

    I assume you using the Scripting Console. Note that from the Scripting Console, you can access a mix of GSS (IDE Scripting) and DSS (Debugger Scripting) functionality. Any kind of console project command is IDE Scripting. setScriptTimeout is a DSS command and would only apply to DSS functionality.

    Robert Wolfe said:

    But this time around, the command never returns without a time out.

    Prior to putting my project in GIT, this command, and others, did not time out.

    Based on this information, it appears the issue may be related to the GIT integration with CCS. I will try to reproduce the keep you posted of my progress

    Thanks

    ki

  • 0 in reply to Ki
    Mastermind 7860 points

    Hi Ki,

    Ki said:

    I assume you using the Scripting Console. Note that from the Scripting Console, you can access a mix of GSS (IDE Scripting) and DSS (Debugger Scripting) functionality. Any kind of console project command is IDE Scripting. setScriptTimeout is a DSS command and would only apply to DSS functionality.

    Would you know of a way to set the timeout for IDE?

    Ki said:
    Based on this information, it appears the issue may be related to the GIT integration with CCS. I will try to reproduce the keep you posted of my progress

    Thanks for looking into this.  One thing I may have noticed about this later project, and version of CCS, is that all the project elements are preceded by the ">" ... the project name, the includes, the sources, the project files, etc.  I'm not sure that was the case when I had run into the similar issue from that previous referenced thread (where it might have just been the project name that was preceded).  That is just from recall, though, since I don't have that project/environment anymore.  But if true, I don't know if that, i.e. all files preceded by the "<", could be causing some of the issue.

    Robert

  • 0 in reply to Robert Wolfe
    TI__Guru**** 450031 points

    Robert Wolfe said:
    Would you know of a way to set the timeout for IDE?

    Try the following in the Scripting Console:

    js:> importPackage(Packages.com.ti.ccstudio.scripting.ui)

    js:> UIScripting.setScriptingTimeout(3000)

    Robert Wolfe said:
    Thanks for looking into this.  One thing I may have noticed about this later project, and version of CCS, is that all the project elements are preceded by the ">" ... the project name, the includes, the sources, the project files, etc.  I'm not sure that was the case when I had run into the similar issue from that previous referenced thread (where it might have just been the project name that was preceded).  That is just from recall, though, since I don't have that project/environment anymore.  But if true, I don't know if that, i.e. all files preceded by the "<", could be causing some of the issue.

    Thanks for the extra data point. I'll keep this in mind when I try to reproduce.

    Thanks

    ki

  • 0 in reply to Robert Wolfe
    Guru 92251 points

    Robert Wolfe said:
    One thing I may have noticed about this later project, and version of CCS, is that all the project elements are preceded by the ">" ... the project name, the includes, the sources, the project files, etc.

    If you mean the GIT "Label Decorations" then ">" means the file / folder / project is "dirty" as far as GIT is concerned. From the CCS preferences:

    I don't know if it is relevant, but another user reported an issue with CCS and products under GIT configuration, where changes to the line endings applied by GIT causes failures - see CCS/AM5728: Discovered products fail to install

  • 0 in reply to Chester Gillon
    Mastermind 7860 points

    Thanks for the reply.

    Chester Gillon said:

    I don't know if it is relevant, but another user reported an issue with CCS and products under GIT configuration, where changes to the line endings applied by GIT causes failures - see CCS/AM5728: Discovered products fail to install

    I didn't encounter any install failures like that, but when poking around the Preferences configuration for GIT you pointed out, I unchecked GIT here:

    and can now run the script commands, i.e. setActiveProject, cleanProject, buildProject, without things timing out.  I also did not need to use the ">" prefix in any of the commands anymore.  I guess this is a solution, or at least a workaround.  The default labeling for GIT can no longer be used, though.

    Regards,

    Robert

  • 0 in reply to Robert Wolfe
    TI__Guru**** 450031 points

    Thanks Robert, Chester,

    I am able to reproduce the issue with CCSv10. I filed a bug for this. The tracking link is:

    https://sir.ext.ti.com/jira/browse/EXT_EP-9799

    Thanks

    ki

  • 0 in reply to Ki
    Mastermind 7860 points

    Thanks guys.

    Robert