04-05-2020
Update (from one hour ago):
Updated the new community sites with latest posts, new users, likes, etc. from legacy site.
Ran an early preprocessing script against the legacy DB.
@Scrutinizer is testing a more refined version of preprocessing which will do even more migration magic. When he is ready, we will run his preprocessing script again the legacy DB and see how it looks.
Thanks for your patience.
We have already fixed the two bugs that we found in the initial launch; but are working to refine more custom bbcode issues.
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view.
I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's... (4 Replies)
Discussion started by: arvindcgi
4 Replies
2. HP-UX
All,
We are migrating an application from HP-UX B.11.00 to HP-UX B.11.31 and both of them have the same informix version - 7.25se. However the compilers are different on both servers.
HP-UX B.11.00 - has B3913DB C.03.33 HP aC++ Compiler (S800)
HP-UX B.11.31 - has PHSS_40631 1.0 HP C/aC++... (2 Replies)
Discussion started by: helper
2 Replies
3. Programming
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies
4. What is on Your Mind?
First a bit of history ....
A number of years ago one of our admins built a number of plugin systems for moderation, including (1) a voting system, (2) a "user feelings" system and (3) a confidential posting system. During this time, I was busy on other projects, not very active in the forums,... (1 Reply)
Discussion started by: Neo
1 Replies
5. What is on Your Mind?
OK.
Like we all do, we learn a lot from tests, test migrations, and so forth.
Today, I started from scratch on test migration 2, armed with a lot more knowledge,
The main differences are as follows:
Installed discourse plugin ruby-bbcode-to-md before starting the install
Modified... (30 Replies)
Discussion started by: Neo
30 Replies
6. What is on Your Mind?
Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily:
Insuring ruby-bbcode-to-markdown is enabled.
Removing line breaks from ICODE to markdown in migration script.
Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies
LEARN ABOUT DEBIAN
test::needsdisplay
Test::NeedsDisplay(3pm) User Contributed Perl Documentation Test::NeedsDisplay(3pm)
NAME
Test::NeedsDisplay - Ensure that tests needing a display have one
SYNOPSIS
In your Makefile.PL...
use inc::Module::Install;
# ... or whatever else you use
# Check for a display
use Test::NeedsDisplay;
# ... your Makefile.PL content as normal
And again in each test script that loads Wx
#!/usr/bin/perl
use strict;
use Test::NeedsDisplay;
# Test content as normal...
DESCRIPTION
When testing GUI applications, sometimes applications or modules absolutely insist on a display, even just to load a module without
actually showing any objects.
Regardless, this makes GUI applications pretty much impossible to build and test on headless or automated systems. And it fails to the
point of not even running the Makefile.PL script because a dependency needs a display so it can be loaded to find a version.
In these situations, what is needed is a fake display.
The "Test::NeedsDisplay" module will search around and try to find a way to load some sort of display that can be used for the testing.
Strategies for Finding a Display
At this time, only a single method is used (and a very simple one).
Debian Linux has a script called "xvfb-run" which is a wrapper for the "xvfb", a virtual X server which uses the linux frame buffer.
When loaded without a viable display, the module will re-exec the same script using something like (for example) "xvfb-run test.t".
As such, it should be loaded as early as possible, before anything has a chance to change script parameters. These params will be resent
through to the script again.
METHODS
There are no methods. You simply use the module as early as possible, probably right after "use strict;" and make sure to load it with only
default params.
Specifically, need must always load it before you set the test plan, otherwise the test script will report two plans, and the harness will
complain about it and die.
# Use it like this ...
use Test::NeedsDisplay;
# ... not like this ...
use Test::NeedsDisplay 'anything';
# ... and not like this.
use Test::NeedsDisplay ();
And that's all there is to do. The module will take care of the rest.
TO DO
- Find alternative ways to launch a display on different platforms
SUPPORT
Bugs should be reported via the CPAN bug tracker at
<http://rt.cpan.org/NoAuth/ReportBug.html?Queue=Test-NeedsDisplay>
For other issues, contact the author.
AUTHOR
Adam Kennedy <adamk@cpan.org>
COPYRIGHT
Copyright 2005 - 2009 Adam Kennedy.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
The full text of the license can be found in the LICENSE file included with this module.
perl v5.10.0 2009-01-04 Test::NeedsDisplay(3pm)