-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build broken and not reporting failure #464
Comments
@PAX523 it looks like when this was committed we didn't get a full update, the test is still referencing local changes rather than the updated |
Apparently |
@dblock is there a general issue with travis not reporting platform test failures? |
My apologies. Copy-paste stupidity. Is this fixed or do you need anything from me now? I actually have another method to add to this structure that I'll submit separately (and doublecheck the tests!) |
The build is fixed, and the OS X tests pass, so we only need you to double check your tests are still doing what they were originally intended to.
|
Hallo Timothy. |
PAX, No, the errors were mine. You can ignore this thread. Dan On 7/6/15 11:54 AM, PAX523 wrote:
|
Sorry, my mistake. You did have some WindowUtils changes that were windows-specific which I moved to win32-only tests. While conceivably some of the functions might be possible to implement cross-platform, some of them are definitely windows only. DesktopWindow is definitely windows-only, as are the methods getWindowIcon, getWindowTitle, getIconSize, getAllWindows, getWindowLocationAndSize, and getProcessFilePath. These need to be refactored if they’re to be cross-platform; if not they belong in the win32 subdirectory.
|
@twall I think JNA build is not properly reporting a non-zero error code when tests fail, that's a real bug in the build scripts somewhere |
I think that’s a setting within the test target; the platform build.xml is probably not propagating test failures to the parent process like the top level build.xml does. I’ll take a look.
|
Motivation: In order to support `native-image`, the project has to provide the corresponding configuration for reflection, JNI and resources. Modifications: - Module `codec-native-quic`: Add profile `native-image-agent` for generating `native-image` configuration - New module `testsuite-native-image`: Add profiles `native-image-quic-server`/`native-image-quic-client` for testing the `native-image` configuration Result: Fixes java-native-access#464
On OSX: https://travis-ci.org/twall/jna/jobs/69478093#L636
The text was updated successfully, but these errors were encountered: