Skip to content
This repository was archived by the owner on May 14, 2026. It is now read-only.
This repository was archived by the owner on May 14, 2026. It is now read-only.

gax-java(windows): Flaky HttpJsonDirectServerStreamingCallableTest.testOnResponseError #1675

Description

@github-actions

Activity

  1. mpeddada1 commented on May 11, 2023

    @mpeddada1
    Contributor

    Stacktrace:

    Error:  Tests run: 9, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 8.529 s <<< FAILURE! - in com.google.api.gax.httpjson.HttpJsonDirectServerStreamingCallableTest
    Error:  com.google.api.gax.httpjson.HttpJsonDirectServerStreamingCallableTest.testOnResponseError  Time elapsed: 2.064 s  <<< FAILURE!
    value of: await(...)
    expected to be true
    	at com.google.api.gax.httpjson.HttpJsonDirectServerStreamingCallableTest.testOnResponseError(HttpJsonDirectServerStreamingCallableTest.java:267)
    
    
  2. added
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on May 11, 2023
  3. changed the title [-]Nightly build for Java 17 on windows-2022 failed.[/-] [+]gax-java(windows): Flaky HttpJsonDirectServerStreamingCallableTest.testOnResponseError[/+] on May 15, 2023
  4. added
    type: cleanupAn internal cleanup or hygiene concern.
    and removed
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Aug 10, 2023
  5. meltsufin commented on Aug 10, 2023

    @meltsufin
    Contributor

    @lqiu96 @blakeli0 Can we prioritize fixing this? It's causing a lot of flaky failures.

  6. lqiu96 commented on Aug 10, 2023

    @lqiu96
    Member

    @lqiu96 @blakeli0 Can we prioritize fixing this? It's causing a lot of flaky failures.

    Sure. I'll take a look.

  7. lqiu96 commented on Aug 11, 2023

    @lqiu96
    Member

    Having a difficult time reproducing this problem on a Windows cloudtop with Java 11. Ran this test for 40k invocations and all passed. Multiple 10k invocation runs have resulted in all passing tests. Need to take another look. Maybe the nightly job is set up differently?

  8. blakeli0 commented on Aug 11, 2023

    @blakeli0
    Contributor

    Maybe the nightly job is set up differently?

    What is the hardware specification for the cloudtop machine and the Github action machine? I guess the machine Github action uses is much worse than the cloudtop. In which case, I don't think we can do much other than increase the wait time. I gave the test itself a quick review and I don't see anything wrong with the setups.

  9. lqiu96 commented on Aug 16, 2023

    @lqiu96
    Member

    Maybe the nightly job is set up differently?

    What is the hardware specification for the cloudtop machine and the Github action machine? I guess the machine Github action uses is much worse than the cloudtop. In which case, I don't think we can do much other than increase the wait time. I gave the test itself a quick review and I don't see anything wrong with the setups.

    Yeah that seems very likely. I'll spend a few hours looking into this issue and I'll double the wait time if I'm still stuck.

  10. blakeli0 commented on Aug 25, 2023

    @blakeli0
    Contributor

    Reopening this issue as it is happening again last night #1939

  11. self-assigned this
    on Dec 7, 2023
  12. suztomo commented on Dec 14, 2023

    @suztomo
    Member

    Marking this as fixed in #2291. Let's reopen if this recurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: cleanupAn internal cleanup or hygiene concern.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions