Community
Participate
Working Groups
Admittedly, this "came to light" partially because I did not want to "split stream" these files for The mentioned scripts have some checks in them to "test input", such as # verify os, ws and arch values passed in are valid before running tests if [ "$os-$ws-$arch" = "linux-gtk-x86" ] || [ "$os-$ws-$arch" = "macosx-cocoa-ppc" ] || [ "$os-$ws-$arch" = "macosx-cocoa-x86" ] || [ "$os-$ws-$arch" = "aix-gtk-ppc" ] || [ "$os-$ws-$arch" = "aix-gtk-ppc64" ] || [ "$os-$ws-$arch" = "solaris-gtk-sparc" ] || [ "$os-$ws-$arch" = "solaris-gtk-x86" ] || [ "$os-$ws-$arch" = "linux-gtk-ppc64" ] || [ "$os-$ws-$arch" = "linux-gtk-ia64" ] || [ "$os-$ws-$arch" = "linux-gtk-x86_64" ] || [ "$os-$ws-$arch" = "hpux-gtk-ia64_32" ] These don't seem that useful to me, in general, or at least too specific. I think we normally want our "test framework" to run testing anything ... even if certain configurations come and go as being "legal". I plan to remove it all together, for now, but if other think it is real important to detect typos early, or something, then please open a feature requests, and I think it'd be best to make more general, such as, in pseudo code if $os is one of linux, macosx, aix (etc.) and if $ws is one of gtk, cocoa, etc. and if $arch is one of x86, ppc, ia64, ia64_32, etc. That way we would catch typing errors but I see little value in restricting whole framework to exactly one set of configurations. Feel free to disagree and explain what's important about this, if I have missed it.
http://git.eclipse.org/c/platform/eclipse.platform.releng.eclipsebuilder.git/commit/?id=404a65748331ee265d92fbb9dca6b8a9ccd90c91
I see I forgot to finish my first sentence in comment 0. I meant ... I did not want to "split stream" these files for bug 391273.
mass change to 'verified', as these bugs are either routine or obviously fixed build breaks.
