-
Notifications
You must be signed in to change notification settings - Fork 68
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
File access only through executor #966
Conversation
/azp run libertem.libertem-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov Report
@@ Coverage Diff @@
## master #966 +/- ##
==========================================
+ Coverage 69.44% 69.46% +0.01%
==========================================
Files 269 269
Lines 12080 12080
Branches 1643 1643
==========================================
+ Hits 8389 8391 +2
+ Misses 3385 3384 -1
+ Partials 306 305 -1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
CI failure looks like sphinx-doc/sphinx#8880 |
Possible workaround: pin sphinx to |
Ok, I'll try to push here. :-) |
One of the windows jobs again hit #963. Good thing is that with Azure Pipelines, we can restart failed jobs, and unlike travis, this also continues running further stages. So if we hit this again while releasing, we can re-trigger without problems (and without having to bump the version...) |
/azp run libertem.libertem-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Closes #965
Contributor Checklist:
Reviewer Checklist:
/azp run libertem.libertem-data
passed