[Allstar007]

Hello since 01.09.2021 there are no more updates for Windows x64, for x86 there are updates from tonight. What is the reason for this? And will nightly builds for x64 come out again? 

Last update 11.09.21
https://mirrors.kodi.tv/nightlies/windows/win32/master/

Last update 01.09.21
https://mirrors.kodi.tv/nightlies/windows/win64/master/

[Fuzzard]

The win64 builds have been failing due to the tests that are run. It's been decided to disable them until someone can dig into it further.
Tests execute when manually run on the build slave, but fails as part of the build jobs.

[Allstar007]

Ok thanks for the feedback, how long can it take before Nightly Build updates are available for download again?

[Fuzzard]

No ETA currently.

[i0zjh02]

No ETA currently.

Any more information yet on when this might get resolved ? Cheers

[WhatZit]

Tests execute when manually run on the build slave, but fails as part of the build jobs.

https://jenkins.kodi.tv/job/WIN-64/17780/consoleFull

Code:


...snip...
12:07:30   Kodi-test.vcxproj -> F:\builds\workspace\WIN-64\kodi-build.x64\Release\kodi-test.exe
12:07:30 Done building
12:07:30 ------------------------------------------------------------
12:07:30 Running testsuite...
12:07:30 Running 671 tests from 92 test suites.
12:07:30 [----------] Global test environment set-up.
12:07:36 Setup of basic environment failed.
12:07:36 Clean shutdown of TestGlobalPattern1
12:07:36 /xbmc/project/BuildDependencies/msys64/usr/bin/sed: can't read f:\builds\workspace\WIN-64\gtestresults.xml: No such file or directory
12:07:36 Could Not Find f:\builds\workspace\WIN-64\gtestresults.xml
12:07:36         1 file(s) moved.
12:07:36 Done running testsuite
12:07:36 ------------------------------------------------------------
12:07:36 New run name is 'xbmc-PR20113-2a37a02-#17780'
12:07:46 [File exists] check if file exists [gtestresults.xml]
12:07:47 Run condition [File exists] enabling perform for step Archive the artifacts, Publish xUnit test result report (wiki)
12:07:47 Archiving artifacts
12:07:52 INFO: Processing GoogleTest-1.8
12:07:54 INFO: [GoogleTest-1.8] - 1 test report file(s) were found with the pattern 'gtestresults.xml' relative to 'f:\builds\workspace\WIN-64' for the testing framework 'GoogleTest-1.8'.
12:07:54 ERROR: [flexible-publish] Publish xUnit test result report (org.jenkinsci.plugins.xunit.XUnitPublisher@3ecce66a) aborted: The result file 'f:\builds\workspace\WIN-64\gtestresults.xml' for the metric 'GoogleTest' is empty. The result file has been skipped.
12:07:54 Build step 'Flexible publish' changed build result to FAILURE
12:07:54 Build step 'Flexible publish' marked build as failure
12:07:54 SSH: Current build result is [FAILURE], not going to run.
12:07:54 [MSBuild] Skipping execution of recorder since overall result is 'FAILURE'
...snip...


So, what difference in Win-Azure environment configuration is there between that working manual console and the failing automated build?

I'm guessing nothing obvious or you'd have found it already