Skip to content

Remove compiler warnings #683

Closed
Closed

Description

@S-MOHAMD

What

All earnings are removed as per process

Acceptance Criteria (DoD)

  • 0 warnings

How

No response

Activity

  1. added theissue type on Sep 22, 2026
  2. changed the title [-]Remove all warnings[/-] [+]Remove compiler warnings[/+] on Sep 22, 2026
  3. cameron-craig-etas commented on Oct 14, 2026

    @cameron-craig-etas
    Contributor

    PR opened in score_cpp_policies to fix incorrect warning: eclipse-score/score_cpp_policies#46

  4. cameron-craig-etas commented on Oct 16, 2026

    @cameron-craig-etas
    Contributor

    Fixing a communication warning here: eclipse-score/communication#1405

  5. cameron-craig-etas commented on Oct 16, 2026

    @cameron-craig-etas
    Contributor

    Fixing score_cpp_policies for Linux here: eclipse-score/score_cpp_policies#46

  6. cameron-craig-etas commented on Oct 16, 2026

    @cameron-craig-etas
    Contributor

    Fixing score_cpp_policies for QNX here: eclipse-score/score_cpp_policies#47

  7. cameron-craig-etas commented on Oct 20, 2026

    @cameron-craig-etas
    Contributor

    Fixed baselibs warning here: eclipse-score/baselibs#707

  8. moved this from Backlog to In Progress in S-CORE Roadmapon Oct 26, 2026
  9. cameron-craig-etas commented on Oct 28, 2026

    @cameron-craig-etas
    Contributor

    We have now fixed all warnings in the defined list in score_cpp_policies. Production code, unit tests and integration tests have warnings as errors turned on.

  10. moved this from In Progress to Done in S-CORE Roadmapon Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

cleanupTasks to cleanup the code

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions