Skip to content

SynthesizeRecognizeTests.SpeechSynthesizerToSpeechRecognitionEngine - NullReferenceException #76626

Closed

Description

@runfoapp

Runfo Tracking Issue: SynthesizeRecognizeTests.SpeechSynthesizerToSpeechRecognitionEngine - NullReferenceException

Build Definition Kind Run Name Console Core Dump Test Results Run Client
40947 runtime PR 76652 net7.0-windows-Release-x86-CoreCLR_release-Windows.7.Amd64.Open console.log runclient.py
40192 runtime PR 76623 net7.0-windows-Release-x86-CoreCLR_release-Windows.7.Amd64.Open console.log runclient.py
39459 runtime PR 76582 net7.0-windows-Release-x86-CoreCLR_release-Windows.7.Amd64.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
1 3 3

Activity

  1. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Oct 4, 2022
  2. danmoseley commented on Oct 4, 2022

    @danmoseley
    Contributor

    apparently here?

    Assert.True(result.Confidence > 0.1);

    looks like this means the timeout expired for recognition - for some reason.

    options

    1. register for SpeechRecognitionRejected event, triggered by check here. question is -- does that count as a pass? if it does, how do we know recognition ever works

      FireSpeechRecognitionRejectedEvent(result);

    2. increase the timeout. default is 30 secs. looks like InitialSilenceTimeout allows that (despite the name)

      TimeSpan eventTimeout = TimeSpan.FromTicks(Math.Max(initialSilenceTimeout.Ticks, _defaultTimeout.Ticks));

    Seems like 2 is reasonable to start.

  3. danmoseley commented on Oct 4, 2022

    @danmoseley
    Contributor

    BTW, this test is kind of the "key" test that verifies recognition works so I would recommend not disabling it as a first approach.

  4. danmoseley commented on Oct 4, 2022

    @danmoseley
    Contributor

    @jeffhandley apparently the bot json didn't get picked up yet as I got tagged 😸

  5. jeffhandley commented on Oct 4, 2022

    @jeffhandley
    Member

    We've not made the change yet. Thanks for tagging me.

  6. danmoseley commented on Oct 4, 2022

    @danmoseley
    Contributor

    I'm looking at improving the test.

  7. ghost added
    in-prThere is an active PR which will close this issue when it is merged
    on Oct 5, 2022
  8. ghost removed
    in-prThere is an active PR which will close this issue when it is merged
    on Oct 6, 2022
  9. ghost removed
    untriagedNew issue has not been triaged by the area owner
    on Oct 6, 2022
  10. ghost locked as resolved and limited conversation to collaborators on Nov 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions