Why is this expectation being retired?

[sid-rotor]

I have the following test

class IMockMePlease {
public:
  virtual ~IMockMePlease() = default;
  virtual int  f1()        = 0;
  virtual void f2()        = 0;
};

class Mocked : public IMockMePlease {
public:
  virtual ~Mocked() = default;
  MOCK_METHOD(int, f1, (), (override));
  MOCK_METHOD(void, f2, (), (override));
};

TEST(Wack, ImConfused) {
  auto mock  = std::make_unique<::testing::StrictMock<Mocked>>();
  auto mock2 = std::make_unique<::testing::StrictMock<Mocked>>();

  ::testing::Expectation e1 = EXPECT_CALL(*mock, f1).WillRepeatedly(
    ::testing::DoAll([]() { std::cout << "Here1" << std::endl; }, 
                            ::testing::Return(6)));
  ::testing::Expectation e2
    = EXPECT_CALL(*mock2, f1)
        .WillRepeatedly(::testing::DoAll([]() { std::cout << "Here2" << std::endl; },
                                                          ::testing::Return(7)));

  EXPECT_CALL(*mock, f2).Times(::testing::AtLeast(1)).After(e1, e2).WillRepeatedly([]() {
    std::cout << "Here3" << std::endl;
  });
  EXPECT_CALL(*mock2, f2).Times(::testing::AtLeast(1)).After(e1, e2).WillRepeatedly([]() {
    std::cout << "Here4" << std::endl;
  });

  int ret;

  ret = mock->f1();
  EXPECT_EQ(ret, 6);
  ret = mock->f1();
  EXPECT_EQ(ret, 6);
  ret = mock->f1();
  EXPECT_EQ(ret, 6);

  mock->f2();
  mock2->f2();
  mock->f2();
  mock2->f2();

  ret = mock2->f1();
  EXPECT_EQ(ret, 7);
  ret = mock2->f1();
  EXPECT_EQ(ret, 7);
  ret = mock2->f1();
  EXPECT_EQ(ret, 7);
}

Now I'd expect this test to fail. Except, I'd expect it to fail because mock->f2() and mock2->f2() don't have a corresponding available expectation since the EXPECT_CALLs for f2() are After(e2). However, this is not the error message I get, instead I see the following:

Note: Google Test filter = Wack*
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from Wack
[ RUN      ] Wack.ImConfused
Here1
Here1
Here1
Here3
Here4
Here3
Here4
unknown file: Failure

Unexpected mock function call - returning default value.
    Function call: f1()
          Returns: 0
Google Mock tried the following 1 expectation, but it didn't match:

tests.cpp:133: EXPECT_CALL(*mock2, f1)...
         Expected: the expectation is active
           Actual: it is retired
         Expected: to be called any number of times
           Actual: never called - satisfied and retired

tests.cpp:158: Failure
Expected equality of these values:
  ret
    Which is: 0
  7

unknown file: Failure

Unexpected mock function call - returning default value.
    Function call: f1()
          Returns: 0
Google Mock tried the following 1 expectation, but it didn't match:

tests.cpp:133: EXPECT_CALL(*mock2, f1)...
         Expected: the expectation is active
           Actual: it is retired
         Expected: to be called any number of times
           Actual: never called - satisfied and retired

tests.cpp:160: Failure
Expected equality of these values:
  ret
    Which is: 0
  7

unknown file: Failure

Unexpected mock function call - returning default value.
    Function call: f1()
          Returns: 0
Google Mock tried the following 1 expectation, but it didn't match:

tests.cpp:133: EXPECT_CALL(*mock2, f1)...
         Expected: the expectation is active
           Actual: it is retired
         Expected: to be called any number of times
           Actual: never called - satisfied and retired
tests.cpp:162: Failure
Expected equality of these values:
  ret
    Which is: 0
  7

[  FAILED  ] Wack.ImConfused (0 ms)
[----------] 1 test from Wack (0 ms total)

[----------] Global test environment tear-down
[==========] 1 test from 1 test suite ran. (0 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] Wack.ImConfused

So for some reason, not only are the actions for the f2() calls succeeding, for some reason the mock2->f1() calls are not succeeding. Why is the expectation on mock2->f1() retired, and why are the expectations for both f2() calls being met? Apologizes if there is a relevant discussion already.

Thanks for any help or suggestions.

[sid-rotor]

Ah of course I think about this right after I post. It is because the call to either f2() advances the DAG created by the After(e1, e2) call, so retires anything behind it on the DAG?