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.

Sign up for GitHub

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

Jump to bottom

update and re-enable qemu backwards-compatibility test #295

Closed
2 tasks
Lotterleben opened this issue Dec 2, 2020 · 0 comments · Fixed by #403
Closed
2 tasks

update and re-enable qemu backwards-compatibility test #295

Lotterleben opened this issue Dec 2, 2020 · 0 comments · Fixed by #403
Labels
difficulty: easy Pretty easy to solve status: blocked Blocked on another issue, or on upstream libraries type: test Test coverage or infrastructure improvements
Milestone
v0.2.0

Comments

@Lotterleben
Copy link
Contributor

after the 0.2.0 release

  • re-enable backward compatibility test in ci.yml (to see what it looked like check here:

    defmt/.github/workflows/ci.yml

    Line 129 in a6edbd1

    - name: Backward compatibility check against decoder v0.1.0
    )
  • update test to the 0.2.0 decoder

see #282 (comment)
@Lotterleben Lotterleben added this to the v0.3.0 milestone Dec 2, 2020
@jonas-schievink jonas-schievink added difficulty: easy Pretty easy to solve status: blocked Blocked on another issue, or on upstream libraries type: test Test coverage or infrastructure improvements labels Jan 15, 2021
@jonas-schievink jonas-schievink mentioned this issue Feb 22, 2021
Merged
@bors bors bot closed this as completed in 0aa637a Feb 22, 2021
@Urhengulas Urhengulas modified the milestones: v0.3.0, v0.2.0 Aug 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
difficulty: easy Pretty easy to solve status: blocked Blocked on another issue, or on upstream libraries type: test Test coverage or infrastructure improvements
Projects
None yet
Milestone
v0.2.0
Development

Successfully merging a pull request may close this issue.

Add back the backwards-compatiblity check
3 participants
@Lotterleben @jonas-schievink @Urhengulas