touch-packages team mailing list archive

Thread
Date

[Bug 1362646] Re: Build race between gtest/gmock and tests can cause build to fail

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>
Date: Tue, 02 Sep 2014 01:45:23 -0000
Reply-to: Bug 1362646 <1362646@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

** Changed in: mir/0.7
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1362646

Title:
  Build race between gtest/gmock and tests can cause build to fail

Status in Mir:
  Fix Committed
Status in Mir 0.7 series:
  Fix Released
Status in “mir” package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:

  1. make -j4
  2. In build directory do "rm -rf gmock/"
  3. make -j4

  Expected result: Second build succeeds
  Actual result: Second build fails with "make[2]: *** No rule to make target 'gmock/libs/gtest/libgtest.a', needed by 'bin/mir_unit_tests'.  Stop." (or similar)

  The problem is that there is no explicit dependency between
  gmock/gtest and our tests. Linking with the gtest/gmock libraries is
  not enough, since GMock is an external CMake project, and CMake
  doesn't seem to track such cross-project dependencies.

  Also seen in https://jenkins.qa.ubuntu.com/job/mir-android-
  utopic-i386-build/1505/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1362646/+subscriptions