Skip to content
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

New package: CuTropicalGEMM v0.1.0 #92740

Merged
merged 1 commit into from
Oct 13, 2023
Merged

New package: CuTropicalGEMM v0.1.0 #92740

merged 1 commit into from
Oct 13, 2023

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator
New package: CuTropicalGEMM v0.1.0
8fc7ec4 
UUID: c2b282c3-c9c2-431d-80f7-a1a0561ebe55
Repo: https://github.com/TensorBFS/CuTropicalGEMM.jl.git
Tree: 8322e96fdafe9f9a4a71367f5411624f94fd05f1

Registrator tree SHA: f73a20c99934db92a256057d0d83ba394036a701
JuliaRegistrator referenced this pull request in TensorBFS/CuTropicalGEMM.jl Oct 4, 2023
@ArrogantGao
Merge pull request #20 from TensorBFS/TropicalGemmC_jll
6be3fc3 
Using TropicalGemmC_jll.jl and removing ./deps
@JuliaRegistrator JuliaRegistrator temporarily deployed to stopwatch October 4, 2023 13:33 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

github-actions bot commented Oct 4, 2023

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

  • Package name similar to 1 existing package.
    1. Similar to TropicalGEMM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.

After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).

If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.

Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

@ArrogantGao
Copy link
Contributor

The name of this package is indeed similar to TropicalGEMM.jl, because this one is the CUDA version of the previous package.

@ericphanson ericphanson merged commit 8167f47 into master Oct 13, 2023
@ericphanson ericphanson deleted the registrator-cutropicalgemm-c2b282c3-v0.1.0-19c56fdd3a branch October 13, 2023 20:03
@JuliaTagBot JuliaTagBot mentioned this pull request Oct 13, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
needs to be manually merged in 3 days new package
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@JuliaRegistrator @ArrogantGao @ericphanson