Wine-Bugs

wine-bugs@list.winehq.org

December 2019

1 participants
7891 discussions

[Bug 48213] New: Identify when to update the latest/ executables
by WineHQ Bugzilla Dec. 1, 2019

Dec. 1, 2019

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: