#1 modular_functions.py failed with "string index out of range" ppc64le f29
Closed 5 years ago by lruzicka. Opened 5 years ago by michelmno.

modular_functions.py failed with "string index out of range" ppc64le f29

I retried locally in a ppc64le openqa server the modularity_tests that failed on modularity_enable_disable_module subtest (previously added in commit below in openQA)

$git log tests/modularity_enable_disable_module.pm
commit 24e68aa8a21e74fb6086a7b80568abda31e686a6 (upstream/modularity_testing)
Author: Lukas Ruzicka <lruzicka@redhat.com>
Date:   Wed Sep 26 15:32:42 2018 +0200
    Create openqa tests to test modularity.

the downloaded script failed at execution time with following Traceback

test.py:50:<listcomp>:IndexError: string index out of range

Traceback (most recent call last):
  File "/root/test.py", line 329, in <module>
    test.run_test(module, oldstream, newstream, fail)
  File "/root/test.py", line 299, in run_test
    self.list_module(module, stream)
  File "/root/test.py", line 152, in list_module
    allmods = self.suite.module_list()
  File "/root/test.py", line 50, in module_list
    raw = [x for x in raw if x[0] != ' ']
  File "/root/test.py", line 50, in <listcomp>
    raw = [x for x in raw if x[0] != ' ']
IndexError: string index out of range

Local variables in innermost frame:
.0: <list_iterator object at 0x7fff73d88828>
x: ''

The associated failing command is
python3 /root/test.py -m nodejs -s 8 -a list

Could we improve error detection and/or add debug traces to identify what is missing on such failure ?


Metadata Update from @lruzicka:
- Issue assigned to lruzicka

5 years ago

Hello, thanks for the catch. I will look into it as soon as I can.

I have run exactly the same script on my F29 and it works without any issue, so we will need to troubleshoot more. I believe that the problem is caused by DNF sending some unexpected output. What version of DNF is there on PowerPC?
Tomorrow, I will add logging support into the script and you will be able to test it once more.
Again, thanks for the catch.

Hello,
the failure was caused by a change in DNF output for which the parsing was not ready. I fixed it and added some logging support. Now, the process leaves a log file modular.log where it stores the INFO traces. You can use --log debug to see more info. Fixed in PR #3 .

Metadata Update from @lruzicka:
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata