VisualGDB’s Unit Tests Issues in CI

Sysprogs forums Forums VisualGDB VisualGDB’s Unit Tests Issues in CI

Tagged: 

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #36203
    Umair
    Participant

    Hi,

    I’m using VisualGDB’s embedded tiny framework for unit testing. I’ve written unit tests and ran them successfully on my local setup[relwithdebinfo build was used]. This is how, my local setup looks like;

    • VisualGDB running on my local PC —[USB Connection]>> J-link debugger —>>> STM32 Device

    While running the same tests from CI, the unit tests STUCK at some unit tests(mostly delay related) and there is no further progress even for waiting more than 10-15 mins; This is my test setup on CI server;

    • VisualGDB running on my CI agent PC —[Network Connection]>> J-link debugger —>>> STM32 Device

    These are the logs I’m getting on CI server. After running some unit tests successfully. It starts to publish these logs on agent server CONSOLE;

    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception
    m240040ec,4
    E01
    Fast Semihosting Client Exception

    ...

    I tried to debug this issue but didn’t find any help. I have attached a log file with this.

    NOTE: I have tested the test setup connection with debugger and that’s successful

     

    Thanks

    Attachments:
    You must be logged in to view attached files.
    #36205
    support
    Keymaster

    No problem, you can always attach to the stuck process to see what is going on inside it. Just make sure the project used for attaching has physically the same executable than the project that is actually running on the device.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.