DRC error count problem

Latest Testing, which will be 6.0.7 seems to have introduced a bug in Violations and Unconnected Items counts

Application: KiCad PCB Editor (64-bit)

Version: (6.0.6-107-gfb2cf7b8be), release build

Libraries:
wxWidgets 3.1.7
libcurl/7.83.1-DEV Schannel zlib/1.2.12

Platform: Windows 10 (build 19044), 64-bit edition, 64 bit, Little endian, wxMSW

Build Info:
Date: Jul 26 2022 05:15:04
wxWidgets: 3.1.7 (wchar_t,wx containers)
Boost: 1.79.0
OCC: 7.6.0
Curl: 7.83.1-DEV
ngspice: 37
Compiler: Visual C++ 1929 without C++ ABI

Build settings:
KICAD_USE_OCC=ON
KICAD_SPICE=ON

IMO this is a showstopper. @Seth_h?

EDIT: it seems to be too late for 6.0.7 because it has been tagged.

I just updated to 6.0.7 on Arch Linux and DO NOT see this behaviour.

Application: KiCad

Version: (6.0.7), release build

Libraries:
wxWidgets 3.2
libcurl/7.84.0 OpenSSL/1.1.1q zlib/1.2.12 brotli/1.0.9 zstd/1.5.2 libidn2/2.3.3 libpsl/0.21.1 (+libidn2/2.3.0) libssh2/1.10.0 nghttp2/1.48.0

Platform: Linux 5.18.14-zen1-1-zen x86_64, 64 bit, Little endian, wxGTK, , tty

Build Info:
Date: Jul 26 2022 07:44:25
wxWidgets: 3.2.0 (wchar_t,wx containers) GTK+ 3.24
Boost: 1.79.0
OCC: 7.5.3
Curl: 7.84.0
ngspice: 37
Compiler: GCC 12.1.0 with C++ ABI 1017

Build settings:
KICAD_USE_OCC=ON
KICAD_USE_EGL=ON
KICAD_SPICE=ON

Quickly identified and fixed

tldr; 6.0.7 does not have this issue and we are proceeding with the announcement soon


This is a mistake in the packaging. The issue appears in some cherry-picked commits that are targeted to 6.0.8. But we were allowing the MS daily builds to do incremental builds and it apparently didn’t pick up the version number change.

OK. Confusingly, the commit message for fb2cf7b8be (which is davidsrsb’s package) is “Begin version 6.0.8 development”, but there’s no tag for 6.0.7 as far as I can see.

:eyes:

Apparently I don’t know enough about git and kicad repo, this is from the 6.0 branch:

The tag is in the 6.0.7 branch :slight_smile:
It is different from previous releases.

Specifically to avoid the issue shown in this thread, we decided to make a 6.0.7 branch from our code freeze point last week and tag there.

Now that the release it tagged, we will delete the branch and it will only be visible when listing tags (not in any branch)

We may choose to use this MO in the future in order to both smooth our development process as well as keep release freezes stable