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

Unit tests are failing for the cpp_message package after merging master to develop #184

Open
JonSmet opened this issue Feb 27, 2023 · 0 comments
Assignees
Labels
anomaly Something isn't working

Comments

@JonSmet
Copy link
Contributor

JonSmet commented Feb 27, 2023

Summary

After merging the master branch to the develop branch after the Isetta Release, unit tests are failing for the cpp_message package for tests related to encoding/decoding BSMs, TrafficControlMessages, and EmergencyVehicleAck messages.

Commit

ce904bd

Expected Behavior

All unit tests should pass.

Actual Behavior

Several unit tests are failing for the cpp_message package.

Steps to Reproduce the Actual Behavior

  1. Build the cpp_message package
  2. Run the unit tests for the cpp_message package

Related Work

No response

@JonSmet JonSmet added the anomaly Something isn't working label Feb 27, 2023
@JonSmet JonSmet self-assigned this Feb 27, 2023
dan-du-car added a commit that referenced this issue Feb 27, 2023
…rgencyVehicleAck messages after merging master to develop (#183)

<!-- Thanks for the contribution, this is awesome. -->

# PR Details
## Description

<!--- Describe your changes in detail -->
While merging `master` to `develop` (PR #182), it was discovered that
the asn1 binaries on the `master` branch did not contain all necessary
compiled code to encode/decode the BSMs, TrafficControlMessages, and
EmergencyVehicleAck messages. This PR fixes this issue by re-compiling
the latest asn1 file used for CARMA, and replacing the old binary files
in CARMA Messenger.

## Related Issue

<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please DO NOT name partially fixed issues, instead open an issue
specific to this fix -->
<!--- Please link to the issue here: -->
Issue #184 

## Motivation and Context

<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?

<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->
Originally, unit tests were failing in the cpp_message package from
BSMs, TrafficControlMessages, and EmergencyVehicleAck messages. Now all
unit tests pass.

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [x] Defect fix (non-breaking change that fixes an issue)
- [ ] New feature (non-breaking change that adds functionality)
- [ ] Breaking change (fix or feature that cause existing functionality
to change)

## Checklist:

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [ ] I have added any new packages to the sonar-scanner.properties file
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [x] I have read the
[**CONTRIBUTING**](https://github.com/usdot-fhwa-stol/carma-platform/blob/develop/Contributing.md)
document.
- [ ] I have added tests to cover my changes.
- [x] All new and existing tests passed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
anomaly Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant