I get that it is technically fixable, but if we can't seem to accomplish it
as a group I categorize that as not fixable. I think this feature requires
more shepherding. "Hey Phil, your test is broken. Do you need pointers for
fixing it?" Think of Zwoop when clang-format is busted or a new Coverity
I'll repeat again, lint is fixable-- people just need to fix their test
code to pass those tests. I'm thinking we should just remove the broader
list, and just email the people that break the tests going forward. This
way we can still (hopefully) clean them up without spamming everyone to
death.
On Mon, Sep 21, 2015 at 9:04 AM Thomas Jackson
wrote:
> Tsqa-lint is intended to pass, but if no one ever looks at the mails then
> they never get better.
> On Sep 18, 2015 6:34 PM, "Leif Hedstrom" wrote:
>
> >
> > > On Sep 18, 2015, at 3:32 PM, Thomas Jackson
> > wrote:
> > >
> > > *TL;DR: if
Tsqa-lint is intended to pass, but if no one ever looks at the mails then
they never get better.
On Sep 18, 2015 6:34 PM, "Leif Hedstrom" wrote:
>
> > On Sep 18, 2015, at 3:32 PM, Thomas Jackson
> wrote:
> >
> > *TL;DR: if you make a commit, and the tests fail-- there is a high
> > probability t
> On Sep 18, 2015, at 3:32 PM, Thomas Jackson wrote:
>
> *TL;DR: if you make a commit, and the tests fail-- there is a high
> probability that your code change broke something. Please take the time to
> figure out if the bug was you or not, and if it isn't let someone know--
> the community can
>>
>
> Turns out there is a bug in the git plugin to jenkins that the error
> message is bad... (
> https://cloudbees.zendesk.com/hc/en-us/articles/205023034-Error-cloning-remote-repo-origin).
> After checking the repo out by logging into the box it seems that someone
> was on box modifying jenk
*TL;DR: if you make a commit, and the tests fail-- there is a high
probability that your code change broke something. Please take the time to
figure out if the bug was you or not, and if it isn't let someone know--
the community can help. TSQA is back on, but tsqa-lint is off for now.*
I can under
+1
On Fri, Sep 11, 2015 at 8:50 AM Leif Hedstrom wrote:
> Hi,
>
> To restore sanity in the email traffic from Jenkins, I have disabled both
> the tsqa and tsqa-lint jobs. Once they are shown to function without errors
> / warnings again, we can enable them.
>
> — Leif
>
>
