Well, not easier for me, I'm afraid. It will delay adding my board
even longer (which is already several months in progress).
And it's just a hobby for me. Otherwise it begins to look like
work :-)
Nevertheless, I'll see what I can do.
On 30-05-2020 22:14, Alexandre Abadie wrote:
> Hi,
>
> You ca
Hi,
You can just put all of them in the same issue. It will be easier to track.
That is what is done in [1].
Alex
[1] https://github.com/RIOT-OS/RIOT/issues/12651
- Le 30 Mai 20, à 21:42, Kees Bakker k...@ijzerbout.nl a écrit :
> OK, first one created. I'm afraid there are many more to co
The reason I ask all these questions is that I'm adding support for
another SODAQ board. And I was trying to do it the right way and
run some tests. Maybe that was a mistake :-)
Anyway, I've created the first issue.
On 30-05-2020 21:30, Marian Buschsieweke wrote:
> Hi,
>
> every failing test indi
OK, first one created. I'm afraid there are many more to come.
On 30-05-2020 21:27, Alexandre Abadie wrote:
> Hi Kees,
>
> To my knowledge, there is no wiki page for this kind of thing.
> The simplest is probably to open an issue and list there the failures with
> their output. This way we can ea
Hi,
every failing test indicates a bug. (From time to time the bug is found in the
test rather than in the code to test.) Feel free to open an issue for the
failing tests. I personally favor a tracking issue that lists each failing test
with a checkbox. It is motivating to tick them of one by one;
Hi Kees,
To my knowledge, there is no wiki page for this kind of thing.
The simplest is probably to open an issue and list there the failures with
their output. This way we can easily track the on going work to fix them.
See [1] as an example.
Alex
[1] https://github.com/RIOT-OS/RIOT/issues/12