Skip to content
Snippets Groups Projects
Select Git revision
  • feature/libtcg-rebase default protected
1 result
Search by author
  • Any Author
  • Anton Anton anjo
1 author
  1. Jul 29, 2022
    • Bin Meng's avatar
      .cirrus.yml: Change winsymlinks to 'native' · 6ad52086
      Bin Meng authored 
      
At present winsymlinks is set to 'nativestrict', and its behavior is:

  a) if native symlinks are enabled and <target> exists, creates
     <destination> as a native Windows symlink;
  b) else if native symlinks are not enabled or if <target> does
     not exist, 'ln -s' fails.

This causes the following error message was seen during the configure:

  "ln: failed to create symbolic link
  'x86_64-softmmu/qemu-system-x86_64.exe': No such file or directory"

Change winsymlinks to 'native' whose behavior is most similar to the
behavior of 'ln -s' on *nix, that is:

  a) if native symlinks are enabled, and whether <target> exists
     or not, creates <destination> as a native Windows symlink;
  b) else if native symlinks are not enabled, and whether <target>
     exists or not, 'ln -s' creates as a Windows shortcut file.

Signed-off-by: default avatarBin Meng <bin.meng@windriver.com>
Acked-by: default avatarThomas Huth <thuth@redhat.com>
Reviewed-by: default avatarYonggang Luo <luoyonggang@gmail.com>
Message-Id: <20220719161230.766063-1-bmeng.cn@gmail.com>
Signed-off-by: default avatarAlex Bennée <alex.bennee@linaro.org>
Message-Id: <20220725140520.515340-5-alex.bennee@linaro.org>
      6ad52086
  3. May 09, 2022
  5. Feb 09, 2022
  7. Jul 14, 2021
  9. May 14, 2021
    • Thomas Huth's avatar
      cirrus.yml: Fix the MSYS2 task · 568740be
      Thomas Huth authored 
      
The MSYS2 task in the Cirrus-CI is currently failing with error messages
like this:

 warning: database file for 'ucrt64' does not exist (use '-Sy' to download)
 :: Starting core system upgrade...
  there is nothing to do
 :: Starting full system upgrade...
 error: failed to prepare transaction (could not find database)

Seems like it can be fixed by switching to a newer release and by refreshing
the database one more time after changing the /etc/pacman.conf file.

Message-Id: <20210504100223.25427-30-alex.bennee@linaro.org>
Reviewed-by: default avatarYonggang Luo <luoyonggang@gmail.com>
Signed-off-by: default avatarThomas Huth <thuth@redhat.com>
      568740be
  11. Mar 24, 2021
  13. Jan 12, 2021
  15. Jan 06, 2021
    • Daniel P. Berrangé's avatar
      cirrus: don't run full qtest on macOS · af229fc3
      Daniel P. Berrangé authored 
      
The Cirrus CI macOS build hosts have exhibited a serious performance
degradation in recent months. For example the "qom-test" qtest takes
over an hour for only the qemu-system-aarch64 binary. This is as much
20-40 times slower than other environments. The other qtests all show
similar performance degradation, as do many of the unit tests.

This does not appear related to QEMU code changes, since older git
commits which were known to fully complete in less than 1 hour on
Cirrus CI now also show similar bad performance. Either Cirrus CI
performance has degraded, or an change in its environment has exposed
a latent bug widely affecting all of QEMU. Debugging the qom-test
showed no easily identified large bottleneck - every step of the
test execution was simply slower.

macOS builds/tests run outside Cirrus CI show normal performance.

With an inability to identify any obvious problem, the only viable
way to get a reliably completing Cirrus CI macOS job is to cut out
almost all of the qtests. We choose to run the x86_64 target only,
since that has very few machine types and thus is least badly
impacted in the qom-test execution.

With this change, the macOS jobs complete in approx 35 minutes.

Signed-off-by: default avatarDaniel P. Berrangé <berrange@redhat.com>
Reviewed-by: default avatarThomas Huth <thuth@redhat.com>
Reviewed-by: default avatarWillian Rampazzo <willianr@redhat.com>
Message-Id: <20210106114159.981538-1-berrange@redhat.com>
Signed-off-by: default avatarAlex Bennée <alex.bennee@linaro.org>
      af229fc3
  17. Nov 25, 2020
  19. Nov 23, 2020
  21. Nov 09, 2020
  23. Oct 22, 2020
  25. Oct 17, 2020
  27. Oct 09, 2020
  29. Sep 16, 2020
  31. Sep 03, 2020
  33. Jul 11, 2020
  35. Jun 16, 2020
  37. Jun 08, 2020
  39. May 06, 2020
  41. Dec 18, 2019
  43. Oct 25, 2019
  45. May 21, 2019
  47. Mar 08, 2019
  49. Feb 08, 2019