Bug 101872

Summary: [PIGLIT] Corrupted temporal json test file blocks execution resume
Product: DRI Reporter: hecmundo <hector.edmundox.ramirez.gomez>
Component: IGTAssignee: Default DRI bug account <dri-devel>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: medium    
Version: DRI git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
200.json
none
200.json.tmp none

Description hecmundo 2017-07-21 16:59:18 UTC
Created attachment 132817 [details]
200.json

Description
=================================
Resuming execution fails due to corrupted json file.

Versions
======================================
Component: intel-gpu-tools
tag: intel-gpu-tools-1.19-96-gfb1ddc4
commit: fb1ddc47003ad6a683db79beeb81b6cbab1feb7c

Component: piglit
tag: piglit-v1
commit: 56e7e5583cd4a3ca15a8cda154d46d168959dd25

How to reproduce
======================================
It´s not really clear how to reproduce this bug. It has appeared suddenly. We need help to replicate this and find a solution. 
But, here´s useful information:

===Log
$ : cat .igt_clone_testing.log
>>> (info) resuming intel-gpu-tools …
>>> (info) iteration (1/1)
>>> (info) cmd (/home/gfx/intel-graphics/intel-gpu-tools/piglit/piglit resume /home/gfx/intel-graphics/intel-gpu-tools/scripts/iteration1 --no-retry)
Traceback (most recent call last):
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/piglit", line 174, in <module>
    main()
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/piglit", line 170, in main
    sys.exit(runner(args))
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/framework/exceptions.py", line 51, in _inner
    func(*args, **kwargs)
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/framework/programs/run.py", line 385, in resume
    results = backends.load(args.results_path)
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/framework/backends/__init__.py", line 175, in load
    return loader(file_path, compression)
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/framework/backends/json.py", line 230, in load_results
    return _resume(filename)
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/framework/backends/json.py", line 293, in _resume
    key=lambda p: int(os.path.splitext(p)[0]))
  File "/home/gfx/intel-graphics/intel-gpu-tools/piglit/framework/backends/json.py", line 293, in <lambda>
    key=lambda p: int(os.path.splitext(p)[0]))
ValueError: invalid literal for int() with base 10: '200.json'
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+
|i|n|t|e|l|-|g|p|u|-|t|o|o|l|s| |[|E|R|R|O|R|]|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+
>>> (info) intel-gpu-tools has finished with output (256)
>>> (err) an error was occurred executing intel-gpu-tools

===Attached files:
In the attachments section are the 200.json and 200.json.tmp file, which is the corrupted one. Open it to see details

Expected Behavior
==============================
 Piglit should resume execution

Current Behavior
==============================
Piglit does not resume execution
Comment 1 hecmundo 2017-07-21 16:59:43 UTC
Created attachment 132818 [details]
200.json.tmp
Comment 2 Dylan Baker 2017-07-21 18:04:34 UTC
This was previous reported, but the reporter never tested the patches I sent.
They're available here, if they work please send a tested-by and I'll merge
them to master:

https://patchwork.freedesktop.org/series/26257/

*** This bug has been marked as a duplicate of bug 101503 ***
Comment 3 hecmundo 2017-07-21 19:25:15 UTC
(In reply to Dylan Baker from comment #2)
> This was previous reported, but the reporter never tested the patches I sent.
> They're available here, if they work please send a tested-by and I'll merge
> them to master:
> 
> https://patchwork.freedesktop.org/series/26257/
> 
> *** This bug has been marked as a duplicate of bug 101503 ***

Tested and worked perfectly. Updated in mailing list as "Tested-by".

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.