[Libre-soc-bugs] [Bug 1126] How to document new bugs/issues

[bugzilla-daemon at libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=1126

--- Comment #34 from Luke Kenneth Casson Leighton <lkcl at lkcl.net> ---
(In reply to Andrey Miroshnikov from comment #32)
> Important point raised during today's meeting with Michiel, having completed
> CI logs of a successful test (when a bug is completed) would greatly aid the
> RfP auditing process.
> 
> I will document this on HDL Workflow:
> - How to access CI system
> - How to initiate a job to run the particular test

it's automatc, everything is run.

> - How to access the logs

jacob's server. there are examples already in the bugtracker.

> - (perhaps how move those logs to an archive on libre-soc.org, so that we
> don't rely on Jacob always having power/internet?)

noOoOoo. the VM allocation is 20 GB and costs significant money.
already explained many times why.

> - Add comment on completed bug linking to CI logs
> 
> 
> I know there are other outstanding tasks on this bug, after this morning
> I'll finally have some time to focus on getting them done.

take your time, the main key thing was to get the action noted here
immediately after the meeting.

(In reply to Andrey Miroshnikov from comment #33)
> (In reply to Andrey Miroshnikov from comment #32)
> > - (perhaps how move those logs to an archive on libre-soc.org, so that we
> > don't rely on Jacob always having power/internet?)
> > - Add comment on completed bug linking to CI logs
> 
> Maybe, attaching the completed log as a file to the bug?


NO, under no circumstances. attachments end up in the *postgres database*
which will end up running the server out of disk space in a matter
of weeks. it *only has 20 GB* for very good reasons, discussed and
explained many times.

however doing a *mirror* onto backed-up secondary storage of those
very same log files, i have no problem with that whatsoever.

the server *has* to stay lean and basic otherwise i cannot back it
up over a mobile internet connection, plus it costs a hell of a lot
of money due to the reliability and service guarantees.

> Also should have instructions in case auditor wishes to confirm the results
> are true by running the CI themselves.

... or the team in lisbon that michiel mentioned, or nlnet themselves.


> Also just remembered, a few brief instructions as to how to run the test for
> the completed bug included as part of the RfP process (need to think this
> one through).

oh yes. that is just "what people write in the report". if the online
CI logs have a line-number hash (like gitweb "...../#L540") then
that will do

-- 
You are receiving this mail because:
You are on the CC list for the bug.