https://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842021-11-23T09:33:29ZopenSUSE Project Management ToolopenQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4667372021-11-23T09:33:29Zokurzokurz@suse.com
<ul><li><strong>Category</strong> set to <i>Support</i></li><li><strong>Assignee</strong> set to <i>okurz</i></li><li><strong>Target version</strong> set to <i>Ready</i></li></ul><p>dheidler wrote:</p>
<blockquote>
<p>Serial text results have a content like <code>Unable to read glibc_locale-7.txt.</code>.<br>
While this can be similar with image results, these are refreshed a few times on the client side using javascript, until a proper image is received.</p>
</blockquote>
<p>so are you saying that refreshing the image multiple times always resolves this error or is this an error that you see reproducibly?</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4667972021-11-23T11:24:27Zdheidlerdheidler@suse.com
<ul></ul><p>The root cause of results not being ready on the server when a test module finishes is very common.<br>
I honestly don't know what it takes so long for - for pngs maybe the optipng is very slow but I don't know about the text results.</p>
<p>Anyway this refresh code (that was originally written by me) appends the unix timestamp to the image url to prevent caching and stores a counter in the dom object to count retries. It retries about three times IIRC with exdending intervals.<br>
When the image has a width > 0px, it is considered successful and stops the retries.</p>
<p>This solves the problem for the broken images I guess nearly all the time but obviously there could be timeouts.</p>
<p>Anyway this is not done for text results a the moment.</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4674872021-11-24T11:17:29Zokurzokurz@suse.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/467487/diff?detail_id=441993">diff</a>)</li></ul><p>Sorry, I still don't fully understand what's the impact. Except for maybe something being slow or inefficient, how are users affected? Are there jobs that reproducibly don't render text results at all? If yes, can you reference such jobs by URL from o3 (or osd)?</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4675022021-11-24T12:03:23Zokurzokurz@suse.com
<ul><li><strong>File</strong> <a href="/attachments/12222">Screenshot_20211124_125544_openqa_showing_unable_to_read_text_results_in_job_details_before_refreshing_job_just_passed.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/12222/Screenshot_20211124_125544_openqa_showing_unable_to_read_text_results_in_job_details_before_refreshing_job_just_passed.png">Screenshot_20211124_125544_openqa_showing_unable_to_read_text_results_in_job_details_before_refreshing_job_just_passed.png</a> added</li><li><strong>File</strong> <a href="/attachments/12219">Screenshot_20211124_130016_openqa_showing_unable_to_read_on_record_info_box_detail.png</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/12219/Screenshot_20211124_130016_openqa_showing_unable_to_read_on_record_info_box_detail.png">Screenshot_20211124_130016_openqa_showing_unable_to_read_on_record_info_box_detail.png</a> added</li><li><strong>Subject</strong> changed from <i>Text results "unable to read" when showing result page during text execution</i> to <i>Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/467502/diff?detail_id=442008">diff</a>)</li><li><strong>Priority</strong> changed from <i>Normal</i> to <i>Low</i></li></ul> openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4675082021-11-24T12:05:12Zokurzokurz@suse.com
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-1 priority-3 priority-lowest" href="/issues/94531">action #94531</a>: OpenQA worker randomly skips uploading artefacts for whole test modules</i> added</li></ul> openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4675112021-11-24T12:05:55Zokurzokurz@suse.com
<ul><li><strong>Category</strong> changed from <i>Support</i> to <i>Regressions/Crashes</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Blocked</i></li></ul><p>For now I will keep this ticket in "Blocked" by <a class="issue tracker-4 status-1 priority-3 priority-lowest" title="action: OpenQA worker randomly skips uploading artefacts for whole test modules (New)" href="https://progress.opensuse.org/issues/94531">#94531</a> within our backlog. You might be onto something here which could help us for the same problem.</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4697432021-12-01T13:27:02Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Blocked</i> to <i>New</i></li></ul><p>Users are affected in the sense that they see "unable to read" for text results when while live-watching the test execution. Refreshing with F5 loads the text results. I assume we need a similar hack than for the images (see <a class="issue tracker-4 status-3 priority-3 priority-lowest closed" title="action: Text results "unable to read" when showing result page during test execution, i.e. while an openQ... (Resolved)" href="https://progress.opensuse.org/issues/102786#note-2">#102786#note-2</a>).</p>
<p>So this is <strong>not</strong> the same as <a class="issue tracker-4 status-1 priority-3 priority-lowest" title="action: OpenQA worker randomly skips uploading artefacts for whole test modules (New)" href="https://progress.opensuse.org/issues/94531">#94531</a> where the text results are missing permanently. This is only about text results missing temporarily because the upload is simply still ongoing and that they're not automatically reloaded. Hence this ticket is also not blocked by <a class="issue tracker-4 status-1 priority-3 priority-lowest" title="action: OpenQA worker randomly skips uploading artefacts for whole test modules (New)" href="https://progress.opensuse.org/issues/94531">#94531</a>.</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4697462021-12-01T13:34:50Zasmorodskyi
<ul></ul><p>I experienced same bug and I want to clarify a bit Impact : so I opened job which was running and keep it open till the end of the job . than I reviewed *already finished job * and I had same experience as described in this ticket . So it is affecting not only people who trying to watch running job but also one's who watching already done but had bad luck to open it while it was running . </p>
<p>Workaround : </p>
<ol>
<li>wait until job will be done . </li>
<li>close tab and open it again </li>
</ol>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4699742021-12-02T10:37:10Zlivdywanliv.dywan@suse.com
<ul><li><strong>Subject</strong> changed from <i>Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running</i> to <i>Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:M</i></li><li><strong>Description</strong> updated (<a title="View differences" href="/journals/469974/diff?detail_id=444531">diff</a>)</li><li><strong>Status</strong> changed from <i>New</i> to <i>Workable</i></li></ul> openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4718162021-12-09T12:45:53Zokurzokurz@suse.com
<ul><li><strong>Assignee</strong> deleted (<del><i>okurz</i></del>)</li></ul><p>was tracking only the "Blocked" state. Now with this ticket being "Workable", back to the backlog</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4793792022-01-11T16:10:59Zmkittlermarius.kittler@suse.com
<ul><li><strong>Assignee</strong> set to <i>mkittler</i></li></ul> openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4797602022-01-12T15:01:48Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Workable</i> to <i>In Progress</i></li></ul><p>PR: <a href="https://github.com/os-autoinst/openQA/pull/4447" class="external">https://github.com/os-autoinst/openQA/pull/4447</a></p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4799532022-01-13T12:06:09Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Feedback</i></li></ul><p>The PR has been merged and I've also tested it locally with a few real test runs. Let's see whether it works in production. Note that with my fix one still gets "Unable to read…" but once the results have been uploaded they should be shown automatically (without having to reload the page). Not sure whether it makes sense to show some loading indication instead as we really cannot easily distinguish missing files from pending ones. (We could always show the loading indication as long as the job is still executed and when it enters a final state we'd consider the files missing. That's not perfect but would be a way to distinguish it if we wanted.)</p>
openQA Project - action #102786: Text results "unable to read" when showing result page during test execution, i.e. while an openQA test is running size:Mhttps://progress.opensuse.org/issues/102786?journal_id=4809042022-01-18T10:54:53Zmkittlermarius.kittler@suse.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul><p>I suppose it is good enough.</p>