TestBot News

Francois Gouget fgouget at codeweavers.com
Wed May 11 08:22:51 CDT 2022


* Test regressions
  When I identify a commit that causes new test failures I create a bug 
  report with the regression keyword and corresponding commit id. But it 
  can be hard to notice for developers who don't subscribe to the 
  wine-bugs mailing list.

  So I will now also add the patch's author to the bug's CC field.


* w10pro64 vs windows.media.speech:speech
  The 2022-04-25 w10pro64 upgrade fixed some speech test issues but it 
  turns out that's only because the tests are now being skipped after 
  the initialization fails with an internal error.

  To help debug the issue I restored a pre-upgrade version of w10pro64 
  from backup and made it available as w10pro64restored and also made 
  the pre-upgrade w10pro64 test configuration available as w10pro64old.

  See bug 52981 for more details:
  https://bugs.winehq.org/show_bug.cgi?id=52981


* New test signing configurations
  I added w7u_tsign and w864_tsign. They are respectively identical to 
  w7u and w864 but have test signing turned on. With w1064_tsign that 
  covers all major Windows versions. If needed I could add test signing 
  configurations to older Windows versions too.

  For now the wine-devel patches are not tested against these new test 
  signing configurations in order to not add more load on the TestBot. 


* debiant
  I added the fonts-arphic-uming package on the Debian Testing VM. This 
  avoids a couple of failures (mostly because the tests use the UMing 
  font instead of 'VL Gothic'), and also avoids a skip in case one runs 
  the tests in the Chinese locale (when you submit a job on a Wine VM 
  you can specify the locale you want but by default patches are only 
  tested in the Chinese locale on debian11).

  While I was at it I performed an update and it looks like the worst of 
  the 32- vs 64-bit package conflicts have been solved.

  There has only been one test run since the update but so far it looks 
  like the update caused no new failure.

  I will do the same on the debian11 VM when I find a good time to take 
  it down for maintenance.


* Rebalancing
  I also moved the debiant VM to the vm3 host. According to my 
  spreadsheet this should allow the vm4 WineTest runs to complete 2 
  hours earlier (12 -> 10 h) but of course vm3 will take 2 extra hours 
  (7 -> 9 hours).


-- 
Francois Gouget <fgouget at codeweavers.com>



More information about the wine-devel mailing list