https://bugs.winehq.org/show_bug.cgi?id=39487
Bug ID: 39487
Summary: Make step dependencies more flexible
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 jobs are split into steps and tasks.
* The steps are numbered and must be executed in order. Each step has an
associated file.
* Each step has one or more tasks which can all be run in parallel.
Typically the first step is the build step associated to the patch. It produces
the 32 and 64 bit executables for the following steps hence why it has to be
executed first. When it fails the other steps are skipped which is not the case
for the other steps.
So the general structure is:
Step 1 - patch.diff - Build
Step 2 - test_32.exe - One task per VM
Step 3 - test_64.exe - One task per VM
So one source of inefficiency is that the 64 bit tests cannot start until all
the 32 bit tests have completed. It does not necessarily make the overall job
execution longer but it can leave a VM host idle while it waits for the
remaining 32 bit tests to complete. And if a developer is watching the job's
page he will not know of 64 bit failures until then.
So while the build step has to come before all others, that condition should be
relaxed for the other steps.
The database schema presented in bug 39412 adds a DependencyNo field to the
Step table so that step dependencies can be made explicit. This would allow
making both test steps depend on build one. Note that with this scheme a given
step could not directly depend on multiple other steps but that does not seem
needed.
It would also make more explicit the fact that test steps cannot be run if the
build one fails instead of hard-coding that behavior in Jobs::UpdateStatus().
--
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.
https://bugs.winehq.org/show_bug.cgi?id=45025
Bug ID: 45025
Summary: Multi-dll patches vs patches website
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 integrates with Wine's patch tracking website by providing it with
the job id of the job corresponding to patches that impact the tests. This
makes it possible to automatically flag patches that cause new test failures on
Windows.
https://source.winehq.org/patches/
However when a patch modifies the tests of multiple dlls (for instance d3d8.dll
and d3d9.dll) the TestBot creates one job per dll. This cannot work with the
patches website which can only deal with one job per patch.
In theory putting all the relavant tasks would be doable since there should be
no collision between the test executables.
The reasons for the current situation are:
* The build step only knows how to build one 3é bit and one matching 64 bit
test executable. So in the d3d8 and d3d9 case it would be unable to create both
d3d8_test.exe and d3d9_test.exe.
* Each step in a job implicitly dependended on the previous step. So a failure
to build d3d8_test.exe would have caused the d3d9 tests to be skipped too.
However this special behavior was specific to the first step so without
modification a failure to build the d3d9 test executable in step 2 would likely
not have prevented the TestBot from trying to run the d3d9 tests.
However now the TestBot supports proper dependencies between steps. So it's
possible to have the d3d8 tests depend on the d3d8 build and the d3d9 tests
depend on the d3d9 build, and have both be completely independent.
There is also progress towards simplifying the build task which would likely
make it simpler to deal with building all the test executables in one task.
However this would cause all the builds to succeed or fail together because all
the other steps would depend on that one build step. So for instance if the
d3d9_test.exe build fails, no test would be run even if d3d8test.exe was
successfully built. That may be acceptable though since the patch would need to
be resubmitted anyway.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39425
Bug ID: 39425
Summary: Improve resilience to VM host outages
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 WineTestBot gets stuck when the connection to the libvirt server
on the VM hosts is broken. This includes cases where the libvirt server is
restarted, the VM hosts is rebooted or cases where there's a network outage.
The reason is that the Engine queries the status of the VMs itself in some
circumstances. This creates a TCP connection which is never recreated in case
it breaks.
The proper fix is to banish all such queries from the Engine: not just to fix
this issue but also because some of these operation can be long (a few seconds)
and block the main loop of the single-threaded Engine, which can in turn cause
the website to lag.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44688
Bug ID: 44688
Summary: Detect stuck processes
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: ---
Sometimes a TestBot worker process can get stuck.
This can happen to LibvirtTool.pl, particularly when dealing with offline VMs.
But it can also happen to regular scripts like WineRunTask.pl when using
TestAgent to send or retrieve a file.
In both cases the TestBot Engine should have a way to detect stuck processes
and simply kill them.
To detect stuck processes add two fields to the VM table.
ChildStarted - The current child process start timestamp.
ChildTimeout - How long the current child process is allowed to run.
Most of our tasks already have timeouts so it's just a matter of reusing this
timeout and adding some leeway. For the revert and offline tasks we could use 5
and 60 minutes respectively. Then the Jobs::_CheckAndClassifyVMs() method can
check those fields and kill the stuck processes. This works because the
Engine's SafetyNet() method schedules jobs every 10 minutes as a fallback.
The reason for using two fields instead of a single ChildDeadline one is that
the ChildStarted field could be useful to know which period to analyze when
collecting the Munin statistics (currently we analyze an arbitrary period of
time that's supposed to cover the worst case).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44554
Bug ID: 44554
Summary: The extension xz is not allowed
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bricou.colin(a)wanadoo.fr
CC: austinenglish(a)gmail.com
Distribution: ---
I would like to attach a log file to a WineHQ post. The extension of the file
is ".xz" because I had to compress it to reduce his size : 91 Mo ------> 1.3
Mo.
But when I try to attach the file, a message apears "The extension xz is not
allowed" on the top, just below of the title "Post a reply".
So I can't send my log file to solve my problem with the help of others users.
You can see the discussion here :
https://forum.winehq.org/viewtopic.php?f=8&t=30214&e=0
Thank you,
Briceco
PS : Sorry, I can't speak or write english very well.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44187
Bug ID: 44187
Summary: Option to associate screenshots to more than one
version
Product: WineHQ Apps Database
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
Wish:
I would like an option to associate screenshots from a previous version to a
new version
This could be done like the "How-to / Note / Warning" checkboxes below the
"Descriptions" text area in "Edit Application Note" where a maintainer can
choose the versions to display this how-to/note/warning.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44708
Bug ID: 44708
Summary: Keep past logs if a test is rerun
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: ---
In some cases the TestBot reruns a test (currently mostly in case of TestBot
error but this could be expanded).
When this happens the previous logs are simply discarded when the tqsk is
restqrted. It would be better to bundle up the old logs in a single file and
make them accessible through a 'Show old logs' link. This would let the
developer or TestBot administrator see what the error was and better diagnose
issues.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42179
Bug ID: 42179
Summary: Better detect which tests need to be rerun
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 sometimes does not always know which tests need to be rerun and
thus tries to run the test executable with no argument. This typically happens
in the following circumstances:
* When a non-C file is patched, such as a resource or JavaScript file.
* When a test file is removed. This case is actually similar to the previous
case where the non-C file is the Makefile.in file.
Note however that if there is only one test file this works anyway because in
that case the test executable just runs that one test by default.
I added some test cases for this in the TestBot test suite:
https://github.com/fgouget/wine/tree/wtbsuite
--
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.
https://bugs.winehq.org/show_bug.cgi?id=41720
Bug ID: 41720
Summary: Advanced bug search excludes NEEDINFO bugs by default
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ken(a)codeweavers.com
Distribution: ---
Go to <https://bugs.winehq.org/query.cgi?format=advanced>. In the Status list,
all statuses except CLOSED and NEEDINFO are initially selected. NEEDINFO
should also be selected. Only CLOSED should be excluded.
I don't know if NEEDINFO bugs are included in the simple search's Status: Open
pop-up menu item. See <https://bugs.winehq.org/query.cgi?format=specific>.
They should be.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=41216
Bug ID: 41216
Summary: Dependency Packages for EL7 compatible Systems
Product: Packaging
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: wine-packages
Assignee: wine-bugs(a)winehq.org
Reporter: b.barwich(a)hotmail.com
CC: michael(a)fds-team.de, sebastian(a)fds-team.de
Distribution: ---
I am running a CentOS 7 system with an old wine version and I would like to
update to the latest official stable Version, but this version is not packaged
on any compatible EL7 repository.
I checked out the instructions on
https://wiki.winehq.org/Fedora
but I found that the guide starts at Fedora 22 while CentOS 7 is mostly
compatible with Fedora 19 and 20 and hardly with Fedora 21 because of Package
Dependencies.
I also checked out the recommended "RPM Fusion" Repository but I had to find
out that it only offers packages for EL5 and EL6 systems. It is not updated yet
to EL7 while effectively suffers from missing Packages that are not shipped by
RHEL.
So without the "RPM Fusion" Repository I checked out how many Package
Dependencies I have available from the required ones in the manual.
The Manual at
https://wiki.winehq.org/Fedora
requires 81 pendent Packages
# echo "alsa-plugins-pulseaudio.i686 glibc-devel.i686 glibc-devel libgcc.i686
libX11-devel.i686 freetype-devel.i686 libXcursor-devel.i686 libXi-devel.i686
libNX_Xext-devel.i686 libXext-devel.i686 libXxf86vm-devel.i686
libXrandr-devel.i686 libXinerama-devel.i686 mesa-libGLU-devel.i686
mesa-libOSMesa-devel.i686 libXrender-devel.i686 libpcap-devel.i686
ncurses-devel.i686 libzip-devel.i686 lcms2-devel.i686 zlib-devel.i686
libv4l-devel.i686 libgphoto2-devel.i686 libcapifax-devel.i686 cups-devel.i686
libxml2-devel.i686 openldap-devel.i686 libxslt-devel.i686 gnutls-devel.i686
libpng-devel.i686 flac-libs.i686 json-c.i686 libICE.i686 libSM.i686
libXtst.i686 libasyncns.i686 libedit.i686 liberation-narrow-fonts.noarch
libieee1284.i686 libogg.i686 libsndfile.i686 libuuid.i686 libva.i686
libvorbis.i686 libwayland-client.i686 libwayland-server.i686 llvm-libs.i686
mesa-dri-drivers.i686 mesa-filesystem.i686 mesa-libEGL.i686 mesa-libgbm.i686
nss-mdns.i686 ocl-icd.i686 pulseaudio-libs.i686 python-talloc.x86_64
sane-backends-libs.i686 tcp_wrappers-libs.i686 unixODBC.i686
samba-common-tools.x86_64 samba-libs.x86_64 samba-winbind.x86_64
samba-winbind-clients.x86_64 samba-winbind-modules.x86_64 mesa-libGL-devel.i686
fontconfig-devel.i686 libXcomposite-devel.i686 libtiff-devel.i686
openal-soft-devel.i686 mesa-libOpenCL-devel.i686 opencl-utils-devel.i686
alsa-lib-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686
pulseaudio-libs-devel.i686 pulseaudio-libs-devel gtk3-devel.i686
libattr-devel.i686 libva-devel.i686 libexif-devel.i686 libexif.i686
glib2-devel.i686"|tr -s " " "\n"|wc -l
81
but on my system I have only 68 / 81 Packages available
# yum info alsa-plugins-pulseaudio.i686 glibc-devel.i686 glibc-devel libgcc.i6
libX11-devel.i686 freetype-devel.i686 libXcursor-devel.i686 libXi-devel.i686
libNX_Xext-devel.i686 libXext-devel.i686 libXxf86vm-devel.i686
libXrandr-devel.i686 libXinerama-devel.i686 mesa-libGLU-devel.i686
mesa-libOSMesa-devel.i686 libXrender-devel.i686 libpcap-devel.i686
ncurses-devel.i686 libzip-devel.i686 lcms2-devel.i686 zlib-devel.i686
libv4l-devel.i686 libgphoto2-devel.i686 libcapifax-devel.i686 cups-devel.i686
libxml2-devel.i686 openldap-devel.i686 libxslt-devel.i686 gnutls-devel.i686
libpng-devel.i686 flac-libs.i686 json-c.i686 libICE.i686 libSM.i686
libXtst.i686 libasyncns.i686 libedit.i686 liberation-narrow-fonts.noarch
libieee1284.i686 libogg.i686 libsndfile.i686 libuuid.i686 libva.i686
libvorbis.i686 libwayland-client.i686 libwayland-server.i686 llvm-libs.i686
mesa-dri-drivers.i686 mesa-filesystem.i686 mesa-libEGL.i686 mesa-libgbm.i686
nss-mdns.i686 ocl-icd.i686 pulseaudio-libs.i686 python-talloc.x86_64
sane-backends-libs.i686 tcp_wrappers-libs.i686 unixODBC.i686
samba-common-tools.x86_64 samba-libs.x86_64 samba-winbind.x86_64
samba-winbind-clients.x86_64 samba-winbind-modules.x86_64 mesa-libGL-devel.i686
fontconfig-devel.i686 libXcomposite-devel.i686 libtiff-devel.i686
openal-soft-devel.i686 mesa-libOpenCL-devel.i686 opencl-utils-devel.i686
alsa-lib-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686
pulseaudio-libs-devel.i686 pulseaudio-libs-devel gtk3-devel.i686
libattr-devel.i686 libva-devel.i686 libexif-devel.i686 libexif.i686
glib2-devel.i686|grep -i nombre|sort|uniq|wc -l
68
from the "RPM Fusion" Repository there are 20 Packages required
# echo "libmpg123-devel.i686 gstreamer-plugins-base-devel gstreamer-devel.i686
gstreamer.i686 gstreamer-plugins-base.i686 gstreamer-devel gstreamer1.i686
gstreamer1-devel gstreamer1-plugins-base-devel.i686
gstreamer-plugins-base.x86_64 gstreamer.x86_64 gstreamer1-devel.i686
gstreamer1-plugins-base-devel gstreamer-plugins-base-devel.i686
gstreamer-ffmpeg.i686 gstreamer1-plugins-bad-free-devel.i686
gstreamer1-plugins-bad-free-extras.i686 gstreamer1-plugins-good-extras.i686
gstreamer1-libav.i686 gstreamer1-plugins-bad-freeworld.i686"|tr -s " " "\n"|wc
-l
20
but without this Repository I have only 8 / 20 Packages available:
# yum info libmpg123-devel.i686 gstreamer-plugins-base-devel
gstreamer-devel.i686 gstreamer.i686 gstreamer-plugins-base.i686 gstreamer-devel
gstreamer1.i686 gstreamer1-devel gstreamer1-plugins-base-devel.i686
gstreamer-plugins-base.x86_64 gstreamer.x86_64 gstreamer1-devel.i686
gstreamer1-plugins-base-devel gstreamer-plugins-base-devel.i686
gstreamer-ffmpeg.i686 gstreamer1-plugins-bad-free-devel.i686
gstreamer1-plugins-bad-free-extras.i686 gstreamer1-plugins-good-extras.i686
gstreamer1-libav.i686 gstreamer1-plugins-bad-freeworld.i686|grep -iE
"nombre[^\:]*:"|sort|uniq|wc -l
8
This is mostly due to RHEL7 not shipping most i686 Packages anymore.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39385
Bug ID: 39385
Summary: Make the VM descriptions visible
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: ---
Each VM has a long description of its hardware and software configuration. They
are meant to help developers figure out what's special about a specific VM and
how it may explain its results. The long descriptions can be found on the
test.winehq.org site by looking at individual reports information.
But they cannot be seen on the testbot.winehq.org site except by the
administrator when editing the VM configuration.
They should be visible as a tooltip/infotip in most places when the VM's name
is displayed.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39414
Bug ID: 39414
Summary: Add a partway job status
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: ---
If a task is completed the corresponding job's status is 'Running' even if none
or the remaining tasks is actually Running. So one can sometimes end up with
dozens of 'Running' jobs when only one or two among them actually has an active
task.
So the idea would be to reserve the 'Running' status to jobs for which one task
is actually running. Jobs where some tasks but not all have completed would
instead have the 'Partway' status (suggestions for another name welcome).
Another issue is that when multiple jobs are in the 'Running' or 'Partway'
state it's hard to know which ones have been modified the most recently because
the 'Ended' field is not set. This is probably less important though and a
waterfall like presentation would help (see bug 39413).
--
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.
https://bugs.winehq.org/show_bug.cgi?id=41600
Bug ID: 41600
Summary: Unable to view pre-moderated post in forum
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: brewmanz(a)gmail.com
Distribution: ---
I've just posted a comment in a forum thread, and wish to alter/add another
comment ... but I can't find my post in 'view your posts'!
--
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.
https://bugs.winehq.org/show_bug.cgi?id=40240
Bug ID: 40240
Summary: ntdll:exception causes the Windows 10 VM to crash
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 ntdll:exception test causes the Windows 10 VM (w1064) to crash. Given that
this does not happen on real hardware it is a TestBot bug.
Incidentally this is why we don't get any WineTest result from that VM.
Either there is a way to avoid the crash by adjusting the QEMU configuration or
a QEMU bug should be filed.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44942
Bug ID: 44942
Summary: It is currently impossible to submit test results for
Wine-staging, it says discontinued.
Product: WineHQ Apps Database
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: blocker
Priority: P2
Component: appdb-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: arnfranke(a)yahoo.com
Created attachment 61047
--> https://bugs.winehq.org/attachment.cgi?id=61047
Wine Staging 3.5 Test Results Unable to check Staging box
I just had a test result come in for "Wine 3.5-Staging". The version is set to
"3.5" without the "Wine-staging" box checked, and I can see why - you can't
check it! Please see the attached image.
Despite WineHQ claiming that it's discontinued, you can download it here:
https://www.reddit.com/r/wine_gaming/comments/88m1mz/wine_staging_35_releas…
This is a blocker for all test results submitted with Wine-Staging. I can't
accept these results as they list an incorrect Wine version (3.5 vs 3.5
staging) so accepting these results as-is would be lying about how it runs in
Wine 3.5. So what am I supposed to do, reject these test results?
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43016
Bug ID: 43016
Summary: Missing component comsvcs
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: leslie_alistair(a)hotmail.com
Distribution: ---
Can someone add component comsvcs which will also cover mtxdm.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39413
Bug ID: 39413
Summary: Make it easier to monitor the TestBot activity
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: ---
At the bottom of the main page there is a list of the VMs and their status.
However the information there is incomplete:
* When a VM is reverting there is no way to know for how long it has been
reverting.
* When a VM is running a task there is no link to the corresponding task.
* There is no history of events so if someone reports that something strange
happened there is no way to check(*).
So it would be nice to have something like BuildBot's Waterfall display.
http://buildbot.buildbot.net/waterfall
(*) Actually one could check the WineTestBot log but that has its own problems
and requires poring over lots of traces. See bug 39410.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42070
Bug ID: 42070
Summary: Add "workaround" to defined keywords list to indicate
that one or more workarounds are available for a bug.
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: o.dierick(a)piezo-forte.be
Distribution: ---
Enhancement:
Add "workaround" to the defined keyword list for open bugs, when one ore more
working workarounds have been found.
For Moderators:
The conditions for the workaround keyword to be valid would be:
- The workaround is documented in the comments or a reference is made to the
AppDB entry where the workaround is documented (or to an external source).
- The workaround is confirmed to be working at least for one person (not just
an hypothetic workaround).
- If multiple workarounds are discussed, the keyword is valid if one workaround
meets the above conditions.
Why the keyword?:
Other users affected by a bug would know that a workaround exists without
having to read all the comments to find out.
If someone has documented a workaround in the AppDB for a specific application,
and the bug is in fact affecting multiple applications, the keyword would
reduce the need to document the workaround in the AppDB for every affected app,
provided that the bug is properly referenced in the multiple AppDB entries.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44526
Bug ID: 44526
Summary: Building Biarch instructions: lxc-templates package is
not mentioned as requirement
Product: WineHQ.org
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: juewei(a)fabmail.org
Distribution: ---
https://wiki.winehq.org/Building_Biarch_Wine_On_Ubuntu#Install_LXC
starts with
sudo apt-get install lxc
that should be
sudo apt-get install lxc lxctl lxc-templates
otherwise the subsequent lxc-create -t ubuntu ... cannot find the ubuntu
template.
I tried to create an account on the wiki, but I still do not see, if it should
be possible for me to suggest edits there directly. Please advise.
thanks,
--
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.
http://bugs.winehq.org/show_bug.cgi?id=32354
Bug #: 32354
Summary: testbot: A crashing test is not detected
Product: Wine-Testbot
Version: unspecified
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: wine.dev(a)web.de
Classification: Unclassified
A 64bit test crashed on all 64bit testbot machines,
but the summary has "0" as "Number of failures".
Test run for the broken patch:
http://testbot.winehq.org/JobDetails.pl?Key=22963&log_301=1#k301
Later test:
http://testbot.winehq.org/JobDetails.pl?Key=23106&log_302=1#k302
(I send a fix for the broken code in wine in some minutes)
--
By by ... Detlef
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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.
https://bugs.winehq.org/show_bug.cgi?id=40237
Bug ID: 40237
Summary: account not deletable
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: BerlinerPaul(a)web.de
Distribution: ---
hi,
I want to delete my account but I'm unable to find some link in the preferences
for this.
best
--
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.
https://bugs.winehq.org/show_bug.cgi?id=39441
Bug ID: 39441
Summary: The reverts keep getting slower
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: ---
A revert that would take under 10 seconds right after creating the snapshot
would take over 7 minutes 6 months later. So every few months this would cause
the TestBot to become really sluggish and barely able to keep up with the patch
influx. Restarting libvirt, rebooting the host, restoring the VM from backup or
even transferring it to another host had no effect on the revert time.
While the revert is taking place the QEmu process fully occupies one core, no
disk I/O is performed and the VM is not running. The exact reason is not yet
known exactly but it seems to have to do with the VM's timer devices,
particularly the rtc one.
To confuse matters further not all VMs are affected: only Windows 2000, XP,
2003, 2008 and 10 suffer from this. The other post Windows Vista are immune.
Yet the guest is not active while the revert is taking place so it should not
have an impact on it.
Finally at WineConf 2015 it was discovered that the revert time of a live
snapshot is simply proportional to the snapshot's age.
This yielded a first workaround which is to refresh the live snapshots
regularly.
Further investigation showed that the common point between the impacted live
snapshots is that they all have the following clock settings
<clock offset='localtime'>
<timer name='rtc' tickpolicy='delay'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
while the unaffected VMs have
<clock offset='localtime'/>
But switching from the former to the latter does not fix the affected VMs.
Still this lead to a better fix which has now been put in place: setting
track='guest' on the rtc timer.
Regardless, something is wrong with the way QEmu handles timers and live
snapshots so a bug was reported:
https://bugs.launchpad.net/qemu/+bug/1505041
Maybe this will shed some light on what's really happening and what the correct
timer settings are.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44581
Bug ID: 44581
Summary: *.winehq.org tls certificate deprecated
(Symantec/GeoTrust/RapidSSL)
Product: WineHQ.org
Version: unspecified
Hardware: Other
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: www-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: tyng(a)cock.li
https://groups.google.com/forum/#!msg/mozilla.dev.security.policy/Oaeqtddo_…
as of today for firefox nightly:
Error code: SEC_ERROR_UNKNOWN_ISSUER
--
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.
https://bugs.winehq.org/show_bug.cgi?id=44844
Bug ID: 44844
Summary: Typo in description of rsaenh component
Product: WineHQ Bugzilla
Version: unspecified
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: bugzilla-unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gijsvrm(a)gmail.com
CC: austinenglish(a)gmail.com
Created attachment 60897
--> https://bugs.winehq.org/attachment.cgi?id=60897
Screenshot showing the bug (typo)
It says "cyrpto" instead of "crypto".
Link: https://bugs.winehq.org/describecomponents.cgi?product=Wine
--
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.