8000 blas threads getter and setter tests now failing on Travis · Issue #86 · kutaslab/fitgrid · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

blas threads getter and setter tests now failing on Travis #86

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.

Sign up for GitHub

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

Jump to bottom
Closed
andportnoy opened this issue Dec 5, 2018 · 7 comments
Closed

blas threads getter and setter tests now failing on Travis #86

andportnoy opened this issue Dec 5, 2018 · 7 comments
Labels
bug Something isn't working

Comments

@andportnoy
Copy link
Collaborator

https://travis-ci.org/kutaslab/fitgrid/builds/464017224#L1843
@andportnoy
Copy link
Collaborator Author

blas.get_n_threads always returns 1. Is this related?

@andportnoy
Copy link
Collaborator Author

conda should create the environment verbosely and let's also print numpy.show_config().

@andportnoy
Copy link
Collaborator Author

Same tests pass on mkgpu and on my laptop.

@andportnoy
Copy link
Collaborator Author

There was a worker version bump:

Compare
https://travis-ci.org/kutaslab/fitgrid/builds/463705553#L3
to
https://travis-ci.org/kutaslab/fitgrid/jobs/464017225#L3

@andportnoy andportnoy mentioned this issue Dec 5, 2018
Merged
@andportnoy
Copy link
Collaborator Author
andportnoy commented Dec 5, 2018 •
edited
Loading

This is definitely due to some external changes. Here's an older (successful) build that I restarted recently: https://travis-ci.org/kutaslab/fitgrid/builds/461986881#L415. Now it fails.

@andportnoy
Copy link
< AAD2 /details-menu>
Collaborator Author
andportnoy commented Dec 6, 2018 •
edited
Loading

These tests pass with stock Travis Python and with conda Python 3.7:
https://travis-ci.org/kutaslab/fitgrid/builds/464624502
https://travis-ci.org/kutaslab/fitgrid/builds/464629223

For now we'll skip these tests when run on Travis. We still test the context manager, so inside the context manager there is a guarantee that NumPy is single-threaded. It's just that when it's single-threaded by default, it doesn't budge and doesn't let us change the number of threads used.

I'll keep this issue open.

@andportnoy andportnoy added the bug Something isn't working label Dec 6, 2018
@turbach turbach mentioned this issue Nov 8, 2019
Closed
@turbach
Copy link
Collaborator
turbach commented Apr 3, 2021

Closed by #87

@turbach turbach closed this as completed Apr 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@turbach @andportnoy
0