Skip to contentSkip to conversation

Unit tests broken on master (#320)

SPDK Luse 1 participant 1 message May 31, 2018 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): spdk/spdk/issues/320/[email protected]

Luse

#1 lore raw

Hi John,

We’re using Trello to track backlog items, work to do, or as a collaboration tool for more involved activities. Github is for reporting suspected bugs and this split does seem to be working pretty good based on the number of folks that have found things to do on Trello – there’s always room for improvement though so open to suggestions from anyone at any time.

On GitHub issues, Anna just started an open bi-weekly issue scrub to try and make sure those have visibility and if you look at Trello it’s recently been re-organized to try and make it more efficient to find things as well.

Thx
Paul

From: John Meneghini [mailto:notifications(a)github.com]
Sent: Wednesday, May 30, 2018 7:27 PM
To: spdk/spdk <spdk(a)noreply.github.com>
Cc: Subscribed <subscribed(a)noreply.github.com>
Subject: Re: [spdk/spdk] Unit tests broken on master (#320)

Thanks for jumping on this Daniel.

Do we want a github issue opened to track this Trello item as well?

I seems to me that Trello doesn’t work well for tracking backlog issues.

/John

From: Daniel Verkamp <notifications(a)github.com>
Reply-To: spdk/spdk <reply(a)reply.github.com>
Date: Wednesday, May 30, 2018 at 7:46 PM
To: spdk/spdk <spdk(a)noreply.github.com>
Cc: John Meneghini <John.Meneghini(a)netapp.com>, Author <author(a)noreply.github.com>
Subject: Re: [spdk/spdk] Unit tests broken on master (#320)

The fix above has been merged as commit 9e9cd51<https://github.com/spdk/spdk/commit/9e9cd51f55ad6319f1ce0067f23d3aac2ba8c932> - please let us know if this does not resolve the issue for you.

I also opened a Trello item to remedy the lack of a Valgrind unit test machine in the build pool: https://trello.com/c/KIsnG1GP/87-add-valgrind-unit-test-machine

Thanks for the report.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<https://github.com/spdk/spdk/issues/320#issuecomment-393354575>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AMVL3Vikza-5SQlLrvFU0YnbQYsu8Pvrks5t3y9AgaJpZM4UT9pb>.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<https://github.com/spdk/spdk/issues/320#issuecomment-393381399>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEb1eNu42y9wlOeu6jH4NSj5VDeX3SU8ks5t31T7gaJpZM4UT9pb>.