-
Notifications
You must be signed in to change notification settings - Fork 5
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
Fix docs-check
job; numpy 2.x fixes
#157
Conversation
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #157 +/- ##
=======================================
Coverage 79.83% 79.84%
=======================================
Files 35 35
Lines 3457 3458 +1
Branches 576 576
=======================================
+ Hits 2760 2761 +1
Misses 560 560
Partials 137 137 ☔ View full report in Codecov by Sentry. |
docs-check
job
This comment was marked as outdated.
This comment was marked as outdated.
Azure Pipelines successfully started running 1 pipeline(s). |
This comment was marked as outdated.
This comment was marked as outdated.
1 similar comment
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
I am genuinely perplexed about this, without installing If there is some kind of caching on the pipelines maybe good to reset everything? I don't think I have the access to do that myself. The numba test troubles are equally odd, I tried on |
This might be because the
Yeah, that's the really weird one. The Python 3.8 is just one of the versions that is made available to the azure agents. I'm not sure yet, and I have no idea why We might want to move to 22.04 as a base image for the azure agent, which does still support the Python versions we need, as far as I can see.
I didn't look further yet, but an issue is that the azure agent doesn't completely clean up the environment after a run, so there may indeed be some files that stick around (like tox environments, the venv, and the cache of pip/uv). I just re-created the containers, and I'll re-run it again, to see if that changed anything. |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Hum... I can reproduce the failures - they only happen in the non-jit case ( |
Hopefully that will be cleaned up by the agent
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Ah I have just been running with |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
Numba and numpy 2.x don't yet agree on the dtype conversion rules, so for disabled numba, we need to explicitly upcast to np.uint16 at some places.
/azp run libertem.libertem-live-data |
Azure Pipelines successfully started running 1 pipeline(s). |
So weird that |
Yeah, extra weird that it works fine for the other jobs, like |
Try to be consistent with other jobs.
Contributor Checklist:
Reviewer Checklist:
/azp run libertem.libertem-live-data
passed