Last modified: 2014-01-19 13:10:28 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T60829, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 58829 - REPORTS-63 Query errors are not shown
REPORTS-63 Query errors are not shown
Status: NEW
Product: Tool Labs tools
Classification: Unclassified
tsreports (Other open bugs)
unspecified
All All
: Unprioritized minor
: ---
Assigned To: Merlijn van Deen (test)
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-12-21 22:34 UTC by Bugzilla Bug Importer (valhallasw)
Modified: 2014-01-19 13:10 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Bugzilla Bug Importer (valhallasw) 2013-12-21 22:34:05 UTC
This issue was converted from https://jira.toolserver.org/browse/REPORTS-63.
Summary: Query errors are not shown
Issue type: Improvement - An improvement or enhancement to an existing feature or task.
Priority: Minor
Status: Open
Assignee: Merlijn van Deen <valhallasw@arctus.nl>

On Fri, 03 Aug 2012 16:06:49, Merlijn van Deen <valhallasw@arctus.nl> opened the following bug:
> When a query fails (due to a syntax error, query killer or something
> else), the report stays in 'generating' mode and does not show any
> indication of an error.
Comment 1 Bugzilla Bug Importer (valhallasw) 2013-12-21 22:34:13 UTC
On Sun, 05 Aug 2012 16:28:27, Merlijn van Deen <valhallasw@arctus.nl> wrote:
> https://github.com/valhallasw/tsreports/pull/5 implements a basic
> version of this, but a message for users should be implemented too.
Comment 2 Merlijn van Deen (test) 2014-01-19 13:10:28 UTC
This was an issue again with the connection issues on Labs.

Because we are now using SGE to schedule jobs, we could implement something like:

IF (now - query_begin_time) > (last_runtime) * (cache_factor)
   AND (there currently is no SGE job with the same name)

THEN submit a new job.

The 'existing job' test can be handled by jsub -once.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links