Skip to content
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.

BatcherImplTest is flaky #1694

Closed
blakeli0 opened this issue Jun 6, 2022 · 1 comment
Closed

BatcherImplTest is flaky #1694

blakeli0 opened this issue Jun 6, 2022 · 1 comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@blakeli0
Copy link
Contributor

blakeli0 commented Jun 6, 2022

BatcherImplTest sometimes fails with the following log:

com.google.api.gax.batching.BatcherImplTest > testThrottlingBlocking FAILED
    org.mockito.exceptions.base.MockitoException: 
    No argument value was captured!
    You might have forgotten to use argument.capture() in verify()...
    ...or you used capture() in stubbing but stubbed method was not called.
    Be aware that it is recommended to use capture() only with verify()
    Examples of correct argument capturing:
        ArgumentCaptor<Person> argument = ArgumentCaptor.forClass(Person.class);
        verify(mock).doSomething(argument.capture());
        assertEquals("John", argument.getValue().getName());
        at com.google.api.gax.batching.BatcherImplTest.testThrottlingBlocking(BatcherImplTest.java:895)
@blakeli0 blakeli0 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jun 6, 2022
@blakeli0
Copy link
Contributor Author

Duplicate of #1615

@blakeli0 blakeli0 marked this as a duplicate of #1615 Jul 28, 2022
@blakeli0 blakeli0 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

1 participant