Pepperfish downtime last night
by Rob Kendrick
Hi,
Summary: We had some downtime, and we're working on a fix.
Services are currently up but may be slower than usual.
Expect moments of downtime throughout the day.
Last night, at approximately 0330 GMT, one of Pepperfish's
virtual machines suffered a kernel issue related to handling
of interrupts, causing it to become unresponsive. Sadly
this happened exactly as a database update was occuring,
causing some corrupted configuration files to be generated
and pushed to other servers. The upshot was that DNS
broke on our main server and on our secondaries. This had
a knock-on effect of also preventing mail being delivered
to us.
A second issue relating to very poor IO performance on one
of our virtual machine hosts has compounded the problem and
slowed a correct fix.
Given the extremely high uptime of the host (Over 1,200 days),
and the lack of anything it any of its logs that might
suggest why IO performance has become disappointing, we plan
on rebooting it (and thus all the virtual machines it hosts)
at some point today. This will mean the following services
will be down:
- ssh access to 'platypus'
- Web server
- IMAP server
- Mailing list delivery server
- One incoming mail server
- One DNS server
Secondary servers hosted elsewhere should receive and store
any email that is delivered while this happens; nothing
should be lost.
Apologies for the disruption.
B.
6 years, 6 months
- 1
- 0
Test Coverage
by Vincent Sanders
I have been attempting to improve the level of test coverage [1]
within NetsSurf recently. This work is mainly geared towards having
sufficient tests to implement cookie handling with some confidence of
correctness.
The current [2] cookie standards are very different to what we have
now and need this refactor to allow their use in the modern web with
javascript etc.
The test coverage is now minimally adequate at 88% of lines and 64% of
conditionals for code that is tested. However the amount of the
codebase tested outside of the utilities and url database is
effectively zero.
It would be a great area for a new contributor (or old ;-) to start
with the codebase and add some tests while improving their familiarity
with the NetsSurf codebase.
Tests are implemented as a series of simple programs using the c check
library. The existing tests should provide enough of a template but
feel free to ask questions here.
[1] http://ci.NetsSurf-browser.org/jenkins/view/Categorized/job/coverage-nets...
[2] https://tools.ietf.org/html/rfc6265
--
Regards Vincent
6 years, 6 months
- 2
- 1
Fw: Atari builds
by Ole Loots
Hello,
did somebody recognize the E-Mail below? It was in reply to the wrong
subject.
Greets,
Ole
Beginn der weitergeleiteten Nachricht:
Datum: Tue, 28 Feb 2017 14:13:39 +1000
Von: Miro Kropáček <miro.kropacek(a)gmail.com>
An: netsurf-dev(a)netsurf-browser.org
Betreff: Atari builds
Hi guys,
although I don't use Netsurf and have no time to dig in, just out of
curiosity, what do you mean by this:
On 06/02/2017 12:25, Vincent Sanders wrote:
>* atari - The atari frontend is built for m68k and coldfire variants
*>* using a variant of the netsurf cross compliation
*>* toolchain/sdk. No serious updates have been made to this
*>* toolchain in some time and it has become a burden.
*>>* Unless this is addressed before the next developer weekend
the *>* frontend will be disabled in the CI and subsequently
code *>* removed.*
There's nothing wrong with our gcc, it's still 4.6.4 and every other
Atari software developer uses it. It's old, yes, but there are some
technical obstacles to move beyond that version (although this may be
no longer the case, see http://d-bug.mooo.com/beyondbrown/post/gcc-6/).
So what exactly burdens you? Is your new code failing to compile on
4.6.4?
Regards,
Miro
6 years, 6 months
- 1
- 0
- ← Newer
- 1
- Older →