• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

mendersoftware / mender
76%
master: 80%

Build:
Build:
LAST BUILD BRANCH: pr_1810
DEFAULT BRANCH: master
Repo Added 16 Sep 2020 01:19PM UTC
Files 145
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH pr_1705
branch: pr_1705
CHANGE BRANCH
x
Reset
  • pr_1705
  • (HEAD detached at 4c17b4b)
  • (HEAD detached at 74712e5)
  • (HEAD detached at 968d41f)
  • (HEAD detached at c008bca)
  • (HEAD detached at ffef645)
  • 2.5.0-build2
  • 2.6.0-build1
  • 3.0.0-build1
  • 3.1.0-build3
  • 3.1.x
  • 3.2.0
  • 3.2.0-build2
  • 3.2.0-build4
  • 3.2.0-build7
  • 3.5.0-build6
  • 4.0.x
  • 5.0.x
  • HEAD
  • feature-client_auth_api
  • feature-partial_updates
  • feature-unified_comms
  • kacf-test
  • lluis-trigger-sync
  • master
  • pr_1613
  • pr_1618
  • pr_1621
  • pr_1622
  • pr_1623
  • pr_1624
  • pr_1625
  • pr_1626
  • pr_1627
  • pr_1629
  • pr_1630
  • pr_1631
  • pr_1632
  • pr_1633
  • pr_1634
  • pr_1635
  • pr_1636
  • pr_1637
  • pr_1638
  • pr_1639
  • pr_1640
  • pr_1641
  • pr_1642
  • pr_1643
  • pr_1644
  • pr_1645
  • pr_1646
  • pr_1647
  • pr_1648
  • pr_1649
  • pr_1650
  • pr_1651
  • pr_1652
  • pr_1653
  • pr_1654
  • pr_1655
  • pr_1656
  • pr_1657
  • pr_1658
  • pr_1659
  • pr_1660
  • pr_1661
  • pr_1662
  • pr_1663
  • pr_1664
  • pr_1666
  • pr_1667
  • pr_1668
  • pr_1669
  • pr_1670
  • pr_1671
  • pr_1672
  • pr_1673
  • pr_1674
  • pr_1675
  • pr_1676
  • pr_1677
  • pr_1678
  • pr_1679
  • pr_1680
  • pr_1681
  • pr_1682
  • pr_1683
  • pr_1684
  • pr_1685
  • pr_1686
  • pr_1687
  • pr_1688
  • pr_1689
  • pr_1690
  • pr_1691
  • pr_1692
  • pr_1693
  • pr_1694
  • pr_1695
  • pr_1696
  • pr_1697
  • pr_1698
  • pr_1699
  • pr_1700
  • pr_1701
  • pr_1702
  • pr_1704
  • pr_1706
  • pr_1707
  • pr_1709
  • pr_1710
  • pr_1711
  • pr_1712
  • pr_1713
  • pr_1714
  • pr_1715
  • pr_1716
  • pr_1717
  • pr_1718
  • pr_1719
  • pr_1721
  • pr_1722
  • pr_1723
  • pr_1724
  • pr_1725
  • pr_1726
  • pr_1727
  • pr_1728
  • pr_1729
  • pr_1730
  • pr_1731
  • pr_1733
  • pr_1734
  • pr_1735
  • pr_1736
  • pr_1737
  • pr_1738
  • pr_1739
  • pr_1740
  • pr_1742
  • pr_1743
  • pr_1744
  • pr_1745
  • pr_1746
  • pr_1747
  • pr_1748
  • pr_1749
  • pr_1751
  • pr_1752
  • pr_1753
  • pr_1754
  • pr_1755
  • pr_1756
  • pr_1757
  • pr_1759
  • pr_1760
  • pr_1761
  • pr_1762
  • pr_1763
  • pr_1764
  • pr_1765
  • pr_1766
  • pr_1767
  • pr_1769
  • pr_1770
  • pr_1771
  • pr_1772
  • pr_1773
  • pr_1774
  • pr_1775
  • pr_1776
  • pr_1777
  • pr_1778
  • pr_1779
  • pr_1780
  • pr_1781
  • pr_1782
  • pr_1785
  • pr_1786
  • pr_1787
  • pr_1790
  • pr_1792
  • pr_1793
  • pr_1795
  • pr_1796
  • pr_1798
  • pr_1799
  • pr_1801
  • pr_1802
  • pr_1803
  • pr_1805
  • pr_1806
  • pr_1807
  • pr_1808
  • pr_1809
  • pr_1810
  • pr_1811
  • pr_1812
  • pr_1813
  • pr_1814
  • pr_1815
  • pr_1816
  • pr_1817
  • pr_1820
  • pr_1821
  • pr_1822
  • pr_1823
  • pr_1824
  • pr_1825
  • pr_1826
  • pr_1827
  • pr_1828
  • pr_1829
  • v0.0.3

10 Dec 2024 02:22PM UTC coverage: 76.236%. First build
1582266657

push

gitlab-ci

lluiscampos
fix: Fix regression updating from Client v4 to Client v5 or newer

It is not related to the major bump of the Client, but it was reported
in Mender Hub with this suspicion so let's keep the Git commit aligned.

While working on internal improvements to support more advance use cases
in standalone mode, we introduced a new version of the standalone store.
See commit 2c1d92212.

In that commit it can be seen the code dealing with the migration (iow
an update triggered from standalone store v1 being committed with
standalone store v2): when missing the state, set the state that will
trigger the state machine into continuing into commit state.

However a later commit aiming to increase robustness of the process
added new states into the standalone state machine, and the migration
from store v1 was not taking into account, provoking a regression where
the client is not able to "continue" an update. See commit 056d9c26f.

(There are more commits in between these to, but the gist of the problem
is captured in these two).

The fix is rather simple, read it by yourself :)

Setting changelog to `None` because the bug has not been released.

Ticket: MEN-7818
Changelog: None

Signed-off-by: Lluis Campos <lluis.campos@northern.tech>

7369 of 9666 relevant lines covered (76.24%)

11188.55 hits per line

Relevant lines Covered
Build:
Build:
9666 RELEVANT LINES 7369 COVERED LINES
11188.55 HITS PER LINE
Source Files on pr_1705
  • Tree
  • List 145
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
1582266657 pr_1705 fix: Fix regression updating from Client v4 to Client v5 or newer It is not related to the major bump of the Client, but it was reported in Mender Hub with this suspicion so let's keep the Git commit aligned. While working on internal improvemen... push 10 Dec 2024 02:31PM UTC lluiscampos gitlab-ci
76.24
See All Builds (2062)
  • Repo on GitHub
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2025 Coveralls, Inc