Skip to content

Debug a CI crash? #79

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

Merged
merged 23 commits into from
Apr 27, 2021
Merged

Debug a CI crash? #79

merged 23 commits into from
Apr 27, 2021

Conversation

mcabbott
Copy link
Owner

@mcabbott mcabbott commented Jan 23, 2021

Re-enabling some things skipped in #57

Closes #73

@chriselrod
Copy link
Contributor

chriselrod commented Mar 21, 2021

As an aside, it may be worth adding the option to use LoopVectorization's threads.
But it won't necessarily be faster until I get around to adding cache-level blocking, e.g. Tullio was ahead above 1000x1000 or so for matrix multiplication on my computer:
Screenshot_2021-03-16 Gadfly Plot

(If LV is involved in any crashes, I'd take a look.)

@mcabbott
Copy link
Owner Author

Would indeed be good to have such an option, impressive stuff!

Re errors, after last commit allowing LV 0.12, there are some in https://github.com/mcabbott/Tullio.jl/pull/79/checks?check_run_id=2158318303 from test/parsing.jl. Would try to boil some down but at present my only computer is an M1 mac on which LV doesn't compile.

@chriselrod
Copy link
Contributor

Would try to boil some down but at present my only computer is an M1 mac on which LV doesn't compile.

I'd appreciate that, especially if you have a workflow for it. Tullio's output isn't the easiest to navigate (neither is LV's, hard problem to avoid with metaprogramming).

Any idea why that is? Both with native Julia and under Rosetta?
I was considering buying a Mac Mini to setup with buildkite for running CI jobs, but I'd prefer to wait to buy an ARM CPU until I can get one with SVE.

@mcabbott
Copy link
Owner Author

Oh good point, I was seeing how far I could get without Rosetta, but with it, I can indeed run things.

The extent of my workflow is to look at what @tullio <expr> verbose=2 grad=false prints out, and trim that. Perhaps it could be more organised somehow!

With native Julia, I think the first hurdle is that HWloc.jl needs a library via BinaryBuilder. Have been meaning to learn a little how all that works, but haven't yet. I can download and build hwloc natively, outside of Julia, so I think it's just a plumbing problem of some sort.

@chriselrod
Copy link
Contributor

Ah. Do any BinaryBuilder packages work yet? Looking at the ARM issue, the most recent binary builder comment seems to imply they don't (i.e., they haven't been built for Apple ARM yet).

@mcabbott
Copy link
Owner Author

None that I have tried work, at the moment. I don't understand whether they can be fixed piecemeal, or must wait for a global re-build.

@mcabbott mcabbott merged commit 83eed9b into master Apr 27, 2021
@mcabbott
Copy link
Owner Author

Merged but not quite fixed? E.g.

https://github.com/mcabbott/Tullio.jl/pull/105/checks?check_run_id=2457882209

1h 17m 29s

  gradients.jl:335
229
  gradients.jl:349
230
ERROR: Package Tullio errored during testing (received signal: KILL)

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.

TODO: reenable ALL tests on Julia 1.6 and Julia nightly
2 participants