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.

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

next/650/20241129/v1 #12185

Merged
merged 7 commits into from
Nov 30, 2024
Merged

Conversation

victorjulien
Copy link
Member

jasonish and others added 7 commits November 29, 2024 20:37
This prevents the clippy warning:

508 | #[derive(FromPrimitive, Debug)]
    |          ^------------
    |          |
    |          `FromPrimitive` is not local
    |          move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_IsakmpPayloadType`
509 | pub enum IsakmpPayloadType {
    |          ----------------- `IsakmpPayloadType` is not local
    |
    = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed
    = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive`
    = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
    = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint
    = note: this warning originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info)
Fix provided by cargo clippy --fix.
'///' style rust comments/documentation come before the item being
documented.

Spotted by clippy.
But we should fix all these soon.
Don't overwrite ut coverage with later tests.
Run various commandlines, checking that they don't error/crash.

Also counts towards coverage.
Flags are:
- unittests
- suricata-verify
- pcap
- livemode
- fuzzcorpus

This should make sure codecov only adds its report after receiving
the results for each of the flags.
Copy link

codecov bot commented Nov 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.16%. Comparing base (287d836) to head (ae10fc3).
Report is 7 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #12185       +/-   ##
===========================================
+ Coverage   49.98%   83.16%   +33.17%     
===========================================
  Files         912      912               
  Lines      257066   257066               
===========================================
+ Hits       128503   213797    +85294     
+ Misses     128563    43269    -85294     
Flag Coverage Δ
fuzzcorpus 60.98% <ø> (-0.01%) ⬇️
livemode 19.41% <ø> (ø)
pcap 44.42% <ø> (+0.01%) ⬆️
suricata-verify 62.70% <ø> (-0.02%) ⬇️
unittests 59.17% <ø> (+50.16%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Copy link
Member

@jasonish jasonish left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks OK. I restarted the failed codeql jobs. API limits were hit.

@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 23610

@victorjulien victorjulien merged commit ae10fc3 into OISF:master Nov 30, 2024
61 checks passed
@victorjulien victorjulien deleted the next/650/20241129/v1 branch November 30, 2024 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants