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

Warnint 64to32 6186 v4 #9169

Closed
wants to merge 4 commits into from

Conversation

catenacyber
Copy link
Contributor

[Link to redmine ticket:
https://redmine.openinfosecfoundation.org/issues/6186

Describe changes:

  • ci : add the -Wshorten-64-to-32 flag to clang after -Wimplicit-int-conversion
  • fix these warnings for all src/a*.c
LIBHTP_BRANCH=pr/399

OISF/libhtp#399

Modifies #9155 with temporary disabling of Terror to get full warnings list

How can I fix the CI about format ? Locally ./scripts/clang-format.sh branch is happy

Ticket: OISF#6186

clang warns and errors on 64 to 32 bits integer conversion
@suricata-qa
Copy link

WARNING:

field baseline test %
SURI_TLPR1_stats_chk
.flow.memuse 592373632 682130008 115.15%

Pipeline 15074

@catenacyber catenacyber force-pushed the warnint-64to32-6186-v4 branch 2 times, most recently from 3f2c835 to a71708b Compare July 10, 2023 14:29
@codecov
Copy link

codecov bot commented Jul 10, 2023

Codecov Report

Merging #9169 (b3e1427) into master (4ccc9ae) will decrease coverage by 0.02%.
The diff coverage is 80.00%.

❗ Current head b3e1427 differs from pull request most recent head a287216. Consider uploading reports for the commit a287216 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #9169      +/-   ##
==========================================
- Coverage   82.34%   82.33%   -0.02%     
==========================================
  Files         968      968              
  Lines      273546   273589      +43     
==========================================
+ Hits       225258   225265       +7     
- Misses      48288    48324      +36     
Flag Coverage Δ
fuzzcorpus 64.60% <76.66%> (-0.01%) ⬇️
suricata-verify 60.70% <73.33%> (-0.02%) ⬇️
unittests 62.90% <36.66%> (-0.01%) ⬇️

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

@victorjulien victorjulien added this to the 8.0 milestone Jul 11, 2023
@suricata-qa
Copy link

Information: QA ran without warnings.

Pipeline 15176

@catenacyber
Copy link
Contributor Author

Rebased in #9257

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