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

Update pr test cases for windows (#2267) #2268

Merged
merged 1 commit into from
Apr 4, 2020
Merged

Conversation

chicm-ms
Copy link
Contributor

@chicm-ms chicm-ms commented Apr 3, 2020

The Memory/CPU resource of azure provided hosts are very limited, it seems 20 intermediate results of each trial is too much, and causing problems on Windows. It appears changing to 2 intermediate result for each trial solved the problem.

There is no intermediate result in the PR test cases in v1.4 and before, and 20 intermediate results were added into each trial job in recent test refactoring.

@QuanluZhang
Copy link
Contributor

The Memory/CPU resource of azure provided hosts are very limited, it seems 20 intermediate results of each trial is too much, and causing problems on Windows. It appears changing to 2 intermediate result for each trial solved the problem.

a little curious about why this is not a problem before?

Copy link
Contributor

@ultmaster ultmaster left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exactly what kind of resource constraints makes it unable to handle 20 intermediate results? Can this, by any chance, be related to previous instability problem on Windows platform?

@chicm-ms
Copy link
Contributor Author

chicm-ms commented Apr 4, 2020

The Memory/CPU resource of azure provided hosts are very limited, it seems 20 intermediate results of each trial is too much, and causing problems on Windows. It appears changing to 2 intermediate result for each trial solved the problem.

a little curious about why this is not a problem before?

It was 0 intermediate result previously, I changed it to 20 during refactoring.

@chicm-ms
Copy link
Contributor Author

chicm-ms commented Apr 4, 2020

Exactly what kind of resource constraints makes it unable to handle 20 intermediate results? Can this, by any chance, be related to previous instability problem on Windows platform?

I ran the same test on our Windows with 56GB Memory 6vcpu for a lot of times, the problem can not be reproduced.
The azure provided win2016 image is on ds2_v2 image: https://docs.microsoft.com/en-us/azure/virtual-machines/dv2-dsv2-series#dsv2-series , which is 7GB Memory.

On azure provided agents, we never test the examples such as mnist, because the example trials can not be launched even on linux due to hardware resource limitation.

@chicm-ms chicm-ms merged commit 4dc9eb9 into v1.5 Apr 4, 2020
@chicm-ms chicm-ms deleted the dev-fix-windows-test branch April 11, 2020 16:39
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants