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

Add ERS test for COSP #851

Merged
merged 1 commit into from
Apr 21, 2016
Merged

Conversation

singhbalwinder
Copy link
Contributor

@singhbalwinder singhbalwinder commented Apr 19, 2016

Add ERS test for COSP

[BFB]

@singhbalwinder singhbalwinder added Atmosphere BFB PR leaves answers BFB labels Apr 19, 2016
@singhbalwinder singhbalwinder changed the title Added ERS test for COSP Adds ERS test for COSP Apr 19, 2016
@susburrows susburrows changed the title Adds ERS test for COSP Add ERS test for COSP Apr 21, 2016
susburrows added a commit that referenced this pull request Apr 21, 2016
@susburrows
Copy link
Contributor

merged to next

@susburrows susburrows merged commit d542345 into master Apr 21, 2016
susburrows added a commit that referenced this pull request Apr 21, 2016
@jgfouca jgfouca deleted the singhbalwinder/add-cosp-ers-test branch August 31, 2016 02:50
agsalin pushed a commit that referenced this pull request Apr 13, 2017
… into master (PR #895)

Test suite:
Test baseline:
Test namelist changes:
Test status: [bit for bit, roundoff, climate changing]

Fixes #851

User interface changes?: no

Code review:

Valgrind is complaining when strncpy or snprintf are used with
non-null-terminated strings.

To eliminate the issue, strncpy and snprintf are replaced with
equivalent character-by-character copy loops in the
instances in which the input string is non-null-terminated.

While this resolves #851 , the clean-up to t_drvstartf/t_drvstops suggested by @bishtgautam should still be implemented.

This is BFB in limited testing using an ACME B case, and should be BFB if not buggy.

* origin/worleyph/timing/non-null-terminated_string_support_fix:
  Update ChangeLog to correct original description of the problem
  Replace strncpy and snprintf where applied to non-null-term. strings
jgfouca pushed a commit that referenced this pull request Feb 27, 2018
rljacob pushed a commit that referenced this pull request May 6, 2021
… into master (PR #895)

Test suite:
Test baseline:
Test namelist changes:
Test status: [bit for bit, roundoff, climate changing]

Fixes #851

User interface changes?: no

Code review:

Valgrind is complaining when strncpy or snprintf are used with
non-null-terminated strings.

To eliminate the issue, strncpy and snprintf are replaced with
equivalent character-by-character copy loops in the
instances in which the input string is non-null-terminated.

While this resolves #851 , the clean-up to t_drvstartf/t_drvstops suggested by @bishtgautam should still be implemented.

This is BFB in limited testing using an ACME B case, and should be BFB if not buggy.

* origin/worleyph/timing/non-null-terminated_string_support_fix:
  Update ChangeLog to correct original description of the problem
  Replace strncpy and snprintf where applied to non-null-term. strings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Atmosphere BFB PR leaves answers BFB
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants