fdcavalcanti opened a new issue, #3680:
URL: https://github.com/apache/nuttx-apps/issues/3680

   ### Description / Steps to reproduce the issue
   
   Hello folks!
   
   Seems some changes on NSH have absolutely obliterated Espressif's internal 
CI.
   I have traced the issue using git bisect to the following commit:
   - `893f0c31eed10adf58ca95b52fffed56f89e43c5` (`readline: remove 5x 
duplicated in redraw code`)
   - PR #3657 
   
   The issue is that `pytest-embedded-nuttx` is parsing the command line and 
fails to match the regex for the `echo $?` command.
   Analyzing the serial output as received by the tool we have this:
   
   - Issues commands:
     - ls /dev
     - echo $?
   
   - Before the changes
   ```
   nsh> #x1B[Kls /dev
   /dev:
    console
    null
    random
    ttyS0
    zero
   nsh> #x1B[K
   nsh> #x1B[Kecho $?
   0
   nsh> #x1B[K
   ```
   
   - After the changes:
   ```
   nsh> #x1B[Kl#x1B[Ks#x1B[K #x1B[K/#x1B[Kd#x1B[Ke#x1B[Kv#x1B[K
   /dev:
    console
    null
    random
    ttyS0
    zero
   nsh> #x1B[K
   nsh> #x1B[Ke#x1B[Kc#x1B[Kh#x1B[Ko#x1B[K #x1B[K$#x1B[K?#x1B[K
   0
   nsh> #x1B[K
   ```
   
   I´m not aware if those are ANSI or UTF-something escape values, but seems 
there is a symbol repeating before each character that is passed to the serial 
output (#x1B[K). 
   
   Please if someone can check and confirm if that is expected. If so, how 
should we parse it?
   
   Thanks in advance.
   
   ### On which OS does this issue occur?
   
   [OS: Linux]
   
   ### What is the version of your OS?
   
   Mint 22
   
   ### NuttX Version
   
   master
   
   ### Issue Architecture
   
   [Arch: risc-v]
   
   ### Issue Area
   
   [Area: NSH]
   
   ### Host information
   
   Board used is `esp32c3-devkit:nsh`.
   
   ### Verification
   
   - [x] I have verified before submitting the report.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to