Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=121042
Your paranoid android.
=== w10pro64 (64 bit report) ===
mshtml:
htmldoc.c:350: Test failed: expected Exec_SETTITLE
htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE
Hey folks,
I've just learned that what we've done all these years is an un
conference (https://en.wikipedia.org/wiki/Unconference) or a BarCamp
(https://en.wikipedia.org/wiki/BarCamp). So we were cool *long* before
these other cats starting copying us.
However, since we are partnering with X.org on Wine Conf, and they use
the slick Indico conference system, we should get with the program.
I would really appreciate it if folks could submit talk ideas:
https://indico.freedesktop.org/event/2/abstracts/
We have, a non zero number of scheduled presentations already, but think
that number may be one. So I would really appreciate it if folks would
submit abstracts.
Cheers,
Jeremy
p.s. Other reminders:
- We have funds available to sponsor travel. If cost makes you
hesitate, please reach out to me privately.
- There is a hotel block you can sign up for
- New this year, it's nice if you sign to show you are coming:
https://indico.freedesktop.org/event/2/registrations/2/.
Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=121023
Your paranoid android.
=== w10pro64_ja (64 bit report) ===
mf:
mf: Timeout
Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=120932
Your paranoid android.
=== w10pro64 (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=120888
Your paranoid android.
=== w10pro64_zh_CN (64 bit report) ===
mshtml:
htmldoc.c:350: Test failed: expected Exec_SETTITLE
htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE
Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=120860
Your paranoid android.
=== w7u_adm (32 bit report) ===
winmm:
midi.c:988: Test failed: bad message 1e/0 from midiStreamOpen, expect 3c7/0
midi.c:1039: Test failed: bad message 3c7/0 from midiStreamOut, expect 3c9/22f940
midi.c:1048: Test failed: bad message 3c9/22f940 from midiStreamClose, expect 3c8/0
=== w7u_adm (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
=== w7u_adm (testbot log) ===
WineRunTask.pl:error: The previous 1 run(s) terminated abnormally
Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=120814
Your paranoid android.
=== debian11 (32 bit Chinese:China report) ===
mmdevapi:
capture.c:205: Test failed: GCP 16553 past ReleaseBuffer(0) initially 16058
Hi,
It looks like your patch introduced the new failures shown below.
Please investigate and fix them before resubmitting your patch.
If they are not new, fixing them anyway would help a lot. Otherwise
please ask for the known failures list to be updated.
The tests also ran into some preexisting test failures. If you know how
to fix them that would be helpful. See the TestBot job for the details:
The full results can be found at:
https://testbot.winehq.org/JobDetails.pl?Key=120787
Your paranoid android.
=== w1064 (32 bit report) ===
d3d11:
d3d11.c:5908: Test failed: Got unexpected query result 0x0000000000000000.
=== debian11 (64 bit WoW report) ===
d3d11:
d3d11.c:1567: Test succeeded inside todo block: d3d11.c:1570: Test marked todo: Format 0x57 - display not supported, feature_level 0x9200, format support 0x200f3f2.