Hi,
Inline
On 10/27/2011 10:00 PM, chris hegarty wrote:
On 27/10/2011 18:09, Chris Gruszka wrote:
This will be resolved when RE sync's jdk7u/7jdku2 to jdk7u/7jdk7u, and
then the jdk7u/jdk7u-dev team forest is sync'ed from jdk7u/7jdk7u
Yes, I get this. I wasn't having a dig at you ;-)
The purpose of my original mail was two fold:
1) to get the repository Ch122065 up, and buildable again
2) clearly show an issue with the current process.
The plan was to sync the repos when we built the stabilisation area, but
clearly this is something we need to revisit.
Cheers,
Edvard
Having the main integration dev forest in an unbuildable state for
such a long period of time is not really an ideal situation. I
received private mails form other who encountered the same problem.
We just need to flag these type of issues and have the
integrator/project owner aware of them so they can be fixed, both repo
and process.
-Chris.
-ChrisG
On 10/27/2011 9:13 AM, Chris Hegarty wrote:
The latest jdk7u-dev OPENJDK build fails due to CR 7099017.
This CR has been fixed in 7u2-dev but not yet integrated into 7u-dev.
I wonder what is the process around when 7u2-dev merges into the
jdk7u-dev main development forest?
We are also seeing a networking regression test that has been fixed in
7u2 phase2, but still fails in jdk7u-dev. A failing regression test is
not too bad, but the main jdk7u-dev forest should build.
-Chris.
