Skip to content

[#1809] Run tests with the compiler from `dev`

Leonid Vasilev requested to merge dk318/#1809-run-tests-with-compiler-from-dev into dev

Motivation and Context

Recently we experienced a really crucial problem: some severe bugs appeared in newer versions of the LIGO compiler. It would be nice to have a job that runs tests with the compiler from dev. It will help us to react to some breaking changes faster.

Related issues

Resolves #1809 (closed) .

✅ Checklist for the LIGO Debugger

  • Tests

    • Bug fixes and new features have corresponding tests added

  • Documentation

    • I checked whether I should update the docs and did so if necessary:

  • launch.json config (if updated)

    • I keep the format of launch.json (in package.json) synced with how the plugin code and the adapter's code work with this configuration.
    • If I changed values in the initial configuration for launch.json, I also searched for them in code and updated accordingly. I keep the default configurations and default values for not listed fields in match.

  • Breaking changes (if applied)

    • If I introduced changes that are not compatible with the older versions of ligo, I updated our version restrictions according to the respective document.

Description

Component

  • compiler
  • website
  • webide
  • vscode-plugin
  • debugger

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance improvement (non-breaking change that improves performance)
  • None (change with no changelog)

Changelog

Checklist:

  • Changes follow the existing coding style (use dune @fmt to check).
  • Tests for the changes have been added (for bug fixes / feature).
  • Documentation has been updated.
  • Changelog description has been added (if appropriate).
  • Start titles under ## Changelog section with #### (if appropriate).
  • There is no image or uploaded file in changelog
  • Examples in changed behaviour have been added to the changelog (for breaking change / feature).

Merge request reports