-
Notifications
You must be signed in to change notification settings - Fork 49
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
Try out PkgEval #335
Try out PkgEval #335
Conversation
@nanosoldier |
... I forgot the subdir argument: @nanosoldier |
Your job failed: could not register new version (Version 1.0.2 already exists). |
At least this verifies that the new error reporting is working fine 🙂 @nanosoldier |
Codecov ReportBase: 82.26% // Head: 83.57% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #335 +/- ##
==========================================
+ Coverage 82.26% 83.57% +1.31%
==========================================
Files 17 17
Lines 2176 2186 +10
==========================================
+ Hits 1790 1827 +37
+ Misses 386 359 -27
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
Your package evaluation job has completed - possible new issues were detected. |
Hmm, all failures are due to the modified SnoopPrecompile failing to load:
@KristofferC Any thoughts on this failure? I haven't seen it before. PkgEval is using a custom registry and actually registering v1.0.3. |
Can you put the custom registry somewhere accessible and we can see if it repros when we use that as our only registry? |
Figured out with the help of @KristofferC that this was an issue with the modified registry. Has been fixed, but PkgEval is busy right now, so I'll trigger again once I've had the change to update the system. |
@nanosoldier |
Update on PkgEvalJob maleadt/SnoopCompile.jl@af9918f: Running |
Update on PkgEvalJob maleadt/SnoopCompile.jl@af9918f: Accepted |
Forgot subdir again: @nanosoldier |
Update on PkgEvalJob maleadt/SnoopCompile.jl@af9918f: Accepted |
Update on PkgEvalJob maleadt/SnoopCompile.jl@af9918f: Running |
Your package evaluation job has completed - no issues were detected. |
That last report looks great (both from a PkgEval/Nanosoldier and SnoopCompile perspective). Feel free to trigger Nanosoldier now whenever it's useful. Note that you currently have to bump the version before triggering, but I'll look into removing that requirement this week, so you can assume that it will be possible to trigger Nanosoldier anywhere on this repository. |
Thanks so much! Just to check that I understand: I just use the same invocation you did, |
Yes, and you can leave out the version bump (I'm currently working on automating that). |
For #334, but including a version bump (which is required as Nanosoldier will actually register this package in a temporary registry).
Ref JuliaCI/Nanosoldier.jl#154; this will probably require a couple of iterations to get a successful/satisfactory run.