wine-bugs December 2019

wine-bugs@winehq.org

1 participants
7424 discussions

[Bug 48216] New: Add a WineTest size, time and test failures comparison page to the TestBot
by WineHQ Bugzilla 01 Dec '19

01 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48216 Bug ID: 48216 Summary: Add a WineTest size, time and test failures comparison page to the TestBot Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- This would expend on the data collected for bug 48215. This would be a new page that lets the user pick two (or three or more) WineTest results and put them in the same size, run time and test unit failure tables as the JobDetails page would if they were all from the same job. For each column the user would pick a CommitId and then get a list of the available task reports (for instance "wxppro (32 bit)", "debian10 (32 bit Chinese:China)"). This would allow comparing a VM's 32 and 64 bit results (these run in separate jobs). Or compare a VM's latest result against its past result(s). Or compare the results of running the tests on Windows 8 with those of Windows 10 on the same hardware. Or comparing a WineTest run that timed out with one that did not. In effect this would be similar to bug 15477 but implemented in the TestBot rather than the on test.winehq.org, the advantage being that the TestBot has the infrastructure needed to dynamically build pages. One approach to implement this would be to pour all the report summary information into a big table. Something like (JobId, StepNo, TaskNo, CommitId, TestUnit, Failures, Size, RunTime). However given the performance issues with our current Perl ORM the performance may well be unacceptably slow (see bug 45023). Another approach would be to use the task-level summary files (described in bug 48215) and use a much smaller table to map commit ids to the tasks with relevant results. So this table would just contain (JobId, StepNo, TaskNo, CommitId) and would be used to know which tasks have results for a given commit id, and once the tasks have been selected, where to find the summary file containing the data to put in the tables. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 48215] New: Add size, time and test unit failures tabs to the JobDetails page
by WineHQ Bugzilla 01 Dec '19

01 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48215 Bug ID: 48215 Summary: Add size, time and test unit failures tabs to the JobDetails page Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- Currently the JobDetails page only provides access to each task's reports and logs. This can make it hard to figure out which test units have failures (bug 47904) and harder still to compare the test unit failures across the tasks. This is ok when testing regular patches since each task typically only runs a single test unit (except for Wine tasks). But for WineTest tasks it would be useful to be able to compare which test units failed for each task. The current workaround is to use test.winehq.org for that, but there too comparing results as its limitations (see bug 15477), and sometimes the reports a rejected which is when it would be nice to be able to dig into them. Similarly it would be quite nice to be able to have a table showing the run time an report size across test unit and tasks. One way to present this would be to have a list of tabs at the top of the JobDetails page: Reports | Unit Failures | Size | Run time The Reports tab would show the usual task reports while the other tabs would show tables with one column per task, one line per test unit and the specified information in the cells. Ideally clicking on a column header would sort the table on that column. This is reasonably easy to do at the JobDetails level: when parsing the reports we can extract all the required information. All that would be required is to save it to a summary file (one line per test unit with the count of failures, size, run time). That would make it easy and quick for JobDetails to retrieve the information and then it's a matter of getting the HTML side in place. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 47344] New: Amazon WorkSpaces
by wine-bugs＠winehq.org 01 Dec '19

01 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=47344 Bug ID: 47344 Summary: Amazon WorkSpaces Product: Wine Version: 4.10 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: stephen.feyrer(a)greensill.com Distribution: --- Created attachment 64675 --> https://bugs.winehq.org/attachment.cgi?id=64675 export WINEDEBUG=+clipboard Tested on Ubuntu 18.04 LTS, wine-3.0 (Ubuntu 3.0-1ubuntu1). I am not able to copy from something like Firefox in X and paste in to wine running Amazon Workspaces client application, neither can I copy from wine running Amazon Workspaces client application and paste back into X. Additionally, I have found that I am unable to copy and paste from wine notepad into the Amazon Workspaces client application or visa versa. The attached log file was generated after numerous copy and paste attempts were applied in all directions with as per the following: cd "${WINEPREFIX:-${HOME}/.wine}/drive_c/Program Files (x86)/Amazon Web Services, Inc/Amazon WorkSpaces" export WINEDEBUG=+clipboard wine workspaces.exe &> ~/wine-4.10_clipboard_log.txt -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 48213] New: Identify when to update the latest/ executables
by WineHQ Bugzilla 01 Dec '19

01 Dec '19

https://bugs.winehq.org/show_bug.cgi?id=48213 Bug ID: 48213 Summary: Identify when to update the latest/ executables Product: Wine-Testbot Version: unspecified Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: unknown Assignee: wine-bugs(a)winehq.org Reporter: fgouget(a)codeweavers.com Distribution: --- The TestBot lets the build and/or Wine VMs provide the following files: 1. TestAgentd.exe Only changes when there is a commit to testbot/src/testagentd/ in the tools repository. 2. TestLauncher32.exe & TestLauncher64.exe Only changes when there is a commit to testbot/src/TestLauncher/ in the tools repository. 3. winetest32.exe & winetest64.exe (future, see bug 47840) Changes whenever Wine is updated. 4. winefiles.txt & wine-parentsrc.txt Changes whenever Wine is updated. (but these should go away, see bug 48033) Currently all files are always retrieved by WineRunReconfig, whether they may have changed or not. With one build and one wine VM this means they are retrieved twice a day. This can be improved a bit by retrieving the TestAgentd and TestLauncher binaries only from build VMs since they are not needed if there is no build VM. Ideally they would only be downloaded if they have changed, and only once in case there are multiple wine VMs for instance. This would also allow WineRunReconfig to determine more accurately when to restart TestAgentd. The way to do so would be for the build scripts to provide a BuildID for each binary in the build log, and to cache this id on the server. WineRunReconfig would then download the new binaries only when the build id in the log differs from the cached one. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-bugs December 2019