date:20181212

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4420

2018-12-12 Thread Miguel Angel Ajo

See 



___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Polygon build broken

2018-12-12 Thread Gabriel Staples, ElectricRCAircraftGuy.com

Seth,

Thanks for the reply. I just want to mention I wasn't trying to get anyone
called out publicly. My thinking was simply that if you know who landed the
diff that broke it, privately messaging them would make sense to me because
they'd most likely be the most familiar with that change and that part of
the code base and would be most apt to fixing it without introducing
further errors or taking extra time to get their bearings. In other words,
that person could most likely fix it the fastest and best. That's all.

I hope I didn't come off wrong,

Gabe

On Wed, Dec 12, 2018 at 10:49 AM Seth Hillbrand  wrote:

> Am 2018-12-12 13:30, schrieb Gabriel Staples, ElectricRCAircraftGuy.com:
> > Seth,
> >
> > You're probably already aware, but just in case: `git blame file_path`
> > will tell you the commit hash, person, & date for every line, to see
> > who landed the problem line, and `git bisect`
> > (https://stackoverflow.com/a/37306623/4561887) will help you binary
> > search between a known good commit and a known bad commit to find out
> > which commit introduced the bug.
>
> Thanks, that's good information.  I take this approach because there's
> little upside in publicly calling attention to mistakes/oversights by
> name, especially in a mailing list archived and searchable for an
> indefinite period.  In the same way that we wouldn't publicly call out a
> person for a mistake in a group meeting (unless we're a very
> dysfunctional workplace).
>
> This was just a heads up that the build is broken.  I'm not in a
> position at the moment to fix it myself but perhaps someone else is.
>
> I do always appreciate the useful git tips though!
>
> Best-
> Seth
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Jenkins build is back to normal : kicad-qa #4986

2018-12-12 Thread Miguel Angel Ajo

See 


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Polygon build broken

2018-12-12 Thread jp charras

Le 12/12/2018 à 19:49, Seth Hillbrand a écrit :
> Am 2018-12-12 13:30, schrieb Gabriel Staples, ElectricRCAircraftGuy.com:
>> Seth,
>>
>> You're probably already aware, but just in case: `git blame file_path`
>> will tell you the commit hash, person, & date for every line, to see
>> who landed the problem line, and `git bisect`
>> (https://stackoverflow.com/a/37306623/4561887) will help you binary
>> search between a known good commit and a known bad commit to find out
>> which commit introduced the bug.
> 
> Thanks, that's good information.  I take this approach because there's
> little upside in publicly calling attention to mistakes/oversights by
> name, especially in a mailing list archived and searchable for an
> indefinite period.  In the same way that we wouldn't publicly call out a
> person for a mistake in a group meeting (unless we're a very
> dysfunctional workplace).
> 
> This was just a heads up that the build is broken.  I'm not in a
> position at the moment to fix it myself but perhaps someone else is.
> 
> I do always appreciate the useful git tips though!
> 
> Best-
> Seth

Should be fixed now.
Thanks, Seth.

-- 
Jean-Pierre CHARRAS

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4419

2018-12-12 Thread Miguel Angel Ajo

See 


Changes:

[jean-pierre charras] Remove useless includes

--
[...truncated 41.05 KB...]
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_filtered_list.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_full_list.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_options.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_pin_filtered_list.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_library_list.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_name_filtered_list.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module_ratsnest.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/module.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/modview_icon.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/morgan1.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/morgan2.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_glabel.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_exactly.cpp.o
[ 20%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_pad.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_polygon.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_rectangle.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_sheet.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_target.cpp.o
[ 21%] Building CXX object bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/move_relative.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/mw_add_gap.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/mw_add_line.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/mw_add_shape.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/mw_add_stub_arc.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/mw_add_stub.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/mw_toolbar.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/net_highlight.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/net_highlight_schematic.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/netlist.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/net_locked.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/net_unlocked.cpp.o
[ 21%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_board.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_component.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_cvpcb.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_document.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_footprint.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_library.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_generic.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_page_layout.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_project.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/new_project_with_template.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/noconn.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/normal.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/online_help.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/open_brd_file.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/open_library.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/open_page_layout.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/open_project.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/open_document.cpp.o
[ 22%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/options_3drender.cpp.o
[ 23%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/options_all_tracks_and_vias.cpp.o
[ 23%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/options_all_tracks.cpp.o
[ 23%] Building CXX object 
bitmaps_png/CMakeFiles/bitmaps.dir/cpp_26/options_all_vias.cpp.o
[

[Kicad-developers] Build failed in Jenkins: kicad-qa #4985

2018-12-12 Thread Miguel Angel Ajo

See 

Changes:

[jean-pierre charras] Remove useless includes

--
Started by an SCM change
Building remotely on debian8 (clang gcc linux) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://github.com/KiCad/kicad-source-mirror.git # timeout=10
Fetching upstream changes from https://github.com/KiCad/kicad-source-mirror.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/KiCad/kicad-source-mirror.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 04aeec12231ae8a7dd5225f85b53d9675a5c4574 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 04aeec12231ae8a7dd5225f85b53d9675a5c4574
Commit message: "Remove useless includes"
 > git rev-list --no-walk b4910658b50c186351d12b22fdac6e65d1edef5d # timeout=10
[kicad-qa] $ /bin/sh -xe /tmp/jenkins756742757935968735.sh
+ cmake --version
cmake version 3.0.2

CMake suite maintained and supported by Kitware (kitware.com/cmake).
+ gcc --version
gcc (Debian 4.9.2-10+deb8u1) 4.9.2
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

+ git --version
git version 2.1.4
+ OPTS= -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON 
-DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON
+ OPTS= -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON -DKICAD_SCRIPTING=ON 
-DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON 
-DBUILD_SHARED_LIBS:BOOL=ON
+ [ -d passed-qa ]
+ [ -d build ]
+ cd build
+ /usr/bin/cmake .. -DCMAKE_BUILD_TYPE=Debug -DBUILD_GITHUB_PLUGIN=ON 
-DKICAD_SCRIPTING=ON -DKICAD_SCRIPTING_MODULES=ON -DKICAD_SCRIPTING_WXPYTHON=ON 
-DBUILD_SHARED_LIBS:BOOL=ON
-- KiCad install dir: 
-- Check for installed GLEW -- found
-- Boost version: 1.55.0
-- Check for installed Python Interpreter -- found
-- Python module install path: lib/python2.7/dist-packages
-- Found wxPython 3.0.1.1/gtk2 (wxWidgets 3.0.1.1)
-- Found wxWidgets: 
-L/usr/lib/x86_64-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_stc-3.0
 (found suitable version "3.0.2", minimum required is "3.0.1.1") 
-- Found wxPython.h in 
/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0/wx/wxPython
-- S3DSG version: 2.0.0
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Found wxWidgets: 
-L/usr/lib/x86_64-linux-gnu;-pthread;;;-lwx_gtk2u_gl-3.0;-lwx_gtk2u_aui-3.0;-lwx_gtk2u_adv-3.0;-lwx_gtk2u_html-3.0;-lwx_gtk2u_core-3.0;-lwx_baseu_net-3.0;-lwx_baseu-3.0;-lwx_baseu_xml-3.0;-lwx_gtk2u_stc-3.0
 (found suitable version "3.0.2", minimum required is "3.0.0") 
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   unit_test_framework
-- Configuring done
-- Generating done
-- Build files have been written to: 

+ echo CMAKE exit code is 0
CMAKE exit code is 0
+ rm -f pcbnew/pcbnewPYTHON_wrap.cxx
+ grep -q ^MAKEJOBS=
+ env
+ echo The MAKEJOBS variable is empty
The MAKEJOBS variable is empty
+ JOBS=4
+ make -j4 pcbnew_python_module
[  0%] Built target page_layout_lexer_source_files
[  0%] Generating version string header
[  0%] Built target idf3
-- Using Git to determine build version string.
-- Found Git: /usr/bin/git (found version "2.1.4") 
[  0%] Built target lib_table_lexer_source_files
[  0%] Built target netlist_lexer_source_files
[  2%] Built target gal
[  2%] Built target legacy_wx
[  2%] [  2%] Built target pcb_plot_lexer_source_files
Built target pcb_lexer_source_files
[  4%] Built target kicad_3dsg
[  4%] Built target lib_dxf
Scanning dependencies of target connectivity
[  4%] Building CXX object 
pcbnew/connectivity/CMakeFiles/connectivity.dir/connectivity_algo.cpp.o
[ 46%] Built target bitmaps
[ 46%] Built target specctra_lexer_source_files
Scanning dependencies of target polygon
[ 46%] Building CXX object polygon/CMakeFiles/polygon.dir/PolyLine.cpp.o
-- Writing 
 file with 
version: (6.0.0-rc1-dev-1380-g04aeec1)
[ 46%] Built target version_header
[ 46%] Building CXX object 
polygon/CMakeFiles/polygon.dir/polygon_test_point_inside.cpp.o
[ 46%] Building CXX object 
pcbnew/connectivity/CMakeFiles/connectivity.dir/connectivity_data.cpp.o
Scanning dependencies of target pcbcommon
[

Re: [Kicad-developers] Polygon build broken

2018-12-12 Thread Seth Hillbrand


Am 2018-12-12 13:30, schrieb Gabriel Staples, ElectricRCAircraftGuy.com:

Seth,

You're probably already aware, but just in case: `git blame file_path`
will tell you the commit hash, person, & date for every line, to see
who landed the problem line, and `git bisect`
(https://stackoverflow.com/a/37306623/4561887) will help you binary
search between a known good commit and a known bad commit to find out
which commit introduced the bug.


Thanks, that's good information.  I take this approach because there's 
little upside in publicly calling attention to mistakes/oversights by 
name, especially in a mailing list archived and searchable for an 
indefinite period.  In the same way that we wouldn't publicly call out a 
person for a mistake in a group meeting (unless we're a very 
dysfunctional workplace).


This was just a heads up that the build is broken.  I'm not in a 
position at the moment to fix it myself but perhaps someone else is.


I do always appreciate the useful git tips though!

Best-
Seth

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Polygon build broken

2018-12-12 Thread Gabriel Staples, ElectricRCAircraftGuy.com

Seth,

You're probably already aware, but just in case: `git blame file_path` will
tell you the commit hash, person, & date for every line, to see who landed
the problem line, and `git bisect` (
https://stackoverflow.com/a/37306623/4561887) will help you binary search
between a known good commit and a known bad commit to find out which commit
introduced the bug.

Gabe


Electric RC Aircraft Guy, LLC
www.ElectricRCAircraftGuy.com 

*Check out my Computa Pranksta

USB
device sold on Amazon!*



On Wed, Dec 12, 2018 at 10:23 AM Seth Hillbrand  wrote:

> Hi All-
>
> A recent commit broke the polygon build
>
> Here's the error:
>
> /home/seth/code/kicad/kicad-launchpad/polygon/PolyLine.cpp: In member
> function ‘bool CPolyLine::TestPointInside(int, int)’:
> /home/seth/code/kicad/kicad-launchpad/polygon/PolyLine.cpp:934:37:
> error: cannot convert ‘CPOLYGONS_LIST’ to ‘const wxPoint*’
>   if( TestPointInsidePolygon( m_CornersList, istart, iend, px, py
> ) )
>   ^
> In file included from
> /home/seth/code/kicad/kicad-launchpad/polygon/PolyLine.cpp:46:
> /home/seth/code/kicad/kicad-launchpad/polygon/./polygon_test_point_inside.h:63:45:
>
> note:   initializing argument 1 of ‘bool TestPointInsidePolygon(const
> wxPoint*, int, const wxPoint&)’
>   bool TestPointInsidePolygon( const wxPoint* aPolysList,
>
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Polygon build broken

2018-12-12 Thread Seth Hillbrand


Hi All-

A recent commit broke the polygon build

Here's the error:

/home/seth/code/kicad/kicad-launchpad/polygon/PolyLine.cpp: In member 
function ‘bool CPolyLine::TestPointInside(int, int)’:
/home/seth/code/kicad/kicad-launchpad/polygon/PolyLine.cpp:934:37: 
error: cannot convert ‘CPOLYGONS_LIST’ to ‘const wxPoint*’
 if( TestPointInsidePolygon( m_CornersList, istart, iend, px, py 
) )

 ^
In file included from 
/home/seth/code/kicad/kicad-launchpad/polygon/PolyLine.cpp:46:
/home/seth/code/kicad/kicad-launchpad/polygon/./polygon_test_point_inside.h:63:45: 
note:   initializing argument 1 of ‘bool TestPointInsidePolygon(const 
wxPoint*, int, const wxPoint&)’

 bool TestPointInsidePolygon( const wxPoint* aPolysList,


___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Python scripting build broken on windows.

2018-12-12 Thread Wayne Stambaugh

On 12/12/2018 2:27 AM, jp charras wrote:
> Le 11/12/2018 à 20:38, Maciej Suminski a écrit :
>> Hi Wayne, Seth,
>>
>> On 12/11/18 7:51 PM, Wayne Stambaugh wrote:
>> [...]
>>> FYI, swig does not support unique_ptr or weak_ptr yet[1].  If you change
>>> any code in pcbnew that gets swigged using these pointer templates, the
>>> python scripting will fail to build.  If you want to use unique_ptr, you
>>> will have to create a swig wrapper for it[2].  SWIG does support
>>> shared_ptr so that may be an option.
>>
>> Sorry for the build errors and thanks for the quick reaction. I have
>> seen unique_ptrs all over the KiCad code, so it has never occurred to me
>> that they need a special treatment for SWIG. I will find another
>> scripting-friendly way to fix the memory leaks.
>>
>> Cheers,
>> Orson
> 
> Hi Orson,
> 
> The issue is due to this method:
> std::unique_ptr GetNewConfig( const wxString& aProgName )
> that cannot be mapped by SWIG, because it returns a unique_ptr.
> 
> This method is not really useful for python scripting.
> So the easy way is just to do not map it in pcbnew.py
> 
> The attached basic patch show hos to do that.
> 
> (There are many other examples in Kicad code that use this trick)
> 

I think you can also use "%ignore GetNewConfig;" in the appropriate swig
file.  The documentation for %ignore can be found here
http://swig.org/Doc3.0/SWIG.html#SWIG_rename_ignore.  I would prefer
this method if possible to keep our headers clean from as many
#ifdef/#endif blocks as possible.

___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] KiCad Janitor moves

2018-12-12 Thread Maciej Sumiński

On 12/12/18 12:25 AM, Seth Hillbrand wrote:
> Am 2018-12-11 12:16, schrieb Maciej Sumiński:
>> Recently KiCad Janitor had been rather unreliable, mostly due to my
>> capricious Internet connection, so a few minutes ago he has got a new
>> home at one of CERN servers. It used to work as a webhook, but in order
>> to improve robustness I have switched it to polling (updates every 2
>> minutes). I expect the setup to be rock-solid, so please ping me anytime
>> KiCad Janitor misbehaves.
> 
> Hi Orson-
> 
> Thanks for keeping Janitor happy!  Once it's settled into its new home,
> can we run the 5.0.2 "Fix Committed"->"Fix Released" script to clear out
> the old reports that were tagged 5.0.2?
> 
> Best-
> Seth

Hi Seth,

Of course, thank you for the reminder. I have just run the script, so
the bug reports are already updated.

Cheers,
Orson



signature.asc
Description: OpenPGP digital signature
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4420

Re: [Kicad-developers] Polygon build broken

[Kicad-developers] Jenkins build is back to normal : kicad-qa #4986

Re: [Kicad-developers] Polygon build broken

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4419

[Kicad-developers] Build failed in Jenkins: kicad-qa #4985

Re: [Kicad-developers] Polygon build broken

Re: [Kicad-developers] Polygon build broken

[Kicad-developers] Polygon build broken

Re: [Kicad-developers] Python scripting build broken on windows.

Re: [Kicad-developers] KiCad Janitor moves

11 matches

Site Navigation

Mail list logo

Footer information