Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Java] Fix for incorrect input and output lengths in run call #3064

Merged
merged 6 commits into from
Feb 21, 2020

Conversation

Craigacp
Copy link
Contributor

Description: The Java code passes the wrong input and output lengths into the native code. I added tests for the behaviour. The native code appears to always execute all outputs, even if they aren't requested, if/when this changes then the other tests can be uncommented to check that that behaviour is preserved by the Java API.

Motivation and Context

@Craigacp Craigacp requested a review from a team as a code owner February 21, 2020 16:05
@snnn
Copy link
Member

snnn commented Feb 21, 2020

/azp run Linux CPU CI Pipeline,Linux GPU CI Pipeline,Linux GPU TensorRT CI Pipeline,MacOS CI Pipeline,Win CPU x86 CI Pipeline,Windows GPU CI Pipeline,Windows GPU TensorRT CI Pipeline

@snnn
Copy link
Member

snnn commented Feb 21, 2020

/azp run Win CPU x64 NoContribops CI Pipeline,MacOS NoContribops CI Pipeline,Linux CPU x64 NoContribops CI Pipeline

@azure-pipelines
Copy link

Azure Pipelines successfully started running 3 pipeline(s).

@azure-pipelines
Copy link

Azure Pipelines successfully started running 7 pipeline(s).

@snnn snnn merged commit a7541f9 into microsoft:master Feb 21, 2020
@Craigacp Craigacp deleted the java-num-inputs-fix branch January 11, 2021 01:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Providing fewer tensor inputs to Java API than model declares as inputs
2 participants